Skip to content
Docs/
/
/
KYC Journey

KYC Journey Webhooks

KYC Journey webhooks notify you about KYC verification lifecycle events.

Note: The sample payloads on this page are pretty-printed. The body Glomo sends is the RFC 8785 canonical form of the same object, and the X-Glomopay-Signature header is computed over those bytes. See Webhook Authentication & Security.

Event TypeDescription
initiated The KYC verification has been initiated.
in_progress The KYC verification is being processed.
completed The KYC verification has been completed successfully.
rejected The KYC verification has been rejected.
action_required The KYC verification requires additional information to proceed.
under_review The KYC verification is under review.
failed The KYC verification failed. The failure_reason field describes the cause.

Sample Payload

{
  "entity_type": "kyc_journey",
  "event_type": "completed",
  "data": {
    "id": "kyc_6819d8046mpKt",
    "status": "completed",
    "customer_id": "cust_6819d7d0lrLvP",
    "bank_enabled": true,
    "bank_name": "HDFC bank"
  }
}

Sample Payload — Failed

{
  "entity_type": "kyc_journey",
  "event_type": "failed",
  "data": {
    "id": "kyc_6819d8046mpKt",
    "status": "failed",
    "customer_id": "cust_6819d7d0lrLvP",
    "failure_reason": "CKYC bureau verification failed with prefilled data"
  }
}

Note: customer_id is null for KYC links created with an email address only (no existing customer record). Consumers should handle this case.

Note: bank_enabled and bank_name are only present when the KYC journey is part of an LRS (Liberalised Remittance Scheme) flow, initiated via a Payment Session. bank_enabled indicates whether the customer's bank is supported for LRS remittance. bank_name is the human-readable name of the resolved bank (e.g. "HDFC bank", "Axis bank"). Both fields are omitted for standalone KYC journeys not linked to an LRS Payment.

Virtual Account

Balance