Webhooks Error Handling & Testing

In this section you will find information on how to handle the error situations and how to test the webhook integration.

Error handling

We make our best to send webhooks reliably. To prevent errors, follow Best Practices. When things go weird, we resolve errors according to these rules:

• When response with HTTP status 4xx is received, we don’t retry the hook. This response status indicates that something is wrong with request body (invalid signature, old event etc…)

• When response with HTTP status 5xx is received or in case of request timeout, we retry the request after few seconds. The maximum number of retries is 5.

Currently, there is no way to retrieve unsent or failed hooks for a consumer. If there are any outages on consumer side, please, get the actual payment/order statuses via Payments/Orders API.

Testing

We recommend to test integration with hook consumer via Back Office.

On hook detail screen, client can create a test request with custom data and Everifin calls the hook endpoint. In Back Office, user sees the response status and body and can verify the response.

Custom data provided by the user (in text area) will be sent as data object as defined in the hook request structure. Request data will be enriched with metadata and headers automatically.