Payments Academy
Payment platform in 2030 1 Payment platform in 2030 NOW 2 Cloud-native payment platform 3 Product owner role in 2030 4 Faster cross-border payments 5 Technology and regulation complexity 6 BA practice A payment platform in 2030 will be built on three foundations that are already visible today. Step 1 of 6 Payment platform in 2030 1 NOW Payment platform in 2030 2 Cloud-native payment platform 3 Product owner role in 2030 4 Faster cross-border payments 5 Technology and regulation complexity 6 BA practice A payment platform in 2030 will be built on three foundations that are already visible today. Step 1 of 6
Cloud-native payment platform 1 Payment platform in 2030 2 Cloud-native payment platform NOW 3 Product owner role in 2030 4 Faster cross-border payments 5 Technology and regulation complexity 6 BA practice The platform will run in the cloud, with the resilience that the cloud provides, and with the operational resilience that DORA requires. Step 2 of 6 Cloud-native payment platform 1 Payment platform in 2030 2 NOW Cloud-native payment platform 3 Product owner role in 2030 4 Faster cross-border payments 5 Technology and regulation complexity 6 BA practice The platform will run in the cloud, with the resilience that the cloud provides, and with the operational resilience that DORA requires. Step 2 of 6
Product owner role in 2030 1 Payment platform in 2030 2 Cloud-native payment platform 3 Product owner role in 2030 NOW 4 Faster cross-border payments 5 Technology and regulation complexity 6 BA practice The product owner's job will be to make the payment disappear into the experience Step 3 of 6 Product owner role in 2030 1 Payment platform in 2030 2 Cloud-native payment platform 3 NOW Product owner role in 2030 4 Faster cross-border payments 5 Technology and regulation complexity 6 BA practice The product owner's job will be to make the payment disappear into the experience Step 3 of 6
Faster cross-border payments 1 Payment platform in 2030 2 Cloud-native payment platform 3 Product owner role in 2030 4 Faster cross-border payments NOW 5 Technology and regulation complexity 6 BA practice Cross-border payments will be faster, cheaper, and more transparent, driven by the G20 roadmap and by the linking of instant payment systems. Step 4 of 6 Faster cross-border payments 1 Payment platform in 2030 2 Cloud-native payment platform 3 Product owner role in 2030 4 NOW Faster cross-border payments 5 Technology and regulation complexity 6 BA practice Cross-border payments will be faster, cheaper, and more transparent, driven by the G20 roadmap and by the linking of instant payment systems. Step 4 of 6
Technology and regulation complexity 1 Payment platform in 2030 2 Cloud-native payment platform 3 Product owner role in 2030 4 Faster cross-border payments 5 Technology and regulation complexity NOW 6 BA practice The technology will be more complex, the regulations will be more numerous, and the customer expectations will be higher, and someone must translate between them. Step 5 of 6 Technology and regulation complexity 1 Payment platform in 2030 2 Cloud-native payment platform 3 Product owner role in 2030 4 Faster cross-border payments 5 NOW Technology and regulation complexity 6 BA practice The technology will be more complex, the regulations will be more numerous, and the customer expectations will be higher, and someone must translate between them. Step 5 of 6
BA practice: future stack roadmap 1 Payment platform in 2030 2 Cloud-native payment platform 3 Product owner role in 2030 4 Faster cross-border payments 5 Technology and regulation complexity 6 BA practice NOW Last reviewed 7 November 2026. Step 6 of 6 BA practice: future stack roadmap 1 Payment platform in 2030 2 Cloud-native payment platform 3 Product owner role in 2030 4 Faster cross-border payments 5 Technology and regulation complexity 6 NOW BA practice Last reviewed 7 November 2026. Step 6 of 6

Steps of this lesson, in order.

0:00 / 4:10 Step 1 of 6

The future payment stack: what a 2030 payment platform looks like

Embedded finance and ISO 20022 data analytics, Lesson 7 of 7, Narration 4:10, D15 Advanced and emerging payments

Event-drivenPayment hubSettlement

What you will learn

Your objective. By the end of this lesson, you will be able to explain future payment stack: what a 2030 payment platform looks like and apply it to a real banking scenario.

Why it matters. For a business analyst, the future stack is a roadmap, not a prediction.

Chapter objective: Embedded payments, banking as a service, and what richer ISO 20022 data makes possible

Key learning points

  • Payment platform in 2030
  • Cloud-native payment platform
  • Product owner role in 2030
  • Faster cross-border payments
  • Technology and regulation complexity
  • BA practice: future stack roadmap

Key terms

Event-driven: An architecture where systems react to events, such as a payment received or a status changed, rather than polling for updates.

Payment hub: A central system in a bank that receives payment instructions from all channels, validates them, applies screening and routing rules, and sends them to the correct clearing system or correspondent.

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.

Payment flow diagram showing The future payment stack: what a 2030 payment platform looks like.

Practise this lesson

Exercise

Map the payment in this lesson through the hub components.

Use the hub components and their order in this lesson.

  1. What to do. List each component the payment passes through, what it does, and what happens if it fails.

Correct result. The payment enters through a channel, passes the gateway, validation, fraud and sanctions checks, routing, and the ledger, then leaves through the right clearing system. A failure at any component stops or holds the payment, and the hub must record where it stopped.

Why. The hub is where most payment requirements live. If you cannot map a payment through it, you cannot specify, test or fix it.

Check your understanding

Practice question

Which of the following best describes future payment stack: what a 2030 payment platform looks like?

Takeaway and next step

What to remember

For a business analyst, the future stack is a roadmap, not a prediction.

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

Open the Payment Lifecycle Simulator →

Builds on "AI in payments operations: reconciliation matching, exception prediction and governance".

Transcript and full text

Show transcript

A payment platform in 2030 will be built on three foundations that are already visible today. The first is ISO 20022 as the universal message standard, with every payment carrying structured data from initiation to settlement. The second is instant settlement, with every domestic system offering real-time clearing and with cross-border settlement moving toward the same speed through linked instant systems. The third is the API as the interface, with every capability exposed as a service that other products can consume. A platform built on these three foundations can serve any customer, any corridor, and any payment type, because the foundations are common. The architecture will be event-driven and cloud-native. The payment hub will publish events to a stream, the consumers will subscribe to the events they need, and the state will be derived from the event log. The platform will run in the cloud, with the resilience that the cloud provides, and with the operational resilience that DORA requires. The platform will be observable, with every event, every metric, and every trace available to the operations team. The platform will be testable, with a test environment that mirrors production and a test pack that covers every message and every exception. The customer experience will be invisible. A customer will not think about the payment, they will think about the outcome: the supplier is paid, the employee is paid, the goods are delivered. The payment will happen in the background, initiated by an API call, a scheduled instruction, or a smart contract, and the customer will see only the status. The product owner's job will be to make the payment disappear into the experience, while the business analyst's job will be to make sure the invisible payment is still screened, still reconciled, and still auditable. Central bank digital currencies and tokenised deposits will be part of the stack, not a separate world. A CBDC will be another settlement asset, alongside central bank reserves, and a tokenised deposit will be another form of commercial bank money. The payment platform must be able to settle in whichever asset the customer chooses, and must be able to convert between them. The business analyst must understand the difference between a CBDC, a tokenised deposit, and a stablecoin, because the regulatory treatment, the risk, and the settlement finality are different for each one. Cross-border payments will be faster, cheaper, and more transparent, driven by the G20 roadmap and by the linking of instant payment systems. Project Nexus is linking the instant systems of Singapore, Malaysia, Thailand, the Philippines and India, so a payment can travel from one to another in seconds. The mBridge project is linking central bank digital currencies for cross-border settlement. The result will be a cross-border payment that settles in seconds, costs a fraction of today's price, and shows the customer the full cost and the expected time before they confirm. The product must be ready for this, and the requirements must state the corridors, the costs, and the times. The business analyst's role in 2030 will be more important, not less. The technology will be more complex, the regulations will be more numerous, and the customer expectations will be higher, and someone must translate between them. The analyst must understand the messages, the architecture, the regulations, and the business, and must be able to write a requirement that a developer can build, a tester can test, and a regulator can approve. The analyst who can do this will be the most valuable person on the team, because they are the one who makes the complex simple. For a business analyst, the future stack is a roadmap, not a prediction. The roadmap must state which foundations the firm will adopt, in which order, and by when. The acceptance criteria must include a test where the roadmap is reviewed against the G20 targets, the scheme roadmaps, and the regulatory timetable, and is found to be consistent. Last reviewed 7 November 2026. Further reading: the G20 roadmap for enhancing cross-border payments; the Bank for International Settlements Project Nexus and mBridge reports; the Committee on Payments and Market Infrastructures work on fast payment systems; the McKinsey Global Payments Report 2024.

A payment platform in 2030 will be built on three foundations that are already visible today. The first is ISO 20022 as the universal message standard, with every payment carrying structured data from initiation to settlement. The second is instant settlement, with every domestic system offering real-time clearing and with cross-border settlement moving toward the same speed through linked instant systems. The third is the API as the interface, with every capability exposed as a service that other products can consume. A platform built on these three foundations can serve any customer, any corridor, and any payment type, because the foundations are common.

The architecture will be event-driven and cloud-native. The payment hub will publish events to a stream, the consumers will subscribe to the events they need, and the state will be derived from the event log. The platform will run in the cloud, with the resilience that the cloud provides, and with the operational resilience that DORA requires. The platform will be observable, with every event, every metric, and every trace available to the operations team. The platform will be testable, with a test environment that mirrors production and a test pack that covers every message and every exception.

The customer experience will be invisible. A customer will not think about the payment, they will think about the outcome: the supplier is paid, the employee is paid, the goods are delivered. The payment will happen in the background, initiated by an API call, a scheduled instruction, or a smart contract, and the customer will see only the status. The product owner's job will be to make the payment disappear into the experience, while the business analyst's job will be to make sure the invisible payment is still screened, still reconciled, and still auditable.

Central bank digital currencies and tokenised deposits will be part of the stack, not a separate world. A CBDC will be another settlement asset, alongside central bank reserves, and a tokenised deposit will be another form of commercial bank money. The payment platform must be able to settle in whichever asset the customer chooses, and must be able to convert between them. The business analyst must understand the difference between a CBDC, a tokenised deposit, and a stablecoin, because the regulatory treatment, the risk, and the settlement finality are different for each one.

Cross-border payments will be faster, cheaper, and more transparent, driven by the G20 roadmap and by the linking of instant payment systems. Project Nexus is linking the instant systems of Singapore, Malaysia, Thailand, the Philippines and India, so a payment can travel from one to another in seconds. The mBridge project is linking central bank digital currencies for cross-border settlement. The result will be a cross-border payment that settles in seconds, costs a fraction of today's price, and shows the customer the full cost and the expected time before they confirm. The product must be ready for this, and the requirements must state the corridors, the costs, and the times.

The business analyst's role in 2030 will be more important, not less. The technology will be more complex, the regulations will be more numerous, and the customer expectations will be higher, and someone must translate between them. The analyst must understand the messages, the architecture, the regulations, and the business, and must be able to write a requirement that a developer can build, a tester can test, and a regulator can approve. The analyst who can do this will be the most valuable person on the team, because they are the one who makes the complex simple.

For a business analyst, the future stack is a roadmap, not a prediction. The roadmap must state which foundations the firm will adopt, in which order, and by when. The acceptance criteria must include a test where the roadmap is reviewed against the G20 targets, the scheme roadmaps, and the regulatory timetable, and is found to be consistent. Last reviewed 7 November 2026. Further reading: the G20 roadmap for enhancing cross-border payments; the Bank for International Settlements Project Nexus and mBridge reports; the Committee on Payments and Market Infrastructures work on fast payment systems; the McKinsey Global Payments Report 2024.

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.