Compliance · Field note

ChangeNOW, SimpleSwap and the AML Score Problem: When Clean Funds Get Flagged

ChangeNOW, SimpleSwap and the AML Score Problem: When Clean Funds Get Flagged

A community summary compiled on BitcoinTalk lists Changelly, ChangeNOW, SimpleSwap and WhiteBit as the four non-custodial swap providers most frequently complained about for KYC-triggered holds — not because their compliance policies differ meaningfully from one another, but because all four rely on the same small set of third-party AML scoring tools, chiefly AMLBot, alongside broader industry names like Chainalysis, Elliptic and TRM Labs. None of these providers publish a false-positive rate for their scoring systems, but it is widely acknowledged across the industry that such rates are meaningful, not negligible, and that clean holders are caught by them regularly.

If your funds have been held by ChangeNOW or SimpleSwap on the basis of an AML score you were never shown, you are dealing with a structural feature of how these platforms operate, not a targeted decision made about you specifically. Understanding how the scoring actually works, and where the industry’s informal standards for review actually sit, is the difference between writing a support ticket that goes nowhere and building a dispute that a compliance analyst can act on.

Why exchanges treat an AML score as ground truth

Non-custodial swap providers generally do not run their own investigative teams capable of independently verifying a transaction’s history. Instead, they license a scoring service, feed each incoming and outgoing address through it, and act on the resulting risk score largely as received. This is partly a matter of cost — building an internal compliance investigations team is expensive — and partly a matter of legal cover, since acting on a recognised third-party score gives the platform a defensible position if regulators later ask why a particular transaction was allowed through or blocked.

The consequence is that the score itself becomes the effective decision-maker, even though it was never designed to be a final word on any individual case. AML scoring tools are built to flag statistical proximity to known bad actors — shared addresses, similar transaction patterns, connections within a certain number of hops on the blockchain graph — not to make a definitive legal finding about any specific user’s intent or knowledge. Exchanges nonetheless often treat a high score as though it were a settled fact rather than a probabilistic flag warranting further review.

How a clean holder ends up with a poor score

The mechanism by which an entirely innocent holder acquires a poor AML score is almost always inherited rather than earned. Every USDT address carries the transaction history of every address that has ever sent funds to it, at least as far back as the scoring tool’s lookback window extends. If an address several transactions upstream was later — sometimes years later — identified as connected to fraud, theft, or sanctions evasion, that taint can propagate forward to every subsequent holder who received funds along that chain, regardless of whether any of them had any knowledge of, or connection to, the original bad actor.

  • A single flagged address several hops upstream can lower the score of every subsequent address in the chain
  • The flag is often applied retroactively, meaning a transaction was clean at the time it happened but is reclassified once the upstream address is later identified as risky
  • Different blockchains carry different baseline exposure — TRC-20 USDT, in particular, sees materially more OTC and fraud-linked contamination than ERC-20 USDT, given usage patterns in certain OTC markets
  • There is generally no user-facing appeal process attached to the scoring tool itself — the score is simply handed to the exchange, which then decides independently how to act on it

This last point deserves particular emphasis. A user cannot contact AMLBot, Chainalysis, Elliptic or TRM Labs directly and ask them to reconsider a specific address’s score. The scoring companies operate as infrastructure providers to the exchanges, not as a consumer-facing service, and any dispute has to be routed through the exchange that used the score to justify its hold, even though the exchange itself did not generate the underlying data.

This creates an awkward accountability gap. The exchange can, and often does, tell a frustrated user that its hands are tied because the score came from an external provider, while the external provider has no direct relationship with the user at all and no obligation to respond to an individual query. The practical effect is that responsibility for the decision is diffused across two organisations, neither of which feels fully accountable for the outcome, and the user is left negotiating with the one party — the exchange — that has the least ability to change the underlying data driving the decision.

The unofficial rule most compliance teams actually apply

Despite the lack of a published, universal standard, informal practice across several compliance teams we have observed converges on treating direct exposure — a transaction one hop away from a known bad address — with far more seriousness than exposure three or more hops removed. A three-hop rule is not written into any public policy document, but it functions as a rough proxy in practice: the further removed a holder is from the original flagged transaction, the more plausible their claim of ignorance becomes, and the less justification a compliance team has for continuing to hold funds indefinitely.

A properly documented dispute makes this distance explicit rather than leaving the compliance team to work it out unprompted. That means reconstructing the actual transaction path — not just asserting innocence, but showing, address by address, how many hops separate the account holder from the specific flagged transaction, and providing whatever independent evidence exists (exchange KYC records, invoices, or other documentation) that the funds in the holder’s own hands came from a legitimate source regardless of what happened further upstream.

It is worth noting that different compliance teams apply this informal rule with different degrees of rigidity. A larger, better-resourced exchange may have a dedicated analyst capable of reviewing a hop-by-hop submission carefully and reaching a considered judgement. A smaller swap provider, operating with a thin compliance team stretched across a high volume of flagged transactions, is more likely to apply a blanket policy regardless of hop distance, simply because there is no capacity to review each case individually. This is one reason similar disputes can resolve quickly on one platform and drag on for months on another, even where the underlying facts are almost identical.

Where UsdtFreeze fits

We work with holders whose funds have been caught by an AML score they had no way to anticipate or contest directly, across ChangeNOW, SimpleSwap, Changelly, WhiteBit and similar platforms. We coordinate with partner counsel across 15+ jurisdictions, since these providers are frequently registered in jurisdictions distinct from where the user resides, and the correct escalation path depends on that corporate structure.

We ask for an NDA before details, given the sensitivity of the address histories and transaction data involved in reconstructing a hop-by-hop dispute. A dispute involving a middleman OTC counterparty somewhere upstream is typically twice as difficult to resolve through the platform’s own support desk alone, which is where our jurisdictional pool of counsel, matched to wherever the platform is actually registered, makes the difference. Our Standard engagement is $20,000 in ETH, with a $10,000 refund if the case is unsuccessful, and VIP hourly rates apply where a case requires deeper on-chain forensic work across multiple addresses. UsdtFreeze is not a law firm. We are the middleman who builds the hop-distance evidence a compliance team is actually looking for, even when no formal appeal process exists for the underlying score itself. If your funds have been flagged on an AML score you cannot see or challenge directly, get in touch, email [email protected], or message @unfreezeusdt.

FAQ

Can I find out my own AML score before sending funds through one of these platforms?
Generally, no. AML scoring tools are built for use by exchanges and compliance teams, not as a consumer-facing lookup service, so most users have no way to check their address’s score in advance of a transaction being flagged.

Does using ERC-20 instead of TRC-20 USDT reduce my risk of being flagged?
It can help, since TRC-20 USDT sees materially higher rates of OTC and fraud-linked contamination in aggregate, but it is not a guarantee, since any address history — on either chain — can carry inherited exposure from a previous holder.

Is there any way to clean an address’s score permanently?
Not directly, since the scoring providers do not offer a public correction process. The realistic path is not to erase the flag but to build a clear, evidenced case for the exchange that the current holder’s own funds and conduct are legitimate, distinct from whatever happened upstream in the address’s history.

Next step

Think a freeze is affecting your position?

Send the tx hashes, exchange references, and rough timeline. We open a jurisdictional pool review under NDA and come back with a candid position.

[email protected] · Telegram @unfreezeusdt · NDA on request