AML Policy

Bitsz.io Anti-Money Laundering, Anti-Terrorism Financing Policy (AML Policy) and Know Your Customer Policy (KYC Policy) aim to minimize risks associated with illegal activities involving the services of bitsz.io. This policy reflects compliance with international standards and local regulatory requirements.

To comply with regulations such as the Fifth Anti-Money Laundering and Anti-Terrorism Financing Directive (5AMLD), bitsz.io establishes internal mechanisms to combat money laundering, terrorism financing, drug trafficking, corruption, and other illicit activities. Suspicious transactions and user activities are scrutinized to ensure compliance.

The platform providing cryptocurrency exchange services must conduct thorough checks on suspicious transactions, including user identification (KYC) and verification of the origin of cryptocurrency assets. Assets under review are held on balance until verification is complete.

By placing an order, the Client consents to potential AML/KYC checks.

1.1. AML/KYC checks for transactions and users are conducted by an appointed AML officer within bitsz.io, in coordination with liquidity providers and cryptocurrency exchanges.

1.2. During these checks, Clients agree to the collection, storage, and transfer of their personal data to relevant authorities or liquidity providers if required.

1.3. AML/KYC procedures include:

  • Continuous monitoring of transactions within bitsz.io;
  • Appointment of a Money Laundering Reporting Officer (MLRO);
  • Application of risk-based approaches;
  • Comprehensive Customer Due Diligence (CDD);
  • Regular staff training to enhance AML/KYC awareness;
  • Collaboration with regulatory and legal entities;
  • Maintaining accurate records and reports.

2. Transactions flagged as high-risk (40% risk or above) or linked to the following categories may be subject to indefinite suspension pending verification:

  • DARK SERVICE
  • SCAM
  • STOLEN
  • MIXING (MIXER)
  • SEXTORTION
  • RANSOMWARE
  • HACK
  • PHISHING
  • TERRORISM FINANCING
  • FRAUD
  • BLACKLIST
  • CYBERCRIME ORGANIZATION
  • NARCOTICS
  • HUMAN TRAFFICKING
  • SANCTIONS
  • GAMBLING

2.1. Liquidity providers or exchanges may request suspension of a transaction until KYC verification is finalized.

2.2. Law enforcement or competent authorities may also request asset freezes pending investigation.

2.3. If suspicious behavior is identified by bitsz.io’s AML officer, transactions may be suspended until all required checks are complete.

3. KYC Documentation Requirements:

Clients must submit the following to confirm the origin of funds:

  • Platform and method used to receive funds (include screenshots and transaction links);
  • Purpose of the transaction;
  • Transaction details (amount, date, time);
  • Communication records with the sender confirming the transfer.

Required supporting documents:

  • Photo ID (passport, ID card, or driver’s license);
  • Selfie holding the ID and a handwritten note with the date and signature.

3.1. Processing times for KYC reviews vary and are case-specific.

3.2. Blocked assets are only refundable post-KYC approval.

3.3. Assets failing AML verification cannot be processed or exchanged.

3.4. Successful KYC may incur a 5% refund fee.

4. Additional transaction fees (up to 5%) may apply for high-risk cases, including those flagged as:

  • DARK SERVICE
  • SCAM
  • STOLEN
  • MIXING (MIXER)
  • TERRORISM FINANCING
  • OTHER HIGH-RISK CATEGORIES

 5. Refunds cannot be processed if:

  • Regulatory authorities or legal orders mandate asset retention;
  • Liquidity providers withhold the funds.

5.1. Refunds for errors or AML-related issues are not possible without KYC compliance.

6. If Clients fail to respond to information requests within 30 calendar days, assets may not be returned.

7. Blocking of transactions may occur if linked to prohibited platforms such as:

  • Tornado Cash, Hydra, Blender.io, Garantex, and others linked to sanctioned entities or activities.

7.1. High-risk wallets or platforms like FreeWallet and Railgun may also prompt transaction blocks by bitsz.io.

8. Liquidity providers may decline to release frozen funds based on clauses 2, 2.3, or 7.

9. Clients are encouraged to contact support through Live Chat for pre-checks regarding potential blocks before initiating transactions.