Webhooks Configuration
Last updated
Last updated
is an HTTP endpoint that is used to receive notifications about events that occur in the Ottu system. For example, if a payment is created, Ottu can send a webhook notification to the merchant's server with the details of the payment. The merchant can then use this information to update their systems. Enhance your Ottu experience with our powerful Webhook Configuration. Take advantage of API payloads, SSL certificate verification options, error notifications, and more.
To access the Webhook Configuration, navigate to Ottu Dashboard > Administration Panel > Webhook > Webhook Config
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).
Imagine a scenario where the merchant’s server experiences downtime for 30 seconds. If the timeout is set to 20 seconds, the retries are set to 3, and the backoff factor is set to 5 seconds, then the following will happen: Keep in mind that the merchant’s server will take 30 seconds to respond, and the number of attempts is 3.
First Try:
Ottu's server will send a request to the merchant's server.
Ottu's server will wait 20 seconds for a response (timeout = 20), and this attempt will fail.
Then Ottu's server will wait 5 seconds for the backoff factor (backoff factor = 5).
Note that the first attempt took 25 seconds.
Second Try:
Ottu's server will retry the request, i.e., send another request.
After 5 seconds, the merchant's server will respond since the server downtime will be over (30 seconds), and the request will be successful.
Version: The version of the webhook API.
Enable webhook notifications: If checked, webhook notifications will be activated.
In this tab, the merchant can define the desired webhook behavior for specific plugins.
Description of Fields:
Enable transaction state webhook notifications: If checked, webhook notifications will be sent for the defined Notification status.
Delete: Deletes the defined plugin webhook configuration.
HMAC key: This key is used to .
Ignore SSL: If checked, the SSL certificate will not be verified when calling the .
Notify on Error: If checked, an email will be sent if an error occurs while calling the .
Email List: Specify the list of email addresses where the error notification should be sent.
Redirect behavior: The redirect behavior is determined by the response to payment events and payment operations.
If the webhook URL returns a status code of 200, the customer will be redirected to the .
Enable retry webhook mechanism: If checked, Ottu will retry the request if the first attempt fails. See the above for further clarity.
Operations webhook_url: The URL where transaction data will be disclosed once an operation transaction flow is triggered. See .
Enable webhook notifications if transaction initiated from API: If checked, will be activated even if the transaction is created via the API.
Webhook plugin: The plugin that the webhook works for. See
Webhook UrL: When a or occurs, Ottu sends an HTTP request to this URL to disclose transactional data.
Notification status: Define the transaction status that will trigger the including paid, failed, authorized, and canceled. Review the for more information.
The webhook_Url specified in the serves as the endpoint for receiving notifications related to both and . If we provide values for both the operation webhook_url and the webhook_Url in the plugin configuration, the system will transmit data to both URLs.
For more information about how and where webhook works in Ottu see .
