Canada Consumer-Driven Banking Act: Bank of Canada Rules
Bill C-15 shifted Canada's Consumer-Driven Banking oversight from FCAC to the Bank of Canada in 2026, with FDX designated for technical API standards.

Under Bill C-15, which received Royal Assent on March 26, 2026, Canada consumer-driven banking oversight moved from the Financial Consumer Agency of Canada (FCAC) to the Bank of Canada, reshaping accreditation for Canadian open banking API platforms and corporate treasury management software. Fintechs, aggregators, and banks must now align API architectures with draft federal regulations published in June 2026 and the Financial Data Exchange (FDX) technical standard.
- Regulator Shift (March 26, 2026): Bill C-15 repealed the 2024 placeholder rules and assigned supervision, accreditation, and operational resilience oversight to the Bank of Canada.
- Draft Regulations (June 27, 2026): Published in Canada Gazette, Part I, detailing consent management, liability allocation, privacy safeguards, and security controls.
- November 2026 Designations: The Department of Finance designated FDX (via its Canadian entity) as the technical standards body and OBSI as the external complaints body.
- Screen-Scraping Exit: Accredited APIs will replace credential-based screen scraping used by legacy data aggregators such as Plaid Canada API and Flinks financial data aggregation.
Why Oversight Moved From FCAC to the Bank of Canada
Consolidating supervision under the Bank of Canada's retail payments supervision mandate eliminates dual-regulator friction for payment service providers already registering under the Retail Payment Activities Act (RPAA). Earlier federal budgets had proposed housing consumer-driven banking inside the FCAC, but overlapping operational-risk examinations prompted Parliament to unify payment and data-sharing supervision.
For payment firms and treasury platforms, this regulatory consolidation mirrors the compliance posture already required under Canada's RPAA operational controls. Entities seeking accreditation to access consumer and small-business banking data must demonstrate incident-response readiness, cryptographic key governance, and segregated data-handling pipelines before connecting to mandatory bank participants.
To prevent duplicative third-party vendor audits across Canada's major banks, the Office of the Superintendent of Financial Institutions (OSFI) aligned Guideline B-10 expectations so federally regulated banks do not have to re-audit every Bank of Canada-accredited fintech independently. That coordination lowers bilateral onboarding bottlenecks that previously delayed enterprise API integrations by six to twelve months.
Technical Standards, Liability, and Key Implementation Milestones
The Department of Finance Canada's Consumer-Driven Banking Framework establishes a single interoperable API specification rather than permitting proprietary bank endpoints. In November 2026, Ottawa designated the Financial Data Exchange (FDX) to govern the Canadian technical standard and named the Ombudsman for Banking Services and Investments (OBSI) as the external complaints body.
- March 26, 2026 (Bill C-15 Royal Assent): Replaced the 2024 framework statute with the updated Consumer-Driven Banking Act (CDBA), formally designating the Bank of Canada as supervisor.
- June 27, 2026 (Canada Gazette, Part I): Released draft Consumer-Driven Banking Regulations codifying common consent dashboards, revocation timelines, and statutory liability rules.
- November 2026 (Standards & Redress Designations): Confirmed FDX as the mandatory technical standards body for standardized OAuth 2.0 / FAPI APIs and OBSI for dispute resolution.
- Liability and Data Scope: Regulations restrict secondary data resale, require explicit duration-bound consent, and assign strict liability tiers when unauthorized data access occurs.
Moving from credential-based screen scraping to tokenized FDX APIs directly affects treasury teams that rely on Canadian cross-border payment gateways and automated bank feeds. When banks decommission legacy scraping interfaces, corporate ERP connectors and middleware providers such as Flinks or Plaid Canada API must migrate clients to OAuth-based consent tokens to prevent reconciliation breaks.
Preparing Corporate Treasury and Fintech Stacks for Live APIs
Treasury engineering teams should map every banking feed against FDX v6+ payload schemas and pair read-access APIs with Payments Canada's Real-Time Rail (RTR) roadmap. While the initial phase of the Consumer-Driven Banking Act focuses on read-only account, balance, and transaction data, combining standardized account verification with ISO 20022 Real-Time Rail treasury architecture enables automated cash-flow forecasting and instant account-to-account funding.
Fintech product leaders should budget for two distinct cost centers ahead of full enforcement: Bank of Canada accreditation readiness (covering penetration testing, SOC 2 Type II or equivalent controls, and incident reporting) and API gateway refactoring to support FDX consent revocation webhooks. Organizations that already maintain RPAA operational risk documentation can reuse much of their governance evidence, reducing duplicate legal and security-audit fees in CAD.
Consent Revocation, Data Liability, and Screen-Scraping Cutoff
Under the June 27, 2026 Canada Gazette draft regulations, accredited data recipients must present standardized consent dashboards that allow consumers and small-business treasurers to inspect active data feeds, verify exact permission scopes, and revoke access in real time. Once a user revokes consent at either the bank or the fintech dashboard, FDX-compliant webhook notifications must terminate token refresh cycles immediately rather than waiting for overnight batch sweeps.
Liability allocation follows a clear fault-based boundary between mandatory bank data holders and accredited third-party recipients. Participating banks must expose reliable, rate-limit-transparent APIs without imposing discriminatory access fees on accredited fintechs, while accredited recipients carry direct accountability for downstream data breaches, unauthorized secondary monetization, and cryptographic credential storage. For Canadian corporate treasurers, retiring credential-based screen scraping eliminates shared-password risks that previously complicated cyber insurance underwriting and internal audit sign-offs across multi-bank cash management workflows.
Strategic Next Steps for Canadian Financial Teams
Audit all existing bank aggregation dependencies in your ERP and treasury stack now to identify any workflows still relying on user-credential screen scraping, and require written FDX migration timelines from data-aggregation vendors. Fintechs seeking direct Bank of Canada accreditation should align their security controls with the June 2026 Canada Gazette draft regulations immediately so engineering teams avoid costly consent-flow rewrites once final enforcement dates take effect.
Take the quizWhat Kind of Holiday Spender Are You? Take the Black Friday QuizStart →- 1Stock Market Today: Dow Slides 1.34% and VIX Jumps 15% at Midday

- 2Joachim Klement to Sell Stocks After S&P 500 Signal

- 3Stock Market Today: Nasdaq, S&P 500 Futures Slide as AI Selloff Deepens

- 4Kenneth Walker’s Groin Injury Puts Cardinals Game in Doubt

- 5Pat Cummins Faces Captaincy Doubts From Mitchell Johnson

Markets · FintechHow to Calculate Compound Interest: Formula, Examples and the Rule of 72
Lifestyle · Food & HealthNormal Blood Pressure Chart by Age: Healthy Ranges Explained
Lifestyle · Food & HealthWhat Is Raynaud’s Syndrome? Why Fingers Turn White in the Cold
Lifestyle · Food & Health4 Ways Walking After Meals Helps Your Body, Doctors Say












