Instant payment systems and ISO 20022 messaging changes around the world: new rails, limits, participants, operating hours and message deadlines, with the opportunity each one opens up.
Updated monthly · Last updated: · Items leave the tracker once their month has passed.
Who runs and sets the rules for instant payments
| Region | Systems and rules | Payments angle | Who it applies to |
|---|---|---|---|
| United States | FedNow (Federal Reserve), RTP (The Clearing House), Fedwire ISO 20022 | Instant payments and high-value wire messaging | Banks, credit unions, processors |
| European Union | Instant Payments Regulation; SEPA Instant | Sending, receiving and payee checks | EU payment providers |
| United Kingdom | Faster Payments (Pay.UK), CHAPS (Bank of England) | Purpose codes and richer ISO 20022 data | UK payment providers |
| Global | Swift CBPR+ and ISO 20022 standards | Cross-border message data such as structured addresses | Banks using Swift |
What changed this month
A short log of new and changed items, updated every month.
Week of Nov 16, 2026
- Tracker launched with 9 instant payment and ISO 20022 changes.
- Next deadline: Mexico SPEI common app transfer experience, Dec 14, 2026.
- Moved here from the Payment Rules and US Regulators trackers so each item appears once.
Instant payments and ISO 20022 tracker
Soonest first. Tap a region or a status to filter; tap again to clear.
FILTER BY REGION
FILTER BY STATUS
| Region | Rule or change | What it means | Opportunity | Key date |
|---|---|---|---|---|
| Canada | Real-Time Rail live, banks joining Our guide → · Source: Our Canada guide | Instant payments live since Nov 9; banks join in phases. | New instant products, fraud scoring and bank onboarding. | Live Nov 9, 2026 Just started |
| Global | Swift CBPR+: unstructured addresses retired Swift / Payments Market Practice Group (network rule) Our guide → · Source: Swift | Cross-border messages need a structured or hybrid address with town and country. Fully unstructured ones can be rejected. | Address parsing, data clean-up and rejection testing before payments fail. | Since Nov 14, 2026 Just started |
| Mexico | SPEI: one standard app transfer experience Our guide → · Source: Banco de México rules (via Regalert) | Every SPEI participant must follow Banxico’s common mobile transfer design. | App redesign, UX testing and SPEI certification support for banks and fintechs. | Dec 14, 2026 Deadline soon |
| Switzerland | Swiss banks must receive SIC instant payments Our guide → · Source: SIX | Remaining retail banks must accept instant payments. | Connectivity, fraud checks and testing for smaller banks. | End of 2026 Deadline soon |
| European Union | Instant euro payments: non-euro EU countries Our guide → · Source: European Central Bank | Non-euro EU banks must receive instant euro payments; sending and payee checks follow in July. | SCT Inst connectivity, Verification of Payee and fraud checks for banks in Poland, Sweden and others. | Receive by Jan 9, 2027 Upcoming |
| United Kingdom | CHAPS: purpose codes on every payment Our guide → · Source: Bank of England | All CHAPS payments must carry an ISO 20022 purpose code. | Purpose-code mapping, data quality checks and CHAPS regression testing. | Nov 2027 Upcoming |
| United States | Fedwire November release moved Federal Reserve (FRB Services) Our guide → · Source: FRB Services | The release planned for Nov 2026 now lands in Nov 2027. | A full year to plan and automate wire regression testing. | Nov 2027 Delayed |
| United States | Fedwire and NSS open Sundays (22×6) Federal Reserve (FRB Services) Our guide → · Source: FRB Services | Wires run 22 hours a day, Sunday to Friday. | Weekend treasury, settlement and liquidity products. | 2028 or 2029 Planned |
| United States | Reg J: intermediaries allowed on FedNow (proposed) Federal Reserve Our guide → · Source: Federal Register | Banks could send FedNow payments through intermediary banks, which opens a path to cross-border instant payments. | Correspondent and cross-border instant payment products. | Final rule date not set Proposed |
WHO OWNS THIS
Instant payments and ISO 20022: roles and sign-off
Each change needs a named owner. The payments product manager owns rail changes; the payments architect owns message formats; operations owns 24/7 readiness; treasury owns liquidity; QA proves message and scheme tests; the head of payments signs off.
1. Roles and responsibilities
- Writes the impact assessment
- Plans build, testing and launch
- Runs go/no-go
- Reports status weekly
- Maps fields and structured data
- Designs translation between formats
- Reviews vendor changes
- Signs the design
- Builds message and routing changes
- Works with the payment hub vendor
- Supports scheme testing
- Fixes defects before go-live
- Tests every message type and edge case
- Runs scheme readiness tests
- Reports pass and fail
- Signs test completion
- Updates procedures and staffing
- Monitors queues and exceptions
- Handles returns and investigations
- Confirms operations are ready
- Plans liquidity for 24/7 and higher limits
- Sets limits and alerts
- Monitors intraday positions
- Signs liquidity readiness
- Checks screening works in real time
- Reviews the impact assessment
- Keeps the evidence pack
- Certifies the rule is met
- Sets priorities and funding
- Accepts remaining risk
- Gives the go-live sign-off
- Reports to leadership
2. Who is accountable for what (RACI)
| Activity | Payments PM | Architect | Engineering | QA lead | Payments ops | Treasury | Head of payments |
|---|---|---|---|---|---|---|---|
| Log the change and name an owner | A | C | I | I | I | I | I |
| Impact assessment | A | R | C | C | C | C | I |
| ISO 20022 data mapping | C | A | R | C | I | I | I |
| Build and routing changes | C | C | A | C | I | I | I |
| Message and scheme testing | C | C | R | A | C | I | I |
| 24/7 operations and liquidity readiness | C | I | I | I | A | R | I |
| Go-live sign-off | R | R | R | R | R | R | A |
A accountable (one per activity, approves) · R responsible (does the work) · C consulted · I informed. The compliance lead checks real-time screening and certifies the rule; not shown as a column.
3. From review to sign-off
4. Sign-off record
One line per change. No signed line, no go-live.
| Item | Prepared by | Reviewed by | Signed off by | When | Evidence |
|---|---|---|---|---|---|
| Swiss SIC instant payments | Payments product manager | QA lead, Treasury lead | Head of payments | Before Dec 31, 2026 | Scheme tests, liquidity plan |
| Instant euro payments, non-euro EU banks | Payments product manager | Payments architect | Head of payments | Before Jan 9, 2027 | Payee check tests |
| CHAPS purpose codes | Payments architect | QA lead | Head of payments | Before Nov 2027 | Message tests |
Titles differ by firm; small teams may combine roles, but the person who builds should not be the only one who signs off. General guidance, not legal advice.
Runbook: from an instant payments or ISO 20022 change to sign-off
How to handle a new rail, limit, operating hours or message change from this tracker. Use one runbook per change. Each phase says when, why, what, who and how, and the evidence to keep.
▸1. Plan · Decide if the item applies to you, how big the change is, and who owns it.
When: As soon as an item appears on the tracker. Target: at least 90 days before the key date (T-90). For proposed rules, inside the comment window.
Why: Late discovery is the main reason teams miss deadlines, pay fines or ship rushed changes. Early planning turns a rule into a normal roadmap item.
What: Decide if the item applies to you, how big the change is, and who owns it.
Who: Owner: Payments product manager. With: Payments architect (reads the spec), Engineering lead (sizes the work), Payments operations lead.
Example: a new instant rail or a higher limit. Confirm channels, customers and limits in scope.
How
- Open the official source linked in the tracker and read the actual text, not only the summary.
- Map it to your products, rails, systems, vendors and customers in scope.
- Run a short gap analysis: what we do today versus what the rule needs.
- Size the work (small, medium, large) and add it to the roadmap with a target date.
- Log risks, assumptions, issues and dependencies in the RAID log.
Evidence to keep
- Impact assessment (applies / does not apply, with reason)
- Gap analysis
- Epic or change request with owner and target date
- RAID log entry
▸2. Prepare · Turn the rule into requirements, a design, a test plan and a rollout plan.
When: T-90 to T-60 days.
Why: Clear requirements and a test plan stop rework and give auditors a straight line from the rule to the change.
What: Turn the rule into requirements, a design, a test plan and a rollout plan.
Who: Owner: Payments product manager. With: Payments architect (data mapping), QA and test lead (test plan), Treasury and liquidity lead.
Example: map each ISO 20022 field and structured address element.
How
- Write requirements that quote the rule clause they come from.
- Agree the design and any vendor or partner changes, with dates.
- Build a traceability matrix: rule clause, requirement, test case, evidence.
- Plan test data, environments and a rollback.
- Book change windows and tell support and operations teams.
Evidence to keep
- Requirements with rule references
- Design or configuration decision
- Traceability matrix (draft)
- Test plan and rollback plan
▸3. Execute · Build or configure, test, and release the change safely.
When: T-60 days to go-live.
Why: This is where the change is built and proven. Testing against the rule, not just the feature, is what protects you.
What: Build or configure, test, and release the change safely.
Who: Owner: Engineering lead. With: Payments architect, QA and test lead, payment hub vendor.
Example: build routing and real-time sanctions screening.
How
- Build or configure the change behind a flag where possible.
- Run unit, system, regression and negative tests, plus UAT with the business.
- Fix defects and re-test; keep the defect log current.
- Hold a go/no-go meeting with clear criteria.
- Release, watch live metrics and keep the rollback ready.
Evidence to keep
- Test results and defect log
- UAT sign-off
- Go/no-go record
- Change ticket and release notes
▸4. Evidence · One evidence pack that shows the rule was understood, built, tested and approved.
When: Collected all the way through; packaged by T-7 days.
Why: If it is not written down, it did not happen. Good evidence makes audits short and calm.
What: One evidence pack that shows the rule was understood, built, tested and approved.
Who: Owner: QA and test lead. With: Payments operations lead (procedures), Treasury and liquidity lead (liquidity plan).
Example: keep scheme test results and message samples.
How
- Create one folder per tracker item with a simple index.
- Store each document with date, version and owner.
- Complete the traceability matrix with links to every test and approval.
- Add screenshots or exports of live configuration where relevant.
- Record training or communications sent to staff and customers.
Evidence to keep
- Evidence index
- Final traceability matrix
- Configuration proof
- Training and communication records
▸5. Audit · Second line (Compliance or Risk) tests the control; Internal Audit may sample it later.
When: From T-7 days to 30 days after go-live.
Why: An independent check finds gaps before a regulator, scheme or customer does.
What: Second line (Compliance or Risk) tests the control; Internal Audit may sample it later.
Who: Owner: Compliance lead (control check). Independent check: Internal audit.
Example: sample payments for complete structured data.
How
- Walk through the evidence pack against the rule text.
- Re-perform a sample of key tests or checks.
- Raise findings with a rating, owner and due date.
- Track findings to closure and re-test the fix.
Evidence to keep
- Control test results
- Findings log with owners and dates
- Closure evidence for each finding
▸6. Review · Post-implementation review: did it work, what broke, what we learned.
When: About 30 days after go-live.
Why: A short look back confirms the change works in real life and makes the next rule easier.
What: Post-implementation review: did it work, what broke, what we learned.
Who: Owner: Payments product manager. With: Payments operations lead, Treasury and liquidity lead (post-live review).
Example: review exceptions, returns and weekend liquidity.
How
- Check live metrics: errors, rejects, exceptions, complaints, incidents.
- Confirm all findings and defects are closed or accepted.
- Note lessons learned and update this runbook if needed.
- Update the tracker status and any related guides.
Evidence to keep
- Post-implementation review notes
- Metrics snapshot
- Lessons learned
▸7. Sign-off · Named people confirm the item is done and the evidence is complete.
When: After the review, and before closing the item.
Why: Formal sign-off shows clear ownership and closes the loop for auditors.
What: Named people confirm the item is done and the evidence is complete.
Who: Owner: Head of payments (approves). Signers in order: Payments product manager, Payments architect, Engineering lead, QA and test lead, Payments operations lead, Treasury and liquidity lead, Compliance lead.
Example: close the item when every signer has signed.
How
- Share the evidence pack and review notes with the approvers.
- Each approver confirms their part in writing, with date.
- Archive the pack in your GRC tool or records system.
- Close the epic and the RAID entries.
Evidence to keep
- Signed approvals (name, role, date)
- Archived evidence pack
- Closed epic and RAID items
Sign-off
Sign in this order: Prepared, then Reviewed, then Certified, then Approved. Each signer checks the evidence of the lines above. Close the item only when every line has a name, date and evidence link. The person who prepares cannot approve.
| # | Role | Stage | Confirms | Evidence | Name and date |
|---|---|---|---|---|---|
| 1 | Payments product manager | Prepared | Impact assessment done; scope and acceptance met | Impact assessment, UAT | ________________ |
| 2 | Payments architect | Reviewed | Data mapping and design correct | Mapping document | ________________ |
| 3 | Engineering lead | Reviewed | Change built, released and stable | Change ticket, release notes | ________________ |
| 4 | QA and test lead | Certified | Message and scheme tests passed | Test results | ________________ |
| 5 | Payments operations lead | Certified | 24/7 procedures and staffing ready | Runbooks, rota | ________________ |
| 6 | Treasury and liquidity lead | Certified | Liquidity and limits ready | Liquidity plan | ________________ |
| 7 | Compliance lead | Certified | Screening and rules met | Control test | ________________ |
| 8 | Head of payments | Approved | Accepts remaining risk and closes the item | Signed approval | ________________ |
Tip: copy this runbook into your own tracker or GRC tool, one copy per rule. Dates are relative to the key date shown in the tracker (T-90 means 90 days before).
Risk and control self-assessment (RCSA): Instant payments and ISO 20022
The main risks for this area, the controls that reduce them, and the risk left after those controls. 4 risks are specific to this area and 6 are shared by every tracker (C1 to C6). Owners match the roles in the Who owns this section above. Reviewed every quarter and checked by the second line. Preventive controls lower likelihood; detective and corrective controls lower impact. Read more in our RCSA guide.
10 risks assessed for this area. Controls bring every high inherent risk down to medium or low.
How to read the heat map: each dot is a risk. It starts at its inherent rating (no controls) and moves to its residual rating (after controls). Score = likelihood x impact: 1 to 6 Low, 8 to 12 Medium, 15 to 25 High. Mid-blue dots are this area; navy dots are shared risks.
QUARTERLY RCSA CYCLE
RISK AND CONTROL REGISTER
| ID | Type | Risk and cause | Control | Owner | Inherent | Residual |
|---|---|---|---|---|---|---|
| IP-R1 | This area | Messages are rejected after a format change Cause: Structured data not mapped; vendor late | Field mapping review and end-to-end message tests Preventive · Per change | Payments architect | Medium 12 L3 x I4 | Low 4 L1 x I4 Control: Effective |
| IP-R2 | This area | Liquidity runs short outside business hours Cause: No weekend funding plan | 24/7 liquidity plan, alerts and limits Preventive · Daily | Treasury and liquidity lead | High 15 L3 x I5 | Low 5 L1 x I5 Control: Effective |
| IP-R3 | This area | Real-time screening slows or fails Cause: Batch screening reused | Real-time sanctions screening with time limits Preventive and corrective · Continuous | Compliance lead | High 15 L3 x I5 | Medium 8 L2 x I4 Control: Effective |
| IP-R4 | This area | Fraud rises with instant, final payments Cause: Controls built for slower rails | Payee checks and real-time fraud scoring Preventive · Continuous | Payments product manager | High 16 L4 x I4 | Medium 8 L2 x I4 Control: Partly effective |
| C1 | Shared | A rule change is missed Cause: No owner watches the sources; news arrives late | Weekly tracker review; every new item gets a named owner within 5 days Preventive and detective · Weekly | Payments product manager | High 20 L4 x I5 | Medium 8 L2 x I4 Control: Effective |
| C2 | Shared | A rule is read the wrong way Cause: Summaries used instead of the rule text; no expert review | The impact assessment is signed against the source text Preventive · Per item | Payments architect | High 15 L3 x I5 | Medium 10 L2 x I5 Control: Effective |
| C3 | Shared | A deadline is missed Cause: Work starts too late; dependencies not tracked | Planning starts at T-90; RAID log and go/no-go before release Preventive and detective · Per item | Payments product manager | High 16 L4 x I4 | Low 6 L2 x I3 Control: Effective |
| C4 | Shared | Testing does not cover the rule Cause: Tests check features, not rule clauses | Traceability from each rule clause to a test, with sign-off Preventive · Per release | QA and test lead | Medium 12 L3 x I4 | Low 4 L1 x I4 Control: Effective |
| C5 | Shared | Evidence is missing at audit time Cause: Documents spread across tools; no index | Evidence pack with an index, checked at T-7 Preventive · Per item | Compliance lead | Medium 9 L3 x I3 | Low 3 L1 x I3 Control: Effective |
| C6 | Shared | Audit findings stay open Cause: No due dates or follow-up | Findings log with owner and due date; monthly review Preventive and detective · Monthly | Compliance lead | Medium 9 L3 x I3 | Low 4 L2 x I2 Control: Partly effective |
Open actions
- IP-R2: test the weekend liquidity plan before Fedwire Sunday hours. Owner: Treasury and liquidity lead.
- IP-R1: run structured address tests for all cross-border flows. Owner: Payments architect.
- Test two controls in this area each quarter and keep the results in the evidence pack. Owner: Compliance lead.
Quarterly attestation
Payments product manager (first line): confirm risks, controls and ratings are current. ________________
Compliance lead (second line review): confirms the review and challenge. ________________
Head of payments: accepts residual risk. ________________
This is a sample RCSA for planning and training. Adjust risks, ratings and owners to your own organisation before use. The full cross-area register is in the monthly portfolio status report.
This tracker is a summary for planning, not legal advice. Dates can change, so always check the official source before acting. The Opportunity column is our own view. Summaries are written in our own words; linked pages remain the property of their publishers. Corrections: sp@paymentconsultant.top.
© 2026 SP Sankar · paymentconsultant.top. This tracker, its summaries, diagrams and layout are original work and are protected. Please do not copy, republish or scrape this page without written permission. You are welcome to link to it. See also Payment Rules Tracker and Payment Tech News.