The overall risk (percentage) is the probability that the address is associated with illegal activity. The sources of risk are the known types of services with which the address has interacted and the percentage of funds accepted from / given to these services for which the overall risk is calculated.

AML Check checks the specified wallet address for connections to known blockchain services. AML Check conventionally groups these services into groups with different levels of risk of illegal activity. The check shows the connections of the checked address to these groups as a percentage. Based on all the links, an average risk score is given, which helps the user to make further decisions about the assets.

Each client determines for himself what percentage of risk is
acceptable for him. Conventionally, the risk score can be divided as
follows:
- 0-25% is a clean wallet/transaction;
- 25-75% is the average level of risk;
- 75%+ such a wallet/transaction is considered risky.
It is also worth paying attention to the red sources of risk in the detailed analysis, described in page

After transaction confirmation, the balance is replenished:
• up to 10 minutes if payment was made within 24 hours after the
invoice was issued,
• up to 25 minutes if payment was made after 24 hours after the
invoice issuance. Overall, BTC, ETH, USDT, and fiat are processed
faster than other coins.

AML Check finds links of a verified address to different users in the blockchain, each with a different conditional risk score.

The overall risk score is the average of all the components found. For example, if out of 2 BTC on the wallet being checked, 1 BTC came from mining (0% risk) and another 1 BTC from Darknet (100% risk), the risk score would be 50%.

By checking counterparties' wallets before a transaction, you can reject their assets if the risk score is high. Also, before transferring funds to other services, you can check your wallet address and save the result (make a screenshot).

If the check shows that your assets had no connection with illegal activity and the service blocked you, you can provide the saved result to confirm the purity of your assets.

The verification results are based on international databases, which are constantly updated. So an address that had 0% risk yesterday may have received or given the asset to a risky counterparty today. In this case, the risk score will change. If you want to be sure of the result and determine what the cause of the high risk is, we can do a detailed check for you. To do so, email us at [email protected]

Address (wallet) check is an analysis of all addresses ever associated with it, from which funds were received and to which funds were sent. Check transaction (you need to specify TxID) and then you select:

- I received the funds (Recipient) and the address to which the funds were received (Deposit). In this case, the addresses from which the funds were received are checked. If you look at a transaction in the blockchain explorer, these are the addresses on the left and everyone they interacted with before the transaction.

— - I sent the funds (Sender) and the address to which the funds were sent to (Withdrawal). In this case, the wallet that received the funds is checked (it is on the right in the blockchain explorer), as well as all its connections before this transaction. Thus, when checking TxID, the risks for the recipient are checked if you choose receiving funds, and the risks for the sender if you choose sending funds.

They stay within your account, and you can use them at any time.

An answer to this depends on your unique risk model. The general recommendation would be to perform an AML check every time you interact with an unknown wallet or a smart contract.

AML Check supports all major blockchains and tokens on them. We are constantly adding support for additional cryptocurrencies. You can always check the up-to-date list of supported cryptocurrencies in web dashboard or in API Documentation .

You can buy additional checks as needed. The number of checks is always displayed within your user information.