# What does the processor do?

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

A slow answer tests your timeout. A processor that won't process tests the platform's failover, and what reaches you when it runs out of options.

**Your answers so far**

- What are you testing next? What my code does when a processor is slow or unavailable.

**Choose one**

- [It answers, but slowly.](https://devportal.qa.winkpg.io/docs/decide/choose-what-to-test/simulate-a-slow-processor.md): Slower than your own client is willing to wait.
- [It refuses to process the payment.](https://devportal.qa.winkpg.io/docs/decide/choose-what-to-test/exercise-failover.md): The merchant has another processor to fall back to, or doesn't.

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