AML / KYC Policy

1. AML/KYC policy objectives

The Service applies AML/KYC measures to:

  • prevent use of the Service for fraud, money laundering, and other illegal activities;
  • protect users and the Service from financial risks and losses;
  • comply with risk management standards and compliance requirements applicable to digital asset transactions.

2. Which transactions may be reviewed

Transactions subject to review (automated and/or manual) may include:

  • transactions with elevated risk profiles based on transaction analytics;
  • transactions linked to addresses/wallets with indicators of illicit activity;
  • transactions with atypical volumes, frequency, or user behavior;
  • transactions flagged by external risk signals (for example, reports of compromised details);
  • transactions that raise doubts about the correctness or source of funds.

3. When verification may be required

The Service may request KYC verification and/or additional information if:

  • the transaction shows elevated risk indicators;
  • there are discrepancies in the request data, details, or payment confirmations;
  • the user uses details that may belong to third parties;
  • there are signs of network/direction errors or substituted details;
  • confirmation of source of funds or authority to dispose of assets is required.

4. What data may be requested

Depending on the situation, the Service may request:

  • identity information (full name, date of birth, ID document—partially redacted if appropriate and permitted);
  • proof of control over details (wallet screenshot, message from account, confirmation of receiving address, etc.);
  • proof of payment/transfer (transaction hash, receipt, slip, statement);
  • selfie/video verification per instructions (to prevent identity substitution);
  • information about the source of funds (e.g., explanation and/or supporting documents—case by case).

The Service requests only what is necessary to review a specific transaction and strives to minimize the amount of data.

5. Review timelines

Review timelines depend on case complexity, the quality of submitted materials, and support load.

Typically, review takes from several minutes to several business days. In non‑standard cases, the timeframe may be extended.

If the user does not provide the requested data within a reasonable time, the request may be suspended or cancelled.

6. Actions in case of suspicious activity

If indicators of suspicious activity are found, the Service may:

  • suspend request execution until the review is completed;
  • request additional information and documents;
  • refuse service;
  • refund funds (where technically possible) to the sender’s details, deducting actual expenses and fees, if permitted and consistent with security requirements.

7. Refusal of service and freezing of funds

Where there are material risk indicators, the Service may suspend the transaction and retain funds until the review is completed.

In some cases, when risks cannot be acceptably reduced, the Service may refuse service and initiate a refund where technically possible.

The Service is not liable for consequences caused by security checks conducted in good faith to prevent fraud and violations.

8. User consent to the policy

By creating a request and using the Service, the user confirms that:

  • they have read this AML/KYC policy and agree to its application;
  • they understand that additional data may be requested and the request may be suspended during review;
  • they undertake to provide accurate information and documents upon request to complete the transaction.