Consent to Start KYC

1. Before starting

The customer asks A‑EXCHANGE to create an external KYC session and confirms that all information belongs to the owner of the current Telegram account. Another person’s document or selfie must not be used.

2. Provider process

• A‑EXCHANGE sends the verified phone and internal customer id to the provider.
• The customer supplies the document and selfie/liveness check directly in an external browser.
• The provider may return status, minimal document attributes, match result, expiry and decline reason.
• Verification usually takes a few minutes, but no exact time is guaranteed and manual review may occur.

3. Minimisation

A‑EXCHANGE does not store the full document number, date of birth or images. It may retain name, type and country, expiry, an irreversible hash of the masked number and result scores within the current backend contract.

4. Consequences and withdrawal

Money-related actions remain blocked without successful verification. A decline, expired document, face mismatch or exhausted attempts may require a retry or support review.

Withdrawal before launch stops the process. Once sent, the provider’s handling is also governed by its terms and applicable law.

5. Version

The service records the user, time, language and version and links current consent records to a new KYC session. A record cannot be changed retroactively.