Canada's Big Six banks (RBC, TD, BMO, Scotiabank, CIBC and National Bank of Canada) are jointly exploring a shared Canadian-dollar tokenized deposit infrastructure. The announcement came on September 22, 2026, twelve days after OSFI stated that tokenized deposits are not legally distinct from traditional deposits. For enterprise buyers, the significance is structural: tokenized deposits keep the legal protections, regulatory oversight and banking relationships treasurers already rely on, while adding the programmability and 24/7 movement of a distributed ledger. It is an exploration, not a launch. But it sets the terms on which corporate liquidity is likely to move on-chain in Canada.
What Was Actually Announced
Precision matters here, so start with what is confirmed.
- Participants: BMO, CIBC, National Bank of Canada, RBC, Scotiabank and TD. The banks expect to add other deposit-taking institutions "at the appropriate time."
- Scope: Canadian-dollar digital money, starting with tokenized deposits.
- Phase one: Moving tokenized deposits efficiently between Canadian financial institutions. This is an interbank use case, not a corporate or consumer wallet product.
- Longer-term goal: Connecting to other emerging digital asset initiatives.
- Status: The word that matters is exploring. The banks have not committed to issuing tokenized deposits, and no launch date, platform or technology vendor has been named.
Treat any claim that corporate clients can already settle on this network as premature. Enterprises should plan for it, not rely on it.
Tokenized Deposits vs. Stablecoins vs. CBDCs
The three terms get used interchangeably. They are different instruments with different risk profiles.
Why Treasurers Lean Toward Tokenized Deposits
Three reasons come up repeatedly.
- Established regulatory perimeter. A tokenized deposit is a bank deposit recorded on a different ledger. OSFI's position is that the technology does not change the legal nature of the product. Capital, liquidity and conduct rules continue to apply.
- Clearer recourse. The claim sits against a bank that is already inside your counterparty framework. With a stablecoin, you assess a separate issuer, its reserve assets and the mechanics of redemption. Canada's framework also bars stablecoin issuers from presenting their coins as deposits or as deposit-insured.
- No new systemic channel. Deposits stay on bank balance sheets. Large-scale migration into stablecoins is the scenario banks and regulators worry about, because it could pull funding out of the deposit base. Tokenized deposits avoid that shift.
Stablecoins are not going away. A regulated Canadian-dollar stablecoin has already launched, and several of the same banks are backing a US-dollar stablecoin issuer. The banks are pursuing both tracks. Treasurers should expect to use each where it fits.
The Power of Interoperability: The Shared Network Advantage
The most important word in the announcement after "exploring" is jointly. A tokenized deposit is only as useful as the number of counterparties that can accept it.
Eliminating Fragmentation
If each bank builds its own proprietary token on its own ledger, the result is a set of walled gardens. A token issued by one bank cannot move to another bank's ledger without a bridge, a reconciliation process or a third-party intermediary. That recreates the friction tokenization is meant to remove.
A shared framework addresses this at the design stage. Common standards for issuance, redemption, identity and messaging let deposits move across institutions without bespoke integration for every pair of banks.
Real-Time B2B Settlement: The Destination
The target state is straightforward. A corporate client at RBC pays a supplier at BMO or TD, and the transfer settles in real time, any day of the year, with no cut-off windows. Phase one does not deliver this directly to corporate clients, because it focuses on interbank movement. But interbank settlement is the prerequisite. Corporate-facing products depend on it.
Two related developments shape the timeline:
- Real-Time Rail. Payments Canada's phased launch of its real-time payments system is expected to begin this quarter. Tokenized deposits will need to coexist with it.
- Project Samara. In March, the Bank of Canada, RBC, TD and Export Development Canada settled a C$100 million tokenized bond using wholesale central bank deposits. It showed that central bank settlement against a ledger is technically feasible in Canada.
The Enterprise Value Proposition
If the network reaches corporate clients, three areas stand to change most.
Corporate Treasury and Liquidity
- Real-time liquidity visibility. Balances held as tokenized deposits can be queried and moved continuously, not only during banking hours. That narrows the gap between where cash sits and where it is needed.
- Automated intraday cash management. Rules-based sweeps can move funds between subsidiary accounts as thresholds are crossed, without a manual instruction cycle.
- Reduced trapped cash. Faster movement between entities shortens the time liquidity sits idle in transit or waiting for a settlement window.
Programmable B2B Payments
- Delivery-versus-payment. A smart contract releases payment only when delivery is confirmed, for example a verified shipment record or a custody transfer. Neither party carries settlement risk.
- Conditional supplier escrow. Funds are held and released automatically when contractual milestones are met, which removes manual verification and invoice-matching cycles.
- Multi-party revenue splits. One inbound payment can be divided across several recipients according to pre-agreed terms at the moment of settlement.
The benefit is not speed alone. Settlement logic becomes part of the payment, which shifts reconciliation work from after the fact to before it.
Cross-Border Efficiency
Phase one is domestic. Cross-border use is a longer-term goal, but the surrounding developments point in that direction. Several of the Big Six are participating in the BIS's Project Agorá, which tests tokenized commercial bank deposits alongside tokenized central bank reserves on a shared platform. Scotiabank and TD are among the 21 banks forming a joint US-dollar stablecoin issuer, targeted for the first half of 2027. If these efforts connect, international settlement could bypass some of the multi-day correspondent banking chain. Do not budget savings against this yet. The connections do not exist.
Technical, Compliance and Risk Realities: What to Audit
An honest assessment of readiness looks at friction as much as upside.
Legacy Systems Integration
Tokenized money is only useful to a treasury team if it appears inside the systems that run treasury.
- ERP and TMS connectivity. SAP, Oracle and your treasury management system need reliable API gateways to the bank's token layer. Map how balances, payment instructions, confirmations and statements will flow.
- Reconciliation. A token movement must match to a ledger entry, an invoice and a bank statement line. Confirm how on-chain events will be translated into the formats your finance systems already accept.
- Dual-rail operation. For years, you will run tokenized and conventional rails side by side. Plan for exception handling when a payment crosses between them.
Regulatory and Compliance Alignment
- OSFI. Tokenized deposits fall under the same prudential framework as traditional deposits. Your bank carries most of that burden, but you should understand how it affects product terms, limits and availability.
- AML and KYC. Existing reporting obligations apply regardless of the ledger. Ask how your bank will extend transaction monitoring, sanctions screening and the travel rule to token transfers, including transfers to counterparties at other banks.
- Accounting and legal treatment. Confirm with your auditors how tokenized deposits will be classified on the balance sheet, and with counsel how smart-contract-based payment conditions are treated under your contracts.
Operational Security
- Wallet and key governance. If your organization holds wallets, decide who controls keys, how signing authority maps to your delegation-of-authority matrix, and what recovery looks like.
- Smart contract access controls. Conditional payment logic is code. Define who can deploy, modify and approve it, and require independent review before production use.
- Segregation of duties. Preserve maker-checker controls on token transactions equivalent to those on wire approvals.
- Incident response. Extend your playbooks to cover key compromise and contract failure, and confirm where responsibility sits between your team and the bank.
Strategic Next Steps for Enterprises
- Conduct a treasury audit. Map where multi-party transactions slow down: settlement delays, cut-off times, trapped balances and manual verification steps. These are the places where tokenized deposits would add the most value.
- Establish a cross-functional task force. Bring treasury, IT and legal into one working group to evaluate digital asset exposure, integration requirements and control implications together, not in sequence.
- Initiate pilot conversations. Speak with your primary Canadian banks about their tokenization sandboxes and integration roadmaps. Ask about timing for corporate access, API standards and the controls they expect clients to run.
The Bottom Line
The Big Six have not yet decided to issue tokenized deposits, and they have not named a platform or timeline. What they have done is agree to design the infrastructure together, with a regulator that has confirmed these instruments are ordinary deposits in law. That combination points toward programmable commercial banking built on the relationships enterprises already hold.
The open questions are about design, sequencing and access. The direction itself is increasingly clear. For corporate liquidity, the question is no longer if it moves on-chain, but when and under whose controls. Teams that map their friction points and build the integration and governance groundwork now will be ready when corporate access opens.
