Why Does Every Saudi Bank Ask for the Amount Before the Name? — Your money moves instantly. You don't.
In September 2020, I produced a 48-page internal assessment of the IPS payment journey at a Saudi retail bank. I named the flow problem precisely. I rated it Priority 4 — needs immediate attention. I recommended fixing it before launch. The stakeholder decision was to push it to phase two. It is now 2026. No Saudi bank has changed this flow.
What I am claiming here is specific: the system had no mechanism for a correct diagnosis to become a changed decision. And the reason it did not is not accidental. So this is not a story about a bank ignoring advice, or a regulator constraining the experience, or engineers who could not build a better solution. None of those readings would be fair or accurate. It is the direct and predictable consequence of how the digital transformation was architectured across governance bodies, accountability structures, and definitions of success from the beginning.
I am taking the transfer flow because it is the smallest, most legible version of that story, and there are many flows that show the same thing. Let me show you what the smallest one reveals.
The Observable Fact
When you want to send money to someone using most payment systems in the world, the first thing the app asks is: who? You select the person. The amount comes after. This is not a design convention. It is how humans think about money transfers. The mental model is: I want to send money to Ahmed. Not: I have SAR 500 that I would like to route to a person I will specify later.
Every comparable payment system in the world starts with the person. Most Saudi banks, across app and channel, start with the amount. This has been the dominant pattern since sarie launched in 2021.
One exception in sequence, and I tested it myself before publishing. Al Rajhi now places the recipient before the amount, and credit where due, it is the best transfer flow in the market. But the structure is unchanged: before any person appears, the user selects the transfer category, the feature, the recipient's bank, and the proxy type. Four system decisions before a human being. And the third one, choosing the recipient's bank manually, is the very step the proxy directory was built to eliminate. The steps were reordered. The architecture was not. Person-first in sequence, system-first in structure.
Which reveals what the invariant actually is. It was never amount-first. Amount-first is one costume. Bank-and-proxy menus are another. The invariant across every Saudi bank is that the bank's internal architecture is always the user's first task. Count the system-taxonomy questions a user must answer before the person appears: WeChat, zero. Venmo, zero. A UK bank, zero. Most Saudi banks, the amount and the rail before anything. Al Rajhi, four system decisions.
When an entire sector organises the same journey around its own internal taxonomy for five years, and the single deviation arrives unmandated, unmeasured, and unnoticed by any authority, you are not looking at design choices. You are looking at a structural output.
The Technical Reason, And Why It Is Not The Real Reason
The backend needs to know the amount before it can determine which rail to use, which proxy rules apply, and which transfer limits are in scope. This is a real constraint. SAMA's IPS mandate introduced transaction thresholds the system must evaluate before routing.
But this is a backend sequencing requirement, not a frontend one. A person-first flow is technically achievable. The frontend collects who and how much, passes both variables simultaneously to the backend, which routes invisibly. On a mature product team, this is approximately two to four additional weeks of design and API work.
Pay.UK launched Faster Payments in 2008 with similar backend routing logic. UK banks maintained person-first flows throughout. When Confirmation of Payee became mandatory in 2020, UK banks absorbed it as a background check on a payee already selected. The regulatory constraint did not restructure the front-end flow. The architecture was person-first before the mandate arrived, so the mandate was folded into it. Saudi banks did not have that architecture when their mandate arrived. They built around the constraint instead of absorbing it.
There is a sharper version of this point. sarie is the same generation of infrastructure as India's UPI and Brazil's Pix. The proxy directory, mobile number, national ID, email, exists precisely so the user never needs to know which rail, which bank, which beneficiary type. India ran the natural experiment: bank apps exposed the rail taxonomy, NEFT against IMPS against RTGS, while UPI apps hid everything behind a phone number. Both models competed in the same market with the same users. UPI now carries the overwhelming majority of India's digital payments. Brazil went further and deleted the legacy taxonomy outright. Saudi banks took Pix-generation rails and rebuilt the pre-proxy taxonomy on top of them, one beneficiary-type menu at a time. The infrastructure is 2021. The presentation is 1995.
That architectural choice, made under time pressure in 2021, was never revisited. And the reason it was never revisited is not technical. It is structural.
Six Actors, Six Definitions Of Done, One Gap
Saudi Arabia's digital payment experience is produced by six actors: five bodies that govern it and the banks that build it, each with a precise mandate and a precise definition of done. When you map those definitions against the transfer flow problem, something becomes visible that no single actor can see from inside its own jurisdiction.
Every actor is doing exactly what it was designed to do. The gap is not a failure of any of them. It is the shape of the space between them.
Why No Bank Fixed It
The governance gap explains why the problem persists sector-wide. But it does not fully explain why no single bank, acting independently, chose to differentiate by fixing it. Five conditions operated simultaneously.
Simultaneous mandate execution. UK banks received Faster Payments in 2008. Monzo launched in 2015. Starling in 2017. Both built person-first flows as a competitive differentiator against legacy banks. The window in which experience quality becomes commercially meaningful was open for years. Saudi banks integrated sarie in 2021, all simultaneously, all against the same compliance deadline. There was no competitive period in which a person-first flow could attract users away from an amount-first competitor. The window was closed before it opened.
Accountability directed upward, not toward the user. In UK digital banking, a head of digital experience has authority over flow decisions and their performance is measured partly by retention metrics that trace back to user satisfaction. In Saudi banking in 2021, accountability ran upward to SAMA's compliance milestone and to the board's transformation KPIs. Done was defined by what the regulator required, not by whether the journey was coherent.
The framework gap. The only experience instruments that reach banks are SAMA's, and every one of them activates after the fact: complaint root-cause analysis, the SAMACARES system, ISO 10004 satisfaction monitoring, quarterly reports to the board. A bank can hold every certification and file every report while running a flow nobody can navigate, because a confusing journey that people eventually push through produces abandonment and support calls, not formal complaints. Nothing in the stack examines a journey before it ships. And the sharpest version of this condition: SAMA's Open Banking Framework includes mandatory customer experience guidelines alongside its business rules. The capability to mandate experience standards exists inside the regulator and was exercised, for open banking APIs. It was not exercised for the flows people use every day.
Visibility without traction. This is the most precise condition. The diagnosis capability existed inside Saudi institutions. My 2020 assessment proves it. Someone saw the problem, named it correctly, quantified it, recommended the fix, and presented it to the right people. The system had no mechanism for that seeing to become a deciding. The person who made the diagnosis was in the knowing room. The stakeholder who made the phase decision was in the doing room. No room connected both simultaneously with consequences attached. Two pieces of evidence, six years apart, close this point. My 2020 assessment flagged the manual bank-selection step in exactly these words: it defeats the purpose of transferring by proxy. In 2026, that step opens the best transfer flow in the market. And somewhere in those same years, one bank quietly moved the recipient ahead of the amount, unmandated, unrecorded, unnoticed by any authority. The stagnation was invisible to governance. So was the improvement. That is the condition demonstrated twice.
Experience as decoration, not infrastructure. When experience quality is understood as a layer applied after decisions are made, it has no standing in the rooms where infrastructure decisions happen. The IPS flow order was decided by product and technology under regulatory pressure. That is an infrastructure decision. Design was not in that room because experience was not classified as infrastructure. That misclassification is why nobody with budget authority, product authority, or regulatory authority felt accountable for the gap between what was built and what humans actually need. Not because they were indifferent. Because accountability only attaches to what is classified as a requirement. Experience quality was classified as an aspiration. Aspirations have no owner. Requirements do. Five years confirm this is not a designer advocacy failure. The diagnosis was clear, rated, documented, presented. What was missing is that no product owner at any Saudi bank, at any point, looked at their own transfer journey and felt it as their problem. Because the system had already assigned experience quality to the function whose output it treats as decoration.
What The Metrics Miss
It is worth pausing on the cashless economy number, because it is genuinely impressive. Electronic payments at 85% of retail transactions is a real achievement, delivered ahead of schedule. Saudi Arabia is, by this metric, one of the most digitally transacting economies in the world.
WeChat Pay in China processed over one billion daily active users at its peak. Three steps. Person first. The cognitive architecture of the product matched the social architecture of the platform. Payment was embedded in relationship, not in a financial instrument.
The surface has changed. The cognitive experience of being a customer has not. A user who abandons the flow and calls customer support has not been included in the digital economy in any meaningful sense. They have been counted in the transaction volume, but they have not been served.
What Is Actually Missing
Not knowledge. The knowledge exists. I wrote it down in 2020. Not frameworks. DGA has built frameworks that say the right things. Not technical capability. Not intent. Every body named in this article is genuinely attempting to serve the public.
What is missing is consequential feedback: feedback that, when it arrives in the institution, lands with the person who has both the authority and the incentive to change the decision.
Currently, satisfaction scores arrive at a digital transformation team. The person who made the flow decision reports to a product director who reports to a business unit head. The satisfaction score and the flow decision are in different chains of command. There is no structural reason they need to meet.
This is not a Saudi problem exclusively. It appears wherever transformation is defined as infrastructure delivery rather than experience quality. But in Saudi Arabia's context, the conditions that produce it are unusually clean and legible. Simultaneous mandate execution. Accountability flowing upward to compliance metrics. Frameworks that measure output rather than architecture decisions. A diagnosed problem, documented and rated, sitting in a phase two backlog for five years.
The same structure produces the same result across every sector the same transformation logic has reached. Healthcare. Education. Government services. Cultural institutions. The surface modernises. The cognitive experience of being a user does not change.
The person who diagnosed the problem in 2020 did everything right. The institution had no mechanism for converting that seeing into a deciding. The same structure is still in place.
What Would Close The Loop
Not more frameworks. A different type of accountability mechanism, one that runs horizontally between the institution and the user, not vertically between the institution and the regulator.
Consumer financial protection with jurisdiction over journey design, not just transaction failures. A switching mechanism that makes experience quality a commercial variable. A maturity index that measures journey decision quality, not just output satisfaction. A mechanism that requires the satisfaction score and the flow decision to be in the same room at the same time with the same consequences attached.
Saudi Arabia has built remarkable digital infrastructure in a compressed time period. The cashless economy target was hit. The rails are live. The frameworks exist. The diagnosis capability is inside the institutions. What has not yet been built is the corridor between diagnosis and decision.
Until that corridor exists, the transfer will start with the bank's architecture instead of the person. And the diagnosis will sit in phase two.
I have mapped the upstream conditions that would structurally prevent this from reproducing itself across sectors. That work is not for a public article.
If you are in a position to act on it,
Reach out