We Already Decided Interac-Only.
Then this is not the right pack. See Interac RTR API Migration.
SKU-CA-02 · Canada
Native RTR Assessment Architecture
CAD 180,000–250,000 fixed. 50% on signature to start. Remainder on delivery. 4 weeks. One participation question, not an Exchange implementation. Zoom this week. Onsite in Toronto by arrangement.
Engagement
For payments architecture, treasury, and operational risk at a Schedule I or mid-tier Canadian bank. One decision pack. Not a build. Not a wave-1 promise.
Direct-to-exchange, Interac-mediated, CSP, or hybrid — decided against your hub, not a slide. Four weeks. CAD 180,000–250,000 fixed.
Scope
The Question This Engagement Answers
Do we connect native to the RTR Exchange, stay on Interac e-Transfer as product and pipe, use a Connection Service Provider, or run a hybrid — and what does that do to hub, liquidity, fraud, and 24/7 operations?
Native means RTR Exchange APIs and ISO 20022 messages (pacs.008, pacs.002, pacs.028, heartbeat), funds available within 60 seconds, 24/7/365, and a settlement-account model if you settle direct.
What You Get
Deliverables
- Options paper — native / Interac-only / CSP / hybrid — tied to your hub
- ISO 20022 impact on the named first workflow
- Settlement-account and liquidity stub
- 24/7 operating-model stub
- Fraud-service handoff and NFR / audit bar
- One recommended first workflow, 90-day path, executive readout
Not Included
Out Of Scope
- Building the VPN, API, or adapter
- Filing Payments Canada membership
- Opening a Bank of Canada settlement account
- A guarantee you will be in wave 1
- Rewriting the hub
Timeline
How The Weeks Run
01
Week 1
Current participation and hub map. Decision criteria with architecture, treasury, and ops risk.
02
Week 2
Options paper. ISO impact. Liquidity and 24/7 stubs.
03
Week 3
Recommended path. Control matrix on the first workflow.
04
Week 4
90-day path. Executive readout.
Prerequisites
What We Need From You
- Named owner across architecture, treasury, ops risk, and fraud
- Current hub diagram and any RTR steering paper — under NDA
- Decision-maker in kick-off and readout
Next
After This Engagement
- Interac RTR readiness and hub first-slice are separate engagements. They are not bundled.
Counsel-Forwardable
Fence
- If a sentence sounds like we build the RTR, file membership, or get you into a wave, it is out.
Credibility
Prior Work
Prior roles. Not fazeZERO client case studies.
- Owned target architecture and modernization roadmaps for BMO’s Real-Time Rail and ISO 20022 programs — Payments Canada connectivity, Interac, hubs, fraud, liquidity, 24/7 NFRs, audit.
- Not: we built the RTR. IBM, CGI, Interac and Deloitte are the delivery partners.
Related Packs
Sequence
Choose Interac RTR if e-Transfer is live and the connection is changing. Native RTR if you still need to decide how to participate. Hub architecture only after that path is named.
Questions
FAQ
Will This Get Us Into Wave 1?
No. We leave you able to show the option and the gaps.
Can You Also Write The Exchange Adapter?
No. That is implementation after this pack is paid.
Next Step
Check Fit
Name the institution and whether the question is send, receive, or both.
Stay in the loop
Subscribe for updates on stablecoin payments, tokenization, and regulated digital-asset infrastructure.