Endpoint
POST:{{baseURL}}/v2/payout
Request Details
Headers
Include these headers in your request:| Header | Value | Required |
|---|---|---|
Content-Type | application/json | β Yes |
x-api-key | YOUR_API_KEY | β Yes |
meCash supports two Payment Channels for CAD Payouts:
- Bank Transfer: Bank Transfer is the traditional way to send money directly into a recipientβs bank account.
- Interac: The Interac E-Transfer is a popular Canadian payment service that lets you send money using an email address or mobile phone number.
Sample Request for Bank Transfer
Sample Request: Interac E-Transfer
Here are examples of how to make a CAD payout request via Interac, using the recipientβs email or mobile number.Request Body Breakdown
| Field | Type | Description | Required |
|---|---|---|---|
quoteId | String | The unique ID of the quote for this payout. | β Yes |
reason | String | The purpose of the transfer (e.g., Payment for services). | β Yes |
invoice | String | Optional identifier for the invoice (returned from file upload). | β No |
remark | String | An optional, additional note about the transaction. | β No |
recipient | Object | An object containing all details about the person receiving the funds. | β Yes |
recipient.name | String | The full name of the recipient or business. | β Yes |
recipient.paymentChannel | String | The payment method. Can be BANK_TRANSFER or INTERAC for CAD payouts. | β Yes |
recipient.currency | String | The ISO currency code. Must be CAD. | β Yes |
recipient.country | String | The recipientβs two-letter ISO country code. Must be CA. | β Yes |
recipient.mobileNumber | String | (Interac Only) The recipientβs mobile number. Either mobileNumber or email is required for Interac. | β Yes |
recipient.email | String | (Interac Only) The recipientβs email address. Either mobileNumber or email is required for Interac. | β Yes |
recipient.type | String | (Interac Only) The recipient type. Can be INDIVIDUAL or BUSINESS. | β Yes |
recipient.stored | Boolean | (Interac Only) Set to true if the recipient is a saved beneficiary. | β Yes |
recipient.address | String | (Bank Transfer Only) The recipientβs full residential or business address. | β Yes |
recipient.account | Object | (Bank Transfer Only) An object containing the recipientβs bank account details. | β Yes |
recipient.account.accountNumber | String | (Bank Transfer Only) The recipientβs bank account number. | β Yes |
recipient.account.bankName | String | (Bank Transfer Only) The name of the recipientβs bank. | β Yes |
recipient.account.address | String | (Bank Transfer Only) The address of the recipientβs bank branch. | β Yes |
recipient.account.sortCode | String | (Bank Transfer Only) The 3-digit institution number for the Canadian bank. | β Yes |
recipient.account.swiftCode | String | (Bank Transfer Only) The recipient bankβs SWIFT/BIC code. | β Yes |
recipient.account.transitNumber | String | (Bank Transfer Only) The 5-digit number identifying the recipientβs bank branch in Canada. | β Yes |
Success Response (Bank Transfer) (200 OK)
If the payout is successfully created, the API returns the following response:copy
Success Response for Interac (200 OK)
If the payout is successfully created, the API returns the following response:copy
Response Breakdown
This table explains each field in the success response payload. Note that some fields in therecipient object are specific to the payment channel used.
| Field | Type | Description |
|---|---|---|
message | String | A confirmation message indicating the result of the request. |
status | String | The overall status of the request, e.g., success. |
data | Object | A container for all the transaction data. |
data.id | String | The unique identifier for this payout transaction. |
data.reason | String | The reason for the payout that was provided in the request. |
data.invoice | String | Optional identifier for the invoice provided in the request. |
data.referenceNumber | String | A unique reference number generated for the payout. |
data.state | String | The current state of the payout (COMPLETED, PENDING, etc.). |
data.quote | Object | An object containing the details of the quote used for this transaction. |
data.quote.target.amount | Number | The converted amount that the recipient is scheduled to receive. |
data.recipient | Object | An object containing details of the recipient. |
data.recipient.name | String | The full name of the recipient. |
data.recipient.email | String | (Interac Only) The recipientβs email address that the e-Transfer notification was sent to. |
data.recipient.paymentChannel | String | The payment channel used for the payout, either BANK_TRANSFER or INTERAC. |
data.recipient.account.accountNumber | String | (Bank Transfer Only) The recipientβs masked bank account number. |
data.recipient.account.bankName | String | (Bank Transfer Only) The name of the recipientβs bank. |
data.recipient.account.sortCode | String | (Bank Transfer Only) The 3-digit institution number of the recipientβs bank. |
data.recipient.account.transitNumber | String | (Bank Transfer Only) The 5-digit transit number of the recipientβs bank branch. |
data.created | String | ISO 8601 timestamp of when the transaction was created. |
data.processed | String | ISO 8601 timestamp of when the transaction was successfully processed. |
Payout Transaction States
The payout transaction can have one of the following states:| State | Description |
|---|---|
COMPLETED | The payout was successfully processed. |
PENDING | The payout is still being processed. |
FAILED | The payout failed to process. |
REFUNDED | The payout has been sent back to sender. |
Error Handling
| Status Code | Meaning | Example Response |
|---|---|---|
400 | Insufficient Balance | Insufficient Balance |
401 | Unauthorized | Invalid API key provided. |
403 | Forbidden | IP not whitelisted |
404 | Not Found | The requested endpoint does not exist. |
422 | Unprocessable Entity | Invalid quote ID provided. |
500 | Internal Server Error | An internal error occurred. |
Best Practices
β EnsurequoteId is valid and linked to an existing quote.β Confirm that the recipientβs account number, transit number, and institution number are correct.
β Use a valid API key in the headers.
β Handle error responses correctly in your integration.

