Meet Atlas Live: liveness detection with no gesture required
Atlas

Review and operations Available

Atlas Console

The review console: analysts only receive the files that need them.

Request a demo Start in the sandbox

Access by invitation: no account yet? Ask for your sandbox workspace.

What it checks

Only the files that need a human.

Your rules settle the clear cases. The console gives your analysts the others, with everything they need to decide.

  • Review queue

    Files to review, assignment, filters by flow and by analyst, handling time tracked.

  • Evidence and checks

    Captures, extracted fields, score and explanation of each check, in one place.

  • List matches

    Each match is qualified before any decision, with a reason and a note.

  • Four-eyes approval

    A decision can require a second analyst, different from the first.

  • Audit trail

    Assignments, qualifications and decisions timestamped, with their author.

  • Reports and exports

    PDF report per file in French or Arabic, decisions exported as CSV.

How it works

From file to decision.

  1. 1 The file arrives Your rules sent it to review, with the reasons.
  2. 2 The analyst examines it Evidence, checks and list matches, on the same screen.
  3. 3 They decide Approved or rejected, with a reason; a second analyst confirms if you require it.
  4. 4 Your system is notified Signed webhook, PDF report and audit trail.

Review queue 12 open filesSample data

  • client-4821 screening_hit To review
  • client-4817 face_match_low To review
  • client-4790 liveness_screen_replay Rejected
  • client-4786 document_type_mismatch Approved
Approve Reject Four-eyes approval
Specimen: invented references.

For developers

Review, through the API too.

The same actions as in the console: assign, qualify a match, decide, approve.

Developer guide Start in the sandbox

Request

curl -X POST https://verify.atlasidv.com/v1/cases/7f3c9a2e-…/decide \
  -H "Authorization: Bearer atlas_sk_sandbox_…" \
  -d '{
    "decision": "approved",
    "reason_codes": []
  }'

Response 202 Accepted 

{
  "verification_id": "7f3c9a2e-…",
  "status": "deciding",
  "decision": "approved"
}

Take the next step

Try Atlas Console on your own flows.

A demo on your real cases, then a sandbox space with synthetic identities to integrate without any real data.

Request a demo Start in the sandbox