interac/bulk-payout

This endpoint is used to create an Interac e-Transfer bulk payout transaction for sending funds.

If a ClientAccountID is provided, the client account's first/last name, and email address will be used for the transaction.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Form Data
string
required

Your account ID

string
required

API key for the account

string
required

Hashed signature for the e-transfer

string

Client Account ID

string

The ID of the contact to use for this transactions. The contacts payment method associated with this transaction type will be used.

number
required

The amount to debit from the customer's bank account.

string

3 character currency code for the currency to fetch transactions for. If this is not specified the transaction will use the account's local currency (generally CAD). NOTE: Currently the eft/fund API endpoint only supports CAD transactions.

string

Recipient's email address. Either EmailAddress or PhoneNumber must be provided

string

Recipient's mobile phone number. (Digits only - no parentheses or dashes allowed.). Either EmailAddress or PhoneNumber must be provided

string

Sender's full name. This is the name that will be used as the sender's name in the notifications to the recipient. If not provided, your VoPay account name will be used.

string
required

Recipient's name, as known by the sender.

string

Recipient's address line 1

string

Recipient's address line 2

string

Recipient's city

string

Recipient's province specified using two character abbreviations (eg. BC, AB)

string

Recipient's country specified using full country name or ISO 3166-1 alpha-2 code.

string

Recipient's postal code.

string

Recipient's language preference. Accepted values: en (English as the default) or fr (French).

integer

1-30 , number of days after which the transfer will be marked as cancelled.

string

Message to recipient. Set by client for the recipient.

string

An optional note to associate with the transaction.

string

An optional reference number which was associated with the transaction.

string
required

Security question for the transaction.

string
required

Answer to the security question. This can be either a plain text answer or a hashed answer. Hashed answers must have leading and trailing whitespace trimmed, be SHA2 hashed and Base64 encoded. If a hashed answer is provided, the HashSalt input is mandatory.

string

The salt used to hash the answer. This input is mandatory if a hashed answer is provided.

string

A unique key which the server can use to recognize and reject subsequent retries of the same request.

string

The parent transaction where the withdrawal will be linked to, can become a split payment with multiple withdrawals. When funds of the parent transaction have been released the system will generate the distributions of these funds automatically.

string

An optional unique identification general ledger code.

string

CPA transaction code. Use the /api/v2/account/transactions/codes endpoint to retrieve a list of valid transaction codes. If not specified, the transaction will be created using code 450 (miscellaneous).

Response

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json