Insights Contact

Trackers

Payments Regulator Tracker

How a payments rule reaches your bankA change can start at any layer; each layer adds detail, and examiners check the result1Laws• Rights and duties for payments• Consumer transfers (EFTA)• Anti-money laundering (BSA)Who: Congress, statesExample: GENIUS Act2Regulations• Laws turned into detailed rules• Reg E, J, CC, II and Z• Proposals open for commentWho: Fed, CFPB, TreasuryExample: Reg J FedNow change3Network rules• Rules every member signs• Formats, limits, cut-offs• Fines for breaking themWho: Nacha, TCH, cards, SwiftExample: Same Day ACH $10M4Bank controls• Policies and procedures• Screening, limits, monitoring• Testing before releaseWho: Product, Ops, ComplianceExample: Swift address checks5Exams and enforcement• Examiners review the bank• Findings and fixes• Penalties when neededWho: OCC, Fed, FDIC, NCUAExample: AML program reviews6Monthly tracker• What changed this month• Deadlines and status• KPIs by payment railWho: This page, every MondayExample: Next 90-day deadlinesWatched every monthFed · CFPB · OCC · FDIC · FinCEN · OFAC · Treasury · Nacha · The Clearing House · Visa · Mastercard · SwiftHow a payments rulereaches your bankEach layer adds detail; examiners check1Laws• Rights and duties for payments• Consumer transfers (EFTA)• Anti-money laundering (BSA)Who: Congress, statesExample: GENIUS Act2Regulations• Laws turned into detailed rules• Reg E, J, CC, II and Z• Proposals open for commentWho: Fed, CFPB, TreasuryExample: Reg J FedNow change3Network rules• Rules every member signs• Formats, limits, cut-offs• Fines for breaking themWho: Nacha, TCH, cards, SwiftExample: Same Day ACH $10M4Bank controls• Policies and procedures• Screening, limits, monitoring• Testing before releaseWho: Product, Ops, ComplianceExample: Swift address checks5Exams and enforcement• Examiners review the bank• Findings and fixes• Penalties when neededWho: OCC, Fed, FDIC, NCUAExample: AML program reviews6Monthly tracker• What changed this month• Deadlines and status• KPIs by payment railWho: This page, every MondayExample: Next 90-day deadlinesWatched every monthFed · CFPB · OCC · FDIC · FinCEN · OFACTreasury · Nacha · TCH · Visa · Mastercard · Swift

← All trackers

Who makes the rules for each US payment rail, and the rule changes coming next. Laws set the rights, regulators write the detail, networks add their own rules, and examiners check that banks follow all of it.

Updated monthly · Last updated: · Items leave the tracker once their month has passed.

Right now the CFPB is examining a narrower set of firms, mainly banks and clear consumer fraud, so state regulators matter more for non-bank payment firms.

Who regulates each payment rail

RailLaw and regulationNetwork rules and operatorWho examines or enforces
ACH
Our guide →
Reg E for consumer payments; UCC 4A for business creditsNacha Operating Rules. Operators: FedACH (Fed) and EPN (The Clearing House)The bank's own regulator (OCC, Fed, FDIC or NCUA); CFPB for consumer protection
Wire
Our guide →
Reg J Subpart B and UCC 4A; Reg E remittance rule for consumer cross-border wiresFedwire Funds (run by the Fed); CHIPS rules (The Clearing House)OCC, Fed, FDIC or NCUA
FedNow
Our guide →
Reg J Subpart C and Operating Circular 8; Reg E for consumersFedNow Service Operating Procedures (Fed)OCC, Fed, FDIC or NCUA; CFPB for consumers
RTP
Our guide →
Reg E for consumers; UCC 4A for business paymentsRTP Operating Rules (The Clearing House)OCC, Fed, FDIC or NCUA; CFPB for consumers
Cards
Our guide →
Reg Z (credit), Reg E (debit and prepaid), Reg II (debit fees and routing)Visa, Mastercard, Amex and Discover rules; PCI DSS for card dataBank regulators for issuers and acquirers; CFPB; card brands fine members
Checks
Our guide →
Reg CC (when funds must be available), Reg J Subpart A, UCC 3 and 4, Check 21Fed check services; image-exchange network rulesOCC, Fed, FDIC or NCUA
P2P and wallets
Our guide →
Reg E; state money-transmitter laws for non-banks (PayPal, Venmo)Zelle network rules (Early Warning); wallet program rulesState regulators for non-banks; bank regulators for banks; CFPB
Cross-border
Our guide →
Reg E remittance rule; OFAC sanctions; FinCEN travel ruleSwift rules and CBPR+ ISO 20022 usage guidelinesBank regulators; OFAC and FinCEN enforce
Stablecoins
Our guide →
GENIUS Act and its implementing rulesIssuer's own reserve and redemption termsOCC, Fed, FDIC, NCUA or a state regulator; Treasury, FinCEN and OFAC for AML and sanctions
All rails
Our guide →
Bank Secrecy Act (AML), OFAC sanctions, Gramm-Leach-Bliley (data privacy)Each network adds its own fraud and risk rulesFinCEN, OFAC, CFPB, FTC and state attorneys general

What changed this month

A short log of new and changed payment rules, updated every month. Newest month first.

Week of Nov 16, 2026

  • To avoid duplicates, topic items moved to their own trackers: instant payments and Fedwire to Instant payments, fees and Reg II to Fees and interchange, stablecoins to Stablecoins, FinCEN rules to Sanctions and AML, and Section 1033 to Open banking.
  • Tracker launched with 16 rule changes across ACH, wire, FedNow, cards, cross-border, stablecoins and AML.
  • Swift CBPR+ unstructured addresses retired from Nov 14, 2026: rejections now possible on cross-border payments.
  • OCC final GENIUS Act rule (issued Oct 21, 2026) takes effect Jan 18, 2027 with the Act itself.
  • Appeals court ruling against Reg II (Oct 26, 2026) means the Fed must rewrite the debit fee cap.

Regulator change tracker

Soonest first. Tap a rail or a status to filter; tap again to clear.

FILTER BY RAIL

FILTER BY STATUS

RailRule or changeWhat it meansOpportunityKey date
ACH, Cross-borderNacha: register IAT contacts in the ACH Contact Registry
Nacha (network rule)
Our guide → · Source: Nacha
Every bank must list a contact for international ACH (IAT) issues.Update registry records and IAT exception-handling runbooks.Jan 1, 2027
Deadline soon
ACHNacha: accepted characters written into the rules
Nacha (network rule)
Our guide → · Source: Nacha
The rules now list the exact characters both ACH operators accept. A file with any other character can be held or rejected.Special-character validation and file tests before release.Jan 1, 2027
Deadline soon
P2P and walletsFDIC custodial deposits (proposed)
FDIC
Our guide → · Source: FDIC
Rules for pooled fintech customer accounts held at partner banks.Ledger and reconciliation tools for banking-as-a-service.Comments open
Proposed
ACH, Cross-borderNacha IAT: optional date of birth and non-bank foreign institutions
Nacha (network rule)
Our guide → · Source: Nacha
IAT entries gain an optional date-of-birth field and can name foreign non-bank account holders.IAT file format changes, sanctions screening and mapping tests.Mar 19, 2027
Upcoming
ACHSame Day ACH limit rises to $10 million
Nacha (network rule)
Our guide → · Source: Nacha
Each Same Day ACH payment can be up to $10 million (from $1 million).Update limit checks, risk controls and file testing for larger payments.Sep 17, 2027
Upcoming

WHO OWNS THIS

US payments regulators: roles and sign-off

Each regulator or network change needs a named owner. The regulatory change lead watches the Fed, CFPB, OCC, FDIC, FinCEN, OFAC, Nacha and the card networks; the payments product manager delivers the change; compliance and the BSA/AML officer confirm controls; the head of payments signs off before the effective date.

1. Roles and responsibilities

Regulatory change lead
Watches regulators and networks every week.
  • Logs new and proposed rules
  • Names an owner within 5 days
  • Approves impact assessments
  • Keeps the rule inventory for exams
Payments product manager
Delivers the change for the affected rail.
  • Writes the impact assessment
  • Plans build and testing
  • Runs go/no-go
  • Reports status weekly
Compliance officer or BSA/AML officer
Owns Reg E, CC, J and II controls, and AML and sanctions.
  • Updates policies and controls
  • Approves AML and sanctions changes
  • Prepares exam evidence
  • Signs compliance readiness
Legal counsel
Reads rules and court decisions.
  • Interprets final and proposed rules
  • Drafts comment letters
  • Tracks litigation such as Reg II and Section 1033
  • Signs the legal reading
Payments operations lead
Runs ACH, wire, FedNow, RTP and card operations.
  • Updates procedures and cut-offs
  • Handles Nacha and Fed registrations
  • Updates fee tables
  • Confirms operations are ready
Engineering and QA lead
Builds and proves the change.
  • Changes systems and file validation
  • Tests each requirement
  • Runs network certification
  • Signs test completion
Finance lead
Fees and budgets.
  • Updates budgets for Fed service prices
  • Models interchange changes
  • Confirms pricing changes
  • Reports cost impact
Head of payments
Business sponsor.
  • Sets priorities and funding
  • Accepts remaining risk in writing
  • Signs off before the effective date
  • Reports to leadership and the board
Internal audit
Independent checks.
  • Tests a sample of rule changes
  • Checks the evidence trail
  • Reports findings
  • Confirms fixes

2. Who is accountable for what (RACI)

ActivityProduct managerReg change leadCompliance / BSALegalPayments opsEngineering and QAHead of payments
Watch regulators and networks weeklyIACIIII
Comment letters on proposed rulesCRCACII
Impact assessment for a final ruleRACCCCI
AML and sanctions program changes (FinCEN, OFAC)CCACRCI
Nacha and Fed rule changes in systemsACCICRI
Fee and pricing updates (Fed service prices)RIIIRCA
Exam and audit readiness evidenceCRACRCI
Go-live sign-off before the effective dateRRRCRRA

A accountable (one per activity, approves) · R responsible (does the work) · C consulted · I informed. The finance lead joins fee items; internal audit tests independently. Neither is shown.

3. From review to sign-off

STEP 1 · WEEKLY
Watch and comment
Regulatory change lead logs changes; legal drafts comments on proposed rules.
Evidence: Rule log, comment letters
STEP 2 · WITHIN 30 DAYS OF A FINAL RULE
Assess
Product manager writes the impact assessment; compliance and legal approve.
Evidence: Signed impact assessment
STEP 3 · BEFORE THE EFFECTIVE DATE
Build and test
Engineering and QA build and test; operations update procedures and fees.
Evidence: Test results, updated procedures
STEP 4 · BEFORE THE EFFECTIVE DATE
Sign off
Compliance, operations and QA confirm readiness; head of payments signs.
Evidence: Sign-off record
STEP 5 · AFTER GO-LIVE
Exam-ready
Compliance files evidence; internal audit samples changes.
Evidence: Evidence pack, audit report

4. Sign-off record

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

ItemPrepared byReviewed bySigned off byWhenEvidence
Nacha accepted characters ruleEngineering and QA leadRegulatory change leadHead of paymentsBefore Jan 1, 2027File validation test results
Fed 2027 service pricesPayments operations leadFinance leadHead of paymentsBefore Jan 1, 2027Updated fee tables, budget approval
FinCEN AML/CFT program rule (proposed)BSA/AML officerLegalHead of paymentsPlan once finalGap assessment

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 US payments rule to sign-off

How to take any rule on this tracker, from the Fed, CFPB, FinCEN, OFAC, Nacha, The Clearing House, the card brands or Swift, 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: Regulatory change lead (logs the rule and names an owner). With: Payments product manager, Legal (reads the rule), Compliance or BSA/AML officer.

Example: Same Day ACH limit to $10 million. Check which products and clients could send larger payments.

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: Payments product manager. With: Legal (comment letters and reading), Engineering and QA lead, Payments operations lead, Finance lead (fees).

Example: update limit rules, risk scoring and client agreements; plan the date with your ACH operator.

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: Engineering and QA lead. With: Payments operations lead (procedures and registrations), Payments product manager.

Example: test files just under, at and over the new limit, plus returns.

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: Compliance officer or BSA/AML officer. With: Regulatory change lead (rule log), Payments operations lead.

Example: keep the Nacha notice, configuration change and test files together.

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: Internal audit (independent). With: Compliance officer for exam requests.

Example: compliance re-checks the Nacha rule text against the change.

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: Regulatory change lead. With: Payments product manager, Compliance officer (post-live review and inventory update).

Example: watch exception and return rates for large Same Day ACH payments.

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 before the effective date). Signers in order: Payments product manager, Legal, Engineering and QA lead, Payments operations lead, Compliance or BSA/AML officer, Regulatory change lead.

Example: sign-off includes the payments operations head and BSA/AML officer.

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
1Payments product managerPreparedImpact assessment done; scope and acceptance metImpact assessment, UAT sign-off________________
2Legal counselReviewedReading of the rule is correctLegal memo________________
3Engineering and QA leadCertifiedChange built; every requirement tested; network certification passedTest results, certification________________
4Payments operations leadCertifiedProcedures, fees and registrations updatedUpdated procedures, fee tables, registry confirmation________________
5Compliance officer or BSA/AML officerCertifiedRegulation met; AML and sanctions controls workControl test results, exam evidence pack________________
6Regulatory change leadCertifiedRule inventory updated; evidence filedRule log entry________________
7Head of paymentsApprovedAccepts remaining risk and closes before the effective dateSigned 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): US payments regulators

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 4 inherent
Medium residual
4
from 6 inherent
Low residual
6
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
REG-R1This areaA sanctions or AML change is not applied
Cause: Screening lists and rules updated by hand
List and rule updates checked and signed by the BSA/AML officer
Preventive · Per change
Compliance officer or BSA/AML officerHigh 15
L3 x I5
Medium 10
L2 x I5
Control: Effective
REG-R2This areaA Nacha or Fed rule change breaks file processing
Cause: File validation not updated
Rule-change test pack for ACH and wire files before each effective date
Preventive · Per change
Engineering and QA leadMedium 12
L3 x I4
Low 4
L1 x I4
Control: Effective
REG-R3This areaA proposed rule becomes final with little lead time
Cause: No plan for proposed rules
Early impact note and comment letter for each proposed rule
Preventive · Per item
Regulatory change leadMedium 12
L3 x I4
Medium 8
L2 x I4
Control: Partly effective
REG-R4This areaA fee or pricing change is not applied
Cause: Fed price updates loaded late
Fee table update and finance sign-off before the effective date
Preventive · Yearly
Payments operations leadMedium 9
L3 x I3
Low 3
L1 x I3
Control: 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
Regulatory change leadHigh 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
Payments 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
Engineering and QA 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
Compliance officer or BSA/AML officerMedium 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
Compliance officer or BSA/AML officerMedium 9
L3 x I3
Low 4
L2 x I2
Control: Partly effective

Open actions

  • REG-R2: add Nacha accepted-character checks to the file test pack. Owner: Engineering and QA lead.
  • REG-R3: write impact notes for the FinCEN proposed rules. Owner: Regulatory change lead.
  • Test two controls in this area each quarter and keep the results in the evidence pack. Owner: Compliance officer or BSA/AML officer.

Quarterly attestation

Payments product manager and Regulatory change lead (first line): confirm risks, controls and ratings are current. ________________

Compliance officer or BSA/AML officer (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.