The GCC Cross-Border Payments Context
The GCC's cross-border payment flows are among the largest in the world by GDP share. The region's dollarised economies: all six GCC currencies are pegged to the USD , simplify some aspects of FX management for intra-GCC flows but create specific dependencies on the USD correspondent banking system. A payment from Doha to Dubai is technically a foreign currency payment that transits the USD clearing system through a US correspondent bank, typically via New York. The systemic concentration of cross-border GCC flows through USD correspondents creates both operational dependency and sanctions compliance obligations that affect every bank and payment institution in the region.
For corporate treasurers, the practical challenges of cross-border payments from GCC markets include: SWIFT payment delays and opacity of the correspondent chain, FX conversion costs embedded in bank transfer fees, sanctions screening at each correspondent hop creating unpredictable delivery timelines, and the growing complexity of AML/CFT documentation requirements for larger cross-border transfers.
For payment institutions and fintechs offering cross-border payment services, the challenges are similar but amplified: correspondent banking access is harder to obtain, the regulatory obligations at each end of the corridor must be managed simultaneously, and the unit economics of cross-border payments are under continuous pressure from digital-first competitors offering transparent, low-cost alternatives on major corridors.
Discuss your requirements →SWIFT GPI and ISO 20022 Migration
SWIFT's Global Payments Innovation (GPI) service has become the standard for correspondent-bank cross-border payments. GPI provides end-to-end tracking of payment status, confirmation of credit to the beneficiary account, and transparency of fees deducted at each correspondent hop. For banks and payment institutions making high-value cross-border payments from GCC markets, GPI connectivity is no longer a differentiator: it is a baseline expectation of corporate clients and increasingly a requirement in scheme and regulatory frameworks.
ISO 20022 — Status and Obligations
The SWIFT ISO 20022 coexistence period ended in November 2025. ISO 20022 MX messages are now the required format for cross-border payment instructions on the SWIFT network. Institutions that have not completed their ISO 20022 migration are processing through a translation layer: which preserves operational functionality but strips out the structured data fields (LEI, purpose code, structured address) that make ISO 20022 payments machine-readable and sanctions-screening-efficient.
The practical gap that ISO 20022 migration creates for non-compliant institutions: payments from a fully MX-capable counterparty to an MT-legacy institution lose their structured data at the translation point. The receiving institution's sanctions screening runs against unstructured data, creating higher false-positive rates, slower processing, and operational cost. Regulators in GCC markets are increasingly monitoring ISO 20022 adoption and migration completion as part of supervisory reviews of payment system participation.
- ISO 20022 migration readiness assessment: gap analysis against MX message requirements
- Structured data field completion: LEI, purpose code, and address structure compliance review
- Sanctions screening calibration for ISO 20022 structured data: reducing false-positive rates while maintaining coverage
- GPI connectivity assessment and optimisation: tracking integration, fee transparency reporting, and SLA management
Multi-Currency Settlement Strategy
For payment institutions and fintechs offering multi-currency payment services: accepting payments in one currency, converting, and delivering in another , the settlement architecture determines both the commercial economics and the operational risk of the business. The key decisions are: which currency pairs to support natively (holding balances in each currency) versus converting through a bridge currency; whether to operate a principal model (holding FX risk on the firm's own balance sheet) or an agency model (passing FX conversion to a partner and earning a margin); and how to manage the FX exposure between the time a customer locks a rate and the time the settlement completes.
FX Risk Management for Payment Firms
A payment firm that quotes a conversion rate to a customer at initiation and settles in the destination currency at a later time carries FX risk in the interval. For small-value consumer remittance, the risk on any individual transaction is immaterial but the aggregate portfolio exposure across simultaneous transactions can be significant during periods of currency volatility. For corporate and B2B payment flows: where individual transaction values may be in the hundreds of thousands of dollars , the FX exposure on a single transaction can be commercially significant.
- FX risk exposure quantification: portfolio-level VaR analysis by currency pair and settlement lag
- Hedging strategy design: forward contracts, options, and natural hedging through currency matching
- Treasury counterparty selection: bank FX desks versus specialist FX providers (Corpay, Convera, Moneycorp, Equals) for payment institution FX execution
- Multi-currency account infrastructure: pooling, virtual account structures, and nostro account management
GCC-Specific FX Considerations
All six GCC currencies maintain USD pegs, which eliminates intra-GCC FX risk for pegged pairs but creates specific dependencies. The Saudi riyal peg has been maintained at 3.75 SAR/USD since 1986; the Qatari riyal at 3.64 QAR/USD since 1980; the UAE dirham at 3.67 AED/USD since 1980. These pegs are credible and well-capitalised, but payment firms operating in the region must still manage: USD liquidity requirements in local banking systems, transfer restrictions that apply in specific market conditions, and the FX conversion economics of payments to non-pegged currency destinations (Indian rupee, Pakistani rupee, Philippine peso, Egyptian pound) which are the dominant remittance corridors.
mBridge and future settlement infrastructure: The mBridge multilateral CBDC platform: developed by CBUAE and SAMA alongside the People's Bank of China and Bank of Thailand , is designed to provide an alternative to USD correspondent banking for cross-border settlement in participating corridors. The platform completed a minimum viable product phase in 2024 and is in expanded testing. Its commercial impact on GCC cross-border payment economics is medium-term, but payment institutions and banks with significant GCC-to-Asia corridor exposure should be tracking mBridge's development and considering its implications for correspondent banking strategy.
Treasury Payments for Corporates
Large GCC corporates: particularly those in the energy, construction, and government sectors , make significant cross-border payment flows for procurement, project financing, and payroll. The payment infrastructure serving these flows is often fragmented: multiple banking relationships in multiple countries, inconsistent payment instruction formats, manual reconciliation against ERP systems, and limited visibility of payment status between initiation and credit confirmation.
Treasury payment optimisation for corporates addresses this fragmentation by rationalising the banking panel, standardising payment instruction formats across the banking group, implementing ISO 20022 payment data structures that enable automated reconciliation, and establishing payment factory structures that centralise cross-border payment execution while maintaining local compliance and regulatory reporting obligations.
Payment Factory and In-House Banking
A payment factory structure routes all group cross-border payment instructions through a single centralised entity: typically the group treasury centre , which holds the external banking relationships and executes payments on behalf of operating subsidiaries. The commercial benefits are: improved negotiating position with banking counterparties (consolidated volumes), reduced banking fees, improved FX conversion economics (netting of offsetting positions), and a single point of control for sanctions screening and AML compliance.
- Payment factory feasibility assessment: volume analysis, legal entity structure, and jurisdictional requirements in each GCC market
- In-house bank structure design: intercompany lending framework, notional pooling, and cross-currency netting
- Banking panel rationalisation: RFP design, relationship bank selection, and account structure optimisation
- ERP integration: SAP, Oracle, and Microsoft Dynamics payment module configuration for ISO 20022 output
- Sanctions screening integration: OFAC, UN, EU, and QCB/SAMA/CBUAE sanctions list screening in the payment initiation workflow
Discuss Your FX and Treasury Payment Requirements
MENA Advisory advises banks, payment institutions, and corporate treasuries on cross-border payment infrastructure, FX risk management, ISO 20022 migration, and treasury payment optimisation across GCC and European markets. Speak with a specialist to discuss your specific situation.
Get in Touch