Table of Contents
- 1. Canada’s payment initiation aims to enhance transaction efficiency
- 2. Legislative Progress Toward Payment Initiation in Canada
- 3. The Role of Payment Initiation in Open Banking
- 4. Key Discussions from Open Banking Expo Canada 2026
- 5. Challenges in Implementing Payment Initiation
- 5.1 Establishing Standards and Secure Infrastructure
- 5.2 Building Trust in Financial Transactions
- 6. Consumer and Merchant Benefits of Payment Initiation
- 7. The Importance of Trust in Open Banking
- 8. Navigating the Future of Payment Initiation in Canada
- 8.1 The Road Ahead: Key Considerations for Stakeholders
- 8.2 Building Trust: The Role of Security and Standards
Canada’s payment initiation aims to enhance transaction efficiency
- Canada is moving from “read access” open banking to “write access” by 2027, enabling payment initiation at scale.
- Industry leaders say the real value of Consumer-Driven Banking comes when data access is paired with action.
- “Pay by Bank” could streamline account-to-account payments and reduce reliance on cards, but only if standards, security, and accountability are clear.
- Trust—built through accreditation, guardrails, and recognizable signals for consumers—will be decisive for adoption.
Payment Initiation Explained
Payment initiation is the “write” side of Consumer-Driven Banking.
– Read access: an app can retrieve your account data (balances, transactions) to power insights.
– Write access: with your explicit consent, an accredited provider can request an action—like initiating a payment from your account.
– “Pay by Bank”: the consumer-facing idea behind payment initiation—paying directly from a bank account (account-to-account) rather than via card rails.
Legislative Progress Toward Payment Initiation in Canada
Canada’s open banking program—officially framed as “Consumer-Driven Banking”—is now on a path that goes beyond sharing account data. The pivotal shift is “write access”: the ability for accredited third parties to initiate actions, including payments, on a customer’s behalf with explicit consent.
In practice, that means moving from APIs that only return information (“read”) to flows where a customer can authorize a specific transaction (“write”) through standardized, supervised interfaces—rather than sharing banking credentials via workarounds like screen scraping.
The legislative anchor is the Consumer-Driven Banking Act (CDBA), passed as part of Bill C-69 in June 2024. The intent is to move the market away from insecure data-sharing practices such as screen scraping and toward secure, standardized API-based access. Implementation has been described in phases: foundational work through 2024 and early 2025, standards and supervision work through 2025, and mandatory read-only API access in early 2026.
| Milestone (high level) | What it means for the market | Timing mentioned in public reporting / targets |
|---|---|---|
| CDBA legislated (Bill C-69) | Legal foundation for Consumer-Driven Banking and API-based sharing | June 2024 |
| Foundation work | Governance setup, early scoping for standards and supervision | 2024–early 2025 |
| Standards & supervision work | Technical standards and accreditation/supervision design | 2025 |
| Read access goes live (mandatory) | Standardized, supervised data access (read-only) | Early 2026 |
| Write access target (includes payment initiation) | Consumer-authorized actions like “Pay by Bank” and account switching | Mid-2027 (target) |
The next milestone is the one the payments industry is watching: write access targeted for mid-2027, which is where payment initiation sits alongside other “action” capabilities such as account switching. At Open Banking Expo Canada 2026, the panel discussion captured the magnitude of this transition—moving from viewing data to writing data “into different organizations,” as moderator Megha Sharma put it.
Oversight has also evolved. Following Budget 2025, responsibility for implementation, accreditation, and supervision shifted from the Financial Consumer Agency of Canada (FCAC) to the Bank of Canada, while FCAC retains a consumer-facing guidance role. The result is a framework that is not only legislative, but operational—requiring standards, supervision, and enforcement to make write access workable in real-world payments.
The Role of Payment Initiation in Open Banking
Payment initiation is the practical bridge between open banking as “information access” and open banking as “transaction capability.” In simple terms, it allows a consumer or business to authorize an accredited third party to initiate a payment directly from a bank account via secure APIs—without relying on traditional card rails or manual online banking steps.
The Open Banking Expo Canada 2026 panel framed the journey as moving “from access to action.” Read access can power budgeting tools, account aggregation, and comparisons—but it stops short of executing outcomes. Write access, by contrast, enables account-to-account payment flows that can be embedded inside apps and merchant checkouts.
Payment initiation is often described as “Pay by Bank.” In the Canadian context, its promise is closely tied to the broader modernization of payments infrastructure, especially the expected arrival of Real-Time Rail (RTR). Wealthsimple’s Abdi Hersi pointed to multiple elements “coalescing together”: the regulatory push, open banking coming online, and RTR expected soon—together creating the conditions for real-time, consumer-driven payments.
End-to-End Pay by Bank
A practical “Pay by Bank” flow (what typically has to happen end-to-end):
1) User chooses Pay by Bank in an app or at checkout.
2) Consent is requested (what account, what amount, who the payee is, and whether it’s one-time or recurring).
3) Strong authentication happens at the user’s financial institution (the “prove it’s you” step).
4) Payment initiation request is sent via standardized APIs to the bank.
5) Bank validates the request (consent, limits, fraud checks, account status) and either accepts or rejects.
6) Confirmation is returned to the app/merchant (so the user sees a clear success/failure outcome).
7) Funds movement/settlement occurs on the underlying rail (where RTR readiness can materially affect speed and confirmation quality).
Checkpoint to watch in real deployments: if steps 2–6 aren’t consistent across institutions, the user experience fragments and adoption suffers.
International comparisons also shape expectations. Panelists referenced the UK experience, where fintechs such as Revolut and Monzo have used open banking capabilities to build products and serve customers more effectively. For Canada, the strategic point is not copying another market’s model, but recognizing the same underlying dynamic: once payment initiation is available, product design can shift from “insights about money” to “moving money” with customer permission.
Key Discussions from Open Banking Expo Canada 2026
At Open Banking Expo Canada 2026, speakers from Citi, Wealthsimple, and Lazer Technologies focused less on whether payment initiation is valuable—and more on what it will take to make it real at scale.
A central theme was that read access is necessary but insufficient. The panel argued that Consumer-Driven Banking’s full value emerges when data can be paired with action—especially payments. Payment initiation was positioned as a way to streamline transactions, reduce reliance on cards, and open new commercial models across the payments ecosystem.
The discussion also surfaced a practical tension: the ecosystem needs standardization, but it also needs incentives. Sonia Bakshi of Citibank argued that standardization “is definitely required,” while cautioning against leaving it solely to banks and fintechs. Her view: a neutral body should set standards, and the system should be commercialized so participants have a reason to invest in building it properly.
“Standardization is definitely required, but we wouldn’t want to leave it to the hands of banks and fintechs. I feel that there should be a body that is neutral which puts in these standardizations.”
Sonia Bakshi, director, digital head Canada at CitibankWhat It Takes to Scale
A simple way to read the panel’s “what it will take” message:
– Standards (Bakshi, Citi): interoperability needs a neutral standard-setter so integrations don’t become one-off deals.
– Incentives (Bakshi, Citi): if banks/fintechs must build and operate it, there has to be a commercial reason to invest and maintain quality.
– Guardrails (Hersi, Wealthsimple): government-set rules help define acceptable risk, responsibilities, and baseline protections.
– Use cases (panel theme): adoption depends on obvious day-to-day wins (faster, lower-cost, better UX) for both consumers and merchants.
– Trust signals (Hersi, Wealthsimple): accreditation needs to be visible at the moment of consent (for example, a recognizable label).
Wealthsimple’s Hersi emphasized the role of government in setting “guardrails,” reflecting a broader point: payment initiation is not just a technical feature; it is a trust and accountability system. The panel also stressed that adoption will hinge on real-world use cases that deliver clear benefits to both consumers and merchants—faster payments, lower costs, and better user experiences.
Finally, the conversation repeatedly returned to trust signals. Hersi highlighted advocacy for a label that accredited institutions could use so customers can quickly identify trusted participants—an attempt to make accreditation visible and meaningful at the moment a consumer is asked to consent.
That kind of signal matters because payment initiation decisions are made in-context (inside an app or at checkout): a clear indicator of accreditation helps consumers distinguish supervised participants from lookalikes before they approve a payment.
Challenges in Implementing Payment Initiation
Payment initiation may be the headline capability of write access, but the path to implementation is constrained by a set of interlocking challenges: standards, infrastructure readiness, accountability, and trust. The Open Banking Expo Canada 2026 panel was explicit that moving from “read” to “write” is a “massive shift,” and that execution details will determine whether the opportunity becomes a widely adopted payment method or a niche feature.
A key dependency is timing and operational readiness. As of March 2026, the Bank of Canada had not committed to a firm launch date for payment initiation, citing the need for further technical and operational preparedness. Another dependency is the Real-Time Rail, expected to launch in late 2026 or early 2027, which is widely seen as important for real-time execution and modern payment experiences.
Security and fraud risk are also not abstract concerns. Deloitte has noted rising fraud activity in financial services from 2024 to 2025, driven by AI-powered scams and synthetic identities—threats that can target open banking channels if controls and monitoring are uneven across participants. This makes consistent standards and supervision more than a compliance exercise: they are prerequisites for adoption.
Key Implementation Tradeoffs
The implementation hurdles often show up as tradeoffs teams must actively manage:
– Speed vs. safety: faster, smoother checkout flows can increase risk if authentication, limits, and monitoring aren’t consistent.
– Openness vs. control: broader third-party participation can drive innovation, but it raises the bar for accreditation and supervision.
– Standardization vs. flexibility: one standard improves interoperability, but it can feel constraining for product teams used to bespoke integrations.
– Commercialization vs. accessibility: participants need economic incentives to build/operate reliably, but fees and complexity can slow adoption.
– Real-time promise vs. rail readiness: “instant” experiences depend on underlying rail availability and uniform integration quality.
Establishing Standards and Secure Infrastructure
Standardization is the foundation for interoperability: without it, payment initiation becomes fragmented, expensive to integrate, and hard to supervise. Canada’s framework mandates a single technical standard, modeled on FDX specifications, to support consistent API-based data and payment flows.
Security protocols described in the broader framework include OAuth 2.0 with multi-factor authentication, TLS 1.3 encryption, incident response runbooks, and an accreditation regime for non-bank third-party providers.
Combined with consistent API standards, these controls are what make “Pay by Bank” viable at scale: they reduce integration ambiguity and create clearer expectations for how authentication, consent, and incident handling should work across participants. Accreditation expectations referenced in reporting include controls such as SOC 2 Type II and insurance requirements—signals that participation is conditional on operational maturity.
Infrastructure readiness is not uniform. Many financial institutions still need to modernize legacy systems and build robust API layers capable of supporting real-time, high-availability payment initiation. That modernization burden is one reason the panel emphasized commercialization: if banks and fintechs are expected to build and maintain the rails, they need a viable economic rationale to invest “enough to make it work in the best way,” as Bakshi argued.
Finally, there is governance: standards must be set and maintained, changes must be managed, and participants must have clarity on what “good” looks like. The panel’s call for a neutral body reflects the risk of leaving standards to bilateral negotiations that can slow adoption and weaken consistency.
Building Trust in Financial Transactions
Trust is the adoption gate for write access. Payment initiation asks consumers to authorize a third party not just to view data, but to move money—raising the stakes for authentication, consent, and accountability.
The framework’s approach includes accreditation and consumer protections such as no consumer liability when using accredited providers, with liability following the data. But trust also needs to be legible in the user experience. Hersi’s proposal for a recognizable label is a practical response: consumers need a quick way to distinguish accredited, supervised participants from lookalikes.
“Trust is a key factor… we’ve been advocating for is a label that financial institutions can use… so clients can quickly identify, ‘this is a trusted institution… I’m willing to engage in Open Banking use cases through their portals’.”
Abdi Hersi, director, payments strategy and partnership development at Wealthsimple
Accountability frameworks matter just as much as security controls. When something goes wrong—an unauthorized payment, a disputed transaction, or a compromised credential—participants need clear rules for investigation, remediation, and liability. Without that clarity, banks may hesitate to open write access broadly, fintechs may struggle to design reliable products, and consumers may decline consent.
Trust is also shaped by outcomes. If early payment initiation experiences are confusing, slow, or error-prone, skepticism will harden. That is why the panel stressed real-world use cases and tangible benefits: trust is built not only through regulation, but through consistently good experiences that match the promise of “faster, cheaper, better.”
Consumer and Merchant Benefits of Payment Initiation
If payment initiation succeeds, its benefits should show up in everyday transactions—especially at checkout, in bill payments, and in recurring account-to-account flows. The Open Banking Expo Canada 2026 discussion framed “Pay by Bank” as a way to streamline transactions and reduce reliance on cards, which implies both cost and experience improvements across the ecosystem.
For consumers, the most visible benefit is convenience paired with control. Payment initiation is designed to be consumer-authorized: the customer consents to a specific action through an accredited provider, rather than sharing banking credentials or relying on insecure workarounds. In a mature implementation, this can translate into smoother payment experiences inside apps consumers already use—without being redirected into clunky banking interfaces.
Speed is another driver. With Real-Time Rail, the combination of real-time payments infrastructure and write-access APIs points toward faster settlement and more immediate confirmation—features that can reduce uncertainty for both payer and payee.
For merchants, the appeal is often framed as lower costs and fewer intermediaries compared with card-based payments. While the panel did not quantify savings, it did highlight “lower costs” as a key adoption driver. Merchants also benefit from improved user experience: fewer checkout steps can reduce abandonment, and clearer payment confirmation can improve fulfillment workflows.
| Who benefits | What “Pay by Bank” can improve | What it depends on (in practice) |
|---|---|---|
| Consumers | Clearer control (explicit consent per action), fewer credential-sharing workarounds | Simple, consistent consent UX; visible accreditation signals; predictable confirmation screens |
| Consumers | Faster confirmation and potentially faster funds movement | Rail readiness (e.g., RTR), bank uptime/latency, consistent API behavior |
| Merchants | Potentially lower payment acceptance costs vs cards (not quantified by the panel) | Commercial model/fees, integration effort, dispute/returns handling that fits merchant ops |
| Merchants | Better checkout conversion (fewer steps) and clearer “paid” status for fulfillment | Standardized flows across banks; reliable success/failure messaging; fraud controls that don’t add friction |
| Ecosystem (banks/fintechs) | New commercial models and embedded payment experiences | Incentives to invest, neutral standards, clear accountability when something goes wrong |
The panel also pointed to new commercial models. Payment initiation can enable embedded payment experiences inside non-bank platforms, and it can support product innovation by fintechs—echoing the UK examples where firms used open banking capabilities to build differentiated offerings. In Canada, Hersi suggested the shift could help “level-set the playing field” between large financial institutions and fintechs, potentially increasing competition and choice.
Still, the benefits are conditional. Without compelling use cases that consumers recognize as better than cards or existing transfers, adoption may stall. The promise is real—but it must be delivered in products that feel safer, simpler, and clearly advantageous.
The Importance of Trust in Open Banking
Trust is the connective tissue of Consumer-Driven Banking, and payment initiation intensifies that requirement. Read access already involves sensitive financial information; write access adds the ability to execute transactions. That is why panelists repeatedly returned to standards, guardrails, and visible signals of legitimacy.
Trust starts with governance: clear rules for who can participate, how they are supervised, and what happens when incidents occur. Canada’s framework relies on accreditation and standardized APIs, with oversight led by the Bank of Canada. But governance must translate into user-facing confidence. A consumer deciding whether to authorize a payment initiation flow needs more than a policy document—they need cues that the provider is accredited and accountable.
Trust also depends on consistent security practices across the ecosystem. Deloitte’s reporting on rising fraud activity underscores the risk of uneven defenses: even if banks are strong, third parties vary in maturity, and attackers will target the weakest link. That makes baseline requirements—authentication, encryption, incident response—not optional features but ecosystem necessities.
Pay by Bank Trust Signals
A quick trust check for any payment initiation (“Pay by Bank”) experience:
– Accreditation is obvious: you can clearly see the provider is accredited (for example, via a recognizable label).
– Consent is specific: amount, payee, and whether it’s one-time vs recurring are clearly shown before approval.
– Authentication is strong: the bank’s sign-in/verification step is clear and doesn’t ask for credential sharing with third parties.
– Confirmation is unambiguous: you get a clear success/failure result and a reference you can save.
– Disputes have a path: the app tells you who to contact and what happens next if something goes wrong.
– Data sharing is minimal: only what’s needed for the payment is requested, and it’s clear how to revoke access.
Finally, trust is reinforced by reliability. Payment initiation must work predictably across institutions, with consistent consent flows and clear dispute pathways. If early implementations are fragmented or confusing, consumers may revert to familiar methods. The panel’s emphasis on standardization by a neutral body and on government guardrails reflects a recognition that trust is not a marketing problem—it is an infrastructure and accountability problem.
Navigating the Future of Payment Initiation in Canada
Canada’s move toward write access by 2027 sets the stage for a meaningful shift in how payments are initiated, authorized, and experienced. But the transition from “access” to “action” will not happen automatically. It will be built—through standards, supervision, infrastructure modernization, and products that prove their value in the real world.
The Road Ahead: Key Considerations for Stakeholders
For policymakers and regulators, the priority is maintaining momentum while ensuring operational readiness: standards must be stable, accreditation must be credible, and guardrails must be clear enough to support innovation without weakening consumer protection.
For banks, the challenge is twofold: modernize systems to support secure, high-availability APIs, and engage commercially in a model where payment initiation can be both safe and economically sustainable.
For fintechs and third-party providers, the opportunity is to design experiences that make payment initiation feel obviously better than existing options—while meeting stringent accreditation and security expectations.
Across all stakeholders, the dependency on Real-Time Rail remains central. If RTR timelines slip or integration is uneven, the “real-time” promise of payment initiation may be harder to deliver at scale.
Key Milestones to Watch Next
What to watch next (a practical roadmap as Canada moves toward write access):
1) Standards get finalized and stabilized (so teams can build once, not rebuild repeatedly).
2) Accreditation becomes operational at scale (clear entry requirements, predictable timelines, visible status).
3) Early write-access pilots prove reliability (consistent consent + confirmation across multiple institutions).
4) RTR milestones translate into user-visible speed (faster confirmation and settlement where applicable).
5) Accountability is tested in the real world (how disputes, errors, and fraud cases are handled end-to-end).
6) “Pay by Bank” earns repeat usage (not just first-time trials) through simpler UX and clear value for consumers and merchants.
Building Trust: The Role of Security and Standards
The Open Banking Expo Canada 2026 panel’s message was consistent: payment initiation is a major opportunity, but adoption will hinge on trust. That trust will be earned through standardized technical approaches, secure infrastructure, clear accountability, and visible accreditation signals at the moment of consent.
If Canada gets those elements right, payment initiation could become the practical engine of Consumer-Driven Banking—turning open banking from a data-sharing framework into a system that enables faster, more efficient, consumer-authorized payments across the economy.
This perspective is informed by Martin Weidemann’s work building and operating payment and fintech systems in regulated, multi-stakeholder environments, where standardization, accreditation, and user-visible trust signals often determine whether new payment rails reach real adoption.
This article reflects publicly available information at the time of writing on Canada’s Consumer-Driven Banking rollout, including stated targets and timelines. Launch dates, oversight arrangements, and rail readiness may change as standards and supporting infrastructure evolve. Where outcomes depend on Real-Time Rail and broader ecosystem implementation, real-world experiences may vary by institution and use case.
I am Martín Weidemann, a digital transformation consultant and founder of Weidemann.tech. I help businesses adapt to the digital age by optimizing processes and implementing innovative technologies. My goal is to transform businesses to be more efficient and competitive in today’s market.
LinkedIn

