Customize Document Verification

In the AdvanGurad console, adjust document verification to match your business needs. Settings are organized at Global Settings and Verification Level layers: Global provides platform defaults; each Level can override where supported. Saved settings are version-snapshotted—applications already created are not affected by later changes.

Customize supported ID documents

Under Global Settings → User Verification → Supported ID documents, define the default countries/regions and document types you accept. This is your platform-wide default scope—Levels that do not use custom document settings inherit this list at verification time.

For each country + document type, you can:

Choose Don't accept, One side, or Two sides
Click Edit / Fields to configure subtypes and required fields

Subtypes are all supported by default. You may switch to allow-only or reject-only specific subtypes (for example, accept national ID but not legacy card types).

Required fields define which OCR outputs must be present after extraction. Available fields include document number, first name, middle name, last name, date of birth, issue date, expiry date, nationality, and English name fields (first / middle / last). Document number and first name are required by default and cannot be deselected.

If a Verification Level needs a different document scope, enable Use custom settings for this level under Configurations → Supported ID documents. Once enabled, that Level uses its own list; later Global changes do not overwrite the Level's saved scope.

Set age restrictions

On the Compliance tab, specify the allowed age range. Both Global and Level expose this: Global holds defaults; each Level saves its own compliance rules under Configurations → Compliance, independent of the custom document-settings switch.

Age check is on by default, range 18–88. New Levels inherit Global compliance values at creation; after save, values belong to that Level and do not auto-update when Global changes. Disabled checks are skipped during verification.

Onboarding minors may be restricted by applicable law. Consult your legal team before lowering minimum age; you accept responsibility for that choice.

Configure document expiry

On the same Compliance tab, control expiry requirements:

Accept only non-expired documents
Require a minimum number of days of remaining validity; 0 means "not expired" only

Same layering as age: Global defaults, Level saves and applies its own values.

Configure nationality restrictions

On Compliance, enable a nationality blocklist and maintain disallowed nationalities. When enabled, documents whose recognized nationality matches the list fail verification. Defaults can be set at Global and adjusted per Level.

Set verification strictness

Under each Level's Configurations → General & match, choose the operating mode. Level only—not available at Global:

Advance (strict) — higher sensitivity on forgery detection; suited to high-assurance flows
Standard — more lenient forgery detection; suited to conversion-focused flows

Enable region matching

On the same General & match page, enable Region matching. When on, the country/region passed when creating an application must match the country/region recognized from the document; missing or mismatched values fail verification.

Region matching and the supported document list are separate: the former aligns your input region with recognition; the latter defines which documents you accept. If you pass a fixed country/region when creating an application, enabling this helps prevent users from submitting documents from unexpected jurisdictions.

Enable name translation

If downstream processes need English names (for example, cross-border reporting or screening), enable Name translation under General & match. Level only.

When OCR does not directly provide English names, the system fills:

First name (English)
Middle name (English) (if applicable)
Last name (English)

You may also mark these English fields as required per document entry under Edit / Fields. Name translation is auxiliary; translation failures typically do not change the final GREEN/RED document outcome.

Configure document capture

Capture settings are Level only—not configured at Global.

Capture method — when creating a Level, on Steps → Document:

Live Capture — user photographs the document in real time (default)
File Upload — user selects from an album or uploads an existing image

Capture experience — under Configurations → Document capture:

Shooting mode — auto scan, manual capture, or both
Fallback on camera failure — whether upload is allowed when the camera is unavailable
Auto-scan timeout — switch to manual capture after timeout
Skip guide page — skip pre-capture instructions
Skip country/document type picker — skip user selection of country and document type (default: skip)

If country or document type is already fixed for the flow, keeping the picker skipped is common; the images users actually submit on the capture screen remain authoritative.