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

​
Required settings checklist

1

Tiered authentication method settings

Accommodating both domestic and international users with a tiered approach
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 ProcessProject Management > Policy and Authentication > Anti-fraud and Forgery Prevention > Face Authentication

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
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
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 DetectionProject Management > Policy and Authentication > KYC Process
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
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).

​
Webhook integration

Required webhook events

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