Interac E-Transfer

How do I deposit, withdraw, request, or send CAD via Interac E-Transfer?

Deposit and withdraw CAD using the Interac E-Transfer instant rail. This guide covers deposits and withdrawals for the customer, requesting money from or sending money to a counterparty, and requesting or sending through a customer-owned Interac e-Transfer external bank account. Requests from and sends to a counterparty are restricted: they are not part of a standard remittance flow and require additional due diligence and explicit compliance approval from Cybrid before production use. See Request money from a counterparty.

ℹ️

Availability

Interac E-Transfer is only available to Canadian banks on the Cybrid Platform and only works with CAD on CAD-based fiat accounts.

ℹ️

Plans and executions

Where plans and executions are enabled, you deposit and withdraw over Interac e-Transfer with a deposit or withdrawal plan instead of a quote and transfer. See the CA Remittance Integration Guide and Migrate to Plans and Executions.

Prerequisites

  • A customer already created and verified
  • A CAD fiat account created for the customer
  • A main deposit bank account in state: created for that fiat account, required for deposits and withdrawals on any customer fiat account. See Customer Deposit Bank Accounts
  • For withdrawals only:
    • The customer's identity record populated with an email address or phone number — a withdrawal to the customer is routed using this contact information
    • A security question and answer that the recipient must answer to claim the funds
  • For requests and sends through an external bank account only: an Interac e-Transfer external bank account in the completed state, created on API version 2026-09-01, owned by either a verified counterparty of the customer or the customer. See Interac e-Transfer accounts and Use a customer-owned Interac e-Transfer account.
    • For a counterparty-owned account: explicit compliance approval from Cybrid to use counterparty requests and sends in production
    • For sends, the customer's identity record must have an email address or phone number, and any email address must be valid: the customer is the originator of the e-transfer, even though the recipient comes from the external bank account
⚠️

Sandbox behavior

In sandbox, Interac E-Transfer deposits complete automatically and the gateway_url returned is not a valid URL. Requests and sends through an Interac e-Transfer external bank account also complete automatically, and failures cannot be simulated. See Sandbox transfers for full sandbox-specific behavior.

Transaction screening and PII shared with banking partner

During Interac E-Transfer transactions, the following details are sent to Cybrid's banking partner:

  • Deposits and withdrawals without an external bank account: the customer's name, email address, phone number, and address
  • Requests through an external bank account: the customer's name, and the email address and phone number on the external bank account
  • Sends through an external bank account: the customer's name, email address, phone number, and address, and the account holder's name with the email address and phone number on the external bank account

Cybrid performs its own checks, and the banking partner and Interac may also run their own screening. A transfer may be rejected for reasons such as risk scoring, sanctions screening, AML compliance checks, or other financial-institution deny-list restrictions. Cybrid does not control or have visibility into the specific reason Interac or the banking partner may reject a transfer.

Deposit flow

The deposit process involves four steps:

  1. Create a funding quote
  2. Execute a transfer with payment_rail set to etransfer
  3. Display the gateway_url so the customer can authorize the payment
  4. Wait for the transfer to transition to completed

Step 1: Create a funding quote

{
  "product_type": "funding",
  "customer_guid": "customer_guid",
  "asset": "CAD",
  "side": "deposit",
  "deliver_amount": 10000
}
ℹ️

deliver_amount vs receive_amount

deliver_amount fixes what you send; fees come out of what the recipient gets. receive_amount fixes what the recipient gets; you pay fees on top. See Create and execute a trade for the canonical explanation.

Step 2: Execute the transfer

Create the transfer with transfer_type set to funding and payment_rail set to etransfer. The quote_guid is the guid from Step 1.

{
  "quote_guid": "quote_guid",
  "transfer_type": "funding",
  "payment_rail": "etransfer",
  "source_participants": [
    {"type": "customer", "guid": "customer_guid", "amount": 10000}
  ],
  "destination_participants": [
    {"type": "customer", "guid": "customer_guid", "amount": 10000}
  ]
}

Step 3: Display the gateway URL

ℹ️

Domain allowlisting

The gateway_url uses the domain etransfer.interac.ca. Allowlist this domain if needed.

⚠️

Asynchronous processing

Generating the gateway_url can take time in both sandbox and production due to sponsor bank response times. Handle asynchronous calls using webhook registration and polling as a backup.

Wait for the transfer to transition to the pending state. Once pending, read the gateway_url from the identifiers array on the transfer. The identifier has type set to gateway_url and value set to the URL to display to your customer. transfer_details.provider_info.gateway_url is PII-protected: it's returned only by GET /api/transfers/{transfer_guid}?include_pii=true with the transfers:pii:read scope, and never on list responses.

Display the gateway_url through your application, email, SMS, or any other channel. When the customer visits the URL, they select their bank and authorize the deposit through their bank's website.

ℹ️

Deposit request expiry

The customer must authorize the deposit before the e-transfer request expires. Deposit requests are valid for 1 day.

Step 4: Wait for completion

Poll GET /api/transfers/{transfer_guid} or register for webhooks to monitor state. Once completed, the funds are available on the platform.

Deposit failure modes

E-transfer request URLs expire if the customer does not authorize them. The customer can also reject the request. In both cases, the transfer transitions to failed:

  • payment_request_expired — the customer did not authorize before the URL expired; deposit requests are valid for 1 day
  • recipient_cancelled — the customer rejected the e-transfer request. API versions before 2026-04-01 report external_vendor_error instead.

Withdrawal flow

The withdrawal process involves four steps:

  1. Create a funding quote with payment_rail set to etransfer
  2. Execute a transfer with payment_rail set to etransfer and a security question/answer pair
  3. Wait for the transfer to transition to completed
  4. Handle any terminal failed states
✅

Auto-Deposit recipients supported

Recipients with Auto-Deposit enabled can receive Interac E-Transfers from the Cybrid Platform. A security_question and security_answer are still required on the transfer request even though Auto-Deposit bypasses the question on the recipient side.

Security questions: examples and best practices

Avoid common, publicly guessable facts such as first names, pet names, or city names. Use "shared secret" questions or inside knowledge known only to you and the recipient.

Example questions

  • What is the password we agreed upon?
  • What item did we discuss yesterday?
  • What is the answer to the secret riddle?
  • What was the first item we decided to buy together?
  • What is the custom code word for this transaction?
  • What flavor of treat did we share on our last visit?
  • What is the name of the made-up place we talked about?

Best practices

  • Use "blind" questions. The question does not need to relate to the answer. The best questions appear random to anyone else.
  • Avoid personal data. Do not use easily researched details such as birthdays, anniversaries, or maiden names.
  • Keep it simple. Interac answers are typically one word, should not have spaces, and should not include special characters.
  • Never reuse combinations. Do not use the same security question and answer for multiple recipients or transactions.

Share the answer safely

  • Use an out-of-band method. Share the answer separately from any message you send the recipient about the transfer itself.
  • Separate the channels. If you send the transfer notification via email, send the answer via SMS.
  • Gold standard. The safest way to share the answer is verbally over a phone call or in person.

Step 1: Create a funding quote

The payment_rail field is required on the quote for e-transfer withdrawals.

{
  "product_type": "funding",
  "customer_guid": "customer_guid",
  "asset": "CAD",
  "side": "withdrawal",
  "payment_rail": "etransfer",
  "deliver_amount": 10000
}
ℹ️

No destination_account_guid required

Unlike EFT withdrawals, Interac E-Transfer withdrawals do not take a destination_account_guid. The recipient is resolved at transfer time: from the customer's email or phone for a withdrawal without an external bank account, or from the Interac e-Transfer external bank account in external_bank_account_guid for a send to a counterparty or a send through a customer-owned account. Either way, the customer is the originator of the e-transfer.

⚠️

Withdrawal network fee

Interac E-Transfer withdrawals include a network fee in the funding quote. The platform charges this fee on every withdrawal, including withdrawals that do not complete — it is not refunded if the e-transfer expires unclaimed or the recipient declines it.

Step 2: Execute the transfer

Create the transfer with transfer_type set to funding and payment_rail set to etransfer. Both security_question (max 40 characters) and security_answer (max 25 characters) are required for e-transfer withdrawals. The recipient must answer the question correctly to claim the funds.

external_bank_account_guid is optional. Without it, the withdrawal goes to the customer's own email or phone from their identity record. To send to a counterparty, or to a customer's Interac e-Transfer address that differs from their identity record, supply the guid of an Interac e-Transfer external bank account. See Send money to a counterparty and Use a customer-owned Interac e-Transfer account.

✅

Character limits

security_question accepts up to 40 characters and security_answer accepts up to 25 characters. Validate length before submitting the transfer.

{
  "quote_guid": "quote_guid",
  "transfer_type": "funding",
  "payment_rail": "etransfer",
  "security_question": "What is the password we agreed upon?",
  "security_answer": "Sunflower",
  "source_participants": [
    {"type": "customer", "guid": "customer_guid", "amount": 10000}
  ],
  "destination_participants": [
    {"type": "customer", "guid": "customer_guid", "amount": 10000}
  ]
}
ℹ️

Withdrawal claim window

After you execute the transfer, the recipient must claim the e-transfer before it expires. Withdrawals are valid for 7 days.

Step 3: Wait for completion

Poll GET /api/transfers/{transfer_guid} or register for webhooks. Once completed, the funds have been sent to the recipient and debited from the customer's fiat account.

Step 4: Handle withdrawal failures

Inspect the failure_code field on the transfer:

  • customer_contact_info_missing — the customer's identity has no email or phone populated. Add an email or phone to the identity and create a new transfer to retry.
  • payment_request_expired — the recipient did not claim the e-transfer before it expired; the claim window is 7 days
  • recipient_cancelled — the recipient declined the e-transfer. API versions before 2026-04-01 report external_vendor_error instead.
  • invalid_security_question — the security question or answer was rejected; the answer must use letters, digits, and hyphens only. API versions before 2026-04-01 report external_vendor_error instead.

If the recipient's bank account is invalid or closed, the transfer fails before funds move. Interac E-Transfer withdrawals are claim-based, so completed withdrawals are generally not returned.

Other failure_code values may apply. See the Cybrid Bank API reference for the full set.

The network fee is charged even when a withdrawal fails. The platform does not refund it if the e-transfer expires unclaimed or the recipient declines it.

Request money from a counterparty

Send an Interac E-Transfer Request for Money directly to a counterparty. The Platform addresses the request to the contact details on the counterparty's Interac e-Transfer external bank account. When the counterparty pays, the funds land in the customer's CAD fiat account.

⚠️

Restricted functionality

Requesting money from and sending money to a counterparty over Interac e-Transfer is not part of a standard remittance flow. It is reserved for specific use cases that require additional due diligence and explicit compliance approval from Cybrid. The functionality may be available in sandbox, but it is not available in production without that approval. Contact Cybrid support to discuss your use case.

The request follows the deposit flow with one addition: set external_bank_account_guid on the transfer. Omit external_bank_account_guid for a standard deposit that the customer authorizes through the gateway_url.

ℹ️

API version

Create the counterparty's Interac e-Transfer external bank account on API version 2026-09-01. See Interac e-Transfer accounts. Once the account exists, the transfer request is accepted on every API version.

Step 1: Create a funding quote

Create a deposit quote for CAD, as in Step 1 of the deposit flow.

Step 2: Execute the transfer

Create the transfer with transfer_type set to funding, payment_rail set to etransfer, and external_bank_account_guid set to the counterparty's Interac e-Transfer external bank account. You should set source_participants to the counterparty and destination_participants to the customer receiving the funds.

{
  "quote_guid": "quote_guid",
  "transfer_type": "funding",
  "payment_rail": "etransfer",
  "external_bank_account_guid": "external_bank_account_guid",
  "source_participants": [
    {"type": "counterparty", "guid": "counterparty_guid", "amount": 10000}
  ],
  "destination_participants": [
    {"type": "customer", "guid": "customer_guid", "amount": 10000}
  ]
}

Step 3: Wait for the counterparty to pay

The Platform sends the Interac request to the counterparty:

  • An external bank account with an email and a phone number receives the request by email and SMS
  • An external bank account with only an email receives the request by email

If the phone number is rejected, the Platform retries the request once by email only.

The request names the customer as the requester. Requests are valid for 1 day.

The transfer still returns a gateway_url in its identifiers array. You do not need to display it, because the counterparty receives the request directly.

Poll GET /api/transfers/{transfer_guid} or register for webhooks to monitor state. Once completed, the funds are available in the customer's fiat account.

External bank account validation errors

The Platform validates the external bank account when you create a request or a send, whether a counterparty or the customer owns the account. A failed check returns 422 with message_code set to invalid_external_bank_account and one of the following error_message values:

error_messageCause
External bank account not foundThe account does not exist or is not visible to the caller
External bank account kind not supportedThe account's account_kind is not raw_routing_details
External bank account not readyThe account is not in the completed state
External bank account asset incorrectThe account's asset does not match the quote's asset
External bank account customer incorrectThe account, or its counterparty, belongs to a different customer than the transfer
External bank account bank incorrectFor a transfer from a bank-level fiat account, the account belongs to a different bank

An Interac e-Transfer external bank account created before API version 2026-09-01 passes these checks, but the transfer fails after it is created. Create the account on 2026-09-01.

Request failure modes

Inspect the failure_code field on a failed transfer:

  • payment_request_expired — the counterparty did not pay before the request expired; requests are valid for 1 day
  • recipient_cancelled — the counterparty declined the request. API versions before 2026-04-01 report external_vendor_error instead.
  • external_vendor_error — an unexpected error occurred with an external vendor or partner service. Most rejections by the banking partner that are not listed here are also reported with this code.
  • party_name_invalid — the customer's name on their identity record is missing or incomplete
  • compliance_rejection — the transfer was rejected for compliance reasons
  • internal_error — an internal error occurred while processing the transfer; create a new transfer to retry

Other failure_code values may apply. See the Cybrid Bank API reference for the full set.

Send money to a counterparty

Send an Interac E-Transfer from the customer's CAD fiat account to a counterparty. The Platform sends the e-transfer to the contact details on the counterparty's Interac e-Transfer external bank account, and the counterparty answers the security question to claim the funds, unless they are registered for Interac Auto-Deposit.

⚠️

Restricted functionality

Requesting money from and sending money to a counterparty over Interac e-Transfer is not part of a standard remittance flow. It is reserved for specific use cases that require additional due diligence and explicit compliance approval from Cybrid. The functionality may be available in sandbox, but it is not available in production without that approval. Contact Cybrid support to discuss your use case.

The send follows the withdrawal flow with one addition: set external_bank_account_guid on the transfer. The same API version rule applies: create the counterparty's external bank account on API version 2026-09-01.

Step 1: Create a funding quote

Create a withdrawal quote for CAD with payment_rail set to etransfer, as in Step 1 of the withdrawal flow. A quote without payment_rail is rejected at transfer creation with 422 and error_message set to Quote must have payment_rail set for this withdrawal rail.

Step 2: Execute the transfer

Create the transfer with transfer_type set to funding, payment_rail set to etransfer, external_bank_account_guid set to the counterparty's Interac e-Transfer external bank account, and a security_question (max 40 characters) and security_answer (max 25 characters). You should set source_participants to the customer sending the funds and destination_participants to the counterparty.

{
  "quote_guid": "quote_guid",
  "transfer_type": "funding",
  "payment_rail": "etransfer",
  "external_bank_account_guid": "external_bank_account_guid",
  "security_question": "What is the password we agreed upon?",
  "security_answer": "Sunflower",
  "source_participants": [
    {"type": "customer", "guid": "customer_guid", "amount": 10000}
  ],
  "destination_participants": [
    {"type": "counterparty", "guid": "counterparty_guid", "amount": 10000}
  ]
}
ℹ️

Auto-Deposit recipients

Always supply a security_question and security_answer. If the recipient is registered for Interac Auto-Deposit, the Platform replaces them with a default security question and a random answer.

The Platform notifies the recipient by email if the customer's identity record has an email address, and by SMS otherwise. A send through an external bank account does not return a gateway_url. Unless the counterparty is registered for Interac Auto-Deposit, they must claim the e-transfer within 7 days, and the network fee applies as for any e-transfer withdrawal.

Step 3: Wait for completion

Poll GET /api/transfers/{transfer_guid} or register for webhooks. Once completed, the funds have been sent to the counterparty and debited from the customer's fiat account.

Send validation errors

Transfer creation runs the same external bank account checks as a request. See External bank account validation errors.

A send can also return 422 with message_code set to destination_too_new and error_message set to External destination is too new when the external bank account has not reached the minimum age configured for your bank. Requests are not subject to this check.

Send failure modes

Inspect the failure_code field on a failed transfer:

  • recipient_cancelled — the recipient declined the e-transfer. API versions before 2026-04-01 report external_vendor_error instead.
  • payment_request_expired — the recipient did not claim the e-transfer before it expired; the claim window is 7 days
  • non_sufficient_funds — the customer's account did not have enough funds
  • invalid_security_question — the security question or answer was rejected; the answer must use letters, digits, and hyphens only. API versions before 2026-04-01 report external_vendor_error instead.
  • customer_contact_info_missing — the customer's identity record has neither an email address nor a phone number, its email address is invalid, or the banking partner rejected the customer's contact details. API versions before 2026-04-01 report invalid_destination instead.
  • external_vendor_error — an unexpected error occurred with an external vendor or partner service. Most rejections by the banking partner that are not listed here are also reported with this code.
  • compliance_rejection — the transfer was rejected for compliance reasons
  • internal_error — an internal error occurred while processing the transfer; create a new transfer to retry

If the recipient's bank account is invalid or closed, the transfer fails before funds move.

Other failure_code values may apply. See the Cybrid Bank API reference for the full set.

The network fee is charged even when a send fails.

Use a customer-owned Interac e-Transfer account

A request or a send can also use an Interac e-Transfer external bank account owned by the customer. Use a customer-owned account when the customer's Interac e-Transfer address differs from the email on their identity record, or when you want Interac to notify the customer directly instead of displaying the gateway_url. The compliance approval required for counterparty requests and sends does not apply to a customer-owned account.

Step 1: Create the external bank account

Create the account with POST /api/external_bank_accounts on API version 2026-09-01. Set account_kind to raw_routing_details, asset to CAD, and customer_guid to the customer. Do not send counterparty_guid.

In counterparty_bank_account_details, add an entry with payment_rail set to ETRANSFER, account_identifier_type set to EMAIL, and the customer's Interac e-Transfer email in account_identifier. An EMAIL entry is required. You can add a second ETRANSFER entry with account_identifier_type set to PHONE_NUMBER and a Canadian number in E.164 format. Do not add bank code entries to the same request: an account created with them does not support Interac e-Transfer.

counterparty_name and counterparty_address carry the customer's holder information and are required. counterparty_email_address is optional. See Customer-owned and bank-owned raw routing accounts for the holder information rules.

POST /api/external_bank_accounts
Content-Type: application/json
Authorization: Bearer YOUR_TOKEN
Accept-Version: 2026-09-01

{
  "name": "external_bank_account_name",
  "account_kind": "raw_routing_details",
  "customer_guid": "customer_guid",
  "asset": "CAD",
  "counterparty_name": {
    "first": "John",
    "last": "Doe"
  },
  "counterparty_address": {
    "street": "123 Main St",
    "city": "Toronto",
    "subdivision": "ON",
    "postal_code": "M5V 2T6",
    "country_code": "CA"
  },
  "counterparty_bank_account_details": [
    {
      "payment_rail": "ETRANSFER",
      "account_identifier_type": "EMAIL",
      "account_identifier": "[email protected]"
    },
    {
      "payment_rail": "ETRANSFER",
      "account_identifier_type": "PHONE_NUMBER",
      "account_identifier": "+14165550123"
    }
  ]
}

Like other customer-owned accounts, the holder name you submit must match the customer's identity record; the account moves to completed once the ownership check passes. Wait for the account to reach the completed state before you use it on a transfer.

⚠️

Account requirements

The customer must be verified. Your bank must have the individual_customer_raw_routing_details feature for an individual customer, or the business_customer_raw_routing_details feature for a business customer; otherwise the request returns 422 with message_code set to not_raw_routing_details_bank. On API versions before 2026-09-01, an EMAIL entry is rejected with invalid_account_number.

Step 2: Request or send money

Follow Request money from a counterparty or Send money to a counterparty, with two differences:

  • Set external_bank_account_guid to the customer-owned account
  • You should set both source_participants and destination_participants to the customer
{
  "quote_guid": "quote_guid",
  "transfer_type": "funding",
  "payment_rail": "etransfer",
  "external_bank_account_guid": "external_bank_account_guid",
  "source_participants": [
    {"type": "customer", "guid": "customer_guid", "amount": 10000}
  ],
  "destination_participants": [
    {"type": "customer", "guid": "customer_guid", "amount": 10000}
  ]
}
{
  "quote_guid": "quote_guid",
  "transfer_type": "funding",
  "payment_rail": "etransfer",
  "external_bank_account_guid": "external_bank_account_guid",
  "security_question": "What is the password we agreed upon?",
  "security_answer": "Sunflower",
  "source_participants": [
    {"type": "customer", "guid": "customer_guid", "amount": 10000}
  ],
  "destination_participants": [
    {"type": "customer", "guid": "customer_guid", "amount": 10000}
  ]
}

Interac notifies the customer at the contact details on the account, as described for requests and sends to a counterparty. The same validation errors, request failure modes, and send failure modes apply.


Did this page help you?