Payments - Introduction / Learning brief
Proxy and alias addressing
Your notes
In simple terms / 01
What this means in plain language
Proxy addressing lets a payer send money using a phone number, email, or identifier instead of a full account number, with a central directory resolving it. This article explains the mechanism, its benefits, and its risks.
A bank account number is precise but hard to remember and easy to mistype. Proxy addressing, also called alias addressing, solves this by letting the account holder register a simpler token, such as a mobile phone number, an email address, or a national identifier, and link it to their account. When a payer wants to send money, they enter the proxy instead of the account number. A central directory looks up the proxy, finds the linked account, and routes the payment. The payer never handles the underlying account details. This makes everyday transfers easier and reduces typing errors, which is why many instant payment systems adopted it. It also introduces risks: a proxy could be registered to the wrong person, or a payer could send to a stranger who happens to hold that alias. Because of this, proxy systems are usually paired with a name check that shows the payer who they are about to pay before they confirm.
Complete lesson / 02
Understand the full idea, step by step
Riya knows Priya's phone number by heart. She does not know Priya's account number — and Priya would rather not read one out across a restaurant table. Increasingly, the phone number is all Riya needs.
A lookup layer on top of the rail
Two separate things just happened, and keeping them separate is the whole lesson. First, a lookup: a shared directory translated the phone number into a real account at a real bank. Second, a payment: an ordinary credit transfer travelled down the same underlying rail it always would — instruction, message, clearing, settlement. The proxy layer changes how a payment is addressed. It changes nothing about how the money moves.
Proxy (alias) addressing
A proxy is a stand-in for an account number: a token such as a mobile number, an email address, a national identifier, or a UPI-style payment ID (UPI — Unified Payments Interface, India's instant payment system). The account holder registers the token, and a central directory records the link between token and account. Every participating bank can register its customers' proxies and query everyone else's — which is why proxy addressing tends to arrive alongside national instant payment systems rather than inside any single bank.
From alias to money
- CUSTOMER
Riya enters Priya's phone number and INR 850.00.
- INSTRUCTION
Bank Alfa queries the shared directory: which account does this proxy resolve to?
- VALIDATION
The directory returns the linked account and its registered name. The app shows the name, so Riya can judge the payee before anything is sent.
- CUSTOMER
Riya confirms. This moment matters most — on an instant rail, settlement is final, so the check happens before the money moves, not after.
- MESSAGE
From here it is an ordinary instant credit transfer: instruction, interbank message, clearing, and settlement on the underlying rail.
- NOTIFICATION
Priya's bank credits her and both sides are told. The directory saw the lookup; it never saw the money.
Did the payment travel through the directory?
No. The directory answered a question and stepped aside. Value moved the way it always does — account entries at the banks, settlement between them. That separation is also a safety property: if the directory were briefly unavailable, no money would be stuck inside it; payments addressed by proxy simply could not be started until it returned.
COMMON CONFUSION
“UPI-style systems replace banks — the app itself holds and moves the money.”
The alias resolves to a real account at a real bank, and the movement is still bank ledgers plus interbank settlement underneath. Proxy addressing replaced the hardest part of the form — the account number — not the rail, the banks, or the settlement behind them.
WHAT IF — A proxy resolves to the wrong person — a mistyped digit, or a recycled phone number whose new holder registered it
What happens: Without a further check, Riya would be paying a stranger — and on an instant rail, a settled payment is final, so recovery depends on the recipient's cooperation and formal processes rather than on any undo button.
How it is handled: This is why the defences sit in front of the confirmation, not behind it: registration controls that verify a person actually holds the token they register, the resolved name displayed to the payer before sending, and clear reporting channels so wrong registrations are corrected and misuse is escalated. The controls exist to catch the error while it is still only a lookup.
STRICTLY SPEAKING
Strictly speaking, real designs differ in what the directory returns, who may register a token, and how names are matched and displayed. In Europe the pairing of an account identifier with a payee-name check is formalised as Verification Of Payee under an EPC scheme rulebook; the United Kingdom's equivalent is Confirmation of Payee. The constant across designs is the pattern itself: resolve the token, show the name, then pay on the ordinary rail.
FOR NOW, REMEMBER
- A proxy is a registered token — phone number, email, payment ID — linked to a real account through a shared directory.
- Addressing and movement are separate layers: the directory resolves the token; the money then travels on the ordinary underlying rail.
- Showing the resolved account name before confirmation is the key control, because instant settlement leaves no easy undo.
- The risks are registration risks — wrong or recycled tokens — met by registration checks, name display, and reporting channels.
TRY IT YOURSELF
The national proxy directory is unavailable for an hour. Which statement about that hour is correct?
One more addressing surprise: sometimes the resolved account turns out to be at the payer's own bank — and then the payment never needs to leave the building at all.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
A proxy or alias links a memorable token, like a phone number, to a real account through a central directory.
- 02
Proxies reduce typing errors and make instant transfers easier for everyday users.
- 03
Because a proxy hides the account, systems pair it with a payee-name check before the payer confirms.
Practical use cases / 04
Where you would use this
A person receives money by sharing only their phone number, keeping their account number private.
A market trader displays an alias so customers can pay quickly without scanning long account details.
A payments operator runs a central directory that resolves aliases to accounts for every participating bank.
Worked example / 05
Put the idea into a real situation
Illustrative example: a fictional payer, Amina Yusuf, wants to send GBP 60.00 to a colleague. She types the colleague's mobile number, +44 7700 900123, as the address. The central directory resolves it to an account at a fictional bank, Meridian Trust, and the app displays the registered name, "J. Okonkwo", before Amina confirms. She recognises the name, approves the GBP 60.00, and the transfer completes in seconds. If the returned name had not matched who she expected, the app would have warned her, and she could have stopped before sending.
Operational sequence / 06
Follow the message and decision path
This compact sequence is a learning model. Exact routing and rulebook behavior can vary by scheme, participant, and implementation.
Read the steps as text
- 01MessageRiya enters Arjun's UPI ID — no account number sharedRiya (payer) → Bank Alfa (Riya's bank / PSP app) · UPI collect / pay request
Riya scans Arjun's QR or types his Virtual Payment Address (VPA / UPI ID), e.g. arjun@bankalfa. She pays a short handle, not a bank account number, so account details stay private.
- 02MessageUPI / NPCI resolves the UPI ID to Arjun's accountBank Alfa (Riya's bank / PSP app) → UPI / NPCI (the switch) · UPI pay request
The NPCI switch looks up the VPA behind the scenes and maps arjun@bankalfa to Arjun's real account at Nordbank, then routes the pay request. The account number is resolved by the network, never revealed to Riya.
- 03PostingRiya authenticates with her UPI PIN and Bank Alfa debits herBank Alfa (Riya's bank / PSP app)
Riya approves the payment by entering her UPI PIN, the RBI-mandated authentication that NPCI implements. Only then does Bank Alfa book the debit against her account.
- DR Riya's account at Bank Alfa — INR 250.00
- 04PostingNordbank credits Arjun within secondsNordbank (Arjun's bank)
The payment routes through NPCI in real time and Nordbank posts the credit to Arjun's account almost immediately. Because UPI is built over the IMPS rails, this works 24/7/365, including nights and holidays.
- CR Arjun's account at Nordbank — INR 250.00
- 05ProcessingArjun can spend the money immediatelyArjun (payee)
From Arjun's side the payment is already complete and the INR 250 is his to use. The customer experience is instant even though the banks have not yet moved central bank money between themselves.
- 06SettlementLater, NPCI settles the net positions at the RBIUPI / NPCI (the switch) → Reserve Bank of India (settlement)
At scheduled cycles NPCI nets every bank's payments against its receipts and settles only the differences in central bank money at the Reserve Bank of India. Customers were paid instantly; the banks square up net afterwards.
Deferred-net settlement: individual payments are cleared continuously but the interbank money moves once per cycle as a single net figure per bank.
- DR Bank Alfa net position at the RBI — INR 250.00
- CR Nordbank net position at the RBI — INR 250.00
Evidence & review / 07
Evidence & review
The generic proxy-directory pattern used by many instant payment systems; UPI, and European and UK name-check schemes, are cited as recognisable shapes, not described at rule level.
What this brief simplifies: A single central directory is assumed; real designs vary in federation, what the lookup returns, registration governance, and name-matching rules. Recovery of a misdirected instant payment is summarised, not proceduralised.
Sources for this brief3
- Market practice
Fast payments - enhancing the speed and availability of retail payments ↗ — CPMI, Bank for International Settlements · Alias/proxy addressing alongside fast payment systems
Predates several major instant payment launches; this site uses it for concepts, not current statistics.
- Scheme-specific ruleversion 1.1 (EPC218-23)
Verification Of Payee scheme rulebook ↗ — European Payments Council · Verification Of Payee name-check pairing
The first rulebook version entered into force on 5 October 2025; version 1.1 was published in March 2026 to address issues found after deployment, and the EPC has announced a version 2.0 for later in 2026.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.