Concept · What could come next

Canada's Real-Time Rail.
Fast payments, not atomic settlement.

Payments Canada’s RTR is the real-time payments rail Canadian banks have been waiting for. ISO 20022 messaging, 24/7/365 availability, settlement on Bank of Canada money. But it moves cash only, not assets, and it does not embed compliance at the rail. Here is what it looks like, end to end, and where the honest gap sits.

~3 seconds end to end ISO 20022 over RTR BoC settlement asset, real-time Payments Canada operated Payments only, no DvP
End-to-end speed
~3sec
submit to credit, every payment
Availability
24/7/365
no batch cut-off, no overnight window
Settlement asset
BoC money
central-bank money, same as Lynx
Messaging standard
ISO 20022
structured data with every payment
Where RTR ends, and where 4orm begins
5 gapsstructural
RTR is cash-only — no asset leg, no DvP atomicity, no compliance at the rail, no canonical multi-party ledger, and no cross-border. These structural gaps stand whatever the per-transaction ceiling. Today the rail also carries a C$100,000 per-transaction maximum (institutions may cap lower) — useful supporting detail, but the gaps above are the real distinction.
✓
Retail payments fit. Peer-to-peer, payroll, e-commerce, small B2B.
< C$100K
✕
Institutional settlement does not. Wholesale, securities DvP, M&A, tokenized assets.
C$1M–C$1B+
RTR · Concept diagram · Canadian interbank payment
Live · 24/7/365
Gold coin · cash leg moving A → B MBlue packet · ISO 20022 message (pacs.008, camt.054) ✓Green ack · confirmation flowing B → A Pulsing dot · station active, message in flight
What RTR doesn’t carry
✕ASSETS ✕SECURITIES (DVP) ✕COMPLIANCE AT RAIL ✕CROSS-BORDER ✕CANONICAL LEDGER ✕> C$100K
Real-Time Rail end-to-end payment flow TOP BAND · BANK OF CANADA SETTLEMENT ASSET Real-time settlement in central-bank money. The rail’s final settlement layer. Bank of Canada Final settlement on central-bank money · instant SETTLES ON MIDDLE BAND · THE RTR RAIL · PAYMENTS CANADA ISO 20022 messaging · real-time clearing · 24/7/365 · cash only, no asset leg. API · ISO 20022 OVER RTR RAIL CAP · C$100K PER TRANSACTION · INSTITUTIONS MAY SET LOWER 01 Submit Bank A → RTR via ISO 20022 02 Validate Message + account checks 03 Clear Real-time clearing · BoC settles ✓ FINAL · IRREVOCABLE 04 Notify Confirmation to Bank B 05 Credit Bank B credits Customer B $ $ $ $ $ pacs.008 camt.054 pacs.002 ✓ ACK ✓ ACK 0.0s submission ~0.4s validated ~1.2s cleared at BoC ~2.0s Bank B notified ~3.0s credit posted BOTTOM BAND · CUSTOMER EXPERIENCE · END-TO-END Customer A taps Send. Customer B sees the credit before Customer A puts their phone away. BANK A · SENDER Customer A account debit posts at submission CHANNEL: APP · ONLINE · BRANCH BANK B · RECEIVER Customer B account credit posts in seconds SAME UX · FASTER WHAT THE CUSTOMER ACTUALLY SEES Same screens. Faster confirmation. No new app. No new login. The transfer that took hours now takes seconds. Money is gone from A in 0.4s, lands at B in ~3s. Same channels, same UX. CASH MOVES IN ~3 SECONDS · SAME CHANNELS · CENTRAL-BANK MONEY NO ASSET LEG · NO DVP · NO ATOMIC SETTLEMENT
Click for index · what every colour, shape, and badge above means
Index · what every colour and shape means above
Moving elements (the animations)
Gold coin Cash leg flowing Bank A → rail → Bank B
Green coin Retail-scale payment (under the C$100K cap)
Blue coin Standard payment in flight along the rail
M Blue packet ISO 20022 message: pacs.008, camt.054, pacs.002
✓ Green packet Acknowledgment / confirmation flowing B → A
Pulsing dot Station active · message currently in flight
Static elements (positions · states · badges)
Gold band Bank of Canada settlement asset layer
Blue band RTR rail itself (Payments Canada operated)
Gray band Customer experience layer (Bank A and Bank B)
✓ FINAL Green badge BoC clearing = legal, irrevocable settlement finality
C$100K CAP Gold pill Per-transaction cap at launch · the hard ceiling
Where RTR lives, where it doesn’t

Same rail, two very different jobs. One fits. One doesn’t.

RTR was designed for retail-scale, cash-only, domestic payments. Inside that lane it is excellent. Outside that lane — institutional, securities, tokenized assets, cross-border — it does not have a story. That is the rail 4orm is being built to operate.

Fits on RTR

Retail-scale, cash-only, domestic payments.

  • Peer-to-peer transfers · Interac-replacement use cases
  • Retail bill pay · utilities, telco, subscriptions
  • Payroll under the cap · weekly/biweekly direct deposit
  • E-commerce checkout · merchant settlement same day
  • Small B2B · supplier payments under C$100K
Does not fit on RTR

Institutional settlement, securities, tokenized assets, cross-border.

  • Institutional cash transfers · anything over the C$100K cap
  • Securities DvP · no asset leg on the rail at all
  • Tokenized real-world assets · bonds, real estate, GICs, T-bills
  • M&A escrow + conditional release · no programmability
  • Cross-border · RTR is domestic Canadian only
  • Canonical multi-party ledger · each bank still keeps its own books
What RTR is

Real-time payments, 24/7/365, in central-bank money.

  • Speed: end-to-end credit in about 3 seconds, not T+1 / T+2.
  • Settlement asset: Bank of Canada money, the same settlement asset as Lynx.
  • Messaging: ISO 20022, so structured data travels with the payment.
  • Availability: 24/7/365, no batch cut-off, no overnight window.
  • Reach: every connected Canadian deposit-taker, instantly.
What RTR is not

Faster payments, not atomic delivery-versus-payment.

  • No asset leg: RTR moves cash. It does not settle tokenized bonds, real estate, or any asset against the cash leg in one instruction.
  • No embedded compliance: KYC, AML, sanctions, and accreditation are still each bank’s own job at the edge.
  • No canonical record across banks: Bank A and Bank B still keep their own ledgers and file their own reports.
  • No cross-border: RTR is domestic Canadian. Cross-border still rides correspondent rails or Lynx + SWIFT.
  • Faster does not mean atomic: a fast payment that fails halfway is still a broken settlement.
The gap · what is still missing once RTR launches

RTR solves the payment-speed problem. It does not solve the settlement-risk problem for tokenized assets.

RTR makes cash move in seconds. But for tokenized real-world assets, settlement is a three-signal event: treasury confirmation, custody confirmation, and canonical ledger commitment, all together or none. RTR delivers one of those three, the cash. The asset leg, the custody confirmation, and the canonical write still need a rail that can do them atomically with the cash.

That is the rail 4orm is being built to operate. RTR is the cash side. 4orm composes it with the asset side, custody, and the canonical ledger into a single atomic settlement event. When RTR launches, 4orm becomes the overlay that turns a fast payment into a complete institutional settlement.

Where 4orm sits

RTR delivers the cash. 4orm composes everything else.

RTR is one of three legs an institutional settlement needs. When 4orm sits on top of RTR, the fast payment becomes a complete atomic settlement event — cash, asset, custody, and canonical ledger, all in one instruction.

RTR delivers

The cash leg, in seconds.

  • Real-time cash transfer, ~3 seconds
  • ISO 20022 messaging
  • BoC settlement asset
  • 24/7/365 availability
  • Domestic Canadian reach
+
4orm adds on top

Everything else needed for atomic institutional settlement.

  • Asset leg · tokenized bonds, real estate, securities
  • Custody confirmation · written into the same event
  • Canonical ledger · one record across both banks
  • Embedded compliance · KYC, AML, sanctions at the rail
  • Atomic guarantee · all legs, or none
Together they deliver
A complete institutional settlement event — cash, asset, custody, and canonical ledger — in one atomic instruction, settled on central-bank money in seconds.

Concept diagram for discussion. Real-Time Rail is operated by Payments Canada; build completed Q3 2025, launch slipped to 2026 to 2027. ISO 20022 messaging, BoC settlement asset. Not yet live. Figures and station naming illustrative; not a Payments Canada or 4orm product specification.