How to AML-check incoming crypto payments and verify invoice payments with Claude
PublicAML · Guide · 15 November 2026
If a business takes USDT or other crypto from clients and partners, two questions come up with every payment. Did the money really arrive: the right asset, the right network and the full amount? And is it clean enough to accept? This guide sets up Claude Code with the free PublicAML plugin to answer both on demand or every day. You need no AML vendor contract and no API key.
Why screen incoming payments at all
Funds that passed through a hack, a scam, a sanctioned wallet or a mixer can follow you. Tether freezes USDT addresses at law-enforcement request, and exchanges block deposits whose recent history is risky. If you accept such a payment, you can end up with a frozen balance or a closed exchange account. Regulated businesses also have to show that they checked.
Exchanges call this KYT, "know your transaction": every incoming transfer is screened before the funds are used. Claude can do the same for a small team. It pulls the transfers, scores each sender, and writes a plain answer with the reason behind any flag.
1. Install the plugin
Inside Claude Code, run these two commands and restart Claude Code:
/plugin marketplace add saloprj/publicaml-claude-plugin /plugin install publicaml@publicaml
2. List your wallets
Create ~/.claude/publicaml-wallets.txt with one receiving wallet per line, as chain and address. Supported chains are bitcoin, ethereum, bsc and tron. Notes after # are optional. To keep a list per project, put the same file as publicaml-wallets.txt in the project folder instead.
The list stays on your machine. Only the addresses being checked go to PublicAML.
tron TXyz... # main USDT wallet ethereum 0xabc... # treasury bsc 0xdef... # BNB Chain
3. Screen what came in
Ask "screen all incoming payments to our wallets this week", or run /publicaml:incoming-payments. For each wallet, Claude:
- pulls incoming transfers since the last check (the first time, the last 7 days);
- drops dust, unknown airdrop tokens and zero-value "address poisoning" transfers that imitate your real counterparties;
- risk-scores every distinct sender once, from 0 to 100, as LOW, MEDIUM, HIGH or CRITICAL;
- for HIGH and CRITICAL senders, explains the path the risk took: for example, "received USDT 2 hops from a sanctioned exchange";
- returns one table with date, wallet, sender, amount, score, what the sender is, and a suggested action.
What to do with each level
- LOW: accept.
- MEDIUM: accept and note the reason. Indirect exposure only is normal for wallets funded from big exchanges.
- HIGH: hold the funds. Ask the counterparty where the money came from, and keep the risk path as evidence.
- CRITICAL or direct sanctions: do not move the funds and do not send them back on your own. Escalate to whoever handles compliance. A refund to a sanctioned address can itself be a violation.
4. Verify that an invoice was paid
Give Claude the invoice facts: receiving wallet, asset and network, amount, invoice date, and the tx hash if the client sent one. You can also attach the invoice PDF. For example: "Did ACME pay invoice 1042: 4,800 USDT TRC-20 to TXyz…? They say the hash is 9f3c…". The /publicaml:verify-invoice-payment skill then works in three steps:
- With a hash, it checks that exact transaction: asset, recipient and amount. Without one, it searches incoming transfers from the invoice date by amount, and adds up partial payments.
- It screens the payer. If the payer is an exchange hot wallet, it says so: the real payer is that exchange's customer.
- It gives one verdict: PAID; PAID, HOLD FOR REVIEW; UNDERPAID or OVERPAID with the difference; WRONG ASSET or WRONG NETWORK (for example USDT sent on Ethereum to a TRON invoice); or NOT FOUND, with what was searched.
5. Make it daily
With /loop 1d /publicaml:incoming-payments, the screening runs once a day while Claude Code is open. Each run picks up only the transfers since the previous one. For an always-on setup on a server, the same tools are available as an API and an MCP server (links below).
Limits
A score is a risk signal built from public blockchain data and our attribution, not a legal verdict. "No history in our index" is not the same as "clean". A transaction that is not yet confirmed or indexed shows as "not found yet": re-check in a few minutes. Never confirm a payment from a screenshot alone; it has to be visible on-chain.
FAQ
- Is it free?
- Yes. The plugin, the MCP server and the checks are free, with no account or API key. Claude Code itself needs a Claude subscription or API access.
- Which chains and assets?
- Bitcoin, Ethereum, BNB Chain and TRON for payments: native coins plus USDT and USDC. Solana for address screening.
- Does it see my funds or keys?
- No. Every tool is read-only. It looks at public blockchain data for the addresses you check and cannot move anything.
- Can I use it without Claude Code?
- Yes. Add the MCP server https://mcp.publicaml.org/mcp to Claude Desktop, claude.ai, Cursor or ChatGPT, or call the REST API. The plugin adds ready-made workflows on top of the same tools.
