Introduction
Webhooks are HTTP callbacks that deliver Swervpay event notifications to your application. When an event occurs, Swervpay sends an HTTPPOST request to the configured URL. Your endpoint should verify the delivery, enqueue or process it idempotently, and respond with a 2xx status code promptly.
You can subscribe to card, collection, customer, payout, wallet, and bill events. See the resource-specific pages for payload examples and event behavior.
Creating a Webhook
You can create a webhook from the dashboard or with the create webhook API. Use the edit webhook API to change its URL, description, or subscribed events.Contactless activation subscriptions
Contactless activation codes are confidential and are not sent to a webhook by default. To receive them, explicitly subscribe one enabled HTTPS webhook tocard.contactless.activation.
Create a subscribed webhook:
- Use HTTPS.
- Return a
2xxresponse. - Be the only enabled webhook subscribed to
card.contactless.activationfor the business.
Supplying
events when editing replaces the webhook’s stored event list. Include every event that should remain explicitly registered. Omitting events preserves the existing list.Authentication
All webhook requests include aX-SWERV-SECRET header for verification. It should match the secret generated when creating the webhook.
The confidential card.contactless.activation event uses an HMAC signature instead of X-SWERV-SECRET. See the card webhook documentation for its headers and verification procedure.
Retry
If a webhook fails, you have two main options to retry the failed delivery:- Retry from developer section of the dashboard
- Using webhook Retry API. You can inspect delivery status and response details with the webhook logs API.