Document Verification (DocV) is a secure way to verify customer identities by validating their government-issued documents. The Document Verification in Kount 360 integration guide describes the steps needed to directly integrate Document Verification.
Note
Before integrating , you must first complete the Identity Proofing Integration Guide.
Integrating Document Verification in Kount 360 requires the following:
-
An organization in Kount 360 with the correct entitlements
-
A client ID to authenticate API calls
-
An API key
-
Access to webhooks
-
Access to SMS messaging configuration
Note
If you do not have access to any of the listed requirements, contact your Implementation Engineer or email support@kount.com.
After setting up your Kount 360 organization, work with your Implementation Engineer to define the flows and thresholds needed for Document Verification, which includes:
-
ID capture
-
ID validation (with risk thresholds)
-
Face capture
-
Face match (with risk thresholds)
-
Optical Character Recognition (OCR) data
Document Verification can be initiated as Direct Document Verification. This workflow lets you start Document Verification directly asynchronously or synchronously.
-
Asynchronous flow: We send a Document Verification link to the customer using SMS text messaging, if a phone number is provided.
-
Synchronous flow: Kount returns the Document Verification link in the API response for the customer.
For Direct Document Verification, you must use the strategy template StrategyWithstepup_DOCV, which is an independent workflow that is not integrated into Policy Management.
To configure the Direct Document Verification strategy:
-
Create an SMS One-Time Hyperlink (OTH) messaging template in Kount 360.
Note
The SMS OTH messaging template must be completed even, if the integration does not send an SMS message to the consumer, to start the Document Verification workflow.
-
Create a new strategy with a unique name, select the template
StrategyWithstepup_DOCV, and then select the SMS OTH message you already completed.
Document Verification sends status updates and final results, using a webhook, to the client.
To create a webhook for Document Verification events:
-
Sign in to Kount 360.
-
Select Admin.
-
Select Product Configuration.
-
Select Webhooks.
-
Select New Webhook.
-
In Event, select the Document Verification Status Update for Identity Proofing.
-
Optional: You can enter a Channel. The Channel allows you to specify which store you want associated with the webhook. The Channel you enter must match the one used when sending data in the request to the POST Orders endpoint.
-
Enter the URL for where you want the webhook sent.
-
Select Enter.
-
Select Confirm to register the webhook.
To begin the Document Verification flow, make a POST request to the Identity Proofing Document Verification endpoint. The request body determines whether the flow is synchronous or asynchronous.
When a Document Verification is triggered, the DocumentVerification endpoint is called.
Go to Document Verification API help for more information.
https://api.kount.com/business/identity-proofing/v1/docv
{
"inquiryId": "12345-567890",
"phoneNumber": "19999999999",
"strategy": "StrategyWithstepup_DOCV"
}
This flow is used when a phone number is provided in the API request. We send a One-Time Hyperlink (OTH) in an SMS message to the provided phone number. A 200 status is returned with a success message, confirming that the link has been sent.
This flow is used when a phone number is not provided in the API request. We generate a One-Time Hyperlink (OTH) and return it directly to the API response. A 200 status with the Document Verification link is returned. Provide the OTH to the end user for them to capture the document verification.
Once the Document Verification workflow is finished, a Status Update webhook event is sent to your configured Document Verification webhook endpoint. This is the primary method for receiving real-time status updates.
After receiving the Status Update webhook event, call the Verify Status API to receive all details collected by Document Verification.
To receive all details related collected by Document Verification, call the Verify Status API endpoint with getDetails as true in the API request.
Sandbox
https://api-sandbox.kount.com/business/identity-proofing/v1/docv/{{AuthenticationId}}?data=all
Production
https://api.kount.com/business/identity-proofing/v1/docv/{{AuthenticationId}}?data=all
The customer can resend the Document Verification link with the Resend API.
When a customer resends the Document Verification link, the Resend API is called.
Go to Identity Proofing Step-up Verification help for more information.
https://api.kount.com/business/step-up/v1/verify
{
"inquiryId": "12345-567890-12345",
"authenticationId": "4d18367d-b86e-4653-a30a-6695a1730507",
"strategy": {
"strategyName": "StrategyWithStepup_DOCV",
"actions": [
{
"method": "DOCV",
"data": {
"resend": true
}
}
]
}
}
{
"inquiryId": "12345-567890-12345",
"authenticationId": "4d18367d-b86e-4653-a30a-6695a1730507",
"decision": "Challenge",
"strategy": {
"strategyName": "StrategyWithStepup_DOCV",
"description": "Strategy with stepup DOCV only",
"status": "active",
"actions": [
{
"method": "DOCV",
"status": "SENT"
}
]
}
}