Key considerations
For every event that happens on Fintoc, Fintoc sends aPOST request with a JSON body to every registered webhook endpoint. From that request, you can parse the whole event detail using the JSON body.
Your webhook endpoint must receive the POST request and parse the event. It then responds with any status code in the 2xx range.
Saving the received event
Every event sent by Fintoc as a webhook has a uniqueid. At a minimum, save the id corresponding to each event in your application’s database. Saving the event id lets you ensure idempotency for received events.
Return a 2xx status code before the timeout
To confirm receipt of an event, respond with a 2xx HTTP status code. Fintoc treats any other status code as a failed attempt.
Respond with a 2xx status code before Fintoc’s delivery timeout. Run any heavy logic your handler triggers asynchronously so the handler returns before the timeout.
Retries and failure handling
Fintoc treats a delivery as a failed attempt if your endpoint responds with any status code outside the2xx range, or if the request times out.
When a delivery fails, Fintoc automatically retries it using exponential backoff, starting 3 seconds after the failed attempt. Fintoc retries an event up to 17 times before giving up.
If every attempt fails, Fintoc stops retrying that event. Keep in mind:
- Fintoc does not disable the webhook endpoint automatically, and does not notify you when it stops retrying an event.
- Fintoc does not support manual replay or a dead-letter mechanism to resend a failed event.