# Receive and verify a webhook

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

Stand up a receiver, subscribe it to transaction events, and prove the delivery that arrives came from this platform.

**Your answers so far**

- What are you testing next? The events my systems receive after a payment.

**What to build**

Run the webhooks blueprint. It registers your endpoint as a signed destination, sends a test delivery, subscribes to the transaction events, and triggers a sandbox sale, so you see a real delivery and verify its signature.

**Worth knowing**

- Delivery is at least once. Test that a repeated event id is ignored, not applied twice.
- Acknowledge within five seconds and process afterward, because a slow acknowledgement is retried.

**Where to go next**

- [Receive and verify webhooks](https://devportal.qa.winkpg.io/docs/blueprints/receive-and-verify-webhooks.md)
- [Webhooks quickstart](https://devportal.qa.winkpg.io/docs/guides/quickstart-webhooks.md)
- [Webhook integration](https://devportal.qa.winkpg.io/docs/guides/webhook-integration.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.