# Trigger a partial approval

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

Send a sale the sandbox approves for less than you asked for, so your code has to read the authorized amount instead of assuming it.

**Your answers so far**

- What are you testing next? What my code does when a payment is refused or comes back.
- Which refusal do you need to see? An approval for less than I asked for.

**What to build**

Run the partial approval blueprint, and decide what your checkout does with the shortfall: collect the rest on another payment method, or cancel the partial approval and ask for a different card.

**Worth knowing**

- A partial approval that nobody acknowledges is voided automatically. Treat it as a state your checkout has to resolve, not as an approval.

**Where to go next**

- [Trigger a partial approval](https://devportal.qa.winkpg.io/docs/blueprints/trigger-a-partial-approval.md)
- [Transaction lifecycle and settlement](https://devportal.qa.winkpg.io/docs/guides/transaction-lifecycle-and-settlement.md)

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