Insights Contact

Trackers

Open Banking and Open Finance Tracker

← All trackers

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

RegionRulesPayments angleWho it applies to
United StatesCFPB personal financial data rights rule (Section 1033)Data access for aggregators and fintechsBanks, card issuers, data users
CanadaConsumer-Driven Banking Act; Bank of Canada oversightData sharing, then payment initiationBanks, credit unions, accredited providers
European UnionPSD2 now, PSD3 and the Payment Services Regulation next; FIDA proposalAccount access and payment initiationBanks 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

RegionRule or changeWhat it meansOpportunityKey date
United StatesCFPB 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
CanadaConsumer-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 UnionOpen 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

Open banking product manager
Owns data access and payment initiation products.
  • Writes the impact assessment
  • Plans API and consent changes
  • Runs go/no-go
  • Reports status
API platform lead
Builds and runs the APIs.
  • Builds data and payment endpoints
  • Meets uptime and speed rules
  • Publishes API reports
  • Fixes defects
Data and consent lead
Owns consent and data use, often with the DPO.
  • Designs consent screens and records
  • Checks data minimisation and deletion
  • Handles revocation
  • Certifies consent controls
Security architect
Protects access.
  • Designs authentication and tokens
  • Reviews third-party access
  • Runs security tests
  • Signs security readiness
Partnerships lead
Works with fintechs and aggregators.
  • Onboards and checks third parties
  • Handles disputes and liability questions
  • Tracks complaints
  • Confirms onboarding is ready
Compliance lead
Checks the rule is met.
  • Reads new rules
  • Approves impact assessments
  • Prepares reporting
  • Keeps evidence
Head of digital banking
Business sponsor.
  • Sets priorities and funding
  • Accepts remaining risk
  • Gives the go-live sign-off
  • Reports to leadership

2. Who is accountable for what (RACI)

ActivityOpen banking PMAPI leadConsent / privacySecurityPartnershipsComplianceSponsor
Log a rule and name an ownerRICIIAI
Impact assessmentACCCCRI
API build and performanceCAICIII
Consent and data use controlsCCACICI
Third-party access and onboardingCCCCACI
Go-live 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 compliance lead logs the item; Open banking product manager is named owner.
Evidence: Log entry
STEP 2 · BY T-90
Assess
Open banking product manager writes the impact assessment with the other leads.
Evidence: Signed impact assessment
STEP 3 · T-90 TO T-30
Build and test
API platform 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 digital banking signs.
Evidence: Go/no-go minutes
STEP 5 · T+30
Post-live check
Compliance lead checks the rule is met and files evidence.
Evidence: Evidence pack

4. Sign-off record

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

ItemPrepared byReviewed bySigned off byWhenEvidence
CFPB Section 1033 rewriteOpen banking product managerCompliance leadHead of digital bankingWhen the new rule is finalGap assessment
Canada consumer-driven bankingAPI platform leadData and consent leadHead of digital bankingBefore launchAccreditation 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

  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: 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

  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: API platform lead. With: Security architect, QA, third-party testers.

Example: build the data endpoints with rate limits and logging.

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: API platform lead. With: Data and consent lead (consent records), Security architect (test results).

Example: keep API performance reports and consent records.

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: Compliance lead (control check). Independent check: Internal audit.

Example: sample consents for scope and expiry.

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: 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

  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: 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

  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
1Open banking product managerPreparedImpact assessment done; scope metImpact assessment, UAT________________
2API platform leadReviewedAPIs built and meet performance rulesPerformance report________________
3Security architectReviewedAccess and tokens secureSecurity review________________
4Data and consent leadCertifiedConsent, data use and deletion correctConsent records________________
5Partnerships leadCertifiedThird-party onboarding readyOnboarding checklist________________
6Compliance leadCertifiedRule met; evidence filedControl test________________
7Head of digital bankingApprovedAccepts 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): 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.

High residual
0
from 4 inherent
Medium residual
3
from 6 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
OB-R1This areaAPIs 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 leadMedium 12
L3 x I4
Low 4
L1 x I4
Control: Effective
OB-R2This areaData 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 leadHigh 15
L3 x I5
Low 5
L1 x I5
Control: Effective
OB-R3This areaA third party misuses access
Cause: Weak onboarding and monitoring
Third-party checks, access monitoring and fast revocation
Preventive and detective · Monthly
Partnerships leadMedium 12
L3 x I4
Medium 8
L2 x I4
Control: Partly effective
OB-R4This areaPlans 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 managerMedium 12
L4 x I3
Low 6
L2 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
Compliance 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
Compliance leadHigh 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
Open banking 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
API platform 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 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
Compliance leadMedium 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.