> ## 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.

# Ticketing / Entertainment KYC setup guide

> ARGOS ID Check configuration guide for anti-scalping and macro prevention in ticketing and entertainment services.

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.

<Warning>
  **Regulatory environment**

  With 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.
</Warning>

***

## Key requirements

| Item                      | Requirement                                     |
| ------------------------- | ----------------------------------------------- |
| **Key regulations**       | Anti-scalping laws (macro/scalping prohibition) |
| **Required verification** | Passport/ID + face authentication               |
| **Security level**        | High (bot prevention focused)                   |
| **Liveness**              | Active mode (macro defense)                     |
| **AML**                   | Not required                                    |
| **Duplicate prevention**  | DI-based 1 person 1 ticket limit                |

***

## Required settings checklist

<Steps>
  <Step title="Pre-verification (Verified Fan) settings">
    **Complete verification before ticket sales open**

    | Setting                   | Recommended value | Rationale                                        |
    | ------------------------- | ----------------- | ------------------------------------------------ |
    | ID Document (Passport/ID) | ON                | Accommodate both domestic and international fans |
    | Universal ID support      | ON                | Support various IDs for international fans       |

    <Info>
      **Strategic value of pre-verification**

      By 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'.
    </Info>

    <Card title="Universal ID support" icon="id-card" href="/dashboard/en/project-management/policy-and-authentication/kyc-process#universal-id-support">
      View universal ID support settings for global users
    </Card>
  </Step>

  <Step title="Name similarity check settings (MRZ check)">
    **Project Management > Policy and Authentication > Anti-fraud and Forgery Prevention > ID-based**

    | Setting        | Recommended value | Rationale                                |
    | -------------- | ----------------- | ---------------------------------------- |
    | MRZ check      | ON                | Cross-verify passport MRZ information    |
    | Name threshold | 85 points         | Allow passport name notation differences |

    <Info>
      **MRZ name similarity comparison**

      MRZ 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.
    </Info>
  </Step>

  <Step title="Macro defense settings">
    **Project Management > Policy and Authentication > Anti-fraud and Forgery Prevention**

    | Setting                | Recommended value      | Rationale                   |
    | ---------------------- | ---------------------- | --------------------------- |
    | **Selfie liveness**    | **Active mode (High)** | Key to blocking macros/bots |
    | Streaming capture only | ON                     | Block pre-recorded videos   |
    | Proxy & VPN detection  | ON                     | Block macro farm networks   |

    <Warning>
      **Importance of active liveness**

      Active 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.
    </Warning>
  </Step>

  <Step title="1 person 1 ticket limit settings">
    **Project Management > Policy and Authentication > Authentication Data**

    | Setting                              | Recommended value              | Rationale                          |
    | ------------------------------------ | ------------------------------ | ---------------------------------- |
    | Deduplication pipeline               | Default method ON              | DI-based duplicate detection       |
    | Duplicate handling                   | Reject submission on duplicate | Prevent hoarding                   |
    | Duplicate approval prevention period | Set according to event period  | Per-event 1 person 1 ticket policy |

    <Info>
      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.
    </Info>

    <Card title="Configure authentication data" icon="arrow-right" href="/dashboard/en/project-management/policy-and-authentication/authentication-data#deduplication-and-submission-management">
      View detailed settings
    </Card>
  </Step>

  <Step title="Submission limit settings">
    **Project Management > Policy and Authentication > Authentication Data > Submission Limits**

    | Setting            | Recommended value    | Rationale                              |
    | ------------------ | -------------------- | -------------------------------------- |
    | Time window        | 1 hour               | Block repeated attempts in short time  |
    | Allowed attempts   | 3 times              | Prevent malicious repeated submissions |
    | Limit scope        | Email + IPv4 address | Block various bypass attempts          |
    | Force block period | 24 hours             | Prevent retry attempts                 |
  </Step>

  <Step title="Face authentication (Face Auth) settings">
    **On-site entry solution (Add-on)**

    | Setting        | Recommended value | Rationale                  |
    | -------------- | ----------------- | -------------------------- |
    | Face Auth      | ON                | Your face is your ticket   |
    | Selfie process | ON                | Prerequisite for Face Auth |

    <Check>
      **Game changer: Your face is your ticket**

      Compare 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.
    </Check>

    <Card title="Face authentication guide" icon="arrow-right" href="/dashboard/en/face-auth-guide">
      View Face Auth detailed guide
    </Card>
  </Step>
</Steps>

***

## Recommended settings summary

```
📋 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**

| Event                 | Action                                     |
| --------------------- | ------------------------------------------ |
| `submission.approved` | Grant queue entry permission               |
| `submission.rejected` | Deny booking eligibility                   |
| `face.auth.matched`   | Allow on-site entry                        |
| `face.auth.failed`    | Deny entry + request identity verification |

<Card title="Webhook setup guide" icon="webhook" href="/en/idcheck/webhooks/overview">
  View detailed webhook event settings
</Card>

***

## Related documentation

<CardGroup cols={2}>
  <Card title="KYC process" icon="users-gear" href="/dashboard/en/project-management/policy-and-authentication/kyc-process">
    ARGOS score, country blacklist, and basic settings
  </Card>

  <Card title="Anti-fraud and forgery prevention" icon="shield-halved" href="/dashboard/en/project-management/policy-and-authentication/anti-fraud-and-forgery-prevention">
    Liveness, selfie, MRZ check, Proxy/VPN detection, and security settings
  </Card>

  <Card title="Authentication data" icon="database" href="/dashboard/en/project-management/policy-and-authentication/authentication-data">
    DI generation, deduplication, submission limits, and data management settings
  </Card>

  <Card title="Face Auth guide" icon="face-smile" href="/dashboard/en/face-auth-guide">
    On-site face authentication setup and usage
  </Card>
</CardGroup>