Payment fee, interchange and pricing rule changes, from central bank service prices to card fee caps and court cases, with the opportunity each one opens up.
Updated monthly · Last updated: · Items leave the tracker once their month has passed.
Who sets payment fees and fee rules
| Region | Rules | Payments angle | Who it applies to |
|---|---|---|---|
| United States | Federal Reserve service prices; Regulation II debit cap; court-approved card settlements | Fed fees, debit interchange, card acceptance rules | Banks, merchants, card issuers |
| United Kingdom | Payment Systems Regulator rules on card scheme fees | Scheme fee transparency | Card schemes, acquirers, merchants |
| Australia | Reserve Bank of Australia interchange and surcharging rules | Interchange caps and surcharges | Issuers, acquirers, merchants |
| India | NPCI and government rules on UPI fees | Merchant fees on large UPI payments | Banks, payment apps, merchants |
What changed this month
A short log of new and changed items, updated every month.
Week of Nov 16, 2026
- Tracker launched with 6 fee and interchange changes.
- Next deadline: UK PSR card scheme fee rules, Nov 30, 2026.
- Moved here from the Payment Rules and US Regulators trackers so each item appears once.
Fees and interchange 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 |
|---|---|---|---|---|
| United Kingdom | PSR card scheme fee governance and transparency Our guide → · Source: PSR | Visa and Mastercard must justify and clearly explain scheme fees. | Acquirers: audit scheme fee lines; prepare for July 2027 transparency. | Nov 30, 2026 Deadline soon |
| United States | Fed service prices for 2027 Federal Reserve Our guide → · Source: Federal Reserve | New Fed fees for check, ACH, FedNow and wire services. | Re-price products and move volume to cheaper or instant rails. | Jan 1, 2027 Deadline soon |
| Australia | Foreign card interchange cap and fee transparency Our guide → · Source: Westpac IQ | Card surcharge ban started Oct 1, 2026; foreign card caps follow. | Pricing, fee reporting and acquirer system changes for merchants and processors. | Apr 1, 2027 Upcoming |
| United States | Visa and Mastercard merchant settlement Federal court (E.D.N.Y.) Our guide → · Source: Payments Dive | Merchants could choose to accept commercial, premium or standard credit cards separately. Standard consumer credit rates capped at 1.25%. | Card acceptance rules, surcharging, routing and pricing changes for acquirers and merchants. | Final approval pending Change pending |
| United States | Debit fee cap (Reg II) struck down Federal Reserve and the courts Our guide → · Source: ABA Banking Journal | An appeals court ruled the Fed let banks count costs the law does not allow. The Fed must rewrite the debit interchange cap. | Debit pricing models, routing and issuer revenue planning. | Rewrite date not set Change pending |
| India | UPI merchant fee on payments above ₹2,000 Our guide → · Source: Inc42 | NPCI postponed the October start; new date not yet notified. | Prepare pricing, billing and merchant notices before fees begin. | Date not set Delayed |
WHO OWNS THIS
Fees and interchange: roles and sign-off
Each fee change needs a named owner. The pricing and fees product manager owns the change; finance models the impact; scheme relations reads network notices; commercial updates customer pricing; billing operations updates systems; legal reviews fee rules and court cases; the head of payments signs off.
1. Roles and responsibilities
- Writes the impact assessment
- Plans price and contract changes
- Runs go/no-go
- Reports status
- Models cost and revenue impact
- Updates budgets
- Tracks margins after changes
- Reviews the result
- Logs fee notices
- Explains the change
- Confirms dates
- Escalates questions
- Updates price lists and contracts
- Sends customer notices
- Handles pushback
- Confirms pricing is ready
- Updates fee tables
- Tests invoices
- Fixes billing errors
- Confirms billing is ready
- Reads fee rules and court decisions
- Reviews contract terms
- Advises on surcharging rules
- Signs the legal reading
- Sets pricing strategy
- Accepts remaining risk
- Gives final sign-off
- Reports to leadership
2. Who is accountable for what (RACI)
| Activity | Pricing PM | Finance | Scheme relations | Commercial | Billing ops | Legal | Head of payments |
|---|---|---|---|---|---|---|---|
| Log a fee or price change | R | C | A | I | I | I | I |
| Cost and revenue impact | C | A | C | C | I | I | I |
| Customer pricing and notices | A | C | I | R | C | C | I |
| Billing system update | C | C | I | I | A | I | I |
| Legal review of fee rules and court cases | I | C | I | C | I | A | I |
| Sign-off | R | R | R | R | R | R | A |
A accountable (one per activity, approves) · R responsible (does the work) · C consulted · I informed.
3. From review to sign-off
4. Sign-off record
One line per fee change. No signed line, no go-live.
| Item | Prepared by | Reviewed by | Signed off by | When | Evidence |
|---|---|---|---|---|---|
| Fed 2027 service prices | Finance lead | Billing operations lead | Head of payments | Before Jan 1, 2027 | Updated fee tables, budget |
| UK PSR scheme fee rules | Pricing and fees product manager | Scheme relations manager | Head of payments | Before Nov 30, 2026 | Fee review |
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 fee or interchange change to sign-off
How to handle a fee, interchange or pricing 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: Pricing and fees product manager. With: Scheme relations manager (reads the notice), Finance lead (cost impact), Legal counsel.
Example: a new interchange cap or fee schedule. Confirm products and customers 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: Pricing and fees product manager. With: Finance lead, Commercial lead (customer pricing), Billing operations lead.
Example: map each fee change to price lists, contracts and billing codes.
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: Billing operations lead. With: Finance lead, Pricing and fees product manager.
Example: update fee tables and billing rules.
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: Finance lead. With: Billing operations lead (billing tests), Commercial lead (customer notices).
Example: keep billing test results and customer notices.
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: Finance lead (control check). Independent check: Internal audit.
Example: sample invoices for the new fees.
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: Pricing and fees product manager. With: Finance lead, Commercial lead (review of margins and complaints).
Example: review margins and complaints after the change.
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: Pricing and fees product manager, Finance lead, Scheme relations manager, Legal counsel, Commercial lead, Billing operations 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 | Pricing and fees product manager | Prepared | Impact assessment done; pricing plan agreed | Impact assessment | ________________ |
| 2 | Finance lead | Reviewed | Cost and revenue impact correct | Financial model | ________________ |
| 3 | Scheme relations manager | Reviewed | Network fee notice read correctly | Notice reference | ________________ |
| 4 | Legal counsel | Certified | Fee rules, contracts and litigation risks reviewed | Legal memo | ________________ |
| 5 | Commercial lead | Certified | Customer pricing and notices ready | Notices, price lists | ________________ |
| 6 | Billing operations lead | Certified | Billing updated and tested | Billing tests | ________________ |
| 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): Fees and interchange
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 |
|---|---|---|---|---|---|---|
| FE-R1 | This area | A fee change is billed wrongly Cause: Fee tables updated late or by hand | Billing tests and invoice sampling before each change Preventive · Per change | Billing operations lead | Medium 12 L3 x I4 | Low 4 L1 x I4 Control: Effective |
| FE-R2 | This area | Margins fall after a cap or fee change Cause: Impact not modelled or not passed on | Finance model and pricing decision before each change Preventive · Per change | Finance lead | Medium 12 L3 x I4 | Low 4 L1 x I4 Control: Effective |
| FE-R3 | This area | Customer notices go out late Cause: Notice periods not tracked | Notice calendar linked to fee dates Preventive · Per change | Commercial lead | Medium 9 L3 x I3 | Low 3 L1 x I3 Control: Effective |
| FE-R4 | This area | A court decision changes fees with little warning Cause: Litigation not watched | Legal watch on fee cases and scenario plans Preventive · Monthly | Legal counsel | Medium 12 L3 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 | Scheme relations 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 | 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 | Pricing and fees 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 | Billing operations 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 | Finance 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 | Finance lead | Medium 9 L3 x I3 | Low 4 L2 x I2 Control: Partly effective |
Open actions
- FE-R4: keep Reg II and card settlement scenarios up to date. Owner: Legal counsel.
- FE-R1: test Fed 2027 fees in billing before Jan 1. Owner: Billing operations lead.
- Test two controls in this area each quarter and keep the results in the evidence pack. Owner: Finance lead.
Quarterly attestation
Pricing and fees product manager (first line): confirm risks, controls and ratings are current. ________________
Finance 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.