# GCC Instant Payments Compared: Aani, sarie, Fawri+ and Fawran

Instant payment products across the Gulf can look similar in a banking app: enter a mobile number, confirm a name and send money. Underneath, the rules differ in ways that affect checkout design, transaction routing, limits, pricing and customer support.

Aani in the UAE, sarie in Saudi Arabia, Fawri+ in Bahrain and Fawran in Qatar are domestic systems. Each runs around the clock, but their published transaction ceilings, aliases and adjacent services are not uniform. A product team operating across GCC markets should treat "instant payments" as a local capability with a country-specific implementation, not as one regional payment method.

## UAE: Aani combines fast transfers with payment requests

The UAE's [Aani service](https://aep.ae/en/services/aani/) handles domestic transfers of up to AED 50,000. Payments are available 24/7 and are designed to complete in under 10 seconds. Users can send money through a mobile number or email address, while QR codes provide another way to initiate a payment.

Aani also supports request-to-pay and split-payment flows. Those functions extend the service beyond a basic person-to-person transfer. A merchant or platform can consider a flow in which the recipient initiates the request, while consumer products can use split payments for shared bills. [ADCB's Aani page](https://www.adcb.com/en/tools-resources/aani/) confirms support for mobile numbers, email addresses, QR codes, payment requests and bill splitting.

The AED 50,000 figure is an outer boundary published by the scheme operator, not a safe value to hard-code. Banks and channels may impose their own controls. A transfer also needs states for pending, completed, rejected and timed out outcomes. "Under 10 seconds" describes the service, but it does not guarantee that every request will return synchronously.

## Saudi Arabia: sarie has explicit fee and transfer thresholds

Saudi Arabia launched sarie on 21 February 2021. The [Saudi Central Bank rulebook](https://rulebook.sama.gov.sa/en/instant-payments-launch-sarie) caps customer fees at SAR 0.50 for transactions of SAR 500 or less and SAR 1 for transactions above SAR 500.

The transfer rules add more detail. [Gulf International Bank's sarie guidance](https://www.gib.com/en/instant-payment-system-sarie) describes 24/7 instant transfers below SAR 20,000. Users can address recipients through a mobile number, email address, National ID or Iqama rather than relying only on an IBAN. Transfers above the instant limit go through normal local payment methods.

Sarie also has a quick-transfer route of up to SAR 2,500 without beneficiary activation. A transfer below SAR 20,000 is not automatically eligible for the least-friction journey, because the SAR 2,500 threshold governs quick transfers without prior activation.

A Saudi implementation therefore needs at least three amount bands: SAR 500 for the lower fee cap, SAR 2,500 for quick transfers, and below SAR 20,000 for sarie eligibility. Values outside the instant-payment threshold need a clear alternative route rather than a generic failure message.

## Bahrain: Fawri+ is fast, but an official page is stale

Bahrain's [Central Bank payment and settlement overview](https://www.cbb.gov.bh/payment-settlement/) describes Fawri+ as a 24x7x365 service that completes transfers within 30 seconds. That page still lists a BD 1,000 daily cap.

BENEFIT later said the daily limit would rise to BD 3,000 per account from 21 July 2025 under a Central Bank of Bahrain directive. The operator's [current announcement](https://benefit.bh/media-centre/news-and-press-releases/Increase-of-Daily-Transfer-Limit-via-Fawri-Plus-to-BD-3000-per-Account) is independently reflected in [Arab Bank Bahrain's EFTS notice](https://www.arabbank.bh/mainmenu/home/important-announcements/important-announcement/electronic-fund-transfer-system), which tells its customers that Fawri+ supports transfers up to BD 3,000.

The newer limit replaces the older one; the two amounts are not separate allowances. Product teams should still verify how their bank has implemented the change before presenting BD 3,000 as available to every user. Keep the value in configuration, with an owner and update process, instead of embedding it in application code.

Bahrain also has the longest operating history among these four systems. The [World Bank fast-payments profile](https://fastpayments.worldbank.org/node/479) says the Bahrain Electronic Fund Transfer System was implemented in 2015. BENEFIT owns and operates it, while the CBB is the overseer. Scheme operations and regulatory oversight are related, but they are not the same support function during an integration or incident.

## Qatar: Fawran exposes bank-level variation

The Qatar Central Bank launched Fawran on 7 March 2024, according to the [Qatar News Agency launch report](https://qna.org.qa/en/news/news-details?id=0036-qcb-launches-%27fawran%27-instant-payment-service&date=7/03/2024). The domestic service runs 24/7, supports transfers through mobile numbers or aliases and verifies the beneficiary's name before payment. Its scheme maximum is QR 50,000 per transaction, although banks may set lower limits according to a customer's profile and risk controls.

That qualification affects real products. [Doha Bank](https://www.dohabank.com.qa/personal/other-services/fawran/) advertises a QR 50,000 daily limit and QR 500,000 monthly limit for its Fawran customers. [QNB's Fawran information](https://www.qnb.com/sites/qnb/qnbqatar/page/en/enfawran.html) publishes bank-specific pricing and lower channel limits. The national scheme ceiling does not predict the amount a customer can send through a particular bank channel.

Beneficiary-name verification should shape the interface as well. The returned name can reduce misdirected payments, but teams need defined behaviour for mismatches, unavailable responses and user cancellation. The alias should not become the authoritative display name in local records.

![Portrait comparison of Aani, sarie, Fawri+ and Fawran showing published amount limits, timing, identifiers and the separate AFAQ cross-border rail](https://cdn.hashnode.com/uploads/covers/60ecf4a0fc37a15ec15655e8/25f06095-b738-402b-998d-f53441658a24.png)

*Visual: SultanByte. Sources and periods: AEP current service page; SAMA rulebook, 17 February 2021; CBB and BENEFIT update effective 21 July 2025; QCB/QNA launch, 7 March 2024; Gulf Payments.*

## AFAQ is the cross-border layer, not the domestic rails

None of the four domestic services should be described as a GCC-wide or cross-border rail. Gulf Payments says [AFAQ launched on 10 December 2020](https://www.gulf-payments.com/en/our-services/) and processes GCC cross-border transactions in local currencies in real time. It supports the UAE dirham, Bahraini dinar, Saudi riyal, Omani rial, Qatari riyal and Kuwaiti dinar.

A product connected to Aani does not gain sarie, Fawri+ or Fawran reach by implication. Domestic initiation, beneficiary rules and limits must remain distinct from any AFAQ-enabled cross-border capability. Teams mapping financial APIs across the UAE and Saudi Arabia can apply the same approach described in SultanByte's analysis of [open-banking API architecture](https://www.sultanbyte.com/uae-saudi-open-banking-api-architecture): local rules belong in market-specific adapters, while shared orchestration sits above them.

## Build a capability registry, not scattered conditionals

Store the country, currency, scheme ceiling, bank or channel limit, supported aliases, fee rule, beneficiary requirements and fallback rail as versioned configuration. Bahrain's revised cap and Qatar's bank-specific limits show why this data needs an owner and an update process.

Keep routing separate from the checkout interface. The front end can present an instant-payment option, but the routing service should decide whether the amount, customer, bank and destination qualify. It should return a precise alternative when they do not. Saudi transfers above the sarie threshold, for example, belong on a normal local method rather than in a retry loop.

Design for uncertain outcomes. Aani targets completion in under 10 seconds and Fawri+ within 30 seconds, yet an application can lose connectivity before it receives confirmation. Idempotency, transaction-status lookup, reconciliation and safe retries are necessary even on a fast rail. Support tools should show the selected scheme, bank reference, alias type, timestamps and final status without exposing more identity data than the agent needs.

Test each bank implementation, not only the scheme description. Limits, fees and channels can differ below the national maximum. Contract tests and monitored production checks should catch those differences before customers encounter a misleading limit or an unexplained rejection.

The four systems all support always-available domestic payments, but they are not interchangeable. The safe architecture is a shared orchestration layer over explicit country and bank adapters. Keep AFAQ separate until a provider can confirm the cross-border route, currencies, settlement and customer eligibility for the exact product being built.

*Cover visual: original artwork by SultanByte.*