Skip to main content

Rejections & Returns Coming Soon

Early preview

International payments are coming soon. This preview gives you an early look at the expected experience so you can begin planning your integration.

Rejection Reasons​

International payments may be rejected at any stage. When a payment is rejected, the payment.rejected webhook event fires and reason is populated on the payment resource.

ReasonDescription
InsufficientFundsLedger debit failed at creation — source account balance too low.
QuoteExpiredThe quote was not used before its expiry time.
QuoteAlreadyUsedThe quote had already been consumed by another payment.
QuoteAccountMismatchThe account on the payment does not match the quote.
AccountClosedThe source account was closed.
AccountFrozenThe source account was frozen.
DacaIsActiveA DACA (Deposit Account Control Agreement) is active on the source account.
OtherAny other reason; a descriptive string is provided in the reason field.

Return Reasons​

International payments may also be returned by the counterparty's bank after they've already been sent. When this happens, the payment moves to Returned status, the payment.returned webhook event fires, and one of the reasons below is populated on reason.

ReasonDescription
CounterpartyAccountClosedThe counterparty's account was closed after the payment was sent.
InvalidCounterpartyAccountThe counterparty's account number is invalid or does not exist.
CounterpartyAccountFrozenThe counterparty's account is frozen or blocked.
IncorrectCounterpartyDetailsThe counterparty's name or other details on the payment don't match the account on file.
CounterpartyBankRejectedThe counterparty's bank rejected the payment.
CounterpartyComplianceHoldThe counterparty's bank returned the payment due to a compliance check.
DuplicatePaymentThe payment was identified as a duplicate.
OtherAny other reason; a descriptive string is provided in the reason field.