Webhooks
Config.money sends webhook events to notify you of important payment lifecycle events. Configure your webhook endpoint in your merchant dashboard to receive these events.Endpoint
Headers
Each webhook request includes the following headers:X-Config-Signature header contains a timestamp and signature that you can use to verify the webhook’s authenticity.
Event Types
Schedule Events
schedule.setup_success
Sent when a customer successfully sets up a collection schedule.
schedule.setup_failed
Sent when a customer fails to set up a collection schedule.
Collection Events
collection.success
Sent when a collection is successfully made from the customer’s account to your merchant wallet.
collection.failed
Sent when a collection fails.
Settlement Events
settlement.success
Sent when funds are successfully settled from your merchant wallet to your destination account.
settlement.failed
Sent when a settlement fails.
Response
Your webhook endpoint should return a 200 OK response to acknowledge receipt of the webhook. If we don’t receive a 200 OK response, we’ll retry the webhook delivery.Retry Policy
If your webhook endpoint is unavailable or returns an error, we’ll retry the delivery with the following schedule:- 1 minute after the first failure
- 5 minutes after the second failure
- 15 minutes after the third failure
- 30 minutes after the fourth failure
- 1 hour after the fifth failure
Security
To verify the authenticity of webhooks, you should:- Check the timestamp in the signature header to ensure the webhook is recent
- Verify the signature using your webhook secret