Skip to main content
The gaming industry has age verification obligations under youth protection laws and gaming industry regulations. For P2E (Play to Earn) games in particular, preventing multi-account abuse is essential to protect the in-game economy.
The global service dilemmaRelying solely on domestic phone verification limits access for international users and overseas citizens. ARGOS enables you to accept global users through passport-based verification.

โ€‹
Key requirements

ItemRequirement
Key regulationsGaming industry laws, youth protection laws (age verification)
Required verificationPhone (domestic) / Passport (international) - tiered approach
Security levelHigh/Medium (Tiered - situational application)
LivenessPassive mode (usability focused)
AMLOptional (risk-based application)
Data collectionDI value (for identification), minimal image retention

โ€‹
Required settings checklist

1

Tiered authentication method settings

Accommodating both domestic and international users with a tiered approach
TargetMethodPurpose
Domestic usersKnowledge-based (phone verification)Fast signup flow
International/overseas usersID Document (passport)Global accessibility
P2E withdrawalID Document requiredEnhanced verification requirement
This meets the minimum identity verification requirements under gaming industry regulations.

Configure KYC process

View detailed settings
2

Age restriction settings

Project Management > Policy and Authentication > KYC Process
SettingRecommended valueRationale
Age limit18 yearsAdult-only rated games
Project Management > Policy and Authentication > Anti-fraud and Forgery Prevention > Face Authentication
SettingRecommended valueRationale
Face-based age verificationON (age threshold 18)Additional selfie-based age verification

Configure age restrictions

View detailed settings
3

1 person 1 account settings (farm prevention)

Project Management > Policy and Authentication > Anti-fraud and Forgery Prevention > Face Authentication
SettingRecommended valueRationale
Selfie processONPrerequisite for face deduplication
Face deduplicationON (reject on duplicate)Block P2E multi-account creation
Key to preventing bot/farm operationsEven if a user signs up with a different email, if the submitted face information (Face Vector) matches an existing record in the database, registration is blocked. This makes it physically impossible for โ€˜farmsโ€™ to create multiple accounts.
4

DI generation settings

Project Management > Policy and Authentication > Authentication Data
SettingRecommended valueRationale
Deduplication pipelineDefault method ONDI-based duplicate detection
Custom DIAdd additional field combinations if neededMore precise duplicate detection
Global application of DIBy generating a unique DI from passport information through ARGOS, you can manage all users by a single โ€˜Digital Identityโ€™ standard regardless of nationality. This solves the database fragmentation problem of separately managing domestic users (CI/DI-based) and international users (email-based).

Configure authentication data

View detailed settings
5

Regional restriction settings

Project Management > Policy and Authentication > Anti-fraud and Forgery Prevention > Meta Info Detection
SettingRecommended valueRationale
Proxy & VPN detectionONBlock bot/macro farm access
Regional pre-screeningON if neededBlock IPs from P2E restricted countries
Project Management > Policy and Authentication > KYC Process
SettingRecommended valueRationale
Blacklist countriesAdd as neededBlock service-unavailable countries
By requiring enhanced verification only for P2E features or currency exchange, you can minimize conversion rate drops while meeting regulatory requirements.
6

Data retention policy

Project Management > Policy and Authentication > Authentication Data
SettingRecommended valueRationale
Partial data deletionONGDPR/Privacy law compliance
Unlike financial companies, gaming companies have less justification for long-term retention of ID copies. Configure automatic deletion of ID images after verification is complete, keeping only metadata (DI, age, nationality).
๐Ÿ“‹ E-Gaming required checklist

โœ… Age limit 18 years setting
โœ… Face deduplication (1 person 1 account)
โœ… DI generation enabled
โœ… Proxy & VPN detection
โœ… Regional pre-screening if needed (regulated country blocking)
โœ… Partial data deletion (privacy protection)

๐Ÿ”น Optional
- Selfie liveness: Passive mode (usability focused)
- AML: Risk-based selective application

โ€‹
Webhook integration

Required webhook events
EventAction
submission.approvedActivate game account
submission.rejectedReject signup (underage/duplicate)
face.duplicateAlert for suspected multi-account

Webhook setup guide

View detailed webhook event settings

KYC process

ARGOS score, age restrictions, country blacklist, and basic settings

Anti-fraud and forgery prevention

Liveness, selfie, Proxy/VPN detection, and security settings

Authentication data

DI generation, deduplication, data retention policy settings

Data protection

Data minimization and automatic deletion settings