What Warns knows about a merchant
Most payments an agent makes go to a merchant it already paid. The first payment to a new merchant is where it has the least to go on. Warns brings three kinds of knowledge to every decision, including that first one.
What Warns looks at
- Your own history. Where you paid each merchant, and what you usually pay. This is what catches a merchant you know that suddenly asks to be paid elsewhere, or charges far more.
- Public records. When the merchant's domain was registered, whether it is listed in the public x402 catalog, the agent identity it publishes if it has one, and what the receiving address did onchain: whether it ever received USDC, and since when.
- Other customers. What other Warns customers saw of the same merchant and the same address, counted without naming anyone (see Privacy).
What other customers bring
On a first contact, your agent has no history with the merchant, but other customers may. Warns can then tell you:
- that other customers pay this merchant at a different address;
- that the price is far above what other customers usually pay for the same thing;
- that payments to this address were blocked or refused for other customers;
- that many unrelated domains recently started asking to be paid at the same address;
- that the merchant asks for another token than its customers usually pay in.
These checks roll out one by one. Each first runs on real traffic without changing any outcome, so its results can be confirmed, then starts to count in decisions. Your own history always comes first: a merchant you already pay is judged on what you know of it.
| Code | When it shows up |
|---|---|
NETWORK_DESTINATION_CHANGED | Other customers pay this merchant at a different address. |
NETWORK_PRICE_OUTLIER | Far above what other customers usually pay, when you have too little history of your own. |
DESTINATION_SEEN_ON_HELD | Payments to this address were blocked or refused for other customers. |
DESTINATION_SHARED_WIDELY | Many unrelated domains started asking to be paid at this address in the last month. |
ASSET_CHANGED | The merchant asks for another token than its customers usually pay in. |
LOW_CONFIDENCE_REVIEW | Warns knows little about the merchant, and the payment is above your amount. Held. |
Agent identity
Some merchants publish an agent identity under ERC-8004, an open standard for agents on Ethereum networks. Warns reads the identity a merchant names on its own site, looks it up in the official registry, and checks that the identity names the merchant's domain in return. When it holds both ways, the merchant is verified on its domain.
- A merchant without an identity is never penalized. Most have none.
- A verified identity raises the confidence. So does a payment to the wallet the identity names, which only the identity's owner can change.
- Warns remembers the first identity it saw verified on each site. A site that was taken over can point to someone else's identity, but it cannot change what Warns saw before, so the switch is noted.
- A site that claims an identity it cannot prove is noted too. A false identity is worse than none.
| Code | When it shows up |
|---|---|
IDENTITY_DOMAIN_MISMATCH | The merchant claims an agent identity that does not name its domain, or that several unrelated sites also claim without proof. |
IDENTITY_CHANGED | The merchant's site no longer proves the identity Warns verified on it before. |
Like the checks above, these first run on real traffic without changing any outcome.
Privacy
- Your payments, agents, policies and reviews are never shown to anyone else.
- What customers share is only counted: how many people paid an address, never who.
- Nothing is used or shown below three other customers, so nobody can be singled out.
- Your own payments never vouch for a merchant to you: Warns only counts the others.
- One customer paying many times counts as one, and cannot set a merchant's usual price alone.
A shared address is not suspect in itself: a payment processor collects for many merchants. That is why a single report never holds anyone's payments, and why what customers refused is never shown on a public page.
Confidence
Each decision carries a confidence from 0 to 100: how much Warns knows about the merchant and the address. It goes up with your own payments there, with public records, and when other customers pay the merchant at the same address. The dashboard shows it on every transaction, under What Warns knew, as little, partly or well known, with the facts behind it.
A low confidence is not a risk. It means Warns has little to go on, and the risk score does not change.
Unfamiliar merchants
In Protect, a payment of 1 USD or more to a merchant Warns knows little about waits for a person, as a review. Nearly all x402 payments are smaller than that, so they are never held for this reason. Once you approve, the agent's retry goes through.
Change the amount, or choose Never, in Settings, Workspace, Unfamiliar merchants. To always let one merchant through, add a policy rule that trusts it with "suppress": ["LOW_CONFIDENCE_REVIEW"].
Merchant and address pages
On a transaction, the merchant's name opens what Warns knows about it: its domain, its agent identity, where you pay it, and where other customers do. The receiving address opens its own page: what it did onchain, what other customers saw of it, and your decisions that involve it.
Next: The traps