# Stop, and ask for another payment method

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

Presenting the same card again gets the same answer. Nothing your code can do changes this one.

**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? Any other code, or none at all.

**What to build**

Don't retry. Tell the customer the payment didn't go through and ask for a different payment method. Record the decline reason code against the order for your support team, and never show the customer the declineReasonDescription text: its wording can change without notice.

**Worth knowing**

- A card the issuer reports as lost or stolen must never be presented again.
- A decline the platform can't classify is treated as terminal on purpose. Stopping is the safe default for a retry decision.
- On a stored payment method, a terminal decline is the moment to ask the customer to update their card rather than to keep charging it.

**Where to go next**

- [Understanding declines and rejections](https://devportal.qa.winkpg.io/docs/guides/understanding-declines-and-rejections.md)
- [Simulate a card decline](https://devportal.qa.winkpg.io/docs/blueprints/simulate-a-card-decline.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.
