See when a payment method issuer has instructed us not to retry
Distinguish between declined payments where the issuer has told us a payment should not be retried, and declined payments with no further information.
What's new?
We added a new declined_not_retryable allowed value for the transaction.payments[].error_code field. It's set by Paddle when a payment attempt fails because it's declined, and the issuer indicated it should not be retried.
Reason why a payment attempt failed. Returns null if payment captured successfully.
How it works
The error_code field against a transaction payment attempt gives you more information about why a payment attempt failed. It's set by Paddle.
When a payment declines, sometimes issuers indicate that the payment method should not be retried. Previously, we returned the error code for these kinds of failures as declined. Now, we return a new declined_not_retryable error code.
Issuers may return declined_not_retryable where payment method accounts are closed, or where a customer revoked authorization to charge a payment method.
Summary of changes
This is a summary of the changes to fields in the Paddle API and webhooks:
transaction.payments[].error_code | Change | New declined_not_retryable allowed value added. |
Next steps
This change is available in version 1 of the Paddle API.
It's a non-breaking change, meaning it doesn't impact existing integrations.
You can work with transactions using the API to see the new allowed value.
