API ReferenceWebhooks
Retry Policy
How Buvei retries failed webhook deliveries.
A delivery is considered failed when your endpoint:
- Returns a non-
2xxHTTP status, or - Does not respond within 10 seconds, or
- Closes the connection before sending headers.
Schedule
| Attempt | Delay after previous |
|---|---|
| 1 | — (immediate) |
| 2 | 1 minute |
| 3 | 5 minutes |
| 4 | 30 minutes |
| 5 | 1 hour |
| 6 | 2 hours |
| 7 | 2 hours |
After 7 failed attempts, the event is marked failed and Buvei stops retrying.
Final retries are spaced hours apart specifically so you can recover from extended incidents. If your endpoint is offline for an hour, you will still receive every event without manual replay.
After all retries fail
There is no automatic catch-up. Reconcile by listing card transactions (GET /cards/{cardId}/transactions) or querying KYC status (GET /kyc/cardholders/{id}) for the time range you missed.
If you anticipate downtime, ask your representative to pause webhook delivery — paused events are queued and resume from the front of the queue when delivery is re-enabled.