# Simulate a slow processor

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

Make the sandbox processor take its time, then make it answer later than your own client will wait.

**Your answers so far**

- What are you testing next? What my code does when a processor is slow or unavailable.
- What does the processor do? It answers, but slowly.

**What to build**

Run the processor latency blueprint, then the safe retry blueprint. The first proves your timeout fires; the second proves what you do next doesn't charge the customer twice.

**Worth knowing**

- A timeout in your client doesn't mean the payment failed. It may have completed, so look it up by its idempotency key before you resend.

**Where to go next**

- [Simulate processor latency](https://devportal.qa.winkpg.io/docs/blueprints/simulate-processor-latency.md)
- [Retry a payment without a double charge](https://devportal.qa.winkpg.io/docs/blueprints/retry-a-payment-safely.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.