> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.idenfy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Crypto and Web3

> Set up KYC, AML screening, and ongoing monitoring for crypto exchanges and Web3 wallet providers to comply with MiCA and Travel Rule.

Crypto exchanges and wallet providers must comply with AML directives, MiCA (Markets in Crypto-Assets Regulation), and Travel Rule requirements. iDenfy helps you meet these obligations with identity verification and screening tools.

## Recommended Features

| Feature                | Purpose                                          | Docs                                       |
| ---------------------- | ------------------------------------------------ | ------------------------------------------ |
| ID Verification (KYC)  | Onboard users with document + face check         | [Create Session](/kyc/generate-token)      |
| AML Screening          | Screen against PEP, sanctions, and adverse media | [AML Screening](/aml/create-profile)       |
| Ongoing AML Monitoring | Detect changes in customer risk profiles         | [AML Monitoring](/aml/monitoring-create)   |
| Face Authentication    | Re-verify users for high-value withdrawals       | [Face Auth](/face-authentication/overview) |
| Questionnaire          | Collect source-of-funds declarations             | [Additional Steps](/kyc/additional-steps)  |

## Sample Token Configuration

```json theme={"system"}
{
  "clientId": "wallet_67890",
  "firstName": "Alex",
  "lastName": "Johnson",
  "callbackUrl": "https://your-exchange.com/api/kyc/callback",
  "expiryTime": 1800,
  "documents": ["ID_CARD", "PASSPORT"],
  "additionalSteps": {
    "questionnaire": true
  }
}
```

## Regulatory Context

* **MiCA** requires crypto-asset service providers (CASPs) in the EU to perform full customer due diligence.
* **Travel Rule** (FATF Recommendation 16) requires originator and beneficiary information for crypto transfers above thresholds.
* **Ongoing monitoring** is mandatory — a one-time check at onboarding is not sufficient.

## Integration Flow

1. User registers on your exchange.
2. Call [Create Session](/kyc/generate-token) to start identity verification.
3. After approval, run an [AML screen](/aml/create-profile) and enable [monitoring](/aml/monitoring-create).
4. For high-risk actions (large withdrawals), trigger [Face Authentication](/face-authentication/overview).