SKU-CA-03 · Canada

Payment Hub Cloud Target Architecture

CAD 220,000–320,000 fixed. 50% on signature to start. Remainder on delivery. 5–6 weeks. One named first slice, not a hub cutover. Zoom this week. Onsite in Toronto by arrangement.

Book a Strategy Call All services

Engagement

For a payments platform owner whose hub is still on-prem and who already has a cloud programme elsewhere. Not the multi-year SI.

24/7 is the constraint. A batch on-prem hub does not become a 10-second exchange by lift-and-shift. Five to six weeks. One named first slice. CAD 220,000–320,000 fixed.

Scope

When This Is The Right Next Step

Choose Interac RTR if e-Transfer is live and the connection is changing. Choose Native RTR if you still need to decide how to participate. This pack is the hub first-slice — only after that path is named.

We will not start until the first slice is named in the agreement.

Path

Pick One Path

Named in the agreement.

Interac send/receive adapter in front of the existing hub
ISO 20022 translation service for the named rail
24/7 heartbeat and ops plane for the named rail

What You Get

Deliverables

Current-state hub map
Target cloud-native / microservices architecture in front of the existing hub
Strangler sequence — what moves first, what stays, what never moves
NFR and audit bar
Interface contract and control matrix for the named slice only
90-day path for the slice, executive readout

Not Included

Out Of Scope

Migrating the payment hub
Standing up the cloud landing zone
Building the bank’s CI/CD factory
Replacing IBM, CGI, Accenture, or the incumbent SI
Running 24/7 production

Timeline

How The Weeks Run

Week 1

Name the slice. Current-state hub map.

Week 2

Target architecture. What sits in front of the hub.

Week 3

Strangler sequence. NFR bar. Dual-control on the slice.

Week 4

Interface contract and control matrix.

Week 5–6

90-day path. Executive readout.

Prerequisites

What We Need From You

Named platform owner across architecture, hub ops, cloud, and change
Current hub diagram and cloud-programme constraints — under NDA
The first slice named before week 1 ends. If we cannot name it, we stop.

We do not become the migration factory by default. A slice build is a separate engagement after this pack is paid.

Counsel-Forwardable

Fence

If a sentence sounds like we migrate the hub, cut over production, or replace the SI, it is out.

Credibility

Prior Work

Prior roles. Not fazeZERO client case studies.

CIBC Capital Markets — payments and FX platform modernization toward cloud-native / microservices without breaking BCP.
BMO Real-Time Rail and ISO 20022 — target architecture across hubs, Interac, fraud, liquidity, 24/7 NFRs.

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

Just Move The Hub To Azure.

That is a multi-year SI. This offer is the blueprint and one slice.

We Have Not Chosen Interac Vs Native Yet.

Then this is not the right pack yet. See Native RTR Assessment.

Will You Replace Our SI?

No.

Next Step

Check Fit

Name the institution, the hub, and the first slice you think is first. We will confirm or shrink it.