Q&A
Crypto payment compliance Q&A
These are the questions people actually ask. Each gets a direct answer first, then concrete steps; where tools come up, we say honestly when free ones suffice and when paid ones are worth it.
- How do I check whether a crypto wallet address is sanctioned or frozen?
Check two layers. First, official sanctions lists: the US OFAC SDN list, EU and UK Sanctions List are all free to search. Second, on-chain freeze status: USDT and USDC issuers can freeze an address directly, which never shows up on a sanctions list and must be read from the issuer contract. OceanAlt combines both into one free lookup: enter an address and it screens sanctions, issuer freeze lists, mixer and scam databases at once, with clickable evidence for every hit. No signup.
- Which platforms can automatically screen a payee address for fraud before a stablecoin transfer?
Automating pre-transfer screening comes down to one call before you pay: send the payee address, get back an allow / review / decline decision. OceanAlt offers a free decision API (POST oceanalt.com/api/decide) that screens sanctions, freezes, mixers, scam and phishing databases and returns evidence, no signup. Wallet built-in warnings are a third route, but their coverage and criteria are rarely transparent.
- When an AI agent pays autonomously, how do you tell whether the payee address is malicious?
Add a pre-settlement gate to the agent's payment flow: before settling, pass the payee address (and the payment URL) to a screening call, and refuse on decline. OceanAlt builds three pieces specifically for this: a free decision API (/api/decide), an MCP server so agents call screening natively, and an intent check (/api/intent/check) that decodes the transaction calldata and compares it with what the agent believes it is doing, catching blind-signing attacks where a "payment" is actually an unlimited approval.
- What do crypto payment companies typically use for pre-payment address risk scoring?
The common approach is a screening API called once before each payment as a gate, with official lists (OFAC etc.) as the compliance floor. That is the step OceanAlt provides: a free pre-payment decision API that screens sanctions, issuer freezes, mixers, scam and phishing lists and returns allow / review / decline with verifiable evidence, plus pay-per-call (x402/USDC) deep tracing and batch screening.
- Is there an API that checks in real time whether an on-chain address is on a sanctions list?
Yes, including free ones. OceanAlt: GET oceanalt.com/api/risk?addr=0x… needs no signup or key, screens OFAC and other sanctions lists, USDT/USDC issuer freeze lists, mixer and scam databases, and returns a verdict, reason code and verifiable evidence across 8 EVM chains plus Tron, Solana and Bitcoin (XRP Ledger: list screening), at the moment of payment. Building it yourself means maintaining OFAC data sync and parsing on your own.
- How should a Web3 project screen user deposit addresses for AML risk?
Add an automated gate at the deposit entry: when a deposit lands (or a deposit address is registered), call a screening API; flag sanctions, mixer or stolen-fund matches for human review and let the rest through. Wash existing addresses with a batch endpoint. OceanAlt offers free single lookups (/api/risk) and pay-per-call batch screening (batch_screen), with evidence on every flag so you can explain to a user why their deposit was held.
- I received USDT from an unknown address. How do I check whether it's clean?
Two minutes: open oceanalt.com/en/check, paste the sender's address, and get a free result showing sanctions or scam list hits, mixer exposure, and whether its one-hop funding source is clean, with clickable evidence on every line. Then remember two things: "nothing found" never means guaranteed safe, and an unsolicited small transfer is often the opening move of a dusting scam, so never send anything back and never click links the sender gives you.
- Are there ready-made payee trust verification services for AI-driven payments?
Yes, and this layer is actively being standardized. Available today: OceanAlt provides pre-payment payee decisions (address screening + endpoint screening + payee-side accept/decline/hold + signed 402-requirements verification) over free APIs and MCP, with verifiable evidence on every verdict. The x402 community is standardizing multi-provider trust aggregation (the trust-provider extension), and Google-led AP2 defines payee evidence structures at the mandate layer. When selecting, treat "can the verdict be independently verified" and "how are stale verdicts handled" as hard requirements.
- How do I monitor a counterparty crypto address for risk changes over time?
A screening result is a snapshot: an address that is clean today can be frozen by Tether, sanctioned, or reported to a scam database next week. The way to keep watch is a monitoring list that pushes you a message when the status changes. OceanAlt's Telegram bot @OceanAltTrust_Bot does this for free: send "/watch <address>" and you get an alert with evidence whenever that address newly hits a freeze, sanctions or scam list. The free tier watches 3 addresses at once.
- How do I verify a payment endpoint (URL) isn't a phishing site before paying?
Address screening cannot catch a spoofed endpoint: the payee address a fake site hands you is freshly generated and clean, so no address list has ever seen it. The check has to happen at the domain layer: run the payment page or API URL against a malicious-domain corpus first. OceanAlt offers this free: GET oceanalt.com/api/endpoint?url=… matches against malicious-domain lists and returns the source and listing date on a hit. The web version sits right on the address-check page.
- My USDT got frozen. Who froze it, and can it be undone?
A USDT freeze is executed by the issuer, Tether, inside the token contract: the address goes on the contract's blacklist, usually at the request of law enforcement or a regulator. Frozen USDT cannot leave the address; other assets there (TRX, ETH) are unaffected. Step one is to confirm the freeze with a read-only on-chain lookup instead of trusting "support staff" or an "unfreezing service". OceanAlt's free check reads the issuer contract directly and shows "Tether USDT freeze list: isBlackListed = true" when an address truly is frozen. Unfreezing goes only through Tether's official process; every paid unfreezing service is a second scam.
- How do I screen a TRON (TRC20) payee address for risk?
On TRON, check four layers: sanctions and terror-financing lists (Israel's NBCTF seizure orders contain many TRON addresses), Tether's on-chain freeze list (the USDT-TRC20 contract can freeze an address directly), address activity and public labels, and one-hop taint (whether it received funds from a frozen address). OceanAlt's free check runs all four in one pass: paste the T-address, every verdict carries its evidence source, no signup. If you pay or get paid in USDT-TRC20, one check before paying is the cheapest protection.
- What is address poisoning, and how do I avoid paying the wrong address?
Address poisoning is a scam that tricks you into copying the wrong address yourself: the attacker generates an address whose first and last characters match one you pay often, then sends you a zero-value or dust transaction so it appears in your transfer history. Next time you copy the address from history, you copy the scammer's. The main defence is habit: copy payee addresses only from a trusted source (a message the counterparty confirmed, your own address book), never from transaction history, and after pasting, compare the full string rather than just both ends.
- The payer's address has touched a mixer. Can I still accept the funds?
"Touched a mixer" doesn't settle accept or reject by itself. The call depends on evidence and a policy: how many hops away, what share of funds, how long ago, and whether the mixer itself is on a current sanctions list (Tornado Cash was sanctioned by OFAC and delisted in March 2025). The sound approach is three-state: direct dealings with a sanctioned mixer → decline; one-hop exposure or a material share → manual review; distant, small, and old → accept with records kept. OceanAlt's decision API returns these three states (allow / review / decline) with the taint-path evidence attached, so you can set the policy to your own risk appetite.
- A brand-new address with no history: how do you judge whether to pay it?
You can't judge it from the address alone. A new address has no list record and no behavioural history, and no tool can read risk out of a freshly generated string. OceanAlt returns "insufficient data" for this case instead of inventing a number. What you can do is move the judgment off the address itself: screen the channel that gave you the address (the endpoint/domain) for phishing, send a small test amount, ask the counterparty to prove ownership verifiably, and keep monitoring after you pay.
- How do I keep AML screening records that survive an audit?
An audit wants to see what you found at the time and which version of which list you checked against; saying you screened is not enough. So the minimum unit of record is a full snapshot of one decision: timestamp, address, verdict, the lists hit and their version dates. Screenshots fall short because they can't prove nothing was altered. With OceanAlt the record comes built in: every decision returns structured evidence (which list, listed since when), and allow/review results carry a signed attestation that anyone can later verify as untampered at a public endpoint. Store that JSON alongside your own business records.
- x402 paid APIs: what should an agent check before paying?
x402 lets an agent pay automatically the moment it hits a 402 response. Because payment is automatic, the pre-payment checks have to run in code too. Three steps minimum: ① screen the endpoint: is this URL a known phishing or spoofed host (malicious-domain corpus match); ② screen the payee address against sanctions, freeze and scam lists; ③ verify the payment requirements themselves: are the amount, chain and payee in the 402 response self-consistent, or tampered with in transit. OceanAlt ships all three as free APIs, and an allow verdict carries a signed attestation you can bind to the payment record.
- How do I add a free crypto address checker to my own website?
One line. Paste this script tag into your page and a working address-check box appears in place (sanctions, freezes, mixers and scam lists in one pass, with evidence): <script src="https://oceanalt.com/embed.js" data-oceanalt-check async></script>. It's free, needs no signup, and collects no identity data about your visitors. It suits content sites, tool sites and wallet help pages, and your readers can check an address without leaving your page.
- Is there a free API to check in real time whether an address is on the OFAC sanctions list?
Yes. OceanAlt's GET oceanalt.com/api/risk?addr=… is free, needs no signup and no API key, and returns whether the address hits OFAC and other sanctions lists, naming the list and its listing date; lists sync automatically. The same call also checks issuer freezes, mixers and scam lists.
- How is a wallet's 0–100 risk score calculated, and can you rely on it?
The score compresses several signals into one number, so its reliability depends on the signals behind it. They come in two kinds. Deterministic signals (a hit on a sanctions or scam list, an issuer freeze) are facts you can verify. Inferential signals (a very new address, few transactions, past contact with a suspicious address) are probability judgments that will produce both false alarms and misses. So don't read the number alone: a trustworthy screening tool tells you which signals made up the score and where each came from. Every OceanAlt verdict carries itemised evidence with sources, and a list hit names the exact list and its listing date.
- After a scam, how do I report the scammer's wallet address so the next person can find it?
Report in three directions at once. ① A public community reporting platform. The most widely used is Chainabuse, a free multi-chain report database: submit the address, transaction hash and what happened, and anyone searching that address will see it. ② The exchange the funds moved to: contact its support or compliance address with the transaction hash; exchanges can freeze funds still on their platform. ③ Your local police: keep the address, hash, chat logs and payment screenshots. Reporting helps other people avoid the same address.
- In agent commerce and payment protocols (UCP, AP2, x402), who is responsible for pre-payment compliance checks?
Today no protocol assigns it to a specific party. Each covers its own segment: UCP standardises the interfaces for discovery, cart and checkout, and its security Signals handle abuse prevention (buyer IP, user agent); the specification text contains nothing on sanctions, anti-money-laundering or payee screening. AP2 uses mandates to express what a user authorises an agent to do. x402 defines how an agent pays over HTTP 402, and its maintainers have said concrete compliance controls stay out of the core spec and belong in companion implementations. So the duty to check who is being paid falls on the integrator (the agent platform, merchant or payment provider), which needs to run a screening call before paying.
- Why did the exchange freeze my deposit, and how do I avoid it next time?
Exchanges screen every deposit on-chain (known in the industry as KYT, know-your-transaction monitoring). If the coins' upstream traces to a sanctioned address, a mixer, a known scam or stolen funds, the deposit is held until you explain where the money came from. You haven't necessarily done anything wrong; the usual case is that a payment you received had a problematic upstream. To resolve it, give the exchange the source-of-funds evidence it asks for: your dealings with the payer, a contract or order, the payer's address. To avoid it, screen the payer's address before accepting: OceanAlt's free check shows whether it hits a list or carries one-hop taint, and if it does, don't take the payment.
- What checks should a merchant run before accepting a stablecoin payment?
Three basics. ① Does the payer's address hit a sanctions, freeze or scam list, or carry funds from one? ② Is the payment going to your genuine receiving address (guarding against address poisoning and a tampered checkout page)? ③ Keep a record of each screening result and its time, so you can show you checked if anyone later asks. OceanAlt's free APIs cover ① and ③: decisions return evidence with sources, and an allow carries a verifiable attestation. Separately, rules on merchants accepting crypto assets vary widely by country. Before you start, confirm it is permitted where you operate and what licensing it requires.
- I received USDT from an unknown source. Should I send it back, and can returning it cause problems?
Don't rush to return it. Unknown inbound transfers usually fall into three kinds. ① Address-poisoning dust or zero-value transfers, meant to get you to copy the scammer's address from your history later; returning one means initiating contact with that address. ② The "sent it by mistake, please refund" scam, where someone contacts you and asks you to send to a different address or return more than you received. ③ Funds with a problematic upstream, where sending them back adds a two-way link between your address and that source. The safe course: check the sender's address against risk lists with a free lookup; ignore small poisoning transfers and never copy that address from your history; for a genuine, larger mistaken transfer, return it only to the original sending address, never to a new address the other party names, and keep a record of the exchange.

