Webhook

Webhooks are user-configured HTTP callbacks that are triggered when a specific event occurs. They allow two applications to communicate by automatically sending event information from one server to another. Unlike APIs, where you need to repeatedly check for updates, webhooks automatically provide real-time notifications whenever an event occurs. TransactBridge sends the event details to the Webhook URL configured by the merchant. These webhooks are sent as POST requests from the TransactBridge server. Authorization headers are also included so that partners can authenticate that the request originated from the TransactBridge server. Merchants can configure the Webhook URL from the TransactBridge Admin Panel to start receiving webhook events.

Admin Panel for Sandbox Navigate to callback Url’s section under the Account settings tab to configure the Webhook URL for sandbox environment.Admin Panel for Production Navigate to callback Url’s section under the Account settings tab to configure the Webhook URL for production environment.

Callback Response

Partners must respond to the webhook with the following JSON response and an HTTP 200 status code:

{
  "ack": true
}

Only the above response with an HTTP 200 status code will be treated as a successful acknowledgement of the webhook.
If the merchant does not acknowledge the webhook, TransactBridge will retry sending the webhook. A maximum of 3 attempts will be made.
If the partner fails to acknowledge the webhook after all 3 attempts, TransactBridge will stop sending subsequent retries for that event.
Partners can also resend the webhook from the Partner Dashboard if required.

Signature Verification

TransactBridge uses the same method to generate the signature that is included in the authorization headers. Partners should verify the signature before processing the webhook to ensure that the request originated from the TransactBridge server and that the payload has not been modified.

Sample Subscription Status

This webhook event is sent to the configured partner URL when the subscription has a status change. Subscription status can be PENDING, PENDING_EXPIRED, TRIAL, ACTIVE, PAUSED, EXPIRED, CANCELLED, FAILED.

"request":
{
"callbackType":"SUBSCRIPTION",
"status":"ACTIVE",
"quoteAmount":"15",
"tbId":"667946642f968332ee9a68e5",
"timestamp":"2026-08-26T06:30:07.953Z",
"currentPeriodStart":"2026-08-25T18:30:00.000Z",
"currentPeriodEnd":"2026-09-25T18:30:00.000Z"
"frequency":"MNTH",
"param1":string"",
"param2":string"",
"param3":string""
}

Sample Payment Mandate Status

This webhook is sent to the configured partner URL when a mandate status is changed.

"request":

{
    "callbackType": "MANDATE",
    "status": "CREATED",
    "tbId": "66ebde6d11107c5eb4a29699",
    "txnId":"68e8cf7db2b6d0610f8cd000",
    "subscriptionId": "68e8cf61b2b6d0610f8cd142",
    "timestamp": "2024-09-19T08:18:53.900Z",
    "payMethod": "UPI",
    "quoteAmount": "100"
}

Geting Started

Manage Subscription

Subs Invoices/ Pay Lifecycle

Subs Checkout

Test Your Subscription

Callback Response

Signature Verification

Sample Subscription Status

Sample Payment Mandate Status

​Callback Response

​Signature Verification

​Sample Subscription Status

​Sample Payment Mandate Status

Callback Response

Signature Verification

Sample Subscription Status

Sample Payment Mandate Status