Live delivery
The gateway queues a signed webhook after a live payment match or recognised reversal. Use the exact raw request body and the documented signature header to verify authenticity, check the timestamp and keep the signing secret on your server. Follow the API reference for the current signature format.
Acknowledge after durable acceptance
Persist the event ID and intended business operation before acknowledging delivery. A success response should mean your system has accepted responsibility for processing it. Use an internal worker for slow provisioning. Do not make receipt of one HTTP request synonymous with a successful router login.
Process duplicates safely
Keep a unique event-ID constraint in your integration. If the same valid event is redelivered, return the recorded outcome or acknowledge it without adding another package. Two receipts with different provider transaction IDs are separate payments even when amounts and timestamps are close.
Sandbox inspection
Sandbox events are retained for inspection and polling. They are not delivered to your live webhook. Use the event JSON to test local handler logic, then separately validate production signatures, retries, outage behaviour and provider receipt matching.
KEEP EXPLORING