Global Webhooks Configuration

General webhook configuration.

After accessing the Webhook Configuration section, the first tab you’ll encounter is General. In this section, merchants can configure their webhook settings according to their preferences by completing the fields below.

Parameters Description:

• HMAC key:

  This key is used to generate signatures.

• Ignore SSL:

  If checked, the SSL certificate will not be verified when calling the webhook URL.

• Notify on Error:

  If checked, an email will be sent if an error occurs while calling the webhook URL.

• Email List:

  Specify the list of email addresses where the webhook URL error notification should be sent.

• Timeout:

  The amount of time that the Ottu server will wait for a response from the merchant server.

• Retries:

  The number of retry attempts the Ottu server will make to resend the request to the merchant server if the first attempt fails. Note that the Enable retry webhook mechanism option should be checked to activate this feature.

• Backoff factor:

  The amount of time the Ottu server will wait before retrying the request (i.e., the time between two attempts).

---

Enhanced Scenario: Managing Server Downtime with Retry Logic

Consider a scenario in which the merchant’s server experiences a temporary downtime lasting 30 seconds. With a timeout duration of 20 seconds, a retry limit set at 3 attempts, and a backoff factor of 5 seconds, the following sequence of events will unfold:

Key Details to Remember:

• The merchant’s server will take a total of 30 seconds to become responsive.

• The retry mechanism allows for 3 attempts in total.

First Attempt:

• Ottu's server initiates a request to the merchant's server.

• Ottu's server waits for up to 20 seconds for a response (configured timeout = 20 seconds). Since the merchant’s server is still down, this attempt will fail due to timeout.

• Ottu's server pauses for 5 seconds before the next attempt (backoff factor = 5 seconds).

Time Elapsed After First Attempt: 25 seconds (20 seconds waiting + 5 seconds backoff).

Second Attempt:

• Ottu's server makes a second request to the merchant’s server.

• As the 5-second backoff has completed, and the server downtime (30 seconds) has passed, the merchant's server is now responsive.

• This second request succeeds, completing the process successfully.

This scenario illustrates how the retry logic with defined timeouts and a backoff factor ensures resilience during temporary server unavailability, helping to mitigate potential disruptions in the payment process.

---

• Version:

  The version of the webhook API.

• Enable retry webhook mechanism? If checked, the retry webhook mechanism becomes operational, permitting Ottu to make multiple attempts to reach the webhook URL if a timeout occurs. If this feature is disabled, no further retries will occur, which could lead to some webhook calls being missed.

• Enable webhook notifications:

  If checked, webhook notifications will be activated.

---

Redirect behavior:

The redirect behavior is determined by the webhook URL response to payment events and payment operations.

• If the webhook URL returns a status code of 200, the customer will be redirected to the redirect_url.

• If the webhook URL returns a status code of 201, the customer will be redirected to the Ottu payment summary page.

• If the webhook URL returns any other status code, the customer will be redirected to the Ottu payment summary page. In this case, Ottu can send an email notification if the Enable webhook notifications option is checked.

---

• Enable retry webhook mechanism:

  If checked, Ottu will retry the request if the first attempt fails. See the Example above for further clarity.

• Operations webhook_url:

  The URL where transaction data will be disclosed once an operation transaction flow is triggered. See Operation Webhook Notification.

If both the Operation webhook_url in the Global Webhooks Configuration and the Webhook URL in the Webhook Plugin Configurations are provided simultaneously, the system will transmit data to both URLs.

• Enable webhook notifications if transaction initiated from API:

  If checked, Payment Webhooks will be activated even if the transaction is created via the API.