Ask Bill!

Transfer errors

Errors specific to the Transfer product

TRANSFER_NETWORK_LIMIT_EXCEEDED

The attempted transfer exceeded the given network's amount limit.
Common causes
  • The attempted transfer's amount exceeded the network specific limit. The error message will indicate which network limit was exceeded. For reference, see the table below.
Troubleshooting steps
API error response
http code 400
{
 "error_type": "TRANSFER_ERROR",
 "error_code": "TRANSFER_NETWORK_LIMIT_EXCEEDED",
 "error_message": "[network] transaction amount cannot exceed [amount]",
 "display_message": null,
 "request_id": "HNTDNrA8F1shFEW"
}
NetworkMaximum Transaction Limit
ACH$10,000,000.00
Same Day ACH$1,000,000.00
RTP$1,000,000.00
RfP$3,500.00
Wire$999,999.99

TRANSFER_ACCOUNT_BLOCKED

The transfer could not be completed because a previous transfer involving the same end-user account resulted in an error or ACH return
Common causes
  • Plaid has flagged the end-user's account as not valid for use with Transfer.
Troubleshooting steps
API error response
http code 400
{
 "error_type": "TRANSFER_ERROR",
 "error_code": "TRANSFER_ACCOUNT_BLOCKED",
 "error_message": "transfer was blocked due to a previous ACH return on this account",
 "display_message": null,
 "request_id": "HNTDNrA8F1shFEW"
}

TRANSFER_NOT_CANCELLABLE

The transfer could not be cancelled
Common causes
  • An attempt was made to cancel a transfer that has already been sent to the network for execution and cannot be cancelled at this stage.
Troubleshooting steps
API error response
http code 400
{
 "error_type": "TRANSFER_ERROR",
 "error_code": "TRANSFER_NOT_CANCELLABLE",
 "error_message": "transfer is not cancellable",
 "display_message": null,
 "request_id": "HNTDNrA8F1shFEW"
}

TRANSFER_UNSUPPORTED_ACCOUNT_TYPE

An attempt was made to transfer funds to or from an unsupported account type
Common causes
  • A guarantee was requested in /transfer/authorization/create for an account whose subtype is not checking or savings (for example, a cash management account). Only checking and savings accounts are eligible for a guarantee with Guaranteed Payments.
Troubleshooting steps
API error response
http code 400
{
 "error_type": "TRANSFER_ERROR",
 "error_code": "TRANSFER_UNSUPPORTED_ACCOUNT_TYPE",
 "error_message": "transfer account type not supported",
 "display_message": null,
 "request_id": "HNTDNrA8F1shFEW"
}

TRANSFER_FORBIDDEN_ACH_CLASS

An attempt was made to 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
API error response
http code 400
{
 "error_type": "TRANSFER_ERROR",
 "error_code": "TRANSFER_FORBIDDEN_ACH_CLASS",
 "error_message": "specified ach_class is forbidden",
 "display_message": null,
 "request_id": "HNTDNrA8F1shFEW"
}

TRANSFER_ORIGINATOR_NOT_FOUND

An association between the sender and the originator client doesn't exist
Common causes
Troubleshooting steps
API error response
http code 400
{
 "error_type": "TRANSFER_ERROR",
 "error_code": "TRANSFER_ORIGINATOR_NOT_FOUND",
 "error_message": "the association between the sender and the originator client doesn't exist",
 "display_message": null,
 "request_id": "HNTDNrA8F1shFEW"
}

INCOMPLETE_CUSTOMER_ONBOARDING

The end customer has not completed onboarding. Their diligence status must be approved before moving funds
Common causes
  • You tried to move funds for an originator that hasn't been approved by Plaid yet
Troubleshooting steps
API error response
http code 400
{
 "error_type": "TRANSFER_ERROR",
 "error_code": "INCOMPLETE_CUSTOMER_ONBOARDING",
 "error_message": "end customer has not completed onboarding. their diligence status must be `approved` before moving funds",
 "display_message": null,
 "request_id": "HNTDNrA8F1shFEW"
}

UNAUTHORIZED_ACCESS

You are not authorized to access this endpoint for your use case
Common causes
Troubleshooting steps
API error response
http code 400
{
 "error_type": "TRANSFER_ERROR",
 "error_code": "UNAUTHORIZED_ACCESS",
 "error_message": "you are not authorized to access this endpoint for your use case.",
 "display_message": null,
 "request_id": "HNTDNrA8F1shFEW"
}

ACH return codes

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

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

Transfer customers should see Common ACH Return Codes in the Help Center for more detailed information on troubleshooting ACH return codes.

Return CodeDescriptionNotes
R01Insufficient fundsAvailable balance is not sufficient to cover the dollar amount of the debit entry
R02Account closedA previously open account is now closed
R03No account or unable to locate accountThe account number structure is valid, but the account number does not correspond to an existing account, or the name on the transaction does not match the name on the account.
R04Invalid account numberThe account number fails the check digit validation or may contain an incorrect number of digits. Commonly caused by invalidated TANs; see Tokenized account numbers for more details.
R05Unauthorized debit to consumer accountA business debit entry was transmitted to a member's consumer account, and the member had not authorized the entry
R06Returned per ODFI's requestThe ODFI has requested that the RDFI return the entry
R07Authorization revoked by customerMember who previously authorized an entry has revoked authorization with the originator
R08Payment stopped or stop payment on itemMember had previously requested a stop payment of a single or recurring entry
R09Uncollected fundsAvailable balance is sufficient, but the collected balance is not sufficient to cover the entry
R10Customer advises not authorizedMember advises not authorized, notice not provided, improper source document, or amount of entry not accurately obtained from source document
R11Customer advises entry not in accordance with the terms of the authorizationA valid authorization exists, but the debit did not conform to its terms (for example, an incorrect amount, an incorrect date, or an incomplete or improperly reinitiated transaction).
R12Branch sold to another DFIRDFI unable to post entry destined for a bank account maintained at a branch sold to another financial institution
R13Invalid ACH routing numberFinancial institution does not receive commercial ACH entries
R14Representative payee deceased or unable to continue in that capacityRepresentative payee is deceased or unable to continue in that capacity, beneficiary is not deceased
R15Beneficiary or account holder deceasedBeneficiary or Account Holder Deceased
R16Account frozenAccess to account is restricted due to a specific action taken by the RDFI or by legal action
R17File record edit criteriaFields rejected by RDFI processing (identified in return addenda)
R18Improper effective entryEntries have been presented prior to the first available processing window for the effective date
R19Amount field errorImproper formatting of the amount field
R20Non-transaction accountPolicies or regulations (such as Regulation D) prohibit or limit activity to the account indicated
R21Invalid company identificationThe company ID information not valid (normally CIE entries)
R22Invalid individual ID numberIndividual id used by receiver is incorrect (CIE entries)
R23Credit entry refused by receiverReceiver 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
R24Duplicate entryRDFI has received a duplicate entry
R25Addenda errorImproper formatting of the addenda record information
R26Mandatory field errorImproper information in one of the mandatory fields
R27Trace number errorOriginal entry trace number is not valid for return entry; or addenda trace numbers do not correspond with entry detail record
R28Routing number or check digitCheck digit for transit routing number is incorrect
R29Corporate customer advises not authorizedRDFI has been notified by business account holder that a specific transaction is unauthorized. Business accounts often automatically decline debits for security purposes. Your customer needs to inform their bank to allow debits that use your tax identifier.
R30RDFI not participant in check truncation programFinancial institution not participating in automated check safekeeping application
R31Permissible return entryRDFI may return a CCD or CTX entry that the ODFI has agreed to accept, even beyond the normal return deadline.
R32RDFI non settlementRDFI is not able to settle the entry
R33Return of XCK entryRDFI 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
R34Limited participation DFIRDFI participation has been limited by a federal or state supervisor
R35Return of improper debit entryACH debit not permitted for use with the CIE standard entry class code (except for reversals)
R36Return of improper credit entry
R37Source Document Presented for PaymentCheck used for an ARC, BOC or POP entry has also been presented for payment
R38Stop payment on source documentStop payment has been placed on a check used for an ARC entry
R40Return of ENR entry by federal government agency (ENR only)
R41Invalid transaction code (ENR only)
R42Routing number or check digit error (ENR only)
R43Invalid DFI account number (ENR only)
R44Invalid individual ID number (ENR only)
R45Invalid individual name/company name (ENR only)
R46Invalid representative payee indicator (ENR only)
R47Duplicate enrollment
R50State law affecting RCK acceptance
R51Item is ineligible, notice not provided, signature not genuine
R52Stop payment on item
R61Misrouted returnReturn entry was sent by RDFI to an incorrect ODFI routing/transit number
R62Incorrect trace number
R63Incorrect dollar amount
R64Incorrect individual identification
R65Incorrect transaction code
R66Incorrect company identification
R67Duplicate returnODFI has received more than one return entry for the same original entry
R68Untimely returnReturn entry did not meet the return deadline
R69Multiple errors
R70Permissible return entry not accepted
R71Misrouted dishonored return
R72Untimely dishonored return
R73Timely original return
R74Corrected return
R80Cross-border payment coding error
R81Nonparticipant in cross-border program
R82Invalid foreign receiving DFI identification

RTP/RfP error codes

failed RTP/RfP transactions will have a failure description. By reading the description, you can troubleshoot and debug failed transactions.

This table can also be viewed as a Google doc.

Failure CodeDescriptionRail(s)Condensed Error CategoryRetryableSuggested Action
1100Other Reasons - Not specifiedBothBeneficiary or compliance information issueNoInvestigate beneficiary data or compliance issues; do not auto-retry.
9909Central Switch system malfunctionRTPNetwork issue (retryable)Yes - auto-retryWait briefly and retry automatically; consider fallback rail if urgent.
9910Instructed Agent signed-offRTPNetwork issue (retryable)Yes - auto-retryWait briefly and retry automatically; consider fallback rail if urgent.
9912Recipient connection unavailableRTPNetwork issue (retryable)Yes - auto-retryWait briefly and retry automatically; consider fallback rail if urgent.
9934Instructing Agent signed-offRTPNetwork issue (retryable)Yes - auto-retryWait briefly and retry automatically; consider fallback rail if urgent.
9946Instructing Agent suspendedRTPNetwork issue (retryable)Yes - auto-retryWait briefly and retry automatically; consider fallback rail if urgent.
9947Instructed Agent suspendedRTPNetwork issue (retryable)Yes - auto-retryWait briefly and retry automatically; consider fallback rail if urgent.
9948Central Switch service suspendedRTPNetwork issue (retryable)Yes - auto-retryWait briefly and retry automatically; consider fallback rail if urgent.
AC02Debtor account is invalidBothIssues with the sending accountNoAsk the sender to correct or switch accounts, then resubmit.
AC03Creditor account is invalidBothIssues with the receiving account (invalid, closed, blocked)NoRequest updated recipient account details or use another payout account.
AC04Account closedBothIssues with the receiving account (invalid, closed, blocked)NoRequest updated recipient account details or use another payout account.
AC06Account is blockedBothIssues with the receiving account (invalid, closed, blocked)NoRequest updated recipient account details or use another payout account.
AC07Creditor account closedBothIssues with the receiving account (invalid, closed, blocked)NoRequest updated recipient account details or use another payout account.
AC13Debtor account type invalidBothIssues with the sending accountNoAsk the sender to correct or switch accounts, then resubmit.
AC14Creditor account type invalidBothIssues with the receiving account (invalid, closed, blocked)NoRequest updated recipient account details or use another payout account.
AG01Transaction forbidden on this type of accountBothIssues with the receiving account (invalid, closed, blocked)NoRequest updated recipient account details or use another payout account.
AG03Transaction type not supported on this accountBothIssues with the receiving account (invalid, closed, blocked)NoRequest updated recipient account details or use another payout account.
AM02Transaction amount exceeds allowed maximumBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
AM04Insufficient fundsBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
AM09Incorrect amount receivedBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
AM12Amount invalid or missingBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
AM13Amount exceeds clearing system limitsBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
AM14Amount exceeds bank-client limitBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
BE04Missing or incorrect creditor addressBothBeneficiary or compliance information issueNoInvestigate beneficiary data or compliance issues; do not auto-retry.
BE06End customer not knownBothBeneficiary or compliance information issueNoInvestigate beneficiary data or compliance issues; do not auto-retry.
BE07Missing or incorrect debtor addressBothBeneficiary or compliance information issueNoInvestigate beneficiary data or compliance issues; do not auto-retry.
BE16Debtor identification invalidBothBeneficiary or compliance information issueNoInvestigate beneficiary data or compliance issues; do not auto-retry.
BE17Creditor identification invalidBothBeneficiary or compliance information issueNoInvestigate beneficiary data or compliance issues; do not auto-retry.
BLKDPayment has been blockedBothBeneficiary or compliance information issueNoInvestigate beneficiary data or compliance issues; do not auto-retry.
CH11Creditor identifier unknownRFPAuthorization declined or customer action requiredNoRespect customer's decision or obtain new authorization.
CUSTCustomer declined paymentBothAuthorization declined or customer action requiredNoRespect customer's decision or obtain new authorization.
DS04Order rejected – content issuesBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
DS0HSigner not authorized for this accountBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
DS24Waiting time expired (incomplete order)BothNetwork issue (retryable)Yes - after correctionRetry the payment with a different idempotency key.
DT04Future date not supportedBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
DUPLDuplicate payment detectedBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
E997Timeout clock has expiredBothNetwork issue (retryable)Yes - after correctionRetry the payment with a different idempotency key.
FF02Syntax error in narrative informationBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
FF03Invalid payment type informationBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
FF08End-to-End ID missing or invalidBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
INSFInsufficient funds for outbound messageBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
MD07End customer is deceasedBothBeneficiary or compliance information issueNoInvestigate beneficiary data or compliance issues; do not auto-retry.
NARRNarrative reason providedBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
NOATAccount does not support this message typeBothIssues with the receiving account (invalid, closed, blocked)NoRequest updated recipient account details or use another payout account.
RC01Bank identifier format incorrectBothRouting or bank identifier issueYes - after correctionSupply a valid routing/BIC and retry.
RC02Bank identifier invalid or missingBothRouting or bank identifier issueYes - after correctionSupply a valid routing/BIC and retry.
RC03Debtor FI identifier invalid or missingBothRouting or bank identifier issueYes - after correctionSupply a valid routing/BIC and retry.
RC04Creditor FI identifier invalid or missingBothIssues with the receiving account (invalid, closed, blocked)NoRequest updated recipient account details or use another payout account.
SL12Debtor opted out of RFPsRFPAuthorization declined or customer action requiredNoRespect customer's decision or obtain new authorization.
TK01Invalid tokenBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
TK02Sender token not foundBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
TK03Receiver token not foundBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
TK04Token expiredBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
TK05Token counterparty mismatchBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
TK06Token value-limit rule violationBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
TK07Single-use token already usedBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.
TK08Token suspendedBothIssues with payment details (amount, currency, token, duplicate, format)Yes - after correctionCorrect the payment amount, currency, token or format, then retry.