Accept Interac e-Transfer alongside cards on one payment gateway.
Interac e-Transfer is the pay-by-bank method Canadian shoppers reach for at checkout. On BazPay it sits behind the same REST API call as cards and wallets — one charge object, one signed webhook, one settlement surface. The shopper approves inside their own online banking; the confirmation lands in seconds.
Built for merchants across the EU, UK, Australia, Canada and New Zealand selling into Canada: e-commerce, subscription software, professional services and digital publishers. Add Interac e-Transfer from the dashboard, not through a separate onboarding.
Why merchants add the Interac e-Transfer payment method alongside cards
Interac e-Transfer is not a rounding-error method for a merchant serving Canada — it is often the first-choice payment for Canadian shoppers online. Four properties keep the integration light and the reconciliation clean.
-
First-class method, not a redirect afterthought
Interac e-Transfer sits behind the same REST API call as cards, wallets and other local APMs. One charge object, one signed webhook envelope, one reporting surface — Canadian checkout is not a separate integration to maintain.
-
Near-instant confirmation from the shopper's bank
The shopper approves the request inside their own online banking. The confirmation reaches BazPay in seconds and fires the same charge.succeeded webhook your fulfilment stack already listens for.
-
Low chargeback exposure on Interac e-Transfer
Because Interac e-Transfer is authenticated inside the shopper's own bank, cardholder-dispute chargebacks do not apply. Refunds go through the merchant. That is why Interac e-Transfer often sits alongside cards for higher-ticket Canadian orders.
-
Reconciles with your other BazPay volume
Interac e-Transfer settlement lines appear on the same statement as card and other APM lines, keyed by rail. Finance teams do not open a second portal to close the book on Canadian traffic.
The Interac e-Transfer payment flow, end to end
Six stages describe a single Interac e-Transfer payment from checkout to settled cycle. The confirmation stage fires the same signed webhook your card flow uses.
-
Shopper picks Interac e-Transfer
Interac e-Transfer appears alongside card and wallet options in your checkout — hosted page, hosted fields or REST API.
-
Give the handle
The shopper enters the email address or mobile number registered with their bank for Interac — no card details, no redirect.
-
Request for Money
The charge is submitted and Interac delivers a Request for Money into the shopper's online or mobile banking.
-
Approve in banking
The shopper signs in to their own bank and approves the request. Interac confirms the payment to BazPay.
-
Webhook fires
BazPay fires a signed charge.succeeded webhook to your fulfilment endpoint — the same event handler cards use.
-
Settle
Funds reconcile per Interac e-Transfer settlement cycle and land in your merchant balance for payout to your local settlement account.
Interac e-Transfer vs a card payment on the same Canadian order
Interac e-Transfer and cards do different things well. Most Canadian checkouts show both and let the shopper decide. The comparison below shows where each earns its place.
| Dimension | Interac e-Transfer | Card + 3-D Secure 2 |
|---|---|---|
| Authentication | Online banking sign-in | Card + 3-D Secure 2 challenge on risk |
| Shopper input | Email or mobile, then a bank sign-in | Card details + optional 3-D Secure challenge |
| Confirmation | Near-instant, bank-driven | Authorisation code from issuer |
| Chargeback exposure | No cardholder-dispute chargebacks | Cardholder dispute rights apply |
| Currency | CAD (Canadian market) | Multi-currency presentment |
| Fits best for | Canadian checkout, small and large tickets | International traffic, subscription renewals |
Card-side detail on card and APM processing. Adjacent local method: iDEAL payments. Wider bank-rail coverage on Faster Payments. Bank-rail context on Single Euro Payments Area processing.
Features that ship with Interac e-Transfer out of the box
Every capability below is on the standard integration — no premium tier for Interac e-Transfer, and no separate SDK. If it works for cards on BazPay, it works for Interac e-Transfer charges too.
-
One charge object
Set
payment_method: "interac"on the charge request. Everything else stays the same as a card charge; Interac e-Transfer is not a bolt-on SDK. -
Handle input UI
The hosted checkout and drop-in JS render the email or mobile field automatically. Custom integrations pass the registered handle through the API as a single field on the charge.
-
charge.succeeded webhook
The same signed HMAC event that fires for a card success fires for an Interac e-Transfer success — one fulfilment handler covers both methods.
-
Refunds
Full and partial refunds initiate from the API or dashboard and return to the shopper as a new Interac e-Transfer initiated from BazPay.
-
Real-time analytics
Approval, cancellation and expiry outcomes on Interac e-Transfer appear in real-time analytics alongside card decline codes for the same order.
-
Metadata propagation
SKU, order and buyer references on the charge metadata ride through to settlement and refund events, so reconciliation stays SKU-level per Interac e-Transfer payment.
-
Plugin support
Maintained plugins for WooCommerce, Magento 2, PrestaShop and Shopware expose Interac e-Transfer alongside cards with a single configuration screen.
-
CAD-native flow
Interac e-Transfer is a CAD method — the shopper sees a CAD amount without cross-currency confusion, and the transaction stays within the domestic Canadian rails.
Create an Interac e-Transfer charge with one REST call
The payment_method field selects Interac e-Transfer. Pass amount and currency (CAD for
Interac e-Transfer) along with the email or mobile handle the shopper registered with their bank. The
response returns a canonical charge object with the pending status; the signed webhook
fires once the bank confirms.
POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
"amount": 12900,
"currency": "CAD",
"payment_method": "interac",
"interac_msisdn": "254712345678",
"return_url": "https://your-shop.example/checkout/return",
"metadata": { "order_id": "ORD-10842" }
}
The response returns the charge with status: "requires_action". Once the
shopper approves in their online banking, the status moves to
succeeded and the webhook fires. Full schema in the
API reference.
Where Interac e-Transfer earns its place at checkout
The four merchant profiles below already rely on Interac e-Transfer on BazPay for the Canadian part of their traffic. Each uses the same charge object and the same signed webhook.
-
Canadian e-commerce storefronts
DTC brands selling into Canada add Interac e-Transfer as the primary local method alongside card and Apple Pay. Storefront plugins ship with the bank-redirect input already wired in.
-
Digital-goods sellers
Software licences, courses and downloadable content use Interac e-Transfer for Canadian buyers; the near-instant confirmation triggers the fulfilment webhook in seconds.
-
Higher-ticket B2B invoicing
Professional-services vendors invoicing Canadian clients use Interac e-Transfer where card chargeback exposure on a large order is a concern — Interac e-Transfer is bank-authenticated per charge.
-
Events and ticketing
Ticketing platforms with a Canadian audience surface Interac e-Transfer first for the fastest completion path — the bank-redirect flow is familiar to Canadian shoppers.
Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM.
Security and compliance signals for Interac e-Transfer processing
Interac e-Transfer is a bank-authenticated method — the shopper approves the payment inside their own bank, so no card data is collected for Interac e-Transfer charges. That keeps the attack surface for Interac e-Transfer narrow by construction. PCI DSS Level 1 covers BazPay's broader environment; Authentication runs natively inside the shopper's bank for Interac e-Transfer and through 3-D Secure 2.2 for cards.
- Interac e-Transfer scheme adherence
- Bank-authenticated flow, no card data collected for Interac e-Transfer charges
- Authentication
- Native strong customer authentication runs inside the shopper's own bank
- GDPR
- In-region data residency; DPA on request
- PCI DSS Level 1
- Covers BazPay's broader environment where cards are also processed
Questions merchants ask about accepting Interac e-Transfer
What is Interac e-Transfer, and where does the Interac e-Transfer payment method work?
Interac e-Transfer is the Canadian pay-by-bank method operated by Interac. The shopper gives the email address or mobile number registered with their bank, then approves the request inside their own online banking. Interac e-Transfer is CAD-denominated and works primarily inside Canada, where it is one of the most-used online payment methods.
How do I accept Interac e-Transfer payments on BazPay?
Set payment_method: "interac" on the standard charge request, or enable Interac e-Transfer in your hosted checkout or storefront plugin. The hosted surface renders the mobile-number field automatically; custom integrations submit the code through the API. Fulfilment listens to the same signed charge.succeeded webhook that cards use.
How fast is confirmation on an Interac e-Transfer payment?
The shopper approves the request inside their own online banking and the confirmation reaches BazPay within seconds. Your charge.succeeded webhook fires immediately after — treat Interac e-Transfer as a near-instant method for release-of-goods and licence fulfilment.
Is there a separate Interac e-Transfer payment app I need to install as a merchant?
No. Interac e-Transfer is not a separate merchant app — the approval proquest is delivered by Interac into the shopper's own online banking, not something a merchant installs. On the BazPay side, everything is a REST API call, a hosted checkout or a storefront plugin — the same shape as any other payment method on the platform.
Does Interac e-Transfer payment Deutschland work? Can New Zealand shoppers pay with Interac e-Transfer?
Interac e-Transfer availability outside Canada depends on the Interac e-Transfer scheme's cross-border rollout and on which banks abroad have joined the scheme. As Interac e-Transfer expands into markets such as New Zealand, merchant coverage grows with it. What BazPay guarantees today is Interac e-Transfer acceptance for shoppers whose banks participate; specific corridor and market availability is confirmed during boarding.
How do refunds work for Interac e-Transfer payments?
Refunds are issued via the API or dashboard and return to the shopper as a new Interac e-Transfer initiated from BazPay. Full and partial refunds are supported; the refund event fires a signed webhook so your fulfilment stack can revoke the entitlement in the same handler that processes card refunds.
How does Interac e-Transfer compare with a card payment on the same Canadian order?
Interac e-Transfer is approved inside the shopper's own bank, so there are no cardholder-dispute chargebacks — refunds go through the merchant directly. Cards work internationally and support saved-card renewals; Interac e-Transfer is CAD-first and Canada-focused but wins on chargeback exposure and completion speed for Canadian shoppers. Most Canadian checkouts offer both and let the shopper pick.
Which merchant types can accept Interac e-Transfer through BazPay?
Merchants across the EU, UK, Australia, Canada and New Zealand: e-commerce sellers, subscription software firms, professional-services businesses and digital publishers. BazPay does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants, and does not act as a merchant of record.
Add Interac e-Transfer to your Canadian checkout on one contract
Share your business model, monthly Canadian volume and existing stack. A named engineer will confirm boarding fit and turn Interac e-Transfer on alongside cards inside one working day. See also merchant acquiring, SEPA and SEPA Instant and pricing.