Skip to content
Banking, Finance & Fintech

Consumer-Driven Banking (Open Banking) in Canada

Consumer-driven banking is Canada's open banking framework, letting consumers direct secure sharing of their financial data with accredited providers. This note explains the Act re-enacted in 2026, the shift to Bank of Canada oversight, accreditation and the technical standard, liability rules, and where read access, write access and payments stand.

Smartphone banking app connecting securely to a bank under consumer-driven banking rules

Key takeaways

  • The Consumer-Driven Banking Act was re-enacted in S.C. 2026, c. 3, with the Bank of Canada as overseer.
  • Most provisions were not yet in force as of the consolidation current to 19 October 2026.
  • Draft regulations published in June 2026 start with accreditation, then common rules within a year.
  • Consumers are not liable for direct losses from unauthorized data use absent gross negligence.
  • Section 11 limits sharing to read access; payment initiation is not yet part of the framework.

What is consumer-driven banking?

Consumer-driven banking is Canada's term for open banking: a regulated system that lets consumers, including businesses, direct their financial institution to share their financial data securely with other accredited providers, such as fintech apps, lenders or other banks. The legal framework is the federal Consumer-Driven Banking Act (CDBA). Its stated purpose, in s. 3, is to establish a framework within which consumers can direct that their data be shared among participating entities of their choice, to ensure that sharing is safe and secure, and to foster competition in the financial sector.

Smartphone banking app connecting securely to a bank under consumer-driven banking rules
Consumer-driven banking replaces screen scraping with accredited, API-based data sharing under federal supervision.

Today, many Canadians use budgeting, lending and accounting apps that access their bank data through "screen scraping": the consumer hands over online banking credentials, and the app logs in on their behalf. That practice creates security and liability problems: the bank cannot tell the app from the customer, credential sharing may breach account terms, and when money goes missing it is unclear who should bear the loss. Consumers also have limited visibility into which apps hold their data and how to revoke access. The Department of Finance has described the goal as replacing it with secure, API-based data sharing. Consumer-driven banking aims to do that under common rules, with an accreditation system, a technical standard, liability rules and complaint handling.

Legislative history and 2026 status

Parliament first enacted a Consumer-Driven Banking Act in 2024 (S.C. 2024, c. 17, s. 198), with the Financial Consumer Agency of Canada (FCAC) as the intended regulator. That version was repealed and replaced by a new Act in the Budget 2025 Implementation Act, No. 1 (S.C. 2026, c. 3), which received royal assent on 26 March 2026. The current Act gives oversight to the Bank of Canada, which already supervises payment service providers under the Retail Payment Activities Act (RPAA).

As of the consolidation current to 19 October 2026, most of the Act's provisions are marked "not in force". On 26 June 2026 the Department of Finance announced the pre-publication of proposed Consumer-Driven Banking Regulations in the Canada Gazette, Part I, with a 60-day comment period. According to Finance, the regulations would take effect in a staggered approach beginning with accreditation, with requirements on common rules and assessment fees following within one year of final publication. Details on phasing for different products and services are to be set out in the final regulations.

ElementPosition under the current Act
RegulatorBank of Canada (the 2024 version contemplated the FCAC)
Data in scope (s. 10)Deposit accounts, registered and non-registered investment accounts, payment products, lines of credit, mortgages or hypothecs and other loans, and other products set by regulation; derived data excluded
ParticipantsBanks listed in the schedule, plus accredited federal and provincial financial institutions, registered payment service providers and other entities
Read versus writeSection 11 requires sharing in a manner that does not let the recipient edit data on the provider's servers
Consumer liability (s. 103)Consumer not liable for direct losses from unauthorized use of data, absent gross negligence (gross fault in Quebec)
Technical standardSet by a technical standards body designated by the Minister under s. 125

Participants and accreditation

A "participating entity" is a bank listed in the schedule to the Act, a federal or provincial financial institution accredited under s. 15, a registered payment service provider accredited under s. 17, or another entity accredited under s. 19. Provincial financial institutions include credit unions and caisses populaires regulated by provincial statutes and certain provincial Crown deposit-takers, which can opt in through accreditation. Under s. 19, the Bank of Canada may accredit other entities, typically fintechs, if satisfied that they meet the requirements set by regulation, on payment of an accreditation fee.

The Act also regulates accredited third-party service providers that provide services to participating entities in relation to their activities under the Act, and it gives the Bank powers to refuse, suspend and revoke accreditation. Accredited entities appear on a public registry that the Bank of Canada will maintain, which consumers and partners can check before sharing data. For fintechs, accreditation will likely require demonstrating security, privacy, operational risk management, complaint handling and financial resources, building on requirements that many already meet as registered payment service providers under the RPAA.

The technical standard

Data must be shared using a single technical standard. Under s. 125, the Minister designates a technical standards body responsible for establishing it, taking into account factors listed in the Act. Participants will have to build or adapt application programming interfaces to that standard, and the timing of the standard's publication is a key planning input for banks and fintechs alike. Firms already using international open banking standards should not assume the Canadian standard will be identical, and should budget for conformance testing and certification.

Liability allocation and consumer protection

A central feature of consumer-driven banking is a clear liability rule. Under s. 103(1), subject to the regulations, unless a consumer has demonstrated gross negligence (or gross fault, in Quebec) in safeguarding their authentication information, the consumer is not liable for financial loss that arises directly from a loss of, unauthorized access to, or unauthorized use of their data in relation to sharing under the Act. Participating entities will need to allocate that risk among themselves, through the regulations and the common rules, and through their own contracts and insurance.

The framework also requires participating entities to obtain and manage consumer consent, keep records, handle complaints, and participate in an external complaints body. Privacy law continues to apply in parallel: the federal Personal Information Protection and Electronic Documents Act (PIPEDA), Quebec's private sector privacy law and other provincial laws govern personal information that is shared. Bill C-15 also added a data mobility framework to PIPEDA, which is not yet in force.

Practical point

Fintechs that rely on screen scraping should plan their transition now. Map the data you use against the categories in s. 10, assess whether you will seek accreditation under s. 19 or partner with an accredited entity, and review whether your customer terms, consent flows and liability allocations will need to change when common rules take effect. Keep a dated record of the analysis, the documents relied on and who approved each decision, so that the reasoning can be explained later if questions arise.

Read access, write access and payments initiation

The current framework is built around data sharing, often called "read access". Section 11 provides that data shared between participating entities must be shared in a manner that does not enable the recipient to edit the data on the provider's servers. The Act as enacted does not set out a regime for "write access", in which a third party would initiate payments or change account settings on the consumer's instruction.

Payment initiation is closely linked to the RPAA, which regulates payment service providers, and to Payments Canada's modernization of the national payment systems, including the Real-Time Rail. Finance's June 2026 release refers to "the next phase of consumer-driven banking" but does not define write access or payment initiation. Businesses planning products that depend on payment initiation should treat it as a future development, subject to further legislation or regulations, rather than a current right. Status should be checked against the final regulations and any subsequent Finance announcements.

Illustration (hypothetical): a Toronto fintech offers small business cash flow forecasting by pulling bank and credit card data through screen scraping. Once the regulations are in force and its target banks participate, it applies to the Bank of Canada for accreditation under s. 19, builds to the designated technical standard, and replaces credential sharing with consented API access. Its terms of service are updated to reflect the statutory liability rule and the external complaints process.

Related fraud measures for banks

The June 2026 package also included proposed amendments to the Financial Consumer Protection Framework Regulations under the Bank Act, with a 30-day comment period, to operationalize anti-fraud amendments made by Bill C-15. According to Finance, banks would need a consumer's express consent before enabling electronic funds transfer capabilities such as wire transfers, consumers could disable certain capabilities, the rules would set timelines for changes to transaction limits, and banks would report specified fraud data to the FCAC.

These measures are separate from consumer-driven banking, which the Bank of Canada will supervise, but they matter to the same product teams. A fintech that relies on a customer's ability to move money from a bank account, for example to fund an investment or repay a loan, should check how consent requirements and transaction limits could affect its user journeys. Banks should design their consent and limit controls so that they do not unintentionally block legitimate data sharing or payments to accredited participants.

Contracts with aggregators and partners

Many fintechs access bank data through aggregators rather than building direct connections. Those contracts should be reviewed now: who will be the participating entity, who bears liability under s. 103 between the parties, how consents are captured and evidenced, what happens to data already collected through screen scraping, and how the arrangement will migrate to the technical standard. Indemnities, data retention and deletion clauses, security audit rights and termination rights tied to loss of accreditation are the main negotiating points.

What banks, credit unions and fintechs should do now

  • Banks listed or expected to be listed in the schedule should prepare API infrastructure, consent management and complaint processes, and budget for assessment fees.
  • Credit unions and provincial institutions should decide whether to seek accreditation, which may be important to compete with larger banks for consumers who want to use third-party apps.
  • Fintechs should review their RPAA status, security and privacy programmes, and contracts with data aggregators, and consider whether to become participating entities or rely on partners.
  • Data aggregators and service providers should assess whether they will be accredited third-party service providers and what obligations follow.
  • All participants should monitor the final regulations, the designation of the technical standards body and the Bank of Canada's supervisory guidance.

Quebec raises additional considerations: Quebec credit unions under the Desjardins framework and Quebec privacy law, including Law 25's rules on consent and transfers outside Quebec, will shape how consumer-driven banking is implemented for Quebec consumers.

How TRW & Co helps with consumer-driven banking

We advise banks, credit unions, fintechs and data aggregators on consumer-driven banking and open banking strategy in Canada. That includes accreditation planning, gap analysis against the Act and draft regulations, consent and privacy frameworks, data sharing and liability agreements, and engagement with the Bank of Canada. Where a filing or opinion requires a Canadian-licensed lawyer, we work with licensed counsel. Our fintech and payments and financial services regulatory work covers related issues; see also our notes on the Retail Payment Activities Act and Real-Time Rail access. To discuss your plans, contact us. This note is general information, not legal advice.

Frequently asked questions

Who regulates consumer-driven banking in Canada?

The Bank of Canada. The Act re-enacted in the Budget 2025 Implementation Act, No. 1, gives the Bank oversight of participating entities, accredited third-party service providers, the technical standards body and the external complaints body. The earlier 2024 version contemplated the Financial Consumer Agency of Canada.

Is the Consumer-Driven Banking Act in force?

Mostly not. The Act received royal assent on 26 March 2026, but most provisions were marked not in force in the consolidation current to 19 October 2026. Draft regulations were pre-published in June 2026 with a 60-day comment period, with a staggered start beginning with accreditation.

What data can be shared?

Section 10 covers data relating to deposit accounts, registered and non-registered investment accounts, payment products, lines of credit, mortgages or hypothecs and other loans, and products added by regulation. Derived data, meaning data enhanced by a participating entity, is excluded.

Can fintechs initiate payments under the framework?

Not under the Act as enacted. Section 11 requires data to be shared in a way that does not allow the recipient to edit data on the provider's servers. Payment initiation, or write access, would require further steps, so businesses should treat it as a future development.

Who bears losses if shared data is misused?

Under s. 103, subject to regulations, a consumer is not liable for financial loss arising directly from unauthorized access to or use of their data in connection with sharing under the Act, unless the consumer was grossly negligent (or committed gross fault in Quebec) in safeguarding authentication information.

Sources

  1. Consumer-Driven Banking Act, S.C. 2026, c. 3, s. 224 (consolidated)
  2. Department of Finance: Pre-publication of regulations (26 June 2026)
  3. Budget 2025 Implementation Act, No. 1, S.C. 2026, c. 3
  4. Personal Information Protection and Electronic Documents Act
  5. Bank of Canada: Retail payments supervision

General information only, not legal advice. References to statutes, courts and authorities describe published law and practice at the date shown.