UK PAYMENTS INFRASTRUCTURE · CAREER SKILLS
UK retail payments infrastructure: skills to build for 2027
The UK is moving from consultation into co-creation of a new retail payments infrastructure Blueprint. This is not a live system or a confirmed launch plan. For people building a payments career, the useful signal is the capability mix: ISO 20022, payment lifecycle operations, fraud controls, migration testing, resilience and clear authority for automated payments.
By Awais Amir · Published 2026-11-05 · Updated 2026-11-05
Know the stage before discussing the opportunity
The Retail Payments Infrastructure Board received 121 consultation responses from payments and technology firms, banks, merchants, trade bodies, consumer groups, consultancies, academics and individuals. Its response identifies prospective design proposals and areas that still need testing.
The current stage is co-creation, not implementation. The Bank, the RPIB, the Design Authority and industry experts will develop the high-level Blueprint from November 2026 to Spring 2027. The industry-owned Delivery Company is then expected to take forward detailed design, procurement, build and implementation.
No operational launch date is confirmed in the response. A strong candidate should distinguish proposed direction, Blueprint, detailed design, procurement, build, migration and live service. Treating those stages as interchangeable creates weak analysis.
Translate the proposed architecture into career skills
The proposed direction is a modular architecture built around common capabilities rather than one system for each payment product. The core would support existing journeys and allow new products or forms of money to use reusable foundations.
A common access foundation is intended to offer secure connection options while keeping shared technical, security and resilience standards. The proposed messaging baseline is ISO 20022, with product-level arrangements able to add data where their service needs it.
A proposed orchestration layer would validate, route and sequence payments, including batches. It could also support a time-limited transition from legacy Faster Payments and Bacs formats. That makes standards interpretation, mapping, testing and exception handling practical skills, not abstract architecture topics.
Settlement would remain coordinated into central bank money. The response leaves detailed choices open and notes that shared services such as fraud prevention, data sharing, directories and alias services need more work.
- ISO 20022: read a payment message, identify required data and explain why consistent implementation matters.
- Journey mapping: follow initiation, validation, routing, clearing, settlement, confirmation and exception handling.
- Migration testing: compare legacy and target formats, reconcile outputs and record failed cases.
- Access and resilience: understand direct and indirect participation, dependencies, service boundaries and failover.
- Fraud controls: separate identity, account ownership, authority and intent.
Learn the whole payment lifecycle
Consultation respondents placed weight on refunds, recalls, disputes, recovery, reconciliation and certainty of fate. These are the points where customers, merchants and operations teams need reliable status information.
Practise describing what happens when a payment is interrupted. Start with the last confirmed stage, identify the next expected message or control, record the unresolved state and explain who owns recovery. Do not assume that a payment failed simply because the customer journey stopped.
This skill applies across operations, implementation, product, risk, compliance, customer support and technical account management. It also improves sales discovery because it replaces feature claims with questions about the customer’s real payment journey.
Understand the emerging journeys without calling them live
The proposed baseline includes existing immediate, batch, recurring, scheduled and cross-border payments. Emerging journeys include account-to-account payments at physical and online points of sale, alias-based payments, interoperability between forms of money, delegated payments, programmability and deferred payments.
Account-to-account acceptance at point of sale needs more than fast infrastructure. Respondents highlighted certainty of fate, refunds, disputes, consumer protection, consistent user journeys and sustainable incentives for merchants and providers.
For agentic payments, respondents said activity should be identifiable, attributable to an accountable principal and backed by verifiable authority. Views still differ on where safeguards should sit and how much autonomy is suitable. That is a useful interview boundary: explain the control problem without claiming a settled model.
Worked practice: map one interrupted payment
Use a fictional account-to-account purchase as a portfolio exercise. A customer approves a £48 payment at 10:02. The merchant receives a pending message, but no final confirmation. The customer’s balance appears reduced and the merchant does not know whether to release the goods.
Draw the journey from payment request through authority, message validation, routing, clearing, settlement coordination and final status. Mark the last confirmed event. Then add the information needed for reconciliation, the timeout rule, the party that can confirm fate and the customer or merchant action while the status remains uncertain.
Create a second version showing recovery. Record the final status, duplicate-prevention check, refund or release decision and evidence retained. This demonstrates payment-operations judgement without pretending that the proposed infrastructure already exists.
- Observed fact: the exact message and timestamp received.
- Unknown: whether clearing or settlement completed.
- Control: prevent an unverified retry from creating a duplicate.
- Owner: the team or participant authorised to resolve the status.
- Evidence: identifiers and messages needed to reconcile the outcome.
Turn the development into honest interview evidence
Do not claim delivery experience if you only studied the proposal. Label your work as a practice exercise and show the reasoning. A concise portfolio pack can include a journey map, ISO 20022 data checklist, migration test cases, an exception log and a one-page explanation of the current programme stage.
For workplace examples, remove confidential names, customer information and sensitive technical detail. Focus on the problem, the evidence you checked, the handover and the result.
The strongest questions for an employer connect architecture to real work: which payment journeys the team owns, how it tests message changes, how failed states are reconciled, where fraud and authority checks sit, and how legacy services will remain safe during migration.
Practise the distinction
| Theme | Skill to build | Evidence to show |
|---|---|---|
| Common ISO 20022 messaging | Map fields, validation rules and extensions | Message checklist and test cases |
| Modular core | Separate core, scheme, product and user-interface responsibilities | Layered journey diagram |
| Phased migration | Test legacy and target paths without guessing cutover | Migration and reconciliation plan |
| Full payment lifecycle | Handle pending, failed, refunded and disputed states | Exception log with decision owners |
| Fraud and authority | Distinguish identity, account ownership, authority and intent | Control map for one payment journey |
| Operational resilience | Identify dependencies, minimum service and failover evidence | Scenario exercise and recovery checks |
Sources and dates
- Bank of England
Checked 5 Nov 2026, 08:33 UK time · Published 2026-11-04 - Bank of England
Checked 5 Nov 2026, 08:33 UK time · Published 2026-11-04 - FCA
Checked 5 Nov 2026, 08:33 UK time · Published 2026-07-02 - UK Finance response to the RPIB consultation
Checked 5 Nov 2026, 08:33 UK time · Published 2026-09-11 - Pay.UK
Checked 5 Nov 2026, 08:33 UK time · Published 2026-09-15