Polling an API every few seconds to check for new transactions is wasteful and slow. Webhooks flip the model: the loyalty platform pushes events to your system the moment they happen.
How Webhooks Work
You register a URL endpoint with the loyalty platform. When an event occurs (transaction, tier change, redemption), the platform sends an HTTP POST to your endpoint with event details. Your server processes it and responds with a 200 status.
Common Webhook Events
- transaction.completed — a customer made a purchase; update your analytics in real-time
- tier.changed — a customer levelled up; trigger a congratulations email
- reward.redeemed — a reward was claimed; update inventory or fulfilment
- wallet.topup — funds were loaded; reconcile your accounting system
- customer.created — new loyalty member; sync to your CRM
Best Practices
- Verify signatures — always validate the webhook signature to prevent spoofed events
- Respond fast — return 200 immediately, process asynchronously. Webhook timeouts are typically 5-10 seconds
- Handle retries — implement idempotency. Webhooks may be delivered more than once
- Log everything — store raw webhook payloads for debugging and audit