Webhooks

Inbound: your payment gateway #

AVRA receives webhooks from your payment gateway, at a signed URL unique to your brand and your gateway — /api/public/payouts/{provider}/webhook/{brand_id} — so that a reward payout's final state comes from the gateway rather than from polling. Every payload is signature-verified, and an unsigned or wrongly signed one is rejected. We have written the tests that prove an empty credential cannot verify anything, because at one point it could.

Outbound: not yet #

Outbound webhooks — AVRA calling your system when a code is scanned, a warranty is registered or a claim is held — do not exist yet. They are the most-requested integration. If you need one now, the honest interim is a scheduled CSV export or a polled read of the dashboard endpoints; say so and we will help you set it up.

Last reviewed 18 Sep 2026 · Something wrong? connect@avrascan.com