Skip to main content
When payments or transactions fail, you’ll receive an object containing the failure reason. Depending on when the failure occurs, this information is returned in the synchronous (API) or asynchronous (webhook) response. The following sections outline the reasons that each of these components might fail.

Payments

When a payment fails in CPN there are no further actions you can take with that payment ID. You should restart the payment workflow by requesting a new quote and accepting it to create a new payment. The payment failure notification includes a failure reason (listed below) and a failure code containing more specific information about the failure. The failure code provides information about how to resolve the issue and create a new payment.

Transactions

If an onchain transaction fails or becomes stuck, you can create a new transaction or attempt to replace or accelerate the transaction. You may continue to troubleshoot onchain transactions until the payment expires. Note that only one transaction can be associated with a given payment, so you must wait until the current transaction fails or attempt to replace it if you need to update the transaction.