Businesses operating in Mexico are obliged to verify their users’ identity using database verification checks as part of the identity verification process.
This guide gives an overview of the verification check of the Mexican Instituto Nacional Electoral (INE). This is the organization that issues the voter ID cards and maintains the voters registry.
The solution is available via API, web flow, and native SDKs.
Contact your solutions engineer for info and configuration.
Prerequisites
You have a regular identity verification (IDV) integration set up with Veriff
The solution/check is configured for that integration by your Solutions Engineer
A verification session generated for the end-user
You have configured the INE registry validation webhook to get responses from Veriff (see the Webhooks section for info)
Flow overview
The flow is a bit different, depending on the method you are using to verify your end-users with Veriff.
Use over SDK
Generate a verification session using the
API keys
and thebaseURL
of the integration used for this solution (see the API Documentation and API Reference[↗] how to find these)Capture end-user’s document and selfie images with Veriff’s SDKs
Send the end-user through the verification flow to capture the images (using the preferred Veriff SDK)
You need the session URL generated in step 1 to use the SDKs (found in response payload as
verification.url
)
Session will be submitted automatically once the end-user takes and submits necessary images
Receive the results from Veriff via INE registry validation webhook
Use over API
Generate a verification session using the a
API keys
and thebaseURL
of the integration used for this solution integration (see the API Documentation and API Reference[↗] how to find these)Veriff strongly recommends you create and send the
endUserId
orvendorData
Veriff strongly recommends you collect and send additional session/device data via POST sessions/{sessionid}/collected-data[↗] for improved fraud detection
Use your image-capturing method, or prepare previously collected end-user selfie and document images
Upload the end-user's media via POST /sessions/{sessionId}/media[↗] call
Specify the
image.context
as appropriate for the image (see Context types (image, video) for more info about image context types)
Patch session status to
submitted
status using PATCH /sessions/{sessionId}[↗] callCheck the decision data and/or session related info from the INE registry validation webhook and/or query the data from the GET /sessions/{sessionId}/decision/ine-registry[↗] endpoint
Find decision and/or session related info
You can get the data from three sources:
Receive the INE registry validation webhook
Query the results via GET sessions/{sessionId}/decision/ine-registry
View the session in Veriff Customer Portal
Webhook payload
Check the INE registry validation webhook payload, see INE webhook documentation for detailed info.
API call
You can use the GET /sessions/{sessionId}/decision/ine-registry[↗] endpoint, see the documentation for more info.
Make sure to add the mandatory query parameter version=1.0.0 to the API URL:
GET sessions/{sessionId}/decision/ine-registry?version=1.0.0
Note: in the respective jurisdiction, an
active = true
credential can be used for identification and related activities; anactive = false
credential could still be in the database, but it cannot be used for identification and related activities.
Sample response of a inactive INE identification number
{
"active": false,
"documentState": "No se obtuvieron datos de la consulta con los parámetros seleccionados"
}
Sample response of a active INE identification number
{
"active": true,
"documentState": "...."
}
Veriff Customer Portal
You can find the verification session related info, including the decision, in the Veriff Customer Portal, under the Webhooks tab.
→ See Review verification in Veriff Customer Portal about how to view the session info in the Veriff Customer portal
Status and reason codes
For an approved
session, see the verification.code
and verification.status
parameters.
If the session was declined
or resubmission_requested
, you can find additional information by checking the verification.status
, verification.code
, verification.reason
and verification.reasonCode
data objects.
For more info about the codes you are seeing, refer to: