# Retry once the issuer or processor recovers

[Retry a payment](https://devportal.qa.winkpg.io/docs/decide/retry-a-payment.md): Whether a payment that didn't go through is worth sending again, and the request that sends it again without charging the customer twice.

Something between the platform and the issuer was unavailable. The card itself wasn't refused.

**Your answers so far**

- What came back from the payment? A decline from the card issuer or the processor.
- Which decline reason code did you get? An availability code.

**What to build**

Wait, then create the payment again as a new transaction under a new idempotency key. The Retry operation isn't offered for these codes, because the card networks only permit resubmitting a decline tied to the cardholder's funds or limits.

**Worth knowing**

- A new attempt needs a new idempotency key. A create that got an answer is replayed under its key for 48 hours, so resending with the old one hands you the same refused transaction.
- CB_OPEN means the platform suspended traffic to a processor that was failing and sent nothing. Retry after it recovers, not straight away.
- Back off between attempts. A burst of retries against an issuer that's down only lengthens the queue it's recovering from.

**Where to go next**

- [Understanding declines and rejections](https://devportal.qa.winkpg.io/docs/guides/understanding-declines-and-rejections.md)
- [Retry a payment without a double charge](https://devportal.qa.winkpg.io/docs/blueprints/retry-a-payment-safely.md)
- [Processor routing and failover](https://devportal.qa.winkpg.io/docs/guides/processor-routing-and-failover.md)

- [Start over](https://devportal.qa.winkpg.io/docs/decide/retry-a-payment.md): go back to the first question.

## See also

- [All documentation](https://devportal.qa.winkpg.io/llms.txt): the machine-readable index of every public page on this site.