Message Notifications
This API provides a reliable interface to manually initiate message notifications for a specific transaction, based on either a provided session_id or order_no. It is particularly useful in scenarios where message notifications—such as SMS, email, or WhatsApp—have not been delivered as expected, often due to issues with third-party services. Additionally, the API is helpful when customer contact information (email or phone number) has been updated, and you want to ensure the customer receives the relevant transaction message notifications again. By using this API, you can ensure that once the issue is resolved or contact details are updated, message notifications can be promptly sent to the customer without requiring a new transaction.
Benefits:
Error Recovery: Allows businesses to resend message notifications after resolving issues with SMS gateways, email providers, or WhatsApp services.
Seamless Customer Communication: Ensures that customers receive critical transaction updates, enhancing the overall payment experience.
Manual Control: Offers manual flexibility for cases where automatic message notifications have failed or been delayed.
Contact Information Updates: Enables re-notifying customers when their email or phone details have been changed.
For further information about the message notification channels that Ottu empowers merchants with, please refer to the Notification Communication Channels section.
Before you can integrate with Ottu's Message Notifications API
, several prerequisites must be fulfilled. These are essential to ensure the API functions correctly and securely.
Checkout API Integration: Prior to using the
Message Notifications API
, you must create a payment transaction via the Checkout API. This step captures vital transaction details, such as:Customer Data: Information like customer_phone for SMS and WhatsApp, and customer_email for Email message notifications is collected.
Optional Order Number: The order_no may also be provided as an alternative reference for the required transaction.
Upon successful creation of the payment transaction, a session_id is generated. This
session_id
or theorder_no
(if provided) becomes a key parameter for sending the message notifications using theMessage Notifications API
.Templates Configuration: Ensure that all relevant message notifications templates (for SMS, email, WhatsApp, etc.) are pre-configured. The Ottu support team can assist with this setup to ensure that message notifications follow your desired format.
Enabling Message Notifications Channels: When creating the payment transaction, enable the required message notification channels (e.g., SMS, email, WhatsApp).
If the transaction is created via the
Checkout API
, message notifications parameters should be provided within the API call.Alternatively, if the transaction is created from the Ottu dashboard, ensure that the designated checkbox for enabling message notifications is selected.
Valid Payment States for Sending Message Notifications: The
Message Notifications API
can only be used for certain payment transaction states. Message notifications can be sent via the following channels for specific payment states:Email:
created
paid
canceled
failed
expired
authorized
voided
refunded
captured
SMS:
created
paid
canceled
failed
expired
authorized
voided
refunded
capture
WhatsApp:
created
paid
canceled
failed
expired
authorized
Optional: SMS Notification Channel If SMS message notifications are required, an SMS provider should be configured for your account. Contact the Ottu support team for assistance with configuring the SMS provider.
Optional: Integrated WhatsApp Channel The following requirements must be met:
WhatsApp Business Account: The merchant must have a registered WhatsApp Business account.
Template Approval: All WhatsApp templates and their content must be pre-approved by Meta/WhatsApp before being used for message notifications.
WhatsApp Integration Authenticator: This acts as the link between WhatsApp and Ottu. Contact the Ottu support team for assistance in configuring the integration.
Supported Methods
For Further information, please refer to the Authentication section.
The Message Notifications API
allows merchants to manually resend message notifications for specific transactions, following a structured process. Here's how it works:
Obtain session_id or order_no: Once the payment transaction is initiated via Ottu dashboard or
Checkout API
and all setup requirements are fulfilled, the merchant will take the generatedsession_id
or the providedorder_no
(if applicable). These identifiers are crucial parameters for theMessage Notifications API
.Send Request via
Message Notifications API
: The merchant sends a request to theMessage Notifications API
, including the following key parameters:session_id
ororder_no
: To identify the transaction for which the message notifications should be sent.Notification Channels: The merchant specifies the required channels (e.g., SMS, email, WhatsApp) through which the message notifications should be sent.
Follow these guidelines to send message notifications for specific payment states using the Message Notifications API
.
Initiating the Transaction: Ensure that all setup requirements are implemented and provide the necessary request payload parameters via the Checkout API. Here's an example of a transaction initiation request:
This initiates the transaction and sets up message notifications across the specified channels (email, SMS, and WhatsApp) for the listed states.
Send Message Notifications for
created
State: Once the transaction has been initiated, obtain the generatedsession_id
or use the providedorder_no
(in this example,order_no
:example_order_no
). To send the message notifications for thecreated
state, use the following request payload to specify the message notifications channels:
This request will send message notifications via the specified channels (SMS, email, WhatsApp) for the transaction linked to order_no
.
Successful Message Notifications Response: If the customer is successfully notified, the merchant will receive the following response payload:
Re-send Message Notifications for the Same or Different States:
Merchants can notify the customer for the same payment state (e.g.,
created
) as many times as needed.To notify the customer for the same or different state, repeat the process outlined in Step 2, using the same
order_no
orsession_id
of the origin transaction.
To ensure optimal use of the Message Notifications API
, follow these best practices to improve efficiency, security, and reliability in your message notifications process:
Ensure Setup Requirements Are Complete: Before sending message notifications, confirm that:
All necessary message notifications templates (SMS, email, WhatsApp) are configured properly.
Message notification channels are enabled during the transaction setup via the
Checkout API
or Ottu Dashboard.SMS and WhatsApp providers are configured in advance with the help of the Ottu support team, especially for critical channels like WhatsApp Business
Leverage order_no for Consistency: Whenever possible, use the
order_no
to send message notifications, especially if it is consistent across multiple systems. This can help maintain uniformity across different services and databases, ensuring message notifications are tied to a well-understood reference.Validate Payment States Before Sending Message Notifications: Only send message notifications for valid payment states, as per the following rules:
Email & SMS: Supported for all payment states such as
created
,paid
,canceled
,failed
, etc.WhatsApp: Supported only for select states (e.g.,
created
,paid
,authorized
).
Ensure that the state you're notifying about matches the appropriate channel capabilities.
Avoid Redundant Message Notifications: While the API allows you to notify the customer for the same payment state multiple times, it is recommended to avoid redundant notifications unless necessary (e.g., only resend notifications if prior communication failed or needs verification). Overuse can lead to customer frustration and unnecessary SMS or email costs.
Handle Response and Errors Gracefully: Always check the API response to ensure the message notifications was successfully sent. If the response indicates an error or failure (e.g., issues with a third-party service like an SMS gateway), build in retry mechanisms or alerts for your team to address the issue promptly.
Secure the API Requests:
Use proper authentication (e.g., API keys, public/private key pairs) to safeguard your message notifications API requests.
Ensure HTTPS is used for all API communications to prevent data interception.
Security is paramount when sending customer-related message notifications containing sensitive transaction data.
Test Message Notifications Before Going Live: Before enabling the
Message Notifications API
in your production environment, thoroughly test message notifications across all intended channels (SMS, email, WhatsApp). Use test transactions and confirm receipt to ensure all message notification templates and channels function as expected.Monitor Third-Party Message Notification Services: Stay proactive by monitoring the health and performance of third-party message notification services (SMS, email, WhatsApp) that your system relies on. Ensure any outages or issues are promptly identified and resolved to prevent missed customer message notifications.
The Message Notifications API
allows merchants to manually resend message notifications for a specific transaction based on session_id
or order_no
. It is useful when message notifications (e.g., SMS, email, WhatsApp) have failed due to issues with third-party providers and need to be resent.
To send a message notification, you need to provide:
Either the
session_id
ororder_no
of the transaction.A list of the message notifications channels you want to send (e.g., SMS, email, WhatsApp).
Message notifications can only be sent for certain payment states, depending on the channel:
Email & SMS: Message Notifications can be sent for
created
,paid
,canceled
,failed
,expired
,authorized
,voided
,refunded
,captured
states.
WhatsApp: Message notifications can only be sent for
created
,paid
,canceled
,failed
,expired
,authorized
There is no limit on how many times you can send a message notification for the same state. However, it's recommended to avoid redundant message notifications unless necessary (e.g., a prior message notification failed).
If the customer is successfully notified, the API will return the following response:
Yes, as long as the order_no
or session_id
is available, message notifications can be sent. However, message notifications and channels should have been properly set up during the transaction creation.
If a message notification doesn't get delivered (due to third-party issues with SMS, email, or WhatsApp providers), you can manually send it again using the Message Notifications API
once the issue is resolved. Additionally, ensure that third-party providers are correctly configured.
To configure your SMS or WhatsApp provider, contact the Ottu support team for assistance. They will help set up the necessary integrations for sending message notifications through these channels.
Yes, you can specify multiple channels (e.g., [sms
, email
, whatsapp
]) in a single API call to send message notifications via multiple platforms simultaneously.
Last updated