# Which refusal do you need to see?

[Choose what to test in the sandbox](https://devportal.qa.winkpg.io/docs/decide/choose-what-to-test.md): Which sandbox scenario proves the part of your integration you're about to ship, and the blueprint that runs it.

Each one arrives in the response body, not as a transport error, and each one is read from a different field.

**Your answers so far**

- What are you testing next? What my code does when a payment is refused or comes back.

**Choose one**

- [A card decline.](https://devportal.qa.winkpg.io/docs/decide/choose-what-to-test/simulate-a-decline.md): The issuer refuses the payment outright.
- [An approval for less than I asked for.](https://devportal.qa.winkpg.io/docs/decide/choose-what-to-test/trigger-a-partial-approval.md): Common on prepaid and debit cards with a low balance.
- [An address or security code that doesn't match.](https://devportal.qa.winkpg.io/docs/decide/choose-what-to-test/drive-address-and-security-code-results.md): The payment may still be approved, and your code has to notice.
- [A bank debit that comes back.](https://devportal.qa.winkpg.io/docs/decide/choose-what-to-test/simulate-an-ach-return.md): An ACH return, which arrives after the debit looked successful.

- [Start over](https://devportal.qa.winkpg.io/docs/decide/choose-what-to-test.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.