{"componentChunkName":"component---src-templates-simple-markdown-js","path":"/introduction/concepts/api-payment-failures/","matchPath":"","result":{"data":{"markdownRemark":{"html":"<h1 style=\"position:relative;\"><a href=\"#payment-failures-with-the-api\" aria-label=\"payment failures with the api permalink\" class=\"anchor before\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a><div class=\"hidden-anchor\" id=\"payment-failures-with-the-api\"></div>Payment failures with the API</h1>\n<!-- Note: This snippet is used (embedded) in two other files: 'ui-payment-failures.md' and 'api-payment-failures.md' -->\n<p>If an in-progress payment fails, Ripple Payments Direct provides details about the failure so that you can take appropriate steps to recover from it. Additionally, it releases any funds that were reserved to complete the payment, and adds them back to your available balance.</p>\n<p>Payment failures can happen for a variety of reasons, some of which are user errors that you can fix, and others that require working with your Ripple liaison or technical services team to resolve. Ripple Payments Direct provides descriptive error messages to help you determine whether you can recover from the failure by simply retrying with the same information, or if you need to make other changes. <!-- For more information about error messages in the API, see [API errors](). --></p>\n<p>The following table lists some commonly occurring payment failures and suggestions for recovery. Note that this is not a complete list of failures that may occur. </p>\n<table>\n<thead>\n<tr>\n<th align=\"left\">Failure reason</th>\n<th align=\"left\">Failure details</th>\n<th align=\"left\">Suggested actions for failure recovery</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td align=\"left\">Insufficient funds</td>\n<td align=\"left\">The available balance in your account is less than the payment amount you specified in your payment request.</td>\n<td align=\"left\">Add funds to your account, request a new quote, and initiate a new payment.</td>\n</tr>\n<tr>\n<td align=\"left\">Past-due invoice</td>\n<td align=\"left\">Your account has a past-due invoice.</td>\n<td align=\"left\">Settle the past due invoice, request a new quote, and initiate a new payment.</td>\n</tr>\n<tr>\n<td align=\"left\">Transaction limit reached</td>\n<td align=\"left\">You have already reached the number of transactions you're allowed to make in a 24-hour period.</td>\n<td align=\"left\">When the next 24-hour period begins, request a new quote, and initiate a new payment.</td>\n</tr>\n<tr>\n<td align=\"left\">Transaction amount limit exceeded</td>\n<td align=\"left\">The payment amount you specified is higher than your account's transaction limit.</td>\n<td align=\"left\">Retry the payment with a payment amount that's lower than your account's transaction limit.</td>\n</tr>\n<tr>\n<td align=\"left\">Inactive beneficiary</td>\n<td align=\"left\">The payment beneficiary you specified is inactive.</td>\n<td align=\"left\">Retry the payment with a valid beneficiary ID.</td>\n</tr>\n<tr>\n<td align=\"left\">Mismatched identity</td>\n<td align=\"left\">The identity ID you provided for the payment beneficiary is not associated with a beneficiary-type identity.</td>\n<td align=\"left\">Retry the payment with an accurate beneficiary identity ID.</td>\n</tr>\n</tbody>\n</table>\n<!-- \nRemoving the \"credit limit reached\" failure scenario for now as it looks like RPD 2.0 customers are only pre-funded for the moment. \n| Credit limit reached | You've already reached your credit limit. Sufficient credit is not available to process the requested payment. | Contact technical support for more information.|\n\n-->","headings":[{"value":"Payment failures with the API","depth":1}]},"contentItem":{"data":{"lastModified":"2025-11-13T00:24:58.000Z","enableToc":null,"disableLastModified":null,"tocMaxDepth":null,"requestLogin":false}},"siteConfig":{"enableToc":false,"disableLastModified":true,"tocMaxDepth":4}},"pageContext":{"matchPath":"","id":"407cd847-d0a5-5754-819f-ac53c53e63ea__redocly content/introduction/concepts/api-payment-failures/","seo":{"title":"Payment failures with the API","description":null,"image":"","keywords":null,"jsonLd":null,"lang":null,"siteUrl":null},"pageId":"introduction/concepts/api-payment-failures.md","pageBaseUrl":"/introduction/concepts/api-payment-failures","type":"markdown","toc":{"enable":true,"maxDepth":4,"headings":[{"depth":1,"value":"Payment failures with the API","id":"payment-failures-with-the-api"}]},"data":{"title":""},"catalogInfo":null,"link":"/introduction/concepts/api-payment-failures/","sidebarName":"__root-sidebar__-data-69308394-sidebars.yaml","isLanding":false,"showPrevButton":null,"showNextButton":null,"apiVersions":null,"apiVersionId":null,"isDefaultApiVersion":null}},"staticQueryHashes":["1123603147","1302185487","1344209882","1398840060","1520077861","1975142765","2667623876","2950305614","3240152602","3743992808","561138138"]}