Open banking and open finance rules: who must share customer financial data, how consent works, which payments third parties can start, and when, with the opportunity each one opens up.
Updated monthly · Last updated: · Items leave the tracker once their month has passed.
Who sets open banking rules
| Region | Rules | Payments angle | Who it applies to |
|---|---|---|---|
| United States | CFPB personal financial data rights rule (Section 1033) | Data access for aggregators and fintechs | Banks, card issuers, data users |
| Canada | Consumer-Driven Banking Act; Bank of Canada oversight | Data sharing, then payment initiation | Banks, credit unions, accredited providers |
| European Union | PSD2 now, PSD3 and the Payment Services Regulation next; FIDA proposal | Account access and payment initiation | Banks and third-party providers |
What changed this month
A short log of new and changed items, updated every month.
Week of Nov 16, 2026
- Tracker launched with 3 open banking and open finance items in the US, Canada and the EU.
- No firm dates yet: all three are still changing.
- Moved here from the US Regulators and Data Governance trackers: the CFPB Section 1033 rewrite, so it appears once.
Open banking 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 States | CFPB open banking rule (Section 1033) rewrite CFPB Our guide → · Source: Consumer Finance Monitor | Compliance dates are on hold by court order while the CFPB redrafts the rule, including whether banks can charge for data access. | Data-sharing APIs, consent management and aggregator pricing. | New proposal pending Change pending |
| Canada | Consumer-driven banking: final rules and launch Department of Finance; Bank of Canada Our guide → · Source: McCarthy Tetrault | Draft rules are out; final rules are aimed for late 2026 or early 2027, with payment access by mid-2027. | Accreditation, consent and API plans for Canadian data sharing. | Final rules late 2026 Change pending |
| European Union | Open finance law (FIDA) set to be withdrawn European Commission Our guide → · Source: Open Banking Tracker | FIDA is listed for withdrawal in the 2027 work programme; open banking under PSD2 and PSD3 stays. | Focus open finance plans on payment account data and commercial deals. | Withdrawal planned Change pending |
WHO OWNS THIS
Open banking and open finance: roles and sign-off
Each rule needs a named owner. The open banking product manager owns the change; the API platform lead builds and runs the APIs; the data and consent lead owns consent and data use; security protects access; partnerships onboards third parties; the head of digital banking signs off.
1. Roles and responsibilities
- Writes the impact assessment
- Plans API and consent changes
- Runs go/no-go
- Reports status
- Builds data and payment endpoints
- Meets uptime and speed rules
- Publishes API reports
- Fixes defects
- Designs consent screens and records
- Checks data minimisation and deletion
- Handles revocation
- Certifies consent controls
- Designs authentication and tokens
- Reviews third-party access
- Runs security tests
- Signs security readiness
- Onboards and checks third parties
- Handles disputes and liability questions
- Tracks complaints
- Confirms onboarding is ready
- Reads new rules
- Approves impact assessments
- Prepares reporting
- Keeps evidence
- Sets priorities and funding
- Accepts remaining risk
- Gives the go-live sign-off
- Reports to leadership
2. Who is accountable for what (RACI)
| Activity | Open banking PM | API lead | Consent / privacy | Security | Partnerships | Compliance | Sponsor |
|---|---|---|---|---|---|---|---|
| Log a rule and name an owner | R | I | C | I | I | A | I |
| Impact assessment | A | C | C | C | C | R | I |
| API build and performance | C | A | I | C | I | I | I |
| Consent and data use controls | C | C | A | C | I | C | I |
| Third-party access and onboarding | C | C | C | C | A | C | 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.
3. From review to sign-off
4. Sign-off record
One line per rule. No signed line, no go-live.
| Item | Prepared by | Reviewed by | Signed off by | When | Evidence |
|---|---|---|---|---|---|
| CFPB Section 1033 rewrite | Open banking product manager | Compliance lead | Head of digital banking | When the new rule is final | Gap assessment |
| Canada consumer-driven banking | API platform lead | Data and consent lead | Head of digital banking | Before launch | Accreditation plan, API 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 open banking rule to sign-off
How to handle an open banking or open finance rule from this tracker. 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: Open banking product manager. With: Compliance lead (reads the rule), API platform lead (sizes the work), Data and consent lead.
Example: a new data access rule. Confirm which accounts, data and customers are 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: Open banking product manager. With: API platform lead, Data and consent lead (consent design), Partnerships lead (third parties).
Example: map each rule clause to an API, consent screen or report.
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: API platform lead. With: Security architect, QA, third-party testers.
Example: build the data endpoints with rate limits and logging.
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: API platform lead. With: Data and consent lead (consent records), Security architect (test results).
Example: keep API performance reports and consent records.
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 consents for scope and expiry.
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: Open banking product manager. With: Partnerships lead, Data and consent lead (post-live review of uptime, errors and consent use).
Example: review uptime, errors and complaints after launch.
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: the head of digital banking (approves). Signers in order: Open banking product manager, API platform lead, Security architect, Data and consent lead, Partnerships 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 | Open banking product manager | Prepared | Impact assessment done; scope met | Impact assessment, UAT | ________________ |
| 2 | API platform lead | Reviewed | APIs built and meet performance rules | Performance report | ________________ |
| 3 | Security architect | Reviewed | Access and tokens secure | Security review | ________________ |
| 4 | Data and consent lead | Certified | Consent, data use and deletion correct | Consent records | ________________ |
| 5 | Partnerships lead | Certified | Third-party onboarding ready | Onboarding checklist | ________________ |
| 6 | Compliance lead | Certified | Rule met; evidence filed | Control test | ________________ |
| 7 | Head of digital banking | 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): Open banking and open finance
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 |
|---|---|---|---|---|---|---|
| OB-R1 | This area | APIs miss uptime or speed rules Cause: Capacity not planned for third-party traffic | API monitoring with alerts and capacity tests Preventive and detective · Continuous | API platform lead | Medium 12 L3 x I4 | Low 4 L1 x I4 Control: Effective |
| OB-R2 | This area | Data is shared beyond what the customer agreed Cause: Consent scope not enforced in the API | Consent scope checks on every call; consent audit Preventive · Continuous | Data and consent lead | High 15 L3 x I5 | Low 5 L1 x I5 Control: Effective |
| OB-R3 | This area | A third party misuses access Cause: Weak onboarding and monitoring | Third-party checks, access monitoring and fast revocation Preventive and detective · Monthly | Partnerships lead | Medium 12 L3 x I4 | Medium 8 L2 x I4 Control: Partly effective |
| OB-R4 | This area | Plans are built for a rule that changes Cause: Rules still being rewritten or withdrawn | Scenario plans and modular API design Preventive · Quarterly | Open banking product manager | Medium 12 L4 x I3 | Low 6 L2 x I3 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 | 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 | Compliance lead | 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 | Open banking 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 | API platform 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
- OB-R4: keep a 1033 scenario plan until the new rule is final. Owner: Open banking product manager.
- OB-R3: add monthly third-party access reviews. Owner: Partnerships lead.
- Test two controls in this area each quarter and keep the results in the evidence pack. Owner: Compliance lead.
Quarterly attestation
Open banking product manager (first line): confirm risks, controls and ratings are current. ________________
Compliance lead (second line review): confirms the review and challenge. ________________
Head of digital banking: 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.