Skip to main content

Onsite Integration

With Onsite verification, Shufti will directly interact with the end user, managing data collection to facilitate age verification. Verification status updates are communicated to the client via callback URL and the Shufti back office.

Request Parameters

The parameters mentioned below are applicable for Onsite age verification.

Age Verification Object

ParametersDescription
is_age_verificationRequired: Yes
Type: String
Accepted Values: "0" (No), "1" (Yes)
Default Value: "0"
Enables age verification.
min_ageRequired: Yes
Type: string
Examples: 18, 21, 13
Minimum acceptable age for verification.
max_ageRequired: No
Type: string
Examples: 65, 25
Maximum acceptable age for verification. Leave empty for no upper limit.
verification_methodRequired: Yes
Type: string
Accepted Values: facial_age_estimation, document_age_check, database_lookup
The age verification method to use.
age_bufferRequired: Conditional
Type: string
Accepted Values: 3, 5, 7, 10
Default Value: 5
Age buffer for facial age estimation (margin of error); required if verification_method is facial_age_estimation.
facial_liveness_checkRequired: Conditional
Type: string
Accepted Values: 0 (No), 1 (Yes)
Default Value: 0
Enable facial liveness check for document verification. Used when verification_method is document_age_check.
allow_fallbackRequired: No
Type: string
Accepted Values: 0 (No), 1 (Yes)
Default Value: 0
Allow fallback to alternative verification methods if the primary method fails or returns inconclusive results.
For facial_age_estimation: Falls back to ID Document Age Check
For database_lookup: falls back to ID Document Age Check.
privacy_preservingRequired: No
Type: string
Accepted Values: 0 (No), 1 (Yes)
Default Value: 0
Enable privacy-preserving mode for minimal data extraction. Only calculated age shown to the merchant.

Onsite Integration

With Onsite verification, Shufti will directly interact with the end user, managing data collection to facilitate age verification. Verification status updates are communicated to the client via callback URL and the Shufti back office.

Request Parameters