Six banks exploring a common approach to digital money deserve attention. It does not justify pretending the future has already shipped.
On September 22, BMO, CIBC, National Bank, RBC, Scotiabank, and TD announced that they are jointly exploring Canadian-dollar digital-money solutions, beginning with tokenized deposits. Their first-phase ambition is to move tokenized deposits efficiently between Canadian financial institutions, with connections to other digital-asset initiatives as a longer-term goal (joint announcement).
For banking and lending executives, the useful question is what to prepare, not what to announce. Start with the operational handoffs that determine whether money can move safely.
The banks frame the initiative around faster, more efficient, and programmable payments, while preserving safety, stability, and regulatory oversight, according to the release. They anticipate including other deposit-taking institutions at the appropriate time; they have not announced open access, a production date, or a selected technology platform.
Those boundaries matter. A shared exploration is a strategic signal; it is not evidence that a lender can begin funding mortgages through a new network next Monday.
Nor should an institution assume the initiative requires replacing its core. The announcement leaves the technical design unspecified, so any claim about a particular architecture would be premature given the published facts.
Consider a hypothetical mortgage ready for disbursement except for one unresolved funding condition. A more capable payment mechanism would not make that condition disappear; it would make the quality of the release decision more consequential.
The same test applies to an incorrect destination account, a duplicate instruction or a mismatch between a payment record and the loan ledger. These are the scenarios to examine before celebrating a shorter settlement path.
That is the operational case for “Policy is the moat.” Translate conditions into explicit permissions, escalation paths, and evidence requirements. The relevant question is not simply whether an instruction can execute; it is whether the institution can explain why it was allowed to execute.
A beautiful transaction flow with an undocumented override is still an undocumented override. A better presentation does not improve the control.
Begin with a map of one real workflow. Identify the source of truth for the borrower, loan status, funding conditions, destination details, and payment outcome.
The map should expose ownership, not just system names. Who resolves a mismatch? Which record controls when two systems disagree? What evidence marks the payment as complete?
Use that map to separate necessary modernization from unnecessary replacement. An existing system may remain useful if it can expose the right state, accept the right events and maintain a reliable audit trail. Test that proposition before declaring the entire stack obsolete.
For smaller institutions, participation diligence should run in parallel with technical work. Ask how access could be structured, which operational responsibilities would remain with the institution, and what service commitments would be required. These are questions for a future arrangement, not terms already promised by the participating banks.
Before moving real funds, consider creating a controlled representation of the selected workflow. Test a completed file, an unresolved condition, a duplicate request, a failed confirmation, and a recovery path.
Use synthetic or appropriately protected data wherever possible. The objective is to understand how decisions and instructions interact, not to assemble a larger pool of sensitive borrower information.
For this exercise, define success in operational terms: no release before required approvals, no silent duplication, a recoverable failure, and a traceable reconciliation. These are proposed test criteria, not claimed capabilities of the banks' initiative.
Ask your technology, treasury, lending and risk leaders to review the same workflow together. Give them a concrete deliverable: the controls that must remain true regardless of the payment mechanism.
The bank announcement identifies an intention to explore more efficient, programmable payments (joint announcement). Your institution does not need to invent a launch date to take that seriously.
Prepare the handoffs. The token will not fix them for you.
No production launch is announced in the September 22 release. The banks say they are exploring development, beginning with tokenized deposits moving between Canadian financial institutions (joint announcement).
The participating banks anticipate including other deposit-taking institutions “at the appropriate time.” The announcement does not publish eligibility criteria, commercial terms or a participation timetable (joint announcement).
The announcement does not specify a technical platform or require a core replacement (joint announcement). A sensible first step is to assess existing integration, authorization, and reconciliation capabilities before deciding what needs to change.
Map the conditions that must be satisfied before releasing funds, then test how those conditions travel across systems. Focus on accountable decisions and exception handling rather than treating a payment innovation as an underwriting shortcut.