Webhook Notification

The Webhook is a way for VIDA to notify partners about updates on identity verification transactions. When a webhook is configured, VIDA will send notifications to the partner's API containing the status of the verification process and other relevant information, such as the unique transactionId and the partner's own transaction ID partnerTrxId (if provided in the API request). This allows partners to easily track the status of their API requests. To receive webhook notifications, the partner's API should be able to accept JSON requests, and should be configured to accept the webhook URL, authentication method, and authentication credentials provided by VIDA.

Webhook Configuration

To set up Webhooks, you will need to contact the VIDA support team. and request for it to be enabled. Please reach out to the VIDA support team for further assistance.

Authorization

VIDA supports OAuth2-based "client credentials" and "Basic Auth" methods for authentication. The partner must share their preferred method of authentication along with the necessary credentials and URL to receive the webhook notifications.

Invocation Request

The invocation request from the webhook is identical to the response received from the Status check API.

Invocation Request Status Code

The status check failure reasons table covers all the possible status code along with the description and recommendation in case of failure.

Webhook Payload Structure

The webhook payload structure will inform partners with the API processing status, for example when the request API is still in-progress due to manual review, or to notify if the transaction successfully processed.

JSON Response

{
  "data": {
    "partnerTrxId": "3282d003-c62c-4b7b-87e4_12112",
    "transactionType": "FULL_FRAUD_ASSESSMENT",
    "transactionId": "3282d003-c62c-4b7b-87e4-9d0a1bbf0c18",
    "status": "<code>"
  }
}

The status field provides detailed information about the current state of the fraud assessment transaction. It may contain the following values:

Status	Description
001	The fraud assessment is in progress
002	The fraud assessment transaction is submitted for manual review
003	The fraud assessment result is accepted and the certificate issued after manual review
004	The fraud assessment result is rejected and the certificate have been not issued after manual review
006	The certificate not issued
007	Certificate is issued

Example of Webhook Payload

When the API in Progress

{
    "partnerTrxId": "3282d003-c62c-4b7b-87e4_12112",
    "transactionType": "FULL_FRAUD_ASSESSMENT",
    "transactionId": "3282d003-c62c-4b7b-87e4-9d0a1bbf0c18",
    "status": 001
}

Submitted for Post Correction

{
    "partnerTrxId": "3282d003-c62c-4b7b-87e4_12112",
    "transactionType": "FULL_FRAUD_ASSESSMENT",
    "transactionId": "3282d003-c62c-4b7b-87e4-9d0a1bbf0c18",
    "status": 002
}

Post Correction Accepted

{
    "partnerTrxId": "3282d003-c62c-4b7b-87e4_12112",
    "transactionType": "FULL_FRAUD_ASSESSMENT",
    "transactionId": "3282d003-c62c-4b7b-87e4-9d0a1bbf0c18",
    "status": 003
}

status: The status of the fraud assessment (ACCEPTED).

Post Correction Rejected

{
    "partnerTrxId": "3282d003-c62c-4b7b-87e4_12112",
    "transactionType": "FULL_FRAUD_ASSESSMENT",
    "transactionId": "3282d003-c62c-4b7b-87e4-9d0a1bbf0c18",
    "status": 004
}

status: The status of the post-correction result if the verification is rejected (REJECTED).

Digital Certificate Issued

{
    "partnerTrxId": "3282d003-c62c-4b7b-87e4_12112",
    "transactionType": "FULL_FRAUD_ASSESSMENT",
    "transactionId": "3282d003-c62c-4b7b-87e4-9d0a1bbf0c18",
    "status": 007
}

When the digital certificate is not issued

This event the digital certificate is not issued, the payload is as follows:

{
    "partnerTrxId": "3282d003-c62c-4b7b-87e4_12112",
    "transactionType": "FULL_FRAUD_ASSESSMENT",
    "transactionId": "3282d003-c62c-4b7b-87e4-9d0a1bbf0c18",
    "status": 006
}