Configuration in v.2.7
Setting Up the AML Module
Make sure the module is activated in the "Modules" section, or activate it if it isn't.
Add one of the 6 supported services in the "AML" ➔ "Add" section.
Remember to top up your balance with the chosen service to be able to check addresses and transactions!
If the service you want to use is not in the drop-down list, you need to install it manually. To do this, download the distribution to update to script version 2.7 (the PHP version does not matter - choose any of the distributions).
Unzip the downloaded distribution on your PC and navigate to the folder at wp-content/plugins/premiumbox/amlcheck
Select the desired module and upload (as user for the site, not as root!) the folder with it using the same path on your server.
After that, go to the AML section in the admin panel and create a copy of the AML module that you downloaded.
In the new window, fill in the authorization details in the "Module Settings" section:
Connecting to the Service
Register on the AMLBot service, log in to your personal account, and generate an ID and key for module authorization.
Enter the generated keys in the corresponding fields in the module settings and save the data.
Connecting to the Service
To connect to the service, contact the manager — they will create a chat with you and representatives from the AML service to discuss connection terms, rates, and other questions.
After gaining access to the service, top up your account to perform client verification checks on your exchange.
Go to your personal account, in the "API Keys" section. Create a new key by clicking the "Create Key" button, and in the pop-up window, specify a desired name for the key and your server's IP address (optional).
Click "Create" and copy the generated keys into a text file.
Enter the generated keys in the corresponding fields in the module settings and save the data.
Connecting to the Service
To connect to the service, contact the manager — they will create a chat with you and representatives from the AML service to discuss connection terms, rates, and other questions.
Log into your personal account and generate a new key by clicking the "Generate" button in the "API" section. Copy the generated key to your clipboard or a text file.
Enter the key in the corresponding field in the module settings and save the data.
Copy the UID in the settings of your profile in the Cryptomus personal account, generate an API key, and then specify them in the settings of the AML module itself
Connecting to the Service
To obtain an API key, send an email to info@getblock.net. Enter the key received from the service representative in the corresponding field in the module settings and save the data.
Connecting to the Service
An API key will be issued by the Matchsystems manager after the terms of service and payment are agreed upon.
Enter the key received from the service representative in the corresponding field in the module settings and save the data.
General Settings
Risk if API doesn't work — the desired risk value (from 0 to 100) that will be assigned to the verification result if no response is received from the API service. The value must be higher than the value set in the "Critical Risk Level for Address/TxID" fields.
Critical Risk Level for Address/TxID — must specify a value (from 0 to 100) above which the module will report a risk for applications in the "Orders" section (before configuring this section, we recommend consulting the manager of the chosen AML service regarding risk level settings).
Waiting Time for Verification Result (sec, max 25-30 sec) — the time to wait for a response from the service after sending data for verification (it is recommended to set a value between 15 and 28).
Script Timeout (sec) — the time during which the site waits for a response from the AML service. If no response is received within the specified time, the site will continue its operation without an answer. If the time is not set or is equal to 0, the standard timeout of 20 seconds applies. There is no universal timeout value as it depends on the specific service's speed.
Disable Logs — turning off logs for checks (not recommended).
Verification Categories — setting risk levels for various categories. Request assistance from the service you are connecting to for fine-tuning the categories (note that each module has its own set of categories for configuration).
Manual Checks
The AML module allows for manual checks of addresses, hashes, and transactions. To perform a check, go to the settings of the configured service, enter the data for verification, and click the "Check" button.
TxID is a unique transaction identifier generated before the transaction is included in the blockchain. It is usually a hash of the transaction data (e.g., inputs, outputs, signatures) but before the transaction is included in a block.
What is it used for? TxID allows for quick identification of a transaction in the blockchain. It is like an "order number" in a system.
Example: When you send cryptocurrency, the TxID is what you see immediately after creating the transaction. It helps track the status of the transaction until it is confirmed.
A transaction hash is a unique identifier that is generated after the transaction is included in a block. It is calculated based on the transaction data and additional information (e.g., block number, time, and other parameters).
What is it used for? The transaction hash is used to verify the integrity of data in the blockchain. It ensures that the transaction has not been altered after being included in a block.
Example: The transaction hash can be compared to a "fingerprint" of the transaction after it is confirmed. It is unique and depends on all the data associated with the transaction in the block.
Analogy
Imagine you are sending a letter:
TxID — is the tracking number you receive immediately after handing the letter to the post office. It helps track the letter until it is delivered.
Transaction Hash — is the unique stamp on the envelope that is applied after the letter is delivered and registered. It confirms that the letter was indeed delivered and has not been altered.
Thus, TxID and transaction hash are two stages of transaction identification: before and after it is included in the blockchain.
Address Check — check the wallet address. Enter the address and select the desired currency.
Transaction Check — check the transaction. Enter the wallet address of the recipient, select the desired currency, enter the TxID, and choose the type of transaction (deposit or withdrawal).
UID Check — check the unique identifier from the transaction verification request response.
Address Check — check the wallet address. Enter the address and select the desired currency.
Transaction Check — check the transaction. Enter the wallet address of the recipient, select the desired currency, and enter the TxID.
Address Check — check the wallet address. Enter the address and select the desired currency.
Transaction Check — check the transaction. Enter the wallet address of the recipient, select the desired currency, and enter the TxID.
Check address — specify the wallet address, as well as select the desired currency and network
Check transaction — specify the recipient's wallet address, enter the TxID and select the desired currency and network
Check hash — check the transaction hash by ID
Address Verification — This feature allows you to check a wallet address. Please enter the address and select the desired currency.
Hash Verification — This feature allows you to verify a transaction. Please provide the TxID and select the appropriate currency.
Address Check — check the wallet address. Enter the address of wallet
Transaction Check — check the transaction. Select the desired currency and enter the TxID
Logging
In the "AML" ➔ "Logs" section, you will find the results of the verifications as well as any errors encountered while using the services.
Module Configuration for Exchange Direction
You can use the module for both address and hash verification without interfering with the request, as well as to prohibit the creation of requests or the disbursement of funds.
Open the settings for the exchange direction where you want to use the verifications and navigate to the "AML" tab. Select the previously configured AML service and set the specified options.
Verification of "Send" and "Receive" Accounts:
No — No verification will be performed.
Yes, during request creation — Verification will be conducted to prevent the creation of a request if the specified risk level is exceeded.
Yes, at payment — The account verification will be performed when accepting a payment made by the client (only if the exchange direction has the merchant module for receiving funds enabled).
Yes, during auto-disbursement — The account verification will be performed before disbursing funds to the client (only if the exchange direction has the auto-disbursement module enabled).
Risk Exceedance: • Nothing — Verifications will be conducted for informational purposes only. • Error — If the risk level specified in the module settings is exceeded, an error will be displayed to the client when creating a request or attempting an auto-disbursement (depending on the settings).
Exchange Amount "From" — Specify the amount from the request, above which the address or transaction verification will be performed. If the amount in the request is below this specified value, no verification will be conducted.
The value should be specified in the currency for which the address will be verified (for example, for verifying a USDT address, specify 1000; for BTC, specify 0.015, etc. — you can set the minimum amounts for which verifications will be performed at your discretion).
TxID Verification:
No — The TxID verification for incoming payments will not be performed.
Yes, at payment — The TxID verification for incoming payments will be performed when accepting a payment made by the client (only if the exchange direction has the merchant module for receiving funds enabled).
Yes, during auto-disbursement — The TxID verification for incoming payments will be performed before disbursing funds to the client (only if the exchange direction has the auto-disbursement module enabled).
Exchange Amount "From" — Specify the amount from the request, above which the hash verification will be performed. If the amount is below this specified value, no verification will be conducted (the amount value is specified in the currency for the "Send" side).
Last updated