> For the complete documentation index, see [llms.txt](https://maxtronize.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://maxtronize.gitbook.io/docs/compliance-and-kyc-flow.md).

# Compliance and KYC Flow

KYC is performed once via Sumsub regardless of which chain the user intends to use. The backend then pushes the approved KYC status to the appropriate chain's whitelist based on which properties the user interacts with.

<br>

![](/files/XhzRTSnRvT2VM0TadZ42)

Diagram 7: Compliance and KYC Flow

<br>

### KYC Process

| Step | Actor       | Action / Description                                                               |
| ---- | ----------- | ---------------------------------------------------------------------------------- |
| 01   | User        | Submits identity documents via Sumsub on the platform                              |
| 02   | Sumsub      | Performs liveness check, document OCR, face match                                  |
| 03   | Sumsub      | AML screening against global watchlists (PEP, sanctions, adverse media)            |
| 04   | System      | Jurisdiction detected from user profile and document country of issue              |
| 05   | India       | RBI and SEBI compliance - Aadhaar/PAN, FEMA rules for foreign investors            |
| 06   | UAE         | DFSA and VARA compliance - Emirates ID, CBUAE AML, VARA token regulations          |
| 07   | USA         | SEC accredited investor check - income or net worth threshold verification         |
| 08   | KYC Service | On approval: pushes whitelist entry to Canton EVM KYC Registry                     |
| 09   | KYC Service | On approval: pushes whitelist entry to Cardano KYC Whitelist                       |
| 10   | User        | Can now transact on Canton EVM, Cardano, or both - based on their property choices |

<br>

### Jurisdiction Requirements

| Requirement                    | India          | UAE            | USA                     |
| ------------------------------ | -------------- | -------------- | ----------------------- |
| Regulator                      | RBI / SEBI     | DFSA / VARA    | SEC / FinCEN            |
| ID Required                    | Aadhaar + PAN  | Emirates ID    | SSN / Passport          |
| Investor Type                  | Retail allowed | Retail allowed | Accredited only (Reg D) |
| AML Screening                  | Required       | Required       | Required                |
| Tax Reporting                  | Form 26AS      | No income tax  | Form 1099 / K-1         |
| Token Classification (Canton)  | Digital Asset  | Virtual Asset  | Security (per SEC)      |
| Token Classification (Cardano) | Digital Asset  | Virtual Asset  | Security (per SEC)      |

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://maxtronize.gitbook.io/docs/compliance-and-kyc-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
