Events

We trigger webhooks for the below mentioned events. Their respective trigger condition is also mentioned to help you better understand their usecase.

Event type	Trigger condition
application.created	On loan agreement generation. User will have to sign the same with OTP verification.
application.submitted	Once agreement is accepted by the user (by verifying OTP)
application.approved	On application approval by the lender.
disbursement.approved	Once the disbursement request is approved by the lender.
disbursement.success	Once the lender approves and initiates the funds disbursement from their bank. It could still take some time for funds to reach the user's bank account.
disbursement.success (mocked)	for partners, where controlled disbursement is enabled, disbursement.success webhook will be shared with an additional `isMocked: Boolean` field in the payload. This denotes that setup for the controlled disbursement is ready and partner can enable the servicing dashboard at this stage for the user.
payment.auto_debit.failed	If interest auto-debit failed, this webhook will be delivered each day until bounced interest is repaid, and accounted by lender
loan.ltv_breach.triggered	On detection of LTV breach (margin shortfall)
loan.closure_requested	On loan closure request shared with lender
loan.closed	Once loan is successfully closed by lender, and the status reflects in SOA.
user.created	In case loan application flow was triggered in Guest mode (without creating unity user first), whenever user submits their PAN in gateway flow, a unity user gets created.
application.feedback	When a user is required to perform additional action, after submitting the loan action. This can happen if lender shares a remark.
application.status_update	Triggered on loan application or active loan's status change. Mirrors loan status api response.

Webhook payloads

You can expect to receive the following payloads for the above mentioned event types.

{
  "userId": "507f1f77bcf86cd799439011",
  "lid": "507f1f77bcf86cd799439012",
  "lender": "bajaj_finserv",
  "assetType": "STOCKS",
  "type": "application.created",
  "requestId": "WH-64f1abc23ef4cd5678",
  "data": {
    "requestedLoanLimit": 12000
  }
}

{
  "userId": "507f1f77bcf86cd799439011",
  "lid": "507f1f77bcf86cd799439012",
  "lender": "bajaj_finserv",
  "assetType": "MUTUALFUND",
  "type": "application.submitted",
  "requestId": "WH-64f1abc23ef4cd5678",
  "data": {
    "requestedLoanLimit": 12000
  }
}

{
  "userId": "507f1f77bcf86cd799439011",
  "lender": "bajaj_finserv",
  "lid": "507f1f77bcf86cd799439012",
  "assetType": "STOCKS",
  "type": "application.approved",
  "requestId": "WH-64f1abc23ef4cd5678",
  "data": {
    "loanNo": "V402RLAS00058498",
    "loanAccountNumber": "133247",
    "loanAccountLimit": 12000
  }
}

{
  "userId": "507f1f77bcf86cd799439011",
  "lid": "507f1f77bcf86cd799439012",
  "lender": "bajaj_finserv",
  "assetType": "STOCKS",
  "type": "application.status_update",
  "requestId": "WH-64f1abc23ef4cd5678",
  "data": {
    "journeyStatus": "FETCH_CKYC",
    "journeyTracker": [
      {
        "status": "REGISTER_LEAD",
        "timestamp": "2025-10-01T08:09:26.485Z"
      },
      {
        "status": "CONFIRM_OFFER",
        "timestamp": "2025-10-01T08:09:30.884Z"
      },
      {
        "status": "FETCH_CKYC",
        "timestamp": "2025-10-01T08:09:41.347Z"
      }
    ],
    "selection": {
      "confirmedAmount": 450000,
      "maxAmount": 800000
    },
    "userId": "507f1f77bcf86cd799439011"
  }
}

{
  "userId": "507f1f77bcf86cd799439011",
  "lender": "bajaj_finserv",
  "lid": "507f1f77bcf86cd799439012",
  "assetType": "MUTUALFUND",
  "type": "disbursement.approved",
  "requestId": "WH-64f1abc23ef4cd5678",
  "data": {
    "loanNo": "V402RLAS00058498",
    "loanAccountNumber": "133247",
    "amount": 11000
  }
}

{
  "userId": "507f1f77bcf86cd799439011",
  "lender": "bajaj_finserv",
  "lid": "507f1f77bcf86cd799439012",
  "assetType": "STOCKS",
  "type": "disbursement.success",
  "requestId": "WH-64f1abc23ef4cd5678",
  "data": {
    "disbursedAmount": 11000
  }
}

{
  "userId": "507f1f77bcf86cd799439011",
  "lender": "bajaj_finserv",
  "lid": "507f1f77bcf86cd799439012",
  "assetType": "MUTUALFUND",
  "type": "payment.auto_debit.failed",
  "requestId": "WH-64f1abc23ef4cd5678",
  "data": {
    "loanNo": "V402RLAS00058498",
    "bouncedInterest": 1200,
    "bounceCharges": 200
  }
}

{
  "userId": "507f1f77bcf86cd799439011",
  "lender": "bajaj_finserv",
  "lid": "507f1f77bcf86cd799439012",
  "assetType": "STOCKS",
  "type": "loan.ltv_breach.triggered",
  "requestId": "WH-64f1abc23ef4cd5678",
  "data": {
    "loanNo": "V402RLAS00058498",
    "shortfallAmount": 1000
  }
}

{
  "userId": "507f1f77bcf86cd799439011",
  "lender": "bajaj_finserv",
  "lid": "507f1f77bcf86cd799439012",
  "assetType": "MUTUALFUND",
  "type": "loan.closure_requested",
  "requestId": "WH-64f1abc23ef4cd5678",
  "data": {
    "lan": "123456",
    "customerName": "John Doe",
    "transactionNumber": "HS92321311243407",
    "toEmail": ["las.crm@bajajfinserv.in"],
    "ccEmail": ["creditops@smallcase.com"]
  }
}

{
  "userId": "507f1f77bcf86cd799439011",
  "lender": "bajaj_finserv",
  "lid": "507f1f77bcf86cd799439012",
  "assetType": "STOCKS",
  "type": "loan.closed",
  "requestId": "WH-64f1abc23ef4cd5678",
  "data": {
    "loanNo": "V402RLAS00058498"
  }
}

{
  "userId": "507f1f77bcf86cd799439011",
  "lender": "bajaj_finserv",
  "lid": "507f1f77bcf86cd799439012",
  "assetType": "MUTUALFUND",
  "type": "user.created",
  "requestId": "WH-64f1abc23ef4cd5678",
  "data": {
    "userId": "507f1f77bcf86cd799439011",
    "interactionId": "INT64822ebcb406ec46428efac0"
  }
}

{
  "userId": "507f1f77bcf86cd799439011",
  "lender": "bajaj_finserv",
  "lid": "507f1f77bcf86cd799439012",
  "assetType": "STOCKS",
  "type": "application.feedback",
  "requestId": "WH-64f1abc23ef4cd5678",
  "data": {
    "userActionRequired": true,
    "userActionType": "OPS_DIGILOCKER",
    "opsFeedback": "There was a data mismatch in your name between previous agreement and submitted PAN card. We request you to proceed with the Digilocker flow."
  }
}

{
  "userId": "507f1f77bcf86cd799439011",
  "lender": "bajaj_finserv",
  "lid": "507f1f77bcf86cd799439012",
  "assetType": "MUTUALFUND",
  "type": "disbursement.success",
  "requestId": "WH-64f1abc23ef4cd5678",
  "data": {
    "disbursedAmount": 11000,
    "isMocked": true
  }
}

Webhook authentication

Each request sent to your webhook endpoint will include an Authorization header with a Bearer token.

Headers

Content-Type: application/json
Authorization: Bearer <token>

The token is a JWT with the following payload, signed with shared partner secret:

{
    "iss": "gateway",
    "iat": <current_unix_timestamp>,
    "exp": <expiration_unix_timestamp>
}

iss: Issuer of the token (fixed value: gateway).
iat: Issued at time, represented as a Unix timestamp.
exp: Expiration time, represented as a Unix timestamp (5 minutes from the issued time).

To authenticate the webhook requests, partner can retrieve the token from the Authorization header and decode the jwt with the shared partner secret

Post decoding, validate the claims:

Issuer: Check that the iss claim is "gateway".

Next steps

Next steps