Payments Academy
UPI in India PAYMENT OPERATIONS STARTED LIVE 01 UPI in India - built around a simple addressing model ACTIVE 02 FedNow in the United States - built by the Federal Reserve and settles QUEUED 03 Faster Payments in the United Kingdom - one of the oldest instant systems QUEUED 04 SEPA Instant Credit Transfer in Europe - must work across more than thirty QUEUED 05 Comparison - shows that there is no single correct QUEUED UPI in India is built around a simple addressing model that hides account numbers behind a virtual payment address. Step 1 of 5 UPI in India STARTED UPI in India built around a simple addressing model ACTIVE FedNow in the United States built by the Federal Reserve and settles QUEUED Faster Payments in the United Kingdom one of the oldest instant systems QUEUED SEPA Instant Credit Transfer in Europe must work across more than thirty countries QUEUED Comparison shows that there is no single correct QUEUED UPI in India is built around a simple addressing model that hides account numbers behind a virtual payment address.
FedNow in the United States PAYMENT OPERATIONS IN PROGRESS LIVE 01 UPI in India - built around a simple addressing model DONE 02 FedNow in the United States - built by the Federal Reserve and settles ACTIVE 03 Faster Payments in the United Kingdom - one of the oldest instant systems QUEUED 04 SEPA Instant Credit Transfer in Europe - must work across more than thirty QUEUED 05 Comparison - shows that there is no single correct QUEUED FedNow in the United States is built by the Federal Reserve and settles in central bank money around the clock. Step 2 of 5 FedNow in the United States IN PROGRESS UPI in India built around a simple addressing model DONE FedNow in the United States built by the Federal Reserve and settles ACTIVE Faster Payments in the United Kingdom one of the oldest instant systems QUEUED SEPA Instant Credit Transfer in Europe must work across more than thirty countries QUEUED Comparison shows that there is no single correct QUEUED FedNow in the United States is built by the Federal Reserve and settles in central bank money around the clock.
Faster Payments in the United Kingdom PAYMENT OPERATIONS IN PROGRESS LIVE 01 UPI in India - built around a simple addressing model DONE 02 FedNow in the United States - built by the Federal Reserve and settles DONE 03 Faster Payments in the United Kingdom - one of the oldest instant systems ACTIVE 04 SEPA Instant Credit Transfer in Europe - must work across more than thirty QUEUED 05 Comparison - shows that there is no single correct QUEUED Faster Payments in the United Kingdom is one of the oldest instant systems, launched in 2008, and it is built for speed inside a single country. Step 3 of 5 Faster Payments in the United Kingdom IN PROGRESS UPI in India built around a simple addressing model DONE FedNow in the United States built by the Federal Reserve and settles DONE Faster Payments in the United Kingdom one of the oldest instant systems ACTIVE SEPA Instant Credit Transfer in Europe must work across more than thirty countries QUEUED Comparison shows that there is no single correct QUEUED Faster Payments in the United Kingdom is one of the oldest instant systems, launched in 2008, and it is built for speed inside a single country.
SEPA Instant Credit Transfer in Europe PAYMENT OPERATIONS IN PROGRESS LIVE 01 UPI in India - built around a simple addressing model DONE 02 FedNow in the United States - built by the Federal Reserve and settles DONE 03 Faster Payments in the United Kingdom - one of the oldest instant systems DONE 04 SEPA Instant Credit Transfer in Europe - must work across more than thirty ACTIVE 05 Comparison - shows that there is no single correct QUEUED SEPA Instant Credit Transfer in Europe must work across more than thirty countries, which makes it the most complex of the four. Step 4 of 5 SEPA Instant Credit Transfer in Europe IN PROGRESS UPI in India built around a simple addressing model DONE FedNow in the United States built by the Federal Reserve and settles DONE Faster Payments in the United Kingdom one of the oldest instant systems DONE SEPA Instant Credit Transfer in Europe must work across more than thirty countries ACTIVE Comparison shows that there is no single correct QUEUED SEPA Instant Credit Transfer in Europe must work across more than thirty countries, which makes it the most complex of the four.
Comparison: no single correct architecture PAYMENT OPERATIONS COMPLETE LIVE 01 UPI in India - built around a simple addressing model DONE 02 FedNow in the United States - built by the Federal Reserve and settles DONE 03 Faster Payments in the United Kingdom - one of the oldest instant systems DONE 04 SEPA Instant Credit Transfer in Europe - must work across more than thirty DONE 05 Comparison - shows that there is no single correct ACTIVE The comparison shows that there is no single correct architecture, only trade-offs that fit a market. Step 5 of 5 Comparison: no single correct architecture COMPLETE UPI in India built around a simple addressing model DONE FedNow in the United States built by the Federal Reserve and settles DONE Faster Payments in the United Kingdom one of the oldest instant systems DONE SEPA Instant Credit Transfer in Europe must work across more than thirty countries DONE Comparison shows that there is no single correct ACTIVE The comparison shows that there is no single correct architecture, only trade-offs that fit a market.

Key points of this lesson, in order.

0:00 / 3:37 Step 1 of 5

How UPI, FedNow, Faster Payments and SEPA Instant Do It Differently

Real-Time Payments Architecture, Lesson 6 of 7, Narration 3:37, D05 Domestic payment systems

SettlementISO 20022pacs.008

What you will learn

Your objective. By the end of this lesson, you will be able to explain UPI, FEDNOW, faster payments and SEPA instant do it differently. UPI in India is built around a simple addressing model that hides account numbers behind a virtual payment address.

Why it matters. A business analyst designing a new instant service must therefore start from the market, the regulation, and the customer need, and only then choose the technical pattern that fits.

Chapter objective: Learner designs real-time payments architecture, covering 24 by 7 availability, instant clearing, liquidity, and failure handling, and explains how it differs from batch systems. Learner applies this skill in realistic banking scenarios, with clear examples and correct terminology throughout.

Key learning points

  • UPI in India
  • FedNow in the United States
  • Faster Payments in the United Kingdom
  • SEPA Instant Credit Transfer in Europe
  • Comparison: no single correct architecture

Key terms

Settlement: The final movement of funds between banks to discharge obligations created by cleared payments. Settlement is usually made in central bank money or through correspondent accounts.

ISO 20022: An international standard for financial messaging that defines XML message formats for payments, securities and trade.

pacs.008: An ISO 20022 message for a financial institution to financial institution customer credit transfer. It replaces MT103 in cross border payments and carries structured debtor, creditor, charges and...

Banking architecture diagram showing How UPI, FedNow, Faster Payments and SEPA Instant Do It Differently.

Practise this lesson

Exercise

Read the ISO 20022 messages message described in this lesson and identify its key parts.

Use the message structure, fields and example in this lesson.

  1. What to do. List the main blocks of the message, name the field that carries the amount, and name the field that identifies the payment.

Correct result. The message is made of blocks, each carrying a part of the payment instruction. The amount field and the identification field are the two a receiving bank checks first, because without them it cannot process or reconcile the payment.

Why. A message is only useful if you can read it. The blocks tell the receiving bank what to do, and the amount and identification fields are what it checks first.

Check your understanding

Practice question

Which of the following best describes UPI, FEDNOW, faster payments and SEPA instant do it differently?

Takeaway and next step

What to remember

A business analyst designing a new instant service must therefore start from the market, the regulation, and the customer need, and only then choose the technical pattern that fits.

Follow INR 120 through every stage, from instruction to beneficiary credit, and note where it can stop.

Open the Payment Lifecycle Simulator →

Builds on "Instant Settlement, Liquidity and Prefunding".

Transcript and full text

Show transcript

UPI in India is built around a simple addressing model that hides account numbers behind a virtual payment address. A customer pays to a handle such as a name followed by a bank identifier, or scans a QR code at a shop, and the system routes the payment to the correct account. The National Payments Corporation of India operates the central switch, and more than 300 banks participate. A street vendor can receive INR 120 for a cup of tea just as easily as a business can receive INR 100,000 for an invoice. Transaction limits are set per transaction and per day, and the system handles billions of payments each month, making it the largest real-time system in the world by volume. FedNow in the United States is built by the Federal Reserve and settles in central bank money around the clock. Banks connect through a service provider or directly, and they exchange ISO 20022 messages such as pacs.008 for the payment and pacs.002 for the status report. The transaction limit at launch in 2023 was USD 500,000, with banks free to set lower limits for their own customers. The Federal Reserve later raised the network maximum to USD 1 million on 24 June 2025 and then to USD 10 million effective November 2025, while the participant default stayed at USD 100,000, so a learner should check the current limit before quoting it, because scheme limits change. FedNow supports request for payment, so a biller can ask a customer for USD 85 for a utility bill, and the customer approves it in their banking app. Adoption has grown steadily, but it coexists with older systems such as ACH and wire transfers, so banks must support several rails at once. Faster Payments in the United Kingdom is one of the oldest instant systems, launched in 2008, and it is built for speed inside a single country. Payments are normally credited within seconds, with a scheme limit of GBP 1 million per transaction, although individual banks set lower limits for retail customers. The system uses its own message formats and a central infrastructure operated by Pay.UK, and settlement happens through prefunded accounts at the Bank of England. Confirmation of payee, added later, checks the beneficiary name before the payment is sent. Faster Payments proves that an instant system can run reliably for more than fifteen years, but it also shows how hard it is to retrofit new features onto an established design. SEPA Instant Credit Transfer in Europe must work across more than thirty countries, which makes it the most complex of the four. A EUR 2,500 payment from a bank in Germany to a bank in France must complete within ten seconds, even though the two banks may use different core systems and different national practices. The scheme is based on ISO 20022 messages, and settlement can happen through the TARGET Instant Payment Settlement service operated by the European Central Bank, or through a clearing house. The European regulation that followed made receiving instant payments mandatory for banks, and it removed the price premium that some banks charged, which sharply increased adoption across the region. The comparison shows that there is no single correct architecture, only trade-offs that fit a market. UPI optimises for inclusion and volume, with simple addressing and low cost per transaction. FedNow optimises for safety, settling in central bank money with strong Federal Reserve backing. Faster Payments optimises for reliability inside one country, with a long operational track record. SEPA Instant optimises for cross-border reach, with a common rulebook across many jurisdictions. A business analyst designing a new instant service must therefore start from the market, the regulation, and the customer need, and only then choose the technical pattern that fits.

UPI in India is built around a simple addressing model that hides account numbers behind a virtual payment address. A customer pays to a handle such as a name followed by a bank identifier, or scans a QR code at a shop, and the system routes the payment to the correct account. The National Payments Corporation of India operates the central switch, and more than 300 banks participate. A street vendor can receive INR 120 for a cup of tea just as easily as a business can receive INR 100,000 for an invoice. Transaction limits are set per transaction and per day, and the system handles billions of payments each month, making it the largest real-time system in the world by volume.

FedNow in the United States is built by the Federal Reserve and settles in central bank money around the clock. Banks connect through a service provider or directly, and they exchange ISO 20022 messages such as pacs.008 for the payment and pacs.002 for the status report. The transaction limit at launch in 2023 was USD 500,000, with banks free to set lower limits for their own customers. The Federal Reserve later raised the network maximum to USD 1 million on 24 June 2025 and then to USD 10 million effective November 2025, while the participant default stayed at USD 100,000, so a learner should check the current limit before quoting it, because scheme limits change. FedNow supports request for payment, so a biller can ask a customer for USD 85 for a utility bill, and the customer approves it in their banking app. Adoption has grown steadily, but it coexists with older systems such as ACH and wire transfers, so banks must support several rails at once.

Faster Payments in the United Kingdom is one of the oldest instant systems, launched in 2008, and it is built for speed inside a single country. Payments are normally credited within seconds, with a scheme limit of GBP 1 million per transaction, although individual banks set lower limits for retail customers. The system uses its own message formats and a central infrastructure operated by Pay.UK, and settlement happens through prefunded accounts at the Bank of England. Confirmation of payee, added later, checks the beneficiary name before the payment is sent. Faster Payments proves that an instant system can run reliably for more than fifteen years, but it also shows how hard it is to retrofit new features onto an established design.

SEPA Instant Credit Transfer in Europe must work across more than thirty countries, which makes it the most complex of the four. A EUR 2,500 payment from a bank in Germany to a bank in France must complete within ten seconds, even though the two banks may use different core systems and different national practices. The scheme is based on ISO 20022 messages, and settlement can happen through the TARGET Instant Payment Settlement service operated by the European Central Bank, or through a clearing house. The European regulation that followed made receiving instant payments mandatory for banks, and it removed the price premium that some banks charged, which sharply increased adoption across the region.

The comparison shows that there is no single correct architecture, only trade-offs that fit a market. UPI optimises for inclusion and volume, with simple addressing and low cost per transaction. FedNow optimises for safety, settling in central bank money with strong Federal Reserve backing. Faster Payments optimises for reliability inside one country, with a long operational track record. SEPA Instant optimises for cross-border reach, with a common rulebook across many jurisdictions. A business analyst designing a new instant service must therefore start from the market, the regulation, and the customer need, and only then choose the technical pattern that fits.

Full lesson text (all scenes)

Completing a lesson updates your progress dashboard on the homepage.

Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.