Payment Gateway Platform Software for Operators across the UAE

Who this is for: merchants building proprietary checkout experiences, smaller PSPs and tier-2 acquirers, fintechs launching gateway propositions, and specialty gateways for verticals like healthcare, education, government, or real estate. Not positioned for Checkout.com or N-Genius scale replacement - those are mature platforms with deep merchant relationships and scheme authority.

Six connected capability areas: (1) Multi-rail checkout with routing intelligence across card schemes, Jaywan, Aani, and wallets. (2) PCI DSS 4.0 lifecycle with cardholder data minimisation and token vault management. (3) 3-D Secure 2.x authentication orchestration with frictionless flow optimisation. (4) Bilingual Arabic checkout as first-class design. (5) CBUAE licensing alignment across Categories I-IV, SVF, Card Scheme Operator, and Open Finance. (6) Merchant operations dashboards for success rate, routing effectiveness, and compliance position.

Around those six, most operators also want: recurring and subscription billing management, refund and dispute workflow with Sanadak referral, and integration with merchant-side POS and e-commerce platforms.

Checkout.com operates UAE as a PSP licensee with strong global PCI DSS, 3-D Secure, and card-scheme capabilities. Network International's N-Genius is a widely-deployed acquirer product. Magnati, Foloosi, PayBy, MyFatoorah, Amazon Payment Services, Telr, and others provide comparable gateway infrastructure.

Custom payment gateway software is designed to sit alongside these platforms, closing UAE-specific gaps - Aani and Jaywan first-class integration rather than side features, bilingual Arabic checkout as design baseline, CBUAE licensing evidence capture per Decree-Law 6/2025, and Article 62 emerging-technology perimeter awareness. The PSP retains its scheme authority; the custom layer handles UAE-specific design and compliance.

At checkout, the platform presents rails the customer is eligible for - card options, Jaywan (for co-badged card flows), Aani (for account-linked request-to-pay), and wallet options (Apple Pay, Google Pay, Samsung Wallet, Careem Pay, PayBy). Customer preference is remembered across sessions.

For card flows, routing intelligence balances fee (interchange, scheme fees, acquirer margin), success rate (by BIN, by merchant category, by amount), and customer preference. Jaywan routes domestically where applicable. Aani routes via request-to-pay for consent-driven transfers. Fallback logic handles rail failures gracefully.

PCI DSS 4.0 transition was complete end-March 2025 with enhanced cardholder data handling requirements. The platform enforces data minimisation - cardholder data tokenised at capture and replaced with network tokens where issuer supports it. Token vault management aligns to scheme standards.

3-D Secure 2.2 is current with 2.3 emerging. Authentication orchestration balances customer friction with fraud reduction - frictionless flow for low-risk transactions, challenge flow where risk scoring warrants. Scheme-level mandate compliance is maintained as schemes evolve requirements.

UAE checkout flows must support Arabic-first and English-first customers equivalently. Right-to-left layout flips navigation, form fields, and iconography - but not just text. Arabic validation messaging, Arabic receipts, and culturally-aware copy are design-level commitments.

Customer language preference is preserved across session, channel (web, mobile, in-store terminal), and recurring payment flows. Checkout completion parity between Arabic-first and English-first is measured and managed as a product KPI.

Retail Payment Services Categories I-IV cover different payment initiation and account information services. Stored Value Facilities licence covers wallet and prepaid products. Card Scheme Operator licence applies to scheme-equivalent operations. Open Finance licence covers data and payment initiation TPP roles.

The platform captures licensing evidence per product - licence scope, condition monitoring, reporting obligations. Article 62 emerging-technology perimeter is mapped. Decree-Law 6/2025 transition readiness against 16 September 2026 deadline tracked as operational metric. The platform is designed to align with CBUAE requirements; licensing application and maintenance remain the operator's responsibility.

Here's where custom payment gateway platform typically sits in a wider stack.

Gateway and acquirer platforms - we sit alongside Checkout.com UAE, Network International N-Genius, Magnati, Foloosi, PayBy, MyFatoorah, Amazon Payment Services, and Telr for core scheme authority and processing.

Payment processing infrastructure - we integrate with ACI Worldwide, FIS, Fiserv, FSS Technologies, Nymcard, and Codebase Technologies for issuer-side and switch infrastructure.

Identity, fraud, and wallet - we connect with UAE PASS, Sumsub, Onfido, Jumio for identity; NICE Actimize, Quantexa, ComplyAdvantage for fraud; Apple Pay, Google Pay, Samsung Wallet, Careem Pay, PayBy for wallet tokenisation.

Integration approach is scoped during discovery. We don't ask you to rip and replace anything that works.

Discovery runs four to six weeks. Working with your payments, product, engineering, and compliance teams, we map current rail acceptance, PCI DSS and 3-D Secure posture, Arabic checkout design, and CBUAE licensing position. Output is a detailed report covering current-state map, platform architecture, integration scope, phased implementation plan, and fixed-price build proposal.

Build for a core gateway platform runs twelve to sixteen weeks from discovery completion. Full multi-rail rollout, Arabic-first checkout, and CBUAE licensing alignment phases in over nine to fifteen months depending on merchant scope.

Pricing varies by merchant scope, rail count, and licensing categories. A bracket isn't published; discovery produces a fixed-price proposal with no obligation to proceed.