nCore webhook events
Last updated
Last updated
Following are the available webhooks you can create to receive event notifications.
Handling
Following are the methods in which nCore platform handles webhooks notifications.
The nCore platform maintains a retry counter and resends the failed notifications by triggering the expired webhooks.
It includes a Basic Auth (encoded in base64) header in the webhook notification message.
The nCore platform pings a configured webhook to validate the credential and connectivity.
To support token uniqueness, each transaction is recognized by a unique transaction token, and each webhook is identified by a unique event token.
Event name
Event type
Send webhook notification when
Status change
CARD_STATUS_CHANGE
A card status is updated
Transaction
TRANSACTION
A transaction is performed by a card
KYC
KYC_RESULT
Changes in user’s KYC request are done
User creation
USER_CREATED
User is created
User status
USER_STATUS_CHANGE
User status is changed
User document
USER_DOCUMENT_ALERT
The document expiration date is approaching
IDV
IDENTITY_VERIFICATION
Identity verification needed
PIN change
PIN_CHANGE
PIN is changed
Auth expiry
EXPIRED_AUTH
Auth/pre-auth is expired
Charges
CHARGE_APPLIED
Charges are applied
Account status
ACCOUNT_STATUS_CHANGE
Account status is changed
Card provisioning
CARD_PROVISIONING
Card is tokenized
Token notification
TOKEN_NOTIFICATION
Digital wallet token status is updated
Card or account creation
SUCCESSFULLY_CREATED
Card or account is successfully created