Receiving events via Webhook works as follows:

Webhook is sent to notify the merchant Software Service that an new order event has happened on Keeta.
The merchant Software Service that implements this webhook, should return an HTTP 200 response code with an empty response body to acknowledge receipt of the webhook event. If Keeta does not receive a 200 acknowledgement response, than the webhook event will be resent based on Keeta policies.
Keeta Webhook Retry Policy The Keeta webhook retry policy is designed to ensure reliable delivery of webhook events. If the merchant Software Service does not acknowledge receipt of a webhook event with a 200 response, Keeta will retry sending the event up to 3 times. The retries will occur at intervals of 1 minute, 2 minutes and finally 3 minutes. If the merchant Software Service still does not acknowledge the event after these retries, the event will be considered undelivered.
Open Delivery will include security headers for all requests made to the merchant Software Service webhook URL.
Header Description
| Header | Description |
|---|---|
| X-App-Id | An Unique Identificator of Keeta |
| X-App-MerchantId | An Unique Identificator of the Merchant receiving the order |
| X-App-Signature | SHA256 hash of the request body, using the client secret as the key |
Webhook Security
Webhook messages are signed so that the merchant Software Service can verify that the sender is a valid Keeta. Webhooks requests contain an X-App-Signature header.