Before consuming the webhooks, you need to register your endpoint on the enterprise dashboard of Digio.
See the integration guide for steps on setting up the webhook on Digio Dashboard
Webhook Events for Digi KRA
| Event | Description |
|---|---|
| KRA.PAN.STATUS.UPDATE | Any updates received from kra for the registered request |
KRA_REGISTER entity is defined by following attributes:
| Key | Type | Description |
|---|---|---|
| Request_ID | string | The request id that was generated and sent over during registration |
| PAN_NUMBER | string | PAN number |
| STATUS | string | Updated Status from CKYC (NOT_CHECKED_WITH_RESPECTIVE_KRA/SUBMITTED/KRA_VERIFIED/ON_HOLD/REJECTED/NOT_AVAILABLE/DEACTIVATED/KRA_VALIDATED/EXISTING_KYC_SUBMITTED/EXISTING_KYC_VERIFIED/EXISTING_KYC_HOLD/EXISTING_KYC_REJECTED/KYC_REGISTERED_WITH_CVLMF/NOT_CHECKED_WITH_MULTIPLE_KRA/INVALID_PAN_FORMAT/KRA_NOT_REACHABLE) |
| KRA_PROVIDER | string | KRA provider for which the status is updated (In case when there are multiple kra’s registered for your account)Possible values are: “CDSL” |
| CLIENT_REFERENCE_ID | string | Unique reference ID passed in the request payload |
Webhook Entities with Payload
-
KRA_REGISTER
{
"entities": [
"kra_register"
],
"payload": {
"kra_register": {
"request_id": "KRA230427173634151B8ZLQJID3BLXO8",
"status": "KRA_VERIFIED",
"pan_number": "CVZPP6699C",
"kra_provider": "CDSL",
"metadata": [],
"client_reference_id": "KID2033000ABCD",
"others": null,
"id": "KRA230427173634151B8ZLQJID3BLXO8"
}
}
}
Reference
For more detailed steps on setting up the webhook and reference for the same
See Webhook Guide