Bank Transfers errors

Errors specific to the Bank Transfers product

BANK_TRANSFER_LIMIT_EXCEEDED

The attempted bank transfer exceeded the account's daily bank transfer or single bank transfer limits.

Common causes

The attempted bank transfer exceeded the account's daily bank transfer or single bank transfer limits. The error message will indicate which transfer limit was exceeded.
A call to a Bank Transfers endpoint was made in Development that did not comply with the following limitations for the use of Bank Transfers in Development:
- Each transaction must be no more than $0.05.
- The sum total of all transactions must be less than $5.00.
- Users may initiate up to 50 ACH credits and 10 Same-Day ACH credits.
- All transactions must be of type credit; debits are not allowed.

Troubleshooting steps

If the limit exceeded was a daily limit, and your use case allows it, retry the transfer again later.

If the error occurred in Development, modify the call to comply with the limitations for Bank Transfers in Development.

If the error occurred in Development and complying with Development restrictions is not possible, test in the Sandbox or Production environments.

API error response
1http code 400
2{
3 "error_type": "BANK_TRANSFER_ERROR",
4 "error_code": "BANK_TRANSFER_LIMIT_EXCEEDED",
5 "error_message": "bank transfer daily transfer limit exceeded",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

Was this helpful?

BANK_TRANSFER_MISSING_ORIGINATION_ACCOUNT

There are multiple origination accounts available for the transfer, but which account to use was not specified.

Common causes

There is more than one origination account associated with the client id, but no account was specified in the request.

Troubleshooting steps

Make sure to specify an origination_account_id when calling /bank_transfer/create or /bank_transfer/balance/get.

API error response
1http code 400
2{
3 "error_type": "BANK_TRANSFER_ERROR",
4 "error_code": "BANK_TRANSFER_MISSING_ORIGINATION_ACCOUNT",
5 "error_message": "origination_account_id is required if multiple origination accounts are available",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

Was this helpful?

BANK_TRANSFER_INVALID_ORIGINATION_ACCOUNT

The origination account specified for the bank transfer was invalid.

Common causes

The origination_account_id specified when calling /bank_transfer/create was invalid.

Ensure that the origination_account_id you are using corresponds to a valid origination account owned by you. You can obtain your origination_account_id from your Plaid Account Manager. Also ensure that the casing matches, as all Plaid identifiers are case-sensitive.

API error response
1http code 400
2{
3 "error_type": "BANK_TRANSFER_ERROR",
4 "error_code": "BANK_TRANSFER_INVALID_ORIGINATION_ACCOUNT",
5 "error_message": "origination_account_id is invalid",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

Was this helpful?

BANK_TRANSFER_ACCOUNT_BLOCKED

The bank transfer could not be completed because a previous transfer involving the same end-user account resulted in an error.

Common causes

The end user has previously marked a bank transfer transaction originated by you as an unauthorized transfer (applies to Plaid developers using FBO accounts only).
Plaid has flagged the end-user's account as not valid for use with Bank Transfers.

Troubleshooting steps

Ask the end user to link a different account with Plaid and re-attempt the transfer with the new account.

(FBO accounts only) Use /bank_transfer/event/list to find previous events for this account_id and determine if any were rejected with an ACH return code of R10 (customer advises not authorized) or R29 (corporate customer advises not authorized). If you find any such transactions, reach out to the end user to understand why the transfer was rejected, in order to prevent re-occurrence of this error with the newly linked account.

API error response
1http code 400
2{
3 "error_type": "BANK_TRANSFER_ERROR",
4 "error_code": "BANK_TRANSFER_ACCOUNT_BLOCKED",
5 "error_message": "bank transfer was blocked due to a previous ACH return on this account",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

Was this helpful?

BANK_TRANSFER_INSUFFICIENT_FUNDS

There was not enough money in the origination account (FBO accounts only) to execute the transfer.

Common causes

An attempt was made to transfer money out of the origination account that would leave the balance of the origination account below the required minimum reserve balance.

Troubleshooting steps

If you have a large number of outstanding pending debit transactions, wait for the batch to post to your account, which will increase your available balance.

Reduce the amount of the transfer and try again.

API error response
1http code 400
2{
3 "error_type": "BANK_TRANSFER_ERROR",
4 "error_code": "BANK_TRANSFER_INSUFFICIENT_FUNDS",
5 "error_message": "bank transfer balance is insufficient to make this request",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

Was this helpful?

BANK_TRANSFER_NOT_CANCELLABLE

The bank transfer could not be canceled.

Common causes

An attempt was made to cancel a bank transfer that has already been sent to the network for execution. Bank transfers cannot be canceled at this stage.

Troubleshooting steps

Use an endpoint such as /bank_transfer/get to check the value of the cancellable property before canceling a transfer.

If applicable, contact the counterparty to the transfer and ask them to return the funds after the transfer has executed.

API error response
1http code 400
2{
3 "error_type": "BANK_TRANSFER_ERROR",
4 "error_code": "BANK_TRANSFER_NOT_CANCELLABLE",
5 "error_message": "bank transfer is not cancellable",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

Was this helpful?

BANK_TRANSFER_UNSUPPORTED_ACCOUNT_TYPE

An attempt was made to transfer funds to or from an unsupported account type.

Common causes

An attempt was made to transfer funds to or from an unsupported account type. Only checking and savings accounts can be used with bank transfers. In addition, if the transfer is a debit transfer, the account must be a debitable account.

Troubleshooting steps

Ask the user to link a different account to use with Bank Transfers.

API error response
1http code 400
2{
3 "error_type": "BANK_TRANSFER_ERROR",
4 "error_code": "BANK_TRANSFER_UNSUPPORTED_ACCOUNT_TYPE",
5 "error_message": "bank transfer account type not supported",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

Was this helpful?

BANK_TRANSFER_UNSUPPORTED_ENVIRONMENT

A Bank Transfers endpoint was called on an unsupported environment.

Common causes

Your Plaid developer account has not been enabled to test Bank Transfers in Development.
Your access to Bank Transfers in Development has expired. Access to Bank Transfers in Development lasts for 4 weeks.

Troubleshooting steps

If you have not already done so, contact your Plaid Account Manager to request that your account be enabled to test Bank Transfers in Development.

API error response
1http code 400
2{
3 "error_type": "BANK_TRANSFER_ERROR",
4 "error_code": "BANK_TRANSFER_UNSUPPORTED_ENVIRONMENT",
5 "error_message": "bank transfers is not supported on this environment",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

Was this helpful?

BANK_TRANSFER_FORBIDDEN_ACH_CLASS

An attempt was made create a transfer with a forbidden ACH class (SEC code).

Common causes

Your Plaid account has not been enabled for the ACH class specified in the request.
The ACH class specified in the transfer request was incorrect.

Troubleshooting steps

Verify that the ACH class in the request is correct.

If you have not already done so, contact your Plaid Account Manager to request that the desired ACH class be enabled for your account.

API error response
1http code 400
2{
3 "error_type": "BANK_TRANSFER_ERROR",
4 "error_code": "BANK_TRANSFER_FORBIDDEN_ACH_CLASS",
5 "error_message": "specified ach_class is forbidden",
6 "display_message": null,
7 "request_id": "HNTDNrA8F1shFEW"
8}

Was this helpful?

ACH return codes

Prefer to learn by watching? A video guide is available for this topic.

All reversed ACH transactions will have an ACH return code. By reading the code, you can troubleshoot and debug reversed transactions.

Return Code	Description	Notes
R01	Insufficient funds	Available balance is not sufficient to cover the dollar amount of the debit entry
R02	Account closed	A previously open account is now closed
R03	No account or unable to locate account	The account number does not correspond to the individual identified in the entry or a valid account
R04	Invalid account number	The account number fails the check digit validation or may contain an incorrect number of digits
R05	Unauthorized debit to consumer account	A business debit entry was transmitted to a member’s consumer account, and the member had not authorized the entry
R06	Returned per ODFI's request	The ODFI has requested that the RDFI return the entry
R07	Authorization revoked by customer	Member who previously authorized an entry has revoked authorization with the originator
R08	Payment stopped or stop payment on item	Member had previously requested a stop payment of a single or recurring entry
R09	Uncollected funds	Available balance is sufficient, but the collected balance is not sufficient to cover the entry
R10	Customer advises not authorized	Member advises not authorized, notice not provided, improper source document, or amount of entry not accurately obtained from source document
R11	Check truncation entry return	To be used when returning a check truncation entry
R12	Branch sold to another DFI	RDFI unable to post entry destined for a bank account maintained at a branch sold to another financial institution
R13	Invalid ACH routing number	Financial institution does not receive commercial ACH entries
R14	Representative payee deceased or unable to continue in that capacity	Representative payee is deceased or unable to continue in that capacity, beneficiary is not deceased
R15	Beneficiary of account holder deceased	Beneficiary or Account Holder Deceased
R16	Account frozen	Access to account is restricted due to a specific action taken by the RDFI or by legal action
R17	File record edit criteria	Fields rejected by RDFI processing (identified in return addenda)
R18	Improper effective entry	Entries have been presented prior to the first available processing window for the effective date
R19	Amount field error	Improper formatting of the amount field
R20	Non-transaction account	Policies or regulations (such as Regulation D) prohibit or limit activity to the account indicated
R21	Invalid company identification	The company ID information not valid (normally CIE entries)
R22	Invalid individual ID number	Individual id used by receiver is incorrect (CIE entries)
R23	Credit entry refused by receiver	Receiver returned entry because minimum or exact amount not remitted, bank account is subject to litigation, or payment represents an overpayment, originator is not known to receiver or receiver has not authorized this credit entry to this bank account
R24	Duplicate entry	RDFI has received a duplicate entry
R25	Addenda error	Improper formatting of the addenda record information
R26	Mandatory field error	Improper information in one of the mandatory fields
R27	Trace number error	Original entry trace number is not valid for return entry; or addenda trace numbers do not correspond with entry detail record
R28	Routing number or check digit	Check digit for transit routing number is incorrect
R29	Corporate customer advises not authorized	RDFI has been notified by business account holder that a specific transaction is unauthorized
R30	RDFI not participant in check truncation program	Financial institution not participating in automated check safekeeping application
R31	Permissible return entry	RDFI has been notified by business account holder that a specific transaction is unauthorized
R32	RDFI non settlement	RDFI is not able to settle the entry
R33	Return of XCK entry	RDFI determines at its sole discretion to return an XCK entry; an XCK return entry may be initiated by midnight of the sixtieth day following the settlement date if the XCK entry
R34	Limited participation DFI	RDFI participation has been limited by a federal or state supervisor
R35	Return of improper debit entry	ACH debit not permitted for use with the CIE standard entry class code (except for reversals)
R36	Return of improper credit entry
R37	Source Document Presented for Payment	Check used for an ARC, BOC or POP entry has also been presented for payment
R38	Stop payment on source document	Stop payment has been placed on a check used for an ARC entry
R40	Return of ENR entry by federal government agency (ENR only)
R41	Invalid transaction code (ENR only)
R42	Routing number or check digit error (ENR only)
R43	Invalid DFI account number (ENR only)
R44	Invalid individual ID number (ENR only)
R45	Invalid individual name/company name (ENR only)
R46	Invalid representative payee indicator (ENR only)
R47	Duplicate enrollment
R50	State law affecting RCK acceptance
R51	Item is ineligible, notice not provided, signature not genuine
R52	Stop payment on item
R61	Misrouted return	Return entry was sent by RDFI to an incorrect ODFI routing/transit number
R62	Incorrect trace number
R63	Incorrect dollar amount
R64	Incorrect individual identification
R65	Incorrect transaction code
R66	Incorrect company identification
R67	Duplicate return	ODFI has received more than one return entry for the same original entry
R68	Untimely return	Return entry did not meet the return deadline
R69	Multiple errors
R70	Permissible return entry not accepted
R71	Misrouted dishonored return
R72	Untimely dishonored return
R73	Timely original return
R74	Corrected return
R80	Cross-border payment coding error
R81	Nonparticipant in cross-border program
R82	Invalid foreign receiving DFI identification