Request Interac(deposit)
Using this API call you can initiate a new Interac transaction. The response will provide you a direct payment link from the Interac system which you will need to handle on your side to get the customer redirected to it for the payment completion.
Required fields
Every request needs 2 headers and 4 body fields, and all of them are required. If any is missing or invalid, the request is refused and no deposit is created.
Headers (both required)
x-api-key: your credentials, as<kid>@<api-key>. If it’s missing you get409with messageMissing API key; if it’s wrong,401.Idempotency-Key: a new UUID v4 for every new deposit. If it’s missing you get400 MISSING_IDEMPOTENCY; if it’s not a UUID v4,400 INVALID_IDEMPOTENCY_KEY.
Body fields (all required)
amount(number): the amount in CAD, for example25or25.50. Greater than 0, at most9999, with at most 2 decimals and no thousands separator. If it’s out of range you get422 INVALID_AMOUNT; with more than 2 decimals,422 INVALID_AMOUNT_PRECISION.payeeEmail(string): the email address of the customer who will pay. It identifies the customer for the one-open-deposit rule and the daily limit. If it isn’t a valid email address you get422 INVALID_EMAIL.name(string): the customer’s full name. If it’s missing or empty you get400 MISSING_NAME.memo(string): your own description of the transaction, 5 to 200 characters. Only letters, digits, spaces and. # , $ @ 'are allowed (no:or-). Otherwise you get400 MISSING_MEMO.
Use real email addresses, including when testing in sandbox, and don’t use the word “test” anywhere in an email field. Interac can reject the transaction, or ban the email address, when it sees test or made-up addresses. The example.com addresses on this page are placeholders only. Thank you for your understanding.
The headers must contain a unique Idempotency-Key (UUID v4) in order for the API call to be successfull. If reusing an older key the response will include the details of the transaction where the key was first used. It will not create a new transaction.
409 Conflict
This endpoint returns 409 Conflict for five different reasons. The HTTP status alone doesn’t tell you which one, so always branch on error.code.
DUPLICATE_PENDING_TRANSACTION_AMOUNT_MISMATCH: the customer already has an open deposit for a different amount. Send the customer back to the open deposit. See the full explanation below.IDEMPOTENCY_KEY_REUSED_WITH_DIFFERENT_REQUEST: theIdempotency-Keywas already used with a different request body. For a new deposit, generate a new key. To replay a request, send exactly the same body: same fields, same values, same field order.IDEMPOTENCY_IN_PROGRESS: a request with thisIdempotency-Keyis still being processed. Wait a few seconds, then retry with the same key and the same body.BLACKLISTED: thepayeeEmailis blocked. Don’t retry. Contact NoLimit support if you think this is a mistake.BAD_REQUESTwith messageMissing API key: thex-api-keyheader was not sent. Sendx-api-key: <kid>@<api-key>.
DUPLICATE_PENDING_TRANSACTION_AMOUNT_MISMATCH
The rule
A customer can have only one open deposit with you at a time.
- Customer means the
payeeEmail, compared case-insensitively, within your partner account. Deposits created by other NoLimit partners don’t count. - Open means the deposit is not final yet:
PENDING,AUTHENTICATED,SENT,FULFILLEDorUNKNOWN. - Deposits that are
COMPLETED,REJECTED,DECLINED,CANCELLEDorINCOMPLETEnever block a new deposit. - Only deposits count here. An open withdrawal to the same email doesn’t block a deposit. Withdrawals have their own, separate check with the same rules.
What happens when the customer already has an open deposit
Same amount as an open deposit: no new Interac request is created. You get 201 Created with the existing deposit: its transactionId, status and interacLink.
- The
transactionIdin this response is the original deposit’s ID, not theIdempotency-Keyyou just sent. Always store thetransactionIdfrom the response instead of assuming it equals your key. - Your new
Idempotency-Keyis now linked to that existing deposit. Replaying it returns the same deposit.
Different amount: the request is refused with 409 Conflict:
error.messagelists every open deposit for this customer, separated by,, newest first. This is the only place the blocking IDs are returned.- “Mark them as rejected or completed” refers to the customer: they complete the open deposit by paying it, or reject it by declining it. Neither you nor NoLimit can close a deposit through the API.
What the 409 does not mean
- The open deposit has not failed. It is still live, and the customer can still pay it. Don’t mark it as failed on your side. Customers often pay the original request minutes after a retry was refused.
- No new deposit was created. There is no new
transactionIdto track, and no new Interac request was sent to the customer.
What happens to your request
- The
Idempotency-Keyyou sent is released, not stored. You can send the same key again later with the same body. - Every retry for a different amount returns the same
409until all the listed deposits are final. Retrying in a loop doesn’t help, and repeated refused attempts look like failed payments in your conversion metrics.
How the open deposit ends
Only one of these ends it:
- The customer pays it, through its
interacLink. It becomesCOMPLETED. - The customer declines it, on the Interac page or in their online banking. It becomes
REJECTEDorDECLINED. - Nobody acts on it for 30 days, and Interac expires it.
There is no API endpoint to cancel an open deposit.
Recommended handling
- Branch on the code. Treat
DUPLICATE_PENDING_TRANSACTION_AMOUNT_MISMATCHas “the customer has an unfinished deposit”, not as a failed payment. - Find the open deposit. Take the transaction ID or IDs from
error.message, or from your own records for that email. CallGET /request/{id}to get itspostedAmount,statusandinteracLink. - Send the customer back to it. Show the amount and the link, for example: “You have an unfinished deposit of $50.00. Complete it, or decline it in your online banking, before starting a new one.”
- Unblock on the final status. When the webhook or
GET /request/{id}shows a final status, the customer can start a new deposit for any amount.
Avoid the 409 in the first place
- Before calling
POST /request, check your own records for an open deposit for that email. If there is one, show it to the customer instead of creating a new request. - If a customer leaves the deposit flow and restarts it for the same amount, reuse the original
Idempotency-Key. You get the original deposit back. - Remind customers about unfinished deposits, for example after one hour and again after one day, so open requests are resolved sooner.
Order of checks
Checks run in this order. Each one can stop the request before the next:
- API key (
401, or409when the header is missing) - Blacklist (
409 BLACKLISTED) - Body validation, including
DAILY_LIMIT_EXCEEDED(400or422) Idempotency-Key(400, or409for the two idempotency codes)- Open-deposit check (
201with the existing deposit, or409 DUPLICATE_PENDING_TRANSACTION_AMOUNT_MISMATCH)
Headers
Your credentials, as <kid>@<api-key>.
A new UUID v4 for every new deposit. Reusing a key with the same body returns the original response; with a different body you get 409 IDEMPOTENCY_KEY_REUSED_WITH_DIFFERENT_REQUEST.
Request
Your own description of the transaction, 5 to 200 characters. Only letters, digits, spaces and . # , $ @ ' are allowed.