Icone PayDocsDelivery & Retries
How we keep delivering events even when your endpoint is temporarily down.
Automatic Retries
We attempt delivery immediately. If your endpoint returns a non-2xx status or times out, the event is queued and retried automatically — you don't need to do anything to receive it once your endpoint recovers.
Backoff Schedule
Retries use exponential backoff over roughly nine hours before an event is considered undeliverable:
| Attempt | Delay after previous |
|---|---|
| 1 | immediate |
| 2 | 1 minute |
| 3 | 5 minutes |
| 4 | 30 minutes |
| 5 | 2 hours |
| 6 | 6 hours |
Dead Letter and Resend
After the final attempt, an event is marked exhausted and kept in your dashboard under the route's Webhooks view. Once your endpoint is healthy, hit Resend to deliver it again. Because deliveries are persisted, nothing is silently lost.
Tip
Pair retries with signature verification and idempotency on
orderId — together they make your integration resilient to both outages and duplicate deliveries.