Regional Wallet Integration: Easypaisa + JazzCash + SADAD + STC Pay Across MENA + South Asia

Designed and shipped the unified wallet-acceptance surface for a regional fintech operating across Pakistan, KSA, Bangladesh, and partial UAE consumer flows. Integrated five wallets, Easypaisa, JazzCash, SADAD, STC Pay, plus Mada-rail acceptance for consumer flows, behind a single internal Wallet API. Built per-merchant routing logic that picks the right rail per cardholder profile, lifted non-card acceptance by 27%, and produced a 94% cross-rail fallback completion rate on transactions that started on card and failed.

The platform's card-first acceptance strategy worked in UAE but lost meaningful conversion in Pakistan and Bangladesh, where consumer share is dominated by mobile-money wallets (Easypaisa + JazzCash + bKash + Nagad), and was suboptimal in KSA where SADAD and Mada-rail are mandated by SAMA + scheme regulation. Each wallet had been integrated piecemeal by different teams; the integrations were bespoke and brittle. Merchant onboarding for wallet-only or wallet-included flows took 3 weeks of bespoke engineering per merchant. The competitive pressure was clear: regional competitors who shipped wallet-first acceptance were winning the consumer-facing checkout conversion. The senior team needed a unified architecture, fast.

• Single internal Wallet API: stable contract, per-wallet adapter beneath, identical merchant-facing experience for any wallet
• Per-wallet adapter library: Easypaisa, JazzCash, STC Pay, SADAD, Mada-rail, each as a separate adapter with consistent capability mapping (init, authenticate, capture, refund, status)
• Per-merchant routing rules: merchant-tier + per-market default + per-amount-band overrides; intelligent fallback when primary rail declines
• Reconciliation per-rail: each wallet has its own settlement file format; built per-wallet reconciliation matching with internal-ledger pairings
• AML/CFT screening integration: every wallet transaction runs through the same sanctions + PEP screening as card traffic; per-wallet KYC re-validation where wallet provides only partial counterparty data
• Dispute pipeline per-wallet: each wallet has its own dispute mechanism (different from scheme card disputes); built case-management ingestion for each
• Merchant onboarding tool: per-merchant wallet enablement, per-merchant fallback policy, A/B testing for routing variants
• Real-time observability: per-wallet uptime, per-wallet auth rate, per-wallet decline reason mix, per-wallet abandonment

• Single internal API fronts all wallets; merchant integration is identical regardless of which wallet executes the transaction
• Per-wallet adapter handles wallet-specific authentication (Easypaisa OTP, JazzCash QR, SADAD merchant code, STC Pay deeplink, Mada PIN-on-glass)
• Routing engine picks the wallet per transaction: per-merchant default first, per-amount-band override, per-cardholder preference, then fallback
• When card route fails (decline / abandonment), the surface offers wallet fallback in the same checkout session, single-session cross-rail recovery
• Reconciliation runs per-wallet daily: wallet settlement file matched against internal ledger with per-wallet break detection
• Sanctions / PEP screening runs uniformly across wallet + card transactions, same screening engine, same audit trail

• Weekly wallet health review: per-wallet uptime, auth rate, decline reasons, abandonment, by merchant tier, by market
• Monthly merchant routing review: routing-rule effectiveness, fallback-completion rate, per-merchant cost-per-transaction trends
• Quarterly wallet-partner alignment: per-wallet roadmap, fee adjustments, joint marketing, regulator-facing posture
• Real-time alerting per-wallet on availability + per-merchant routing anomalies
• Annual scheme + regulator attestation: wallet integration evidence, AML pipeline coverage, dispute-handling audit

Owned the regional wallet integration programme end-to-end as Product & Program lead, unified Wallet API architecture, per-wallet adapter design, routing-engine logic, reconciliation per-rail, AML pipeline unification, merchant-onboarding tooling, and the wallet-partner relationship management. Direct accountability for non-card acceptance lift, merchant onboarding cycle compression, cross-rail fallback rate, and per-transaction cost reduction.

• Lifted non-card acceptance by 27% on cohort merchants, driven primarily by Easypaisa + JazzCash + STC Pay adoption
• Cut merchant onboarding cycle from ~21 days to ~7 days for wallet-only merchants
• Reduced average per-transaction acquiring cost by ~38% on routed wallet traffic vs. international scheme equivalent
• Reached 94% cross-rail fallback completion rate, transactions that failed on card recovered through wallet in the same session
• Removed three single-rail dependencies, each wallet had previously been a single point of failure; the unified API + adapter pattern eliminated that
• Established the per-merchant routing-rule discipline as a repeatable framework, not a per-engagement custom job
• Onboarded two additional wallets (after the initial five) in ~4 weeks each, validating the adapter pattern

• Chose unified API + per-wallet adapter over per-wallet integration, heavier upfront engineering; produced the 4-week new-wallet onboarding cycle and removed bespoke-per-engagement work
• Built single-session cross-rail fallback, added engineering complexity (state management across rails within a checkout session); recovered the engineering investment in the 94% fallback-completion rate
• Standardised reconciliation per-wallet to internal-ledger pairings, additional finance + engineering coordination per wallet; saved months of ops-cleanup when settlement files arrived in unexpected formats
• Insisted on uniform AML/CFT screening across wallet + card, required wallet partners to agree to additional KYC data sharing in some cases; produced the audit posture that closed regulator inquiries on wallet-traffic compliance

• Regional wallets are the consumer experience in MENA + South Asia. Card-first acceptance in Pakistan or Bangladesh loses the largest segment of the market.
• Per-wallet adapter architecture is the right pattern over bespoke per-wallet integration. The investment in the adapter layer pays back at the third wallet, not the first.
• Single-session cross-rail fallback is the conversion-recovery move most platforms miss. Failed-card → next-session-retry loses 30%+ of the recoverable transactions; failed-card → same-session wallet recovers 90%+.
• AML/CFT pipeline must run uniformly across all rails. Per-wallet exceptions ('the wallet has its own KYC') create regulator-facing audit gaps that are hard to close after the fact.
• Wallet-partner relationships are an ongoing operating function, not a one-time integration. The quarterly partner alignment is what keeps the integration current as wallet partners change their own APIs.

Every regional fintech in MENA + South Asia eventually has to ship wallet acceptance. The teams that do it well, unified API, per-wallet adapter, intelligent routing, cross-rail fallback, uniform AML, capture the conversion lift, the cost reduction, the merchant-onboarding speed, and the regulator posture as one bundle. The teams that ship bespoke per-wallet integrations end up with five brittle pipelines, five reconciliation surfaces, five compliance gaps, and per-merchant engineering work that does not scale. This is the playbook for the first.