Instant payments are now the default expectation in the Gulf. A transfer between two banks in Riyadh, Dubai or Kuwait City settles in seconds, at any hour, usually from a phone number or an alias rather than an IBAN. Behind that experience are three national rails that behave differently, and a bank or fintech that integrates with them as if they were one more batch file will find out quickly why that does not work.
This guide explains how sarie, Aani and WAMD work, what the numbers say about adoption, and what connecting to them demands from the core, the channels and the operations team.
sarie: Saudi Arabia’s instant payment system
The Saudi Central Bank launched sarie in February 2021, built with IBM and Mastercard’s Vocalink on ISO 20022 messaging. It handles transfers of up to SAR 20,000 instantly and quick transfers of up to SAR 2,500 using an alias such as a mobile number, email or national ID instead of an IBAN. Adoption has been steep: 593 million transactions worth SAR 2.5 trillion in 2024, with volume up roughly sixty percent year on year. Every bank in the Kingdom is a direct participant, and licensed payment institutions connect through sponsor banks or directly under SAMA’s rules.
sarie also underpins the request-to-pay and payment-initiation use cases that SAMA’s open banking framework added in 2024, so a bank’s sarie integration is increasingly exercised by third parties, not only its own app.
Aani: the UAE’s instant payment platform
Al Etihad Payments, the CBUAE subsidiary, launched Aani in October 2023 as part of the Financial Infrastructure Transformation programme. It supports transfers by mobile number, email or QR code, request-to-pay, split bills and a standalone app alongside integration inside participating bank apps. The central bank reported 12.5 million registered users by April 2026, and by then the platform had been integrated into the apps of all major banks, exchange houses and several wallets, with proxy registration linking phone numbers to accounts.
Aani sits alongside the UAE’s domestic card scheme Jaywan and the Open Finance platform, which means a UAE bank’s payment stack now has three new national integrations within three years.
WAMD and KACH: Kuwait’s instant and clearing rails
Kuwait’s instant transfer service WAMD launched in 2022 on the KNET network, allowing transfers between accounts at any local bank using a mobile number. Growth has been strong, with the Central Bank of Kuwait reporting annual increases above sixty percent in both volume and value. In January 2026 CBK launched the Kuwait Automated Clearing House (KACH), a modern low-value interbank clearing system on ISO 20022 that operates around the clock and supports credit transfers, direct debits and request-to-pay. Together WAMD and KACH replace the batch-era infrastructure most Kuwaiti banks still run their payment operations around.
What the rails demand from your stack
The first demand is real-time posting. An instant payment must debit, credit and confirm in seconds, which means the core, or an integration layer in front of it, must post outside end-of-day windows and handle the rail’s timeout semantics correctly. Banks that still batch internal postings end up with customers who see money leave but not arrive.
The second is idempotency and reconciliation. Instant rails retry; your systems must recognise a repeated message as the same payment, never post it twice, and reconcile against the rail’s records continuously rather than nightly. Request-to-pay adds a state machine of its own.
The third is fraud screening within the latency budget. Authorised push payment fraud is the fastest-growing fraud type on every instant rail in the world. Screening has to happen inside the few hundred milliseconds available, which pushes banks toward behavioural models and pre-computed risk features rather than rule engines alone.
The fourth is alias management. Phone number and email proxies must be registered, verified, moved when the customer changes bank, and protected against account takeover. This is a product in its own right, and a frequent source of customer complaints when done as an afterthought.
ISO 20022 is the common thread
sarie, Aani and KACH all speak ISO 20022, and Gulf banks are completing their SWIFT cross-border migration to the same standard. Rich, structured messages are an opportunity: remittance information, purpose codes and structured addresses improve reconciliation, sanctions screening and analytics. They are also a burden if your core stores a forty-character free-text field and truncates the rest. A canonical payment data model in the integration layer, designed around ISO 20022 from the start, saves rework on every rail that follows.
How Eurisko helps
Eurisko builds the channel and integration layers that sit between a bank’s apps and the national rails, including payment orchestration, alias management, request-to-pay journeys and real-time fraud hooks, for banks in Saudi Arabia, the UAE, Kuwait and Lebanon. If your instant payment integration is live but fragile, or you are connecting to a new rail such as KACH or AlTareq, our fintech team can help.
