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
| Code | Type | Title | Description | Status |
|---|---|---|---|---|
| USR_062 | USER_ERROR | Transaction limit reached | Payment failed because you have already made the maximum number of transactions in a 24-hr period. Try again later. | 402 |
| USR_064 | USER_ERROR | Credit limit reached | Payment failed because you have already reached your credit limit. | 402 |
| USR_066 | USER_ERROR | Invoice past due | Payment failed because you have a past-due invoice. If you have already submitted a payment confirmation, try again later or contact Ripple technical support. | 402 |
| USR_067 | USER_ERROR | Insufficient balance | Payment failed due to insufficient balance. Add funds to your account and try again. | 402 |
| USR_151 | USER_ERROR | Invalid identity information | Payment 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_152 | USER_ERROR | Conflicting beneficiary name info | Payment 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_166 | USER_ERROR | Incorrect account number | Payment failed because the account number you provided doesn’t match the beneficiary’s account number. | 400 |
| USR_169 | USER_ERROR | Unable to find payment destination | Payment failed because the beneficiary’s account you specified could not be found. Try again with valid beneficiary information. | 400 |
| USR_171 | USER_ERROR | Incorrect request data format | Payment failed because one or more fields in the request contain incorrectly formatted data. Try again with correctly formatted request parameters. | 400 |
| USR_172 | USER_ERROR | Inactive beneficiary account | Payment failed because the beneficiary account you specified for this payment is inactive. Try again with a valid and active beneficiary account. | 400 |
| USR_173 | USER_ERROR | Conflicting beneficiary name info | Payment 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_201 | USER_ERROR | Transaction limit reached | Payment failed because you have already made the maximum number of transactions in a 24-hr period. Try again later. | 400 |
| USR_203 | USER_ERROR | Insufficient credit | Payment failed because the payment amount exceeds your available credit. If you recently paid an invoice, your available credit may not yet reflect the payment. | 400 |
| USR_204 | USER_ERROR | Invoice past due | Payment failed because you have a past-due invoice. If you have already submitted a payment confirmation, try again later or contact Ripple technical support. | 400 |
| USR_205 | USER_ERROR | Insufficient balance | Payment failed due to insufficient balance. Add funds to your account and try again. | 400 |
| USR_206 | USER_ERROR | Too many pending direct debit transactions | Payment failed because you have too many pending direct debit transactions. Try again after some of the pending transactions are complete. | 400 |