Dodo Payments webhook
Failed payments, disputes, renewals that need attention and refunds from Dodo Payments.
Setup
- In the Dodo Payments dashboard open Developer, then Webhooks, and add an endpoint. You get a signing key that starts with whsec_.
- In PingLoom open Webhooks, choose New webhook source, pick Dodo Payments, paste the signing key, choose the events and create it. Copy the endpoint URL.
- Paste the PingLoom URL as the endpoint URL in Dodo Payments and subscribe to payment, subscription, refund and dispute events.
- Send a test event from the Dodo dashboard. It appears under Recent requests on the PingLoom source page.
Verification
Dodo Payments follows the Standard Webhooks signing scheme. Each request carries webhook-id, webhook-timestamp and webhook-signature headers; the signature is HMAC-SHA256 over the id, the timestamp and the raw body with your whsec_ signing key. PingLoom rejects requests whose timestamp is more than five minutes off and uses webhook-id to drop repeats.
Events
You choose which events become alerts when you create the source, and you can change it later on the source page.
| Event | Priority | On by default |
|---|---|---|
| Payment failed | high | Yes |
| Dispute opened | high | Yes |
| Subscription on hold (renewal failed) | high | Yes |
| Subscription cancelled | normal | Yes |
| Refund processed | normal | Yes |
| Sales (payment succeeded) | low | No |
| Subscription active | low | No |
| Subscription renewed | low | No |
PingLoom keeps the amount, the payment, subscription and product ids and a masked email such as m***@example.com. Names and card details are never copied.