Insights Contact

Trackers

Fees and Interchange Tracker

← All trackers

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

RegionRulesPayments angleWho it applies to
United StatesFederal Reserve service prices; Regulation II debit cap; court-approved card settlementsFed fees, debit interchange, card acceptance rulesBanks, merchants, card issuers
United KingdomPayment Systems Regulator rules on card scheme feesScheme fee transparencyCard schemes, acquirers, merchants
AustraliaReserve Bank of Australia interchange and surcharging rulesInterchange caps and surchargesIssuers, acquirers, merchants
IndiaNPCI and government rules on UPI feesMerchant fees on large UPI paymentsBanks, 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

RegionRule or changeWhat it meansOpportunityKey date
United KingdomPSR 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 StatesFed 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
AustraliaForeign 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 StatesVisa 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 StatesDebit 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
IndiaUPI 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

Pricing and fees product manager
Owns pricing for payment products.
  • Writes the impact assessment
  • Plans price and contract changes
  • Runs go/no-go
  • Reports status
Finance lead
Owns payments economics.
  • Models cost and revenue impact
  • Updates budgets
  • Tracks margins after changes
  • Reviews the result
Scheme relations manager
Reads network and central bank fee notices.
  • Logs fee notices
  • Explains the change
  • Confirms dates
  • Escalates questions
Commercial lead
Owns merchant and client pricing.
  • Updates price lists and contracts
  • Sends customer notices
  • Handles pushback
  • Confirms pricing is ready
Billing operations lead
Runs billing systems.
  • Updates fee tables
  • Tests invoices
  • Fixes billing errors
  • Confirms billing is ready
Legal counsel
Fee rules, contracts and litigation.
  • Reads fee rules and court decisions
  • Reviews contract terms
  • Advises on surcharging rules
  • Signs the legal reading
Head of payments
Business sponsor.
  • Sets pricing strategy
  • Accepts remaining risk
  • Gives final sign-off
  • Reports to leadership

2. Who is accountable for what (RACI)

ActivityPricing PMFinanceScheme relationsCommercialBilling opsLegalHead of payments
Log a fee or price changeRCAIIII
Cost and revenue impactCACCIII
Customer pricing and noticesACIRCCI
Billing system updateCCIIAII
Legal review of fee rules and court casesICICIAI
Sign-offRRRRRRA

A accountable (one per activity, approves) · R responsible (does the work) · C consulted · I informed.

3. From review to sign-off

STEP 1 · WITHIN 5 DAYS
Log and assign
The scheme relations manager logs the item; Pricing and fees product manager is named owner.
Evidence: Log entry
STEP 2 · BY T-90
Assess
Pricing and fees product manager writes the impact assessment with the other leads.
Evidence: Signed impact assessment
STEP 3 · T-90 TO T-30
Build and test
Billing operations lead builds; changes are tested against each rule clause.
Evidence: Test results
STEP 4 · BY T-14
Go/no-go
All leads confirm readiness; the head of payments signs.
Evidence: Go/no-go minutes
STEP 5 · T+30
Post-live check
Finance lead checks the result and files evidence.
Evidence: Evidence pack

4. Sign-off record

One line per fee change. No signed line, no go-live.

ItemPrepared byReviewed bySigned off byWhenEvidence
Fed 2027 service pricesFinance leadBilling operations leadHead of paymentsBefore Jan 1, 2027Updated fee tables, budget
UK PSR scheme fee rulesPricing and fees product managerScheme relations managerHead of paymentsBefore Nov 30, 2026Fee 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

  1. Open the official source linked in the tracker and read the actual text, not only the summary.
  2. Map it to your products, rails, systems, vendors and customers in scope.
  3. Run a short gap analysis: what we do today versus what the rule needs.
  4. Size the work (small, medium, large) and add it to the roadmap with a target date.
  5. 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

  1. Write requirements that quote the rule clause they come from.
  2. Agree the design and any vendor or partner changes, with dates.
  3. Build a traceability matrix: rule clause, requirement, test case, evidence.
  4. Plan test data, environments and a rollback.
  5. 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

  1. Build or configure the change behind a flag where possible.
  2. Run unit, system, regression and negative tests, plus UAT with the business.
  3. Fix defects and re-test; keep the defect log current.
  4. Hold a go/no-go meeting with clear criteria.
  5. 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

  1. Create one folder per tracker item with a simple index.
  2. Store each document with date, version and owner.
  3. Complete the traceability matrix with links to every test and approval.
  4. Add screenshots or exports of live configuration where relevant.
  5. 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

  1. Walk through the evidence pack against the rule text.
  2. Re-perform a sample of key tests or checks.
  3. Raise findings with a rating, owner and due date.
  4. 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

  1. Check live metrics: errors, rejects, exceptions, complaints, incidents.
  2. Confirm all findings and defects are closed or accepted.
  3. Note lessons learned and update this runbook if needed.
  4. 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

  1. Share the evidence pack and review notes with the approvers.
  2. Each approver confirms their part in writing, with date.
  3. Archive the pack in your GRC tool or records system.
  4. 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.

#RoleStageConfirmsEvidenceName and date
1Pricing and fees product managerPreparedImpact assessment done; pricing plan agreedImpact assessment________________
2Finance leadReviewedCost and revenue impact correctFinancial model________________
3Scheme relations managerReviewedNetwork fee notice read correctlyNotice reference________________
4Legal counselCertifiedFee rules, contracts and litigation risks reviewedLegal memo________________
5Commercial leadCertifiedCustomer pricing and notices readyNotices, price lists________________
6Billing operations leadCertifiedBilling updated and testedBilling tests________________
7Head of paymentsApprovedAccepts remaining risk and closes the itemSigned 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.

High residual
0
from 3 inherent
Medium residual
3
from 7 inherent
Low residual
7
from 0 inherent

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.

Likelihood
5
10
15
20
25
4
8
12
16
20
3
6
9
12
15
2
4
6
8
10
1
2
3
4
5
R1
R2
R3
R4
C1
C2
C3
C4
C5
C6
12345
Impact

QUARTERLY RCSA CYCLE

IdentifyList risks for this area
AssessRate likelihood and impact
Map controlsLink each risk to controls
TestCheck controls work, with evidence
RateSet residual risk
ActAgree actions, owners, dates
ReportShare results and sign off

RISK AND CONTROL REGISTER

IDTypeRisk and causeControlOwnerInherentResidual
FE-R1This areaA 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 leadMedium 12
L3 x I4
Low 4
L1 x I4
Control: Effective
FE-R2This areaMargins 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 leadMedium 12
L3 x I4
Low 4
L1 x I4
Control: Effective
FE-R3This areaCustomer notices go out late
Cause: Notice periods not tracked
Notice calendar linked to fee dates
Preventive · Per change
Commercial leadMedium 9
L3 x I3
Low 3
L1 x I3
Control: Effective
FE-R4This areaA court decision changes fees with little warning
Cause: Litigation not watched
Legal watch on fee cases and scenario plans
Preventive · Monthly
Legal counselMedium 12
L3 x I4
Medium 8
L2 x I4
Control: Partly effective
C1SharedA 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 managerHigh 20
L4 x I5
Medium 8
L2 x I4
Control: Effective
C2SharedA 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 counselHigh 15
L3 x I5
Medium 10
L2 x I5
Control: Effective
C3SharedA 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 managerHigh 16
L4 x I4
Low 6
L2 x I3
Control: Effective
C4SharedTesting 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 leadMedium 12
L3 x I4
Low 4
L1 x I4
Control: Effective
C5SharedEvidence 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 leadMedium 9
L3 x I3
Low 3
L1 x I3
Control: Effective
C6SharedAudit findings stay open
Cause: No due dates or follow-up
Findings log with owner and due date; monthly review
Preventive and detective · Monthly
Finance leadMedium 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.