Aadhaar OCR Verification

The Aadhaar OCR Verification journey involves entering the Aadhaar front image and Aadhaar Back image in the Base 64 or S3 URL format.

Businesses can configure these checks with our Aadhaar OCR Verification journey

📘
Journey ID will be shared as part of Onboarding

Journey Output Data

{
  "key_name": "AADHAAR",
  "key_status": "CHECKED",
  "key_data": [
    {
      "name": "Suresh Gudivada",
      "key_id": "xxxxxxxx1234",
      "dob": "13-08-1990",
      "gender": "Male",
      "address": "S/O,Satyamurthy Flat 10, Lake view apartment Somajiguda Beside Ramalayam Hyderabad Telangana 500001",
      "address_street": "Lake view apartment",
      "address_landmark": "Beside Ramalayam",
      "address_house": "Flat 10",
      "address_area": "Somajiguda",
      "address_district": "Hyderabad",
      "address_state": "Telangana",
      "address_country": "India",
      "address_pincode": "500001",
      "photo": "<S3 URL of the captured face photo if verified from user upload and face verification>",
      "liveness_photo": "<S3 URL of the captured face photo if verified from user upload and face verification>",
      "ocr_image": "<S3 URL of the user provided Aadhaar card photo>",
      "document_front": "<S3 URL of the front Aadhaar card photo>",
      "document_back": "<S3 URL of the back Aadhaar card photo>"
    }
  ]
}

📘
This journey does not include any pre-configured Ownership or Fraud Checks. To add these checks, please contact your Account Manager.

Key Status

Status	Description
VERIFIED	Data is retrieved from the source of truth
CHECKED	Data is derived or obtained from third parties
IN_PROGRESS	Currently verifying data with the official source or third parties
FAILED	User-shared data is invalid or incorrect
UNVERIFIED	User-shared data without confirmation from official sources
USER_DONT_HAVE	User states they lack the specified ID

Updated 3 months ago