Verification ChecksIdentity

Liveness Check

Uses live facial verification to confirm the person is present and actively completing the check.

Send LIVENESS_CHECK in checksRequested to run this check.

LIVENESS_CHECK is accepted as a public alias of FACE_MATCH. The initial creation response remains DRAFT. After processing starts, retrieve the report to obtain the Verifisha-hosted action URL that the subject must open.

The request

POST /api/v1/reports
{
  "subject": {
    "fullName": "Jane Doe",
    "idNumber": "36901234",
    "email": "jane@example.com",
    "phone": "+254712345678",
    "country": "KE",
    "subjectType": "INDIVIDUAL"
  },
  "checksRequested": [
    "LIVENESS_CHECK"
  ],
  "purpose": "Remote identity verification",
  "consent": {
    "mode": "VERIFISHA_HOSTED"
  }
}

The acknowledgement

Creation is asynchronous. The report comes back as a draft; the check runs after.

201 Created
{
  "reports": [
    {
      "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
      "status": "DRAFT",
      "paymentState": {
        "status": "NOT_REQUIRED",
        "amount": {
          "amount": 0.1,
          "currency": "KES"
        }
      },
      "consentState": {
        "status": "NOT_REQUIRED"
      }
    }
  ],
  "count": 1
}

Subsequent report excerpt after check.started

{
  "status": "PROCESSING",
  "externalActions": [
    {
      "type": "HOSTED_VERIFICATION",
      "checkType": "FACE_MATCH",
      "url": "https://app.verifisha.com/verify/session-token",
      "status": "PENDING"
    }
  ]
}

The result

When the check finishes, this arrives at your webhook. COMPLETED means it ran — read riskLevel and flags to decide what it found.

On this page