Most banking screens are thin layers over deep plumbing. Designing well means knowing which pipe you are pressing on, what it costs, what it guarantees, and where the bad actors are trying to get in.
The simplest description of a bank is a place that holds, moves, and lends money. The interesting question is how each of those verbs works in practice. Holding looks like a deposit account, but it is shaped by capital rules, deposit insurance, and minimum reserve requirements. Moving looks like a transfer, but the transfer takes a route, a rail, with its own settlement times, costs, finality rules, and limits. Lending looks like a credit line, but it is governed by capital, by suitability, by the credit bureau, and by the customer's salary in the eyes of the bank.
This chapter is about the pipes. The deeper you understand them, the less you guess in design reviews and the more you propose. Two areas matter most for retail design: payment rails and fraud.
Payment rails inside the UAE
"Transfer" is a single button on a screen and it can mean five different things underneath. UAEFTS is the legacy bilateral system used for high-value and timed transfers. IPI, the Immediate Payment Instruction system, was for years the rail behind "instant" claims even when settlement was not strictly real time. Aani is the new instant payments platform launched by the CBUAE through Al Etihad Payments and is fast becoming the default for retail. DirectRemit is ENBD's branded cross-border product offering near-instant remittances to selected corridors, primarily India, Pakistan, the Philippines, Sri Lanka, the United Kingdom, Egypt, and a handful of others. SWIFT covers everything else in the international space and remains the only realistic option for many corridors and currencies.
Payment rails1 / 5
01 / 05
Domestic, large value
UAEFTS
Tap to flip
01 / 05
The UAE Funds Transfer System, the central bank's domestic clearing rail. Carries the high-value and many of the standard interbank flows. Settles within working hours. The "from a bank, to a bank" backbone for non-instant transfers.
02 / 05
Domestic, retail
IPI
Tap to flip
02 / 05
The Immediate Payment Instruction system, historically used for low-value retail transfers presented to customers as "instant". Increasingly succeeded by Aani for the consumer journey, but still common in the rails behind the curtain.
03 / 05
Instant payments
Aani
Tap to flip
03 / 05
The CBUAE instant payment platform run by Al Etihad Payments. Twenty-four-hour settlement, addressing by mobile number or Emirates ID, request-to-pay, and a richer payment data model than its predecessors. The strategic default for retail.
04 / 05
Cross-border, branded
DirectRemit
Tap to flip
04 / 05
ENBD's near-instant remittance product to selected corridors, with India, Pakistan, the Philippines, Sri Lanka, the United Kingdom, and Egypt the most prominent. Free or near-free at the customer level for many corridors, with embedded FX margin.
05 / 05
International
SWIFT
Tap to flip
05 / 05
The global messaging network that underpins international transfers in less specialised corridors and currencies. Slower and pricier, with intermediary banks adding cost and delay. SWIFT GPI brings improved tracking but does not change the underlying economics.
UAEFTS
The central bank's domestic clearing rail for higher-value transfers.
IPI
Immediate Payment Instruction, the older retail-instant rail.
Aani
The CBUAE instant payment platform, the new default for retail.
DirectRemit
ENBD's near-instant cross-border product to selected corridors.
SWIFT
The global messaging network for international transfers.
What "instant" actually means
For a customer, instant means the recipient sees the money. For an engineer, it means a settlement event closing within seconds. For a designer, the gap matters. A confirmation screen that says "Sent" before the rail has confirmed is dishonest. A confirmation that waits for the rail and shows a spinner for fifteen seconds is honest but punishes the user. The right design is usually a layered confirmation: the request is accepted instantly, the rail confirms shortly after, and the screen updates without the customer having to refresh. Aani makes the honest path much easier than it used to be.
Money: deposits, lending, capital
Deposits are not free for the bank. They sit against capital and reserve requirements, and they earn or pay rates depending on the type. Current accounts are stable and inexpensive. Term deposits are predictable but more costly. Savings and call deposits sit between. The mix matters because it determines the bank's funding cost, which determines the rates it can offer on lending. As a designer, you do not need to model that mix, but you should know that a default account selection on a transfer screen, or a nudge to keep money in a savings account, is part of how the bank manages its book.
Lending is where conduct, capital, and customer experience meet most directly. The Al Etihad Credit Bureau holds the credit history of UAE residents, and it is consulted on most lending decisions. Salary transfer requirements, debt burden ratios capped by the CBUAE, and minimum income thresholds are not arbitrary; they are conduct rules that shape the application form. Designing a lending journey without internalising those rules produces a beautiful funnel that fails most applicants in underwriting.
Fraud, the adversarial layer
Every screen designed to help a customer is also a screen that someone, somewhere, is trying to misuse. UAE-specific fraud has its own grammar. The most common patterns are not technically sophisticated; they are social. A scammer impersonates the bank, a courier, a government agency, a delivery service. The customer is talked into reading a one-time password aloud, into installing a remote-access app, into adding a beneficiary, or into approving a transfer they will spend the next week regretting. The defence is a combination of intent friction, education at the right moment, and infrastructure that detects and slows risky transfers without making safe ones unbearable.
Fraud patterns in the UAE1 / 6
01 / 06
Authorisation theft
OTP scams
Tap to flip
01 / 06
The customer receives an OTP and is told by a fake agent to read it out for "verification". The OTP authorises a transfer or a card-not-present transaction. Defence: never display OTPs without contextual transaction details and explicit warnings.
02 / 06
Account takeover
SIM swap
Tap to flip
02 / 06
An attacker convinces a mobile carrier to port the victim's number to a new SIM, then resets banking credentials and intercepts OTPs. Mitigated by device-bound authentication, behavioural analytics, and SIM-change signals shared between bank and carrier.
03 / 06
Impersonation
Social engineering
Tap to flip
03 / 06
A scammer poses as the bank, a courier, the police, or a government department to drive a customer to share credentials, add beneficiaries, or install screen-share apps. Defence is education at the moment, plus warning copy in the right places.
04 / 06
Pseudo-financial
Investment scams
Tap to flip
04 / 06
Crypto, FX, and "exclusive" trading platforms that promise outsized returns. Money leaves through a transfer or a card and rarely returns. Defence: corridor-based screening, friction on first-time large transfers, and unambiguous customer education.
05 / 06
Long-form deception
Romance scams
Tap to flip
05 / 06
An attacker forms a relationship with a victim over weeks or months and asks for transfers in escalating amounts. The hardest pattern to disrupt without intruding. Pattern-based detection, family-aware safeguards, and trained agents on the phone do most of the work.
06 / 06
Voice phishing
Vishing
Tap to flip
06 / 06
A phone call, often from a spoofed number, claiming to be the bank's fraud team or a courier. The customer is moved through a script towards an authorisation. Defence: caller-ID context, in-app callbacks instead of cold calls, and clear rules of engagement that customers can repeat.
OTP scams
Customer is tricked into sharing a one-time password.
A bank's reputation is set on the bad day, not the good one. The good day is invisible. The bad day is the day a transfer goes wrong, a card is declined, a payment is duplicated, a customer is scammed. Most of what we should obsess over as designers is exactly those moments: the dispute flow that lets a customer report a problem at three in the morning, the fraud-block message that tells the customer what happened without making them feel small, the recovery path that returns money quickly when it should be returned. The pipes do not care about feelings. The screens, and the people they reach, do.
Reflections
For one journey, design the confirmation screen for a successful Aani transfer and the equivalent for a SWIFT transfer. What changes and why?
Pick a single fraud pattern and write the in-app warning copy that would have helped a customer in the moment without nagging the rest.
Imagine you are reviewing a "frictionless" first-time transfer. What is the smallest amount of friction you would re-introduce, and where?