Payment Notification
The Ottu payment system provides a webhook designed specifically for payment events, including authorization, purchase, failed, canceled, and error. Whenever any of these payment events occur, Ottu will automatically trigger the webhook, sending a JSON payload to the specified webhook_url provided in the Checkout API. This JSON payload includes all relevant payment event results, payment details, and payment gateway responses, allowing merchants to receive and process this information in real-time, and to update their own systems accordingly.
By integrating with Ottu's payment webhook, merchants can streamline their payment processes and enhance their payment workflows. With publicly documented details and straightforward integration instructions, developers can seamlessly integrate Ottu's payment system into their own applications and online stores. Ultimately, the Ottu payment webhook provides a reliable, secure, and efficient way for merchants to manage their payment processing, enabling them to focus on growing their business and serving their customers.
The initial amount of the payment transaction. See amount Must be positive Max length: 24 Min value: 0.01
The merchant should always check if the received amount from Ottu side is the amount of the order, to avoid user changing the cart amount in between.
Indicates whether to capture delivery address It will be present only if the merchant includes it during the creation of the transaction.
Indicates whether to capture delivery location It will be present only if the merchant includes it during the creation of the transaction.
The currency code of the payment transaction For more details, https://en.wikipedia.org/wiki/ISO_4217 3 letters code
Where to pass the customer’s email address Have to be a valid email address It will be present only if the customer includes it while making the payment of the transaction. Max length 128
For the customer's first name It will be present only if the customer includes it while making the payment of the transaction. Max length 64
Customer ID is created by a merchant, and stored in the merchant database It will be present only if the merchant includes it during the creation of the transaction. Max length 64
For the customer's last name It will be present only if the customer includes it while making the payment of the transaction. Max length 64
Where to pass the customer’s phone number It will be present only if the customer includes it while making the payment of the transaction Max length 32
The extra information for the payment details, which the merchant has sent it in key value form. The presence of the element will depend on whether the merchant includes it during transaction creation by adding each element from the plugin field configuration. For example:
It represents a markup amount on the original amount. It will only be present if the merchant adds it in the currency configuration and includes it during the transaction creation. Must be positive Max length: 24 Min value: 0.01
The code of the payment gateway used to proceed the payment Max length 16
The name of the payment gateway used to proceed the payment Max length 64
It will contain the raw payment gateway response sent by the payment gateway to Ottu It will only be present in response to the PG's callback request for the transaction.
This object contains information about the user who created the transaction from Ottu side, specifically, the user who generated the payment URL It will only be present if the merchant includes the initiator ID in the payload when creating the transaction
Whether the transaction was carried out in a sandbox environment. It will only be present when PG's setting configured as sandbox
A message indicating the cause of a payment attempt failure., which is directly related to the payment attempt itself It will only be present if a payment attempt records an error. Max length 255.
Merchant unique identifier for the transaction such like : ABC123_1, ABC123_2 Max length 128
It is the amount that is credited to the merchant's bank account It will only be present if a capture action is being processed on the transaction and the paid amount is recorded Must be positive Max length: 24 Min value: 0.01
It is a unique identifier for the payment attempt, which can be used as a tracking identifier Max length 128
The payment amount paid back from the merchant to the customer. It will only be present if a refund action is being processed on the transaction and the refunded amount is recorded. Must be positive Max length: 24 Min value: 0.01
The amount remaining to be paid in the transaction. (amount – settled amount) Must be positive It will only be sent if the editable amount option is turned on. Max length: 24 Min value: 0.01
Could be "success", "pending", "failed", "canceled", "error", and "cod". See payment transaction states Max length 50
Ottu unique identifier which gets generated when the transaction is created. It can be used to perform subsequent operations, like retrieve, acknowledge, refund, capture, and cancelation Max length 128
Is the amount with the same currency of the initiating amount,
For editable amount: It is the amount that the customer enters at the checkout page
For non-editable amount: The settled amount is the same value as the original payment amount
It will be present only if transaction is paid, authorized or cod
It is one of the Payment transaction state. And could one of the below: created, pending, attempted, authorized, paid, failed, canceled, expired, invalided, or cod. Max length 50
The ID of the transaction log associated with the transaction. Max length 32-bit String (2^31 - 1) It will be sent only if transaction type is BULK as it's a bulk identifier.
The payment amount resulted by performing void operation It will only be present if a void action is being processed on the transaction and the voided amount is recorded Must be positive Max length: 24 Min value: 0.01
Last updated