How to monitor transfers above a minimum amount
Set a minimum amount for one asset in Monitoring: base units, an inclusive threshold, and checks using artificial data.
Updated:
In Monitoring, you can track transfers from a specified amount by setting “Minimum amount” under “Advanced filters” for an address in the selected project. The threshold is an integer in the selected asset’s smallest units. The comparison is inclusive: a transfer equal to the threshold qualifies, while a smaller one does not.
Start with one asset on one network. For example, you may want to monitor incoming transfers of a particular token to your address. This is a rule for the amount of an individual transfer, not its dollar value, the total received during a day, or a setting for messages from an external provider.
Prepare the asset and units
Select a project with the “Monitoring” service available, a public address, and permission to change its settings. Make sure the required network is available for operational monitoring. Adding a public address does not require a private key or recovery phrase.
Establish the exact asset and its number of decimal places. A token name is not enough: the network and identifier must match the selected monitoring method. If you receive USDT, do not treat different networks or similar-looking tokens as one asset. The choice is explained in “What is the difference between a network and a token?”.
Convert the human-readable amount into base units by multiplying it by ten to the power of the asset’s number of decimal places. Do not use a rounded dollar equivalent. For an asset with six decimal places, a threshold of 10 units is entered as 10000000. This is an example of scale, not a universal threshold for every coin.
Step 1. Open the add-address form
Open “Monitoring”, select the project, and open “Addresses”. Click “Add addresses”. On the “Manually” tab, select the network and enter the public address. Wait for the format check result; check ownership of the address and connection readiness separately.
In the address usage section, select “One asset”. Leave “Asset” empty for the network’s native coin, or enter the supported identifier for a token on the selected network. For this example, leave “Incoming” enabled. If you need outgoing transfers, check their support and the direction setting separately.
Do not select all assets at once for your first rule: one numeric threshold in different smallest units does not represent the same economic amount. Setting a specific network and asset pair lets you verify the calculation without mixing scales.
Step 2. Set the minimum amount
Expand “Advanced filters”. In “Minimum amount”, with the “Base network units” hint, enter the calculated integer, for example 10000000 for the scale described above. This value corresponds to the min_amount parameter.
Do not enter a decimal fraction, coin symbol, currency sign, or thousands separators here. An empty value means no separate minimum amount is set. The number is not automatically converted from dollars or adjusted to the exchange rate.
“Minimum confirmations” is a different condition. Do not change it to compensate for an incorrect amount. The threshold is checked for each individual transfer being evaluated: several smaller receipts are not automatically added together into one qualifying payment.
Step 3. Save and check the rule
Click “Add address” and complete the security check shown if your account requires it. After saving, open the address, find the rule for the correct project, and check the asset, direction, and saved minimum. Make sure the connection is active; successfully entering a number alone does not prove this.
If an address is used in several projects, check the selected rule specifically. Another project may have a different threshold and receive different events. A transfer appearing in another project does not mean your minimum was ignored.
Step 4. Check the boundary without a real transfer
For a threshold of 10000000, the expected results in smallest units are:
| Transfer amount | Amount check |
|---|---|
| 9999999 | Below the threshold; does not qualify |
| 10000000 | Equal to the threshold; qualifies |
| 10000001 | Above the threshold; qualifies |
Check these cases using prepared artificial data in a local test of your integration. All examples must have the same network, asset, address, and direction; otherwise you are testing a different condition. Sending cryptocurrency is not required to check the filter’s arithmetic. This boundary check does not confirm delivery of a notification to the selected recipient; check the notification route separately.
If the result differs from what you expected
First compare the smallest units and scale, then the asset, direction, project, and whether the rule is active. Check the actual transfer amount rather than its current estimate in the display currency. The TXID will help investigate the record. A Monitoring event alone does not confirm an order has been paid: that requires a link to an invoice and a check of its state.