Instant payments (A2A)المدفوعات الفورية A2A

An instant transfer between accounts is money moving from your account to somebody else's directly, in seconds, with no card and no card network in between. It is called account to account (من حساب إلى حساب), or A2A.

This is not merely an old bank transfer made faster. It is a payment rail that changes when decisions become final and who bears mistakes.

If instant transfers are cheaper and faster, why haven't cards died?

A reasonable question. This kind of payment is called account-to-account (التحويل من حساب إلى حساب), or A2A. A sarie transfer lands in seconds, costs a merchant far less than a card, and passes no four intermediaries. So why does everyone not switch tomorrow?

The answer is one word: reversal.

Pay by card and receive damaged goods, or nothing at all, and you call your bank and raise a dispute. The transaction is reversed, your money comes back, and the burden falls on the merchant to prove delivery. An instant transfer is final. The money left, and there is no button that brings it back.

So what you pay in card fees is not the price of moving money. It is the price of insurance. You are buying the right to deny a transaction and to be believed initially.

That produces a pattern visible in every market. Instant transfers win for bills, rent and paying people you know, where you know the recipient and expect no dispute. Cards win for buying from a merchant you do not know, especially online.

There is a second reason too: a credit card lends to you. An instant transfer takes the money from your balance now, and gives you no thirty free days.

Four networks, one shared idea

Saudi Arabia has sarie, India uses UPI, Brazil uses Pix, and the United Kingdom has Faster Payments. Their operators, limits, and detailed rules are not identical. SAMA owns sarie as a national system. Brazil's central bank operates the core Pix infrastructure. India's National Payments Corporation operates UPI under central-bank oversight, while Pay.UK runs Faster Payments within the British regulatory framework.

What they share is a common domestic rail connecting banks and payment providers under one rule set. Every bank does not need a separate connection and bilateral contract with every other bank. Your bank sends a standard message, the recipient's bank accepts it, and settlement follows the system's rules. A small app can therefore build a useful payment experience on infrastructure serving the whole market.

These rails generally do not charge a percentage of the shopping basket in the way card acceptance commonly does. Their purpose is efficient money movement, not selling a card brand to each merchant. Banks and apps can still apply fixed fees or customer limits. The underlying economics nevertheless make small and frequent payments attractive, which is one reason QR-based account payments became common in India and Brazil.

The alias is part of the product

Customers do not want to type a long account number for every payment. Instant systems therefore link accounts to easier identifiers, such as a phone number, payment address, or Pix key. Sarie can use a mobile number, national ID, Iqama, email address, or a business's unified number. Money does not enter the phone itself. It reaches the bank account linked to that identifier.

This linking service is an alias directory. It must prove that an account holder controls an identifier before registering it. It also needs rules for recycled phone numbers, closed accounts, and conflicting registrations. An alias reduces typing mistakes but creates a new responsibility for keeping the link accurate.

Confirmation of payee adds another practical barrier before sending. A customer enters an identifier and the bank displays the matching account holder's name. This does not prove that the sale is honest or that the merchant will deliver. It can, however, expose a supposed company asking for payment into an unrelated individual's account.

Finality changes the meaning of approval

The point at which a payment becomes settled between institutions is called settlement finality. The sending bank cannot simply pull the entry back because its customer changed their mind. It may request a return from the recipient, banks may cooperate after a mistake or fraud, and an authority may freeze funds that remain in the receiving account. Those are recovery processes, not a native purchase-dispute right equivalent to a card chargeback.

Card schemes give cardholders a chargeback process for defined reasons. A customer can dispute through the issuing bank, after which the network may ask the merchant for evidence. Value can be taken back well after the purchase. An instant bank transfer does not acquire the same buyer protection merely because an app labels the button "pay."

That difference helps a merchant supplying goods immediately. The merchant receives final funds without an equivalent card dispute appearing weeks later. It hurts a customer who pays a fake shop, because receipt of money does not prove delivery of goods. Certainty for the recipient creates greater responsibility before confirmation for the sender.

When the victim authorises the payment

An authorised push payment scam, or APP scam (احتيال الدفع المُصرَّح به), tricks a person into sending the money themselves. The criminal does not necessarily steal a password. They may impersonate a bank employee and claim the account is under attack. They may advertise a cheap phone and pressure the buyer to transfer immediately. They may impersonate a chief executive and send an urgent invoice to an accounts clerk.

In each case, the bank sees its real customer using a familiar device and passing authentication. A fingerprint or one-time code proves who pressed the button. It does not prove that the person understood the criminal's deception.

Fraud controls therefore examine context before execution. They look for a new recipient, an unusual amount, a recently changed device, or an account receiving many payments and rapidly emptying them. The bank can show the recipient's name and a warning specific to the situation. Depending on applicable rules, it can delay a high-risk transaction or refer it for human review.

A generic warning box that everyone dismisses is weak protection. "Beware of fraud" does not explain why this payment looks dangerous. A useful screen can state that the bank will never ask a customer to move money into a "safe account." It can ask whether someone on the phone is instructing the customer.

Controls also belong at the receiving institution. An account that collects victims' money and rapidly forwards it is often called a money mule account. The recipient's bank can detect the pattern, restrict suspicious movement, and investigate. The sending bank cannot solve the problem alone, because every participant benefits when the network closes fraudulent destinations.

A payment experience, not just a transfer

A merchant needs more than a printed account number. It creates a payment request carrying the amount, order reference, and destination, then presents it through a link or QR code. The customer's banking app opens the request, displays the details, collects approval, and returns a status. The merchant should never ship goods merely because a buyer sent a screenshot of a receipt.

The merchant matches the network notification to the order in its own ledger. Two payments of the same amount need separate identifiers. An expired request must not be confused with a new order. A refund is a new payment in the opposite direction with its own reason and record. It does not erase the original transfer.

This work is reconciliation and exception handling. Instant settlement does not remove it. A payment may succeed while the customer's connection fails before displaying the result. A merchant can receive a late or repeated notification. The app must query the authoritative final status instead of inferring failure from a frozen screen.

Sarie in Saudi Arabia

SAMA launched sarie in 2021 for low-value domestic transfers among participating institutions. It operates around the clock, including weekends. It supports IBANs and alternative identifiers, and provides account verification for the intended recipient. SAMA sets participation rules and applicable system limits.

Sarie's existence does not let every app connect directly. A bank or payment provider needs the appropriate regulatory status and technical access. A consumer app may create the interface while a partner bank executes the actual movement. Ask who holds the account, who submits the payment order, and who handles a complaint.

A product team can assess an instant-payment journey at three moments. Before payment, it measures recipient-name accuracy and the quality of fraud interventions. During payment, it measures response time and status clarity. After payment, it measures reconciliation and error handling. "Two seconds" is not a complete success metric if the customer reached the wrong destination in those seconds.

This distinction prepares you for balances stored inside apps. An account-to-account payment moves funds between accounts at financial institutions. A wallet may instead record a balance owed by a non-bank company. The next question is no longer rail speed. It is where customers' money sits and how it is protected.