Multiple small deposits are merged for review because the compliance system measures cumulative amounts and cumulative frequency, not individual amounts. Even if each deposit stays below the single-trigger threshold, once the total reaches or exceeds the local Travel Rule (Travel Rule) compliance threshold, the system groups those transactions together and asks you to provide source‑of‑funds information.
Different jurisdictions define "how long before it counts as one trigger" differently. For example, the EU Travel Rule applies to all transfers with no minimum amount exemption. FinCEN in the US uses a threshold of USD 3,000 equivalent, Singapore is SGD 1,500, and Japan is JPY 100,000. If your deposits within a short period (usually 24‑72 hours) cumulatively reach that amount, even if every single deposit is below the threshold, the system treats them as one "merged transaction" and activates the Travel Rule verification process.
The core logic is: the amount itself isn't the only risk‑control criterion. Whether the fund path can be traced, whether the fund behavior matches a real user profile, and whether the information matches are the system's main concerns.
Step 1: After a merged review is triggered, confirm the time range and cumulative amount covered
Find out which deposits the platform has grouped for "merged review" and what cumulative threshold has been reached. In your deposit history or assets page, look for records marked "Under Review", "Pending Verification" or "Source of Funds Required". The platform usually shows the number of merged deposits and the total amount. Cross‑check the local Travel Rule threshold that applies to you or your platform (e.g. USD 3,000 in the US, no minimum in the EU) to confirm whether the cumulative total triggered verification, identify the specific deposit range and time period, and note the total amount that triggered the review.
Step 2: Identify how the merged review was triggered
Scenario A: Triggered by cumulative amount — your multiple small deposits within the monitoring window (e.g. 24 hours) exceeded the local compliance threshold, automatically triggering a request for source‑of‑funds information.
Scenario B: Triggered by cumulative number of transactions — some risk rules are based on deposit frequency. If the same account makes frequent deposits in a short time, even very small ones, the system may trigger manual review or merged verification.
Step 3: Prepare a source‑of‑funds explanation for all merged deposits
For all the deposits that have been merged, prepare a single source‑of‑funds statement. Because the system treats these as one overall transaction, you need to explain the source of the entire batch at once, not each deposit separately. The documents required depend on the source type:
Scenario A: Funds come from another exchange (your account or a friend's) — provide a screenshot of the withdrawal record from the sending platform (including amount, time, TxID), the KYC name of the sending account (must match the beneficiary information you submitted), and a list of TxIDs for each deposit.
Scenario B: Funds come from a self‑custody wallet (your own) — provide the wallet address, verify ownership through message signing or AOPP, and supply a list of TxIDs for all the merged transfers.
Scenario C: Funds come from a third party (e.g. a friend transferring on your behalf) — provide the name of the sending platform for all the merged deposits, the sender's KYC name, and relevant withdrawal records from the sending platform.
Risk warning
If new deposits keep arriving in your account while the merged review is ongoing, they may be added to the same review window, further increasing the cumulative amount and the scope of funds you need to explain. It is wise to pause large deposits after a review is triggered until the review is completed.
Common reasons for failure
Many people believe each small deposit is "safe" as long as it stays below the threshold, ignoring the cumulative merging logic. But the compliance system has a mechanism that merges multiple deposits from the same account within a short cycle. Deliberately splitting deposits only gets you flagged as "structuring". Another problem: the merged review requires proof of the source of all merged deposits, not just one of them. Submitting incomplete proof will cause the review to be rejected.
Next steps
After you receive a merged review notice, first confirm the time range, total number of deposits, and cumulative amount. Prepare a complete source‑of‑funds statement covering all merged deposits and submit it in the format required by the platform. If the review takes longer than 48 hours, be ready to pause new large deposits during that period so they aren't counted in the current review window.
