Payment webhooks
Paydot posts a signed event to your server when a payment reaches a final status. This lets you release an order without polling.
Webhooks tell you how a payment ended. To start one, see Generate a payment link.
Configure an endpoint
Section titled “Configure an endpoint”An account owner sets the endpoint under Online Payments in the Paydot portal. Paydot generates a
signing secret at the same time, beginning whsec_.
The endpoint must meet these requirements:
- Use HTTPS on port 443 over TLS 1.2 or 1.3. The URL cannot contain credentials, a query string or a fragment.
- Resolve to a public address. Private, loopback and reserved ranges are rejected.
- Be the final URL. Paydot does not follow redirects.
Test before you go live
Section titled “Test before you go live”Use Send test event in the portal to exercise your integration before a real payment exists. A test
event has the same shape as a real one, but its type is webhook.test and its ids are prefixed
evt_test_, so it cannot be mistaken for a payment that actually happened.
Next steps
Section titled “Next steps”| Page | What it covers |
|---|---|
| The event | Payload, field reference and the status vocabulary |
| Verifying signatures | HMAC verification, with Node, Python, PHP and Java examples |
| Responding | Response deadline, idempotency and ordering |
| Delivery and retries | What happens when your endpoint is down |
| Rotating the secret | Rolling a new secret without dropping events |
| Versioning | What can change without warning |
| Troubleshooting | Mapping a failed delivery to its cause |