# What came back from the payment?

[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.

Each of these is retried differently, and some aren't retried at all. Read the resultCode on the response, or the HTTP status when there's no transaction.

**Choose one**

- [Nothing. The request timed out or the connection dropped.](https://devportal.qa.winkpg.io/docs/decide/retry-a-payment/ask-before-you-resend.md): You don't know whether the payment happened.
- [A failure. The platform couldn't complete the request.](https://devportal.qa.winkpg.io/docs/decide/retry-a-payment/send-a-new-payment-once-the-fault-clears.md): The resultCode names a fault, such as TimeoutWaitingForProcessorResponse.
- [A decline from the card issuer or the processor.](https://devportal.qa.winkpg.io/docs/decide/retry-a-payment/which-decline-reason-code.md): The resultCode is Decline, or another refusal value.
- [A refusal by the merchant's own rules.](https://devportal.qa.winkpg.io/docs/decide/retry-a-payment/change-the-request-before-sending-it-again.md): A policy rejection, a review decline, or a 403 screening stop.

- [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.