Skip to content

API payment failures

Payment failures are a special class of errors that occur only after a payment is created.

They require you to investigate and resolve the underlying condition before retrying.

Common causes include:

  • Insufficient balance
  • Credit or transaction limits exceeded
  • Past-due invoices
  • Invalid or inactive beneficiary account details

For the list of applicable codes, see the Payment failure codes reference section in the error codes reference.

Payment Failure Codes Table

CodeTypeTitleDescriptionStatus
USR_062USER_ERRORTransaction limit reachedPayment failed because you have already made {0} transactions in a 24-hr period. Try again later.402
USR_064USER_ERRORCredit limit reachedPayment failed because you have already reached your credit limit.402
USR_066USER_ERRORInvoice past duePayment failed because you have a past-due invoice. If you have already submitted a payment confirmation, try again later or contact technical support.402
USR_067USER_ERRORInsufficient balancePayment failed due to insufficient balance. Add funds to your account and try again.402
USR_151USER_ERRORInvalid identity informationPayment failed due to one or more errors in the beneficiary identity details. Create a new beneficiary identity with valid values and try again.400
USR_152USER_ERRORConflicting beneficiary name infoPayment failed because both Cdtr.Nm and Cdtr.StrdNm fields are populated in the beneficiary identity information. Only one of these fields must be present. If the beneficiary is an institution, specify only Cdtr.Nm. If the beneficiary is an individual, specify only Cdtr.StrdNm.400
USR_153USER_ERRORInvalid beneficiary account identifierPayment failed because the beneficiary account identifier you provided is invalid. Create a new beneficiary identity with a valid value in the CdtrAcct.Othr.Id field.400
USR_154USER_ERRORMissing beneficiary account identification scheme codePayment failed because the beneficiary’s account identification scheme code is missing. Create a new beneficiary identity with the value specified in the CdtrAcct.Id.Othr.SchmeNm.Cd field.400
USR_155USER_ERRORInvalid beneficiary account identification scheme codePayment failed because the beneficiary’s account identification scheme code is invalid. Create a new beneficiary identity with a valid scheme code specified in the CdtrAcct.Id.Othr.SchmeNm.Cd field. For more information, contact your Ripple liaison.400
USR_156USER_ERRORMissing Beneficiary InformationPayment failed because the beneficiary identity doesn’t have the required PII. Create a new beneficiary identity with the required Cdtr object and try again.400
USR_157USER_ERRORMissing beneficiary account informationPayment failed because the originator identity doesn’t have required information about the beneficiary’s account where the funds will be received. Create a new beneficiary identity with the required CdtrAcct object and try again.400
USR_158USER_ERRORMissing beneficiary namePayment failed because the beneficiary identity doesn’t contain the beneficiary’s name. Create a new beneficiary identity with the required Cdtr.Nm field if the beneficiary is an institution, or the Cdtr.StrdNm field if the beneficiary is an individual and try again.400
USR_159USER_ERRORMissing beneficiary account identifier and typePayment failed because the beneficiary’s unique account identifier and the identifier type are missing. Create a new beneficiary identity with this information in the CdtrAcct.Id.Othr field and try again.400
USR_160USER_ERRORMissing beneficiary account identifierPayment failed because the beneficiary’s unique account identifier is missing. Create a new beneficiary identity with this information in the CdtrAcct.Id.Othr.Id field and try again.400
USR_161USER_ERRORMissing beneficiary namePayment failed because the beneficiary identity doesn’t contain the beneficiary’s name. Create a new beneficiary identity with the required Cdtr.Nm field if the beneficiary is an institution, or the Cdtr.StrdNm field if the beneficiary is an individual and try again.400
USR_162USER_ERRORMissing beneficiary account identifier and typePayment failed because the beneficiary’s unique account identifier and the identifier type are missing. Create a new beneficiary identity with this information in the CdtrAcct.Id.Othr field and try again.400
USR_163USER_ERRORMissing beneficiary account identifierPayment failed because the beneficiary’s unique account identifier is missing. Create a new beneficiary identity with this information in the CdtrAcct.Id.Othr.Id field and try again.400
USR_166USER_ERRORIncorrect account numberPayment failed because the account number you provided doesn’t match the beneficiary’s account number.400
USR_169USER_ERRORUnable to find payment destinationPayment failed because the beneficiary’s account you specified could not be found. Try again with valid beneficiary information.400
USR_170USER_ERRORUnable to find payment destinationPayment failed because the beneficiary’s account you specified could not be found. Try again with valid beneficiary information.400
USR_171USER_ERRORIncorrect request data formatPayment failed because one or more fields in the request contain incorrectly formatted data. Try again with correctly formatted request parameters.400
USR_172USER_ERRORInactive beneficiary accountPayment failed because the beneficiary account you specified for this payment is inactive. Try again with a valid and active beneficiary account.400
USR_173USER_ERRORConflicting beneficiary name infoPayment failed because both Cdtr.Nm and Cdtr.StrdNm fields are populated in the beneficiary identity information. Only one of these fields must be present. If the beneficiary is an institution, specify only Cdtr.Nm. If the beneficiary is an individual, specify only Cdtr.StrdNm.400
USR_174USER_ERRORInvalid beneficiary account informationPayment failed because there are one or more errors in the beneficiary account information. Try again with valid beneficiary account information.400
USR_201USER_ERRORTransaction limit reachedPayment failed because you have already made {0} transactions in a 24-hr period. Try again later.400
USR_203USER_ERRORInsufficient creditPayment failed because the payment amount of {0} USD is higher than your available credit amount of {1} USD. If you recently paid an invoice, the available credit amount shown here may be subject to change.400
USR_204USER_ERRORInvoice past duePayment failed because you have a past-due invoice. If you have already submitted a payment confirmation, try again later or contact technical support.400
USR_205USER_ERRORInsufficient balancePayment failed due to insufficient balance. Add funds to your account and try again.400
USR_206USER_ERRORToo many pending direct debit transactionsPayment failed because you have too many pending direct debit transactions. Try again after some of the pending transactions are complete.400