SKU-CA-01 · Canada

Interac RTR API Migration Readiness

CAD 160,000–220,000 fixed. 50% on signature to start. Remainder on delivery. 4 weeks. One named Interac connection path, not a hub transformation. Zoom this week. Onsite in Toronto by arrangement.

Book a Strategy Call All services

Engagement

For a Head of Payments, Interac product owner, or payments architect at a Canadian FI already live on Interac e-Transfer. One connection path. Not a Payments Canada filing.

The product stays e-Transfer. The pipe does not. Four weeks. One named connection path. CAD 160,000–220,000 fixed. 50% on signature to start.

Scope

What “one Connection Path” Means

Current Interac e-Transfer adapter → ISO 20022 / Interac API uplift → hub → fraud and AML → customer channel unchanged → exception handling → evidence retained.

Legacy XML/SOAP is being sunset; e-Transfer volume begins clearing and settling on the Real-Time Rail from the Q1 2027 migration wave. Autodeposit, Request Money, and commercial limits stay.

What You Get

Deliverables

RACI + to-be map of the named Interac path
Dual-control design for irrevocable 24/7 items
Control matrix with owners and evidence
Exception route when an ISO message fails or credit is not available in 60 seconds
Test-readiness pack and 90-day path
Executive readout

Not Included

Out Of Scope

Building or operating the RTR Exchange
Acting as Interac, a CSP, or a Payments Canada delivery partner
Rewriting the Interac adapter or running Interac certification
Filing membership or a Bank of Canada settlement account
Changing the customer e-Transfer experience
A wave-1 promise

Timeline

How The Weeks Run

Week 1

Name the connection path. As-is map of the current Interac API version and message flow.

Week 2

Gap to the RTR-era Interac interface. Dual-control and exception design.

Week 3

Control matrix, evidence design, test-readiness pack.

Week 4

90-day path, test checklist, executive readout.

Prerequisites

What We Need From You

Named owner across payments ops, Interac product, fraud, and architecture
Current Interac interface version and sequence diagrams — under NDA
No production admin or keys
Decision-maker in kick-off and readout

Further implementation is optional and only after this engagement is paid. Native RTR and hub first-slice are separate engagements.

Counsel-Forwardable

Fence

Not Interac. Not Payments Canada. Not the SI. No keys. No 2 a.m. seat.

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 — hubs, Interac, fraud, liquidity, 24/7 NFRs. Not: we built RTR.

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

We Already Have Interac. Why Do We Need This?

The customer product stays. The connection does not. The gap is the operating model around the new interface.

Central 1 / Our Processor Says They Will Connect For Us.

They own their pipe. You still own the bank-side path: hub, fraud, exceptions, evidence, and 24/7 ops.

Can You Do Native RTR In The Same Fee?

No. That is a separate engagement — Native RTR Assessment.

Will This Get Us Into Wave 1?

No. Wave membership is yours and Payments Canada’s.

Next Step

Check Fit

Name the institution and the Interac connection path.