AML Policy and Regulation

AML Policy

Purpose and Core Principles:Our service strives to prevent the use of the Multival.is platform for money laundering or terrorist financing.

1. Requirements for Creating Applications

To prevent illegal operations, the Service establishes the following requirements:
  • Personal Transfers: It is recommended to carry out transfers only in your own favor. If funds are transferred to a third party, the Client confirms that they have access to the recipient and assumes responsibility for such transfer and any associated risks.
  • Data Accuracy: All contact and personal data in the Application must be up-to-date and completely accurate.
  • Anonymization Prohibition: It is forbidden to create Applications using anonymous proxy servers or other anonymous connections (TOR, VPN, etc.).
  • Disclosure of Information: Data may be transferred to authorities upon request from law enforcement agencies, court orders, or requests from payment system administrations.

2. AML Verification and Risk Levels (Risk Score)

Each transaction undergoes an automated risk assessment procedure based on established parameters:
Risk LevelScore ValueStatus / Action
Low0% – 25%Acceptable
Medium25% – 60%Acceptable
High Medium60% – 70%Likely rejection
High70% – 100%Unacceptable
Important: An application is rejected if the risk exceeds 60% or if the amount in specific categories (markers) exceeds 5/100. Prohibited Categories (Markers): Gambling/Betting; Darknet Market; Black Market Services; Scam/Fraud; Mixer/Tumbler; Ransomware; Malware; Terrorist Financing; Sanctioned Addresses; Stolen Funds/Hack; Child Abuse. Direct transfers from the following platforms are prohibited: Bitpapa, NetEx24.net, Commex, Garantex, Hydra, Blender.io, Lazarus Group, Genesis Market, ChipMixer, Capitalist, Rapira, Cryptomus, etc.

3. Preliminary AML analysis of the address

The Client has the opportunity to independently check the address on the page: https://multival.is/en/aml-checker To use this, you must be a registered user and purchase checks in your account. Results can be sent to the operator in the chat for coordination.

4. Refund Policy and KYC Procedures

If a transfer is identified as "High Risk Score," execution is suspended. The client is offered a choice:
  1. Completion of the KYC procedure (identity verification).
  2. Refund of funds with commission deduction.
Technical requirement for refund: In TRC-20, ERC-20, and BEP-20 networks, the presence of a native asset (TRX, ETH, or BNB) on the sending address is required to pay for gas equivalent to 3–5 USDT. Refunds are processed within 48 hours. Requests are only accepted from the Email specified in the application.

5. Sanctions and Geography

Transactions with persons and companies from OFAC, UN, EU, and Canada lists are prohibited. Service is limited for countries: Afghanistan, Iraq, Iran, North Korea, Russia, Belarus, USA, Syria, and others (as per the full list).

6. Final Provisions

Users are prohibited from using the Service to carry out unlawful actions, fraudulent operations, or to circumvent current sanction restrictions. The Service reserves the right to:
  • deny the provision of services;
  • suspend the execution of an operation;
  • perform a refund in the event of identified AML risks.
The fact of using the Service confirms the User's agreement with the AML Policy. Additionally, the use of independent AML analyzers is permitted, the results of which may be accepted by the service when making a decision: https://www.chainalysis.com https://www.elliptic.co A KYC request is carried out only if there are justified grounds and in the event of identifying transactions related to stolen funds, sanctioned addresses, or terrorist financing. Information may be shared with competent authorities, including: financial intelligence; law enforcement agencies; AML providers; payment systems. In such cases, the service may request the following materials: • proof of identity (passport, ID card, or other official document); • a photo of the Client with the document; • confirmation of wallet ownership (screenshots, message signature); • description of the source of funds; • confirmation of the origin of funds; • confirmation of the transaction (screenshots, txid, transaction history).  

Protected by

Powered by