Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developers.argosidentity.com/llms.txt

Use this file to discover all available pages before exploring further.

Modern anti-scalping regulations designate fraudulent ticket purchases using macro programs as punishable offenses. To prevent scalping, strong verification is needed to confirm that the ‘ticket purchaser’ and ‘attendee’ are the same person.
Regulatory environmentWith scalper prices for popular events reaching 40x or more above face value, ticket sellers now have legal obligations to implement technical measures to block macro attacks.

​
Key requirements

ItemRequirement
Key regulationsAnti-scalping laws (macro/scalping prohibition)
Required verificationPassport/ID + face authentication
Security levelHigh (bot prevention focused)
LivenessActive mode (macro defense)
AMLNot required
Duplicate preventionDI-based 1 person 1 ticket limit

​
Required settings checklist

1

Pre-verification (Verified Fan) settings

Complete verification before ticket sales open
SettingRecommended valueRationale
ID Document (Passport/ID)ONAccommodate both domestic and international fans
Universal ID supportONSupport various IDs for international fans
Strategic value of pre-verificationBy performing ARGOS ID Check during the ‘Verified Fan’ verification stage before ticket sales open, only identity-verified users can enter the booking queue, providing first-line defense against bots. This is the most complete technical implementation of the anti-scalping regulation’s intent to ‘ensure fair booking opportunities’.

Universal ID support

View universal ID support settings for global users
2

Name similarity check settings (MRZ check)

Project Management > Policy and Authentication > Anti-fraud and Forgery Prevention > ID-based
SettingRecommended valueRationale
MRZ checkONCross-verify passport MRZ information
Name threshold85 pointsAllow passport name notation differences
MRZ name similarity comparisonMRZ check compares the similarity between names read from MRZ and names extracted via OCR. For international users, verification often fails due to different passport name order (John Doe vs Doe John). Setting the name threshold to 85 points flexibly allows such notation differences, reducing friction in on-site operations.
3

Macro defense settings

Project Management > Policy and Authentication > Anti-fraud and Forgery Prevention
SettingRecommended valueRationale
Selfie livenessActive mode (High)Key to blocking macros/bots
Streaming capture onlyONBlock pre-recorded videos
Proxy & VPN detectionONBlock macro farm networks
Importance of active livenessActive liveness, which requires users to respond in real-time to on-screen instructions (turn head, open mouth, etc.), is extremely difficult for pre-recorded videos or macro programs to bypass. It’s a more powerful Turing test than simple CAPTCHA.
4

1 person 1 ticket limit settings

Project Management > Policy and Authentication > Authentication Data
SettingRecommended valueRationale
Deduplication pipelineDefault method ONDI-based duplicate detection
Duplicate handlingReject submission on duplicatePrevent hoarding
Duplicate approval prevention periodSet according to event periodPer-event 1 person 1 ticket policy
Using the DI value generated by ARGOS, the system blocks one real person from hoarding tickets by creating multiple accounts. This neutralizes scalpers’ ‘multi-account volume acquisition’ strategy.

Configure authentication data

View detailed settings
5

Submission limit settings

Project Management > Policy and Authentication > Authentication Data > Submission Limits
SettingRecommended valueRationale
Time window1 hourBlock repeated attempts in short time
Allowed attempts3 timesPrevent malicious repeated submissions
Limit scopeEmail + IPv4 addressBlock various bypass attempts
Force block period24 hoursPrevent retry attempts
6

Face authentication (Face Auth) settings

On-site entry solution (Add-on)
SettingRecommended valueRationale
Face AuthONYour face is your ticket
Selfie processONPrerequisite for Face Auth
Game changer: Your face is your ticketCompare the facial data registered during booking with facial recognition at on-site kiosks for entry. Since the ‘face’ becomes the entry ticket rather than a ticket (QR code), it becomes physically impossible to transfer or sell to others.Previously, preventing scalping required on-site staff to manually compare IDs and faces, taking hours for entry. With ARGOS Face Auth, attendees can pass through gates at walking speed (walk-through), and scalpers have no way to transfer purchased tickets.

Face authentication guide

View Face Auth detailed guide
📋 Ticketing required checklist

✅ ID Document method (passport/ID)
✅ Selfie liveness - Active mode (High)
✅ Streaming capture only
✅ DI-based deduplication (1 person 1 ticket)
✅ Submission limits (3 attempts per hour)
✅ Proxy & VPN detection
✅ MRZ check - Name threshold 85 points

🔹 Optional (highly recommended)
- Face Auth (face ticket): Complete scalping prevention

​
Webhook integration

Required webhook events
EventAction
submission.approvedGrant queue entry permission
submission.rejectedDeny booking eligibility
face.auth.matchedAllow on-site entry
face.auth.failedDeny entry + request identity verification

Webhook setup guide

View detailed webhook event settings

KYC process

ARGOS score, country blacklist, and basic settings

Anti-fraud and forgery prevention

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

Authentication data

DI generation, deduplication, submission limits, and data management settings

Face Auth guide

On-site face authentication setup and usage