The payment rules and changes coming next, country by country, and the opportunity each one opens up for payment, compliance and testing teams. Each row links to the official or source page and to our guide for that country.
Last updated: Thursday, November 19, 2026 · Checked twice a day against official sources for new and changed rules. Rules leave the tracker a few months after they take effect.
FILTER BY COUNTRY
FILTER BY STATUS
| Country | Rule or change | What it means | Opportunity | Key date |
|---|---|---|---|---|
| India | RBI Domestic Money Transfer Directions Our guide → · Source: Reserve Bank of India |
Walk-in NEFT capped at ₹50,000, with extra checks on every transfer. | Authentication, monitoring and limit testing for cash transfers. | Since Nov 11, 2026 Just started |
| South Africa | Non-banks join the national payment system Our guide → · Source: Cliffe Dekker Hofmeyr |
Fintechs, telcos and retailers can connect directly, first around March 2027. | Direct-access builds, PayShap integration and certification for non-bank firms. | From Mar 2027 Upcoming |
| Singapore | Corporate cheques phased out Our guide → · Source: Linklaters |
MAS roadmap moves businesses from cheques to new e-payment options during 2027. | Invoice and payout e-payment products (EDP) for firms leaving cheques. | During 2027 Upcoming |
| Brazil | Customer consent for credit offered in Pix Our guide → · Source: Lets Money |
Banks need the customer’s prior OK to offer credit inside Pix (Resolution BCB 603). | Consent flows, credit-offer controls and testing for Pix apps. | Jul 1, 2027 Upcoming |
| Mexico | Digital Payments Law (bill) Our guide → · Source: Mexico News Daily |
Bill to grow phone payments over SPEI and CoDi and cut cash use. | Mobile acceptance and phone-number payments for merchants. | Bill before Congress Proposed |
| Kenya | National Payment System Policy (draft) Our guide → · Source: Central Bank of Kenya |
CBK draft policy for the next phase of Kenya’s payment system. | Instant-payment switch and interoperability work for banks and wallets. | Draft 2026 Proposed |
| European Union | PSD3 and Payment Services Regulation Our guide → · Source: European Parliament |
Council adopted its position; Parliament’s final vote is next. | Plan fraud data sharing, payee checks and open banking upgrades. | Parliament vote pending Change pending |
WHO OWNS THIS
Payment rules: roles and sign-off
Every rule on this tracker needs a named owner within 5 days. The payments product manager owns the change from impact assessment to go-live; compliance and legal confirm the reading of the rule, QA proves it with tests, and the head of payments gives the final sign-off.
1. Roles and responsibilities
- Writes the impact assessment with compliance
- Turns the rule into requirements and a plan
- Runs go/no-go and keeps the evidence
- Reports status every week
- Logs new rules and names an owner within 5 days
- Approves the impact assessment
- Checks controls after go-live
- Keeps the evidence for exams
- Confirms what the rule requires
- Advises on unclear or conflicting rules
- Reviews customer terms and notices
- Signs the legal reading
- Designs and builds the change
- Estimates effort and flags risk early
- Supports scheme or network testing
- Fixes defects before go-live
- Traces each rule clause to test cases
- Runs scheme and network certification tests
- Reports pass, fail and open defects
- Signs test completion
- Updates procedures, cut-offs and controls
- Trains staff before go-live
- Handles scheme and network registrations
- Confirms operations are ready
- Tracks bulletins and mandates
- Books certification windows
- Gets scheme confirmations
- Escalates scheme issues
- Sets priorities and funding
- Accepts remaining risk in writing
- Gives the go-live sign-off
- Reports to leadership
- Challenges impact assessments for high-risk rules
- Tests a sample of changes each year
- Checks the evidence trail
- Confirms fixes are done
2. Who is accountable for what (RACI)
| Activity | Product manager | Compliance lead | Legal | Engineering | QA lead | Payments ops | Head of payments |
|---|---|---|---|---|---|---|---|
| Log a new rule and name an owner (within 5 days) | R | A | I | I | I | I | I |
| Impact assessment | R | A | C | C | C | C | I |
| Legal reading of the rule | C | C | A | I | I | I | I |
| Requirements and backlog | A | C | I | R | C | C | I |
| Build the change | C | I | I | A | C | I | I |
| Test against each rule clause | C | C | I | R | A | C | I |
| Scheme or network certification | A | C | I | R | R | C | I |
| Operations readiness: procedures and training | C | C | I | I | I | A | I |
| Go/no-go and go-live sign-off | R | R | C | R | R | R | A |
| Post go-live check and evidence filed | R | A | I | C | C | R | I |
A accountable (one per activity, approves) · R responsible (does the work) · C consulted · I informed. Risk and internal audit test independently and are not shown.
3. From review to sign-off
4. Sign-off record
One line per rule change. No signed line, no go-live.
| Item | Prepared by | Reviewed by | Signed off by | When | Evidence |
|---|---|---|---|---|---|
| Mastercard TLID on card-on-file charges | Payments product manager | Compliance lead, QA and test lead | Head of payments | Before Dec 1, 2026 | Impact assessment, test results, scheme confirmation |
| Nacha IAT contact registration | Payments operations lead | Compliance lead | Head of payments | Before Jan 1, 2027 | Registry confirmation |
| Instant euro payments, non-euro EU banks | Payments product manager | Compliance lead, Legal | Head of payments | Before Jan 9, 2027 | Impact assessment, go/no-go minutes |
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 a country rule to sign-off
How to take any rule on this tracker, in any country, from first sight to signed-off evidence. Use one runbook per rule. 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: Compliance lead (logs the rule and names the owner), Legal (reads the rule), Engineering lead (sizes the work), Payments operations lead (process impact).
Example: a new instant-payment rule in Brazil. Check if you send or receive Pix, and which partner bank or PSP is affected.
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: Business analyst, Engineering lead, QA and test lead (traceability), Scheme and network relations (certification windows).
Example: ask the local partner bank for its own deadline, which is often earlier than the regulator date.
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: QA and test lead, Payments operations lead, Scheme and network relations (certification tests).
Example: test local formats, limits and cut-off times in the partner sandbox.
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 product manager, Payments operations lead (procedures and training records).
Example: keep the regulator notice, partner confirmation and test results together per country.
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 testing). Independent check: Risk and internal audit.
Example: compliance re-checks the local rule text, in translation where needed.
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: Compliance lead, Payments operations lead, Engineering lead (post-live review at T+30).
Example: compare reject and return rates for that country before and after.
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, Legal, Engineering lead, QA and test lead, Payments operations lead, Compliance lead.
Example: sign-off includes the country or regional compliance owner.
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, requirements, UAT sign-off | ________________ |
| 2 | Legal counsel | Reviewed | Reading of the rule is correct | Legal memo | ________________ |
| 3 | Engineering lead | Reviewed | Change built, released and stable | Change ticket, release notes | ________________ |
| 4 | QA and test lead | Certified | Every rule clause tested and passed; scheme or network certification done | Traceability matrix, test and certification results | ________________ |
| 5 | Payments operations lead | Certified | Procedures, cut-offs, monitoring and training ready | Runbooks, training records | ________________ |
| 6 | Compliance lead (regulatory change) | Certified | Rule met and controls work; findings closed | Control test results, findings log | ________________ |
| 7 | 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): Payment rules
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 |
|---|---|---|---|---|---|---|
| PR-R1 | This area | Partner bank or scheme deadline is earlier than the regulator date Cause: Only the regulator notice is tracked |
Written confirmation of dates from each partner bank and scheme Preventive · Per item |
Payments product manager | Medium 12 L3 x I4 |
Low 4 L1 x I4 Control: Effective |
| PR-R2 | This area | Scheme or network certification window is missed Cause: Test slots booked late |
Certification calendar; slots booked at T-90 Preventive · Per item |
Scheme and network relations | Medium 12 L3 x I4 |
Low 4 L1 x I4 Control: Effective |
| PR-R3 | This area | A country rule is applied to the wrong products or customers Cause: Scope not mapped |
Scope map of products, rails and countries in every impact assessment Preventive · Per item |
Payments product manager | Medium 12 L3 x I4 |
Low 4 L1 x I4 Control: Effective |
| PR-R4 | This area | Operations are not ready at go-live Cause: Procedures, cut-offs and training done late |
Readiness checklist signed by operations at go/no-go Preventive · Per release |
Payments operations lead | Medium 12 L3 x I4 |
Low 4 L1 x I4 Control: 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 |
Compliance lead (regulatory change) | 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 |
Legal counsel | 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 (regulatory change) | 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 (regulatory change) | Medium 9 L3 x I3 |
Low 4 L2 x I2 Control: Partly effective |
Open actions
- PR-R2: book scheme certification slots for all Q1 2027 deadlines. Owner: Scheme and network relations.
- C6: add automatic reminders for findings past their due date. Owner: Compliance lead.
- Test two controls in this area each quarter and keep the results in the evidence pack. Owner: Risk and internal audit.
Quarterly attestation
Payments product manager and Compliance lead (first line): confirm risks, controls and ratings are current. ________________
Risk and internal audit (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. See also Payment Tech News.