Door 02
Bank PaymentsArchitecture
Interac, RTR, Aani, ISO 20022, and a first hub slice. Prior roles at BMO and CIBC — not fazeZERO client case studies.
Positioning
How To Choose
Your SI will build it. They should not also write the target architecture they are measured against.
Prior work: BMO Real-Time Rail and ISO 20022 — hubs, Interac, fraud, liquidity, 24/7 operating standards. CIBC payments modernization toward cloud-native microservices. Not: we built RTR or Aani.
SKU-CA
Canada
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.
Interac RTR API Migration Readiness
The product stays e-Transfer. The pipe does not. Four weeks. CAD 160–220k.
Open pack →Native RTR Assessment Architecture
Direct-to-exchange, Interac-mediated, CSP, or hybrid — decided against your hub. CAD 180–250k.
Open pack →Payment Hub Cloud Target Architecture
Blueprint plus one named first slice. Not the migration. CAD 220–320k.
Open pack →SKU-AE
GCC / UAE
Choose Aani if you are already connected and the bank-side path is still thin. Multi-rail if several rails are landing on one hub. Hub architecture only after the rail path is named.
Aani Production Operating Model
Connected is not production-grade. Four weeks. AED 450–700k.
Open pack →Multi-Rail + ISO 20022 Assessment
Aani, UAEFTS, SWIFT, AFAQ and Buna on one hub. AED 500–750k.
Open pack →Payment Hub Target Architecture
Blueprint plus one named first slice. Not the migration. AED 600–850k.
Open pack →Commercial
Shared Terms
- 50% on signature to start. Remainder on delivery.
- One named path or first slice in the agreement.
- Further implementation is optional and only after the pack is paid.
Next Step
Book A Strategy Call
Name the institution and whether the question is Interac, native RTR, Aani, multi-rail, or hub first-slice.
Stay in the loop
Subscribe for updates on stablecoin payments, tokenization, and regulated digital-asset infrastructure.