Corrections Policy

A directory of payment methods is a directory of things that change without telling anyone. Some of what is on this site is already out of date, and some of it was wrong when we published it. The question that matters is not whether we make errors — it is what happens when one is found.

What counts as an error

Four kinds, in descending order of how urgently we treat them.

A wrong acceptance claim. We say a merchant takes a stablecoin it does not take, or list a network it does not settle on. This is the most serious category, because acting on it can cost someone money — a wrong-network transfer is unrecoverable. These are fixed the same day we can verify the correction.

A stale record. The claim was right and is no longer. A gateway dropped an asset, a merchant switched provider, an option was withdrawn. Fixed as soon as we can confirm, and logged as a dated change.

A factual error in prose. A misstated fee, a wrong date, a mischaracterised policy. Fixed on verification.

A typo or broken link. Fixed, not logged.

What is not an error

Disagreement with an assessment. If a page says a merchant’s documentation is unclear, and the documentation is unclear, that is not something we will remove because the merchant would prefer we had not noticed. The same goes for the several profiles that tell readers a card would serve them better.

A verification status you would like to be higher. The status follows the evidence. If you publish a clear payment page on your own domain, the status changes because the evidence changed — that is the whole mechanism, and it is described in the verification methodology. Asking for the badge is not evidence.

An accurate listing you find unflattering. We will not remove a correct record on request. We will absolutely correct an incorrect one.

How to report one

Contact us with the merchant, what is wrong, and — this is the part that determines how fast it moves — a URL. A link to the merchant’s own payment page settles almost any dispute in minutes. Without one we have to find the evidence ourselves, and sometimes we cannot.

Merchants correcting their own record should use claim a listing, which asks the right questions in the right order.

What happens next

1. We check it. Against the merchant’s own documentation first, its payment processor second, and a real checkout where we can reach one. Your report is a pointer to evidence, not the evidence itself — and that applies to reports from the merchant as much as from anyone else.
2. We correct or we explain. If the evidence supports the correction, the record changes. If it does not, we will tell you what we found and why we are leaving it.
3. We log it. Every accepted correction that touches an acceptance claim is recorded as a dated change with a link to the source, and appears in What’s Changed and in the record’s own history.
4. We re-date the verification. A corrected record carries a fresh check date, so the badge reflects when we last actually looked.

Timeframes

We do not run a support desk and will not pretend to a service level we cannot hold. What we will say:

• Wrong acceptance claims are treated as the priority. If you send a URL, expect same-day action.
• Everything else is handled in batches, typically within a week.
• If we disagree, you will get a reply saying so rather than silence.

Withdrawals

Sometimes the right correction is to remove a listing. This has already happened several times and the precedents are in the tree:

• A merchant that turned out to accept only Bitcoin and Litecoin — withdrawn as out of scope.
• A merchant whose service is receiving stablecoins rather than spending them — withdrawn, because the directory answers one question and that was not it.
• A merchant that stopped accepting — kept, marked no longer accepting, because people still search for it and a missing page is not an answer.

Removing a wrong listing is a better outcome than keeping a plausible one.

Corrections we have made

Every one that altered an acceptance claim is on What’s Changed, dated, with the evidence attached. We do not maintain a separate corrections page, because a corrections page nobody reads is worse than a change feed people do.

Errors in the aggregate data

The Stablecoin Spend Index is computed from the merchant records at build time. There is no separate statistics store, so a figure there cannot be wrong on its own — if a number looks wrong, a record is wrong, and correcting the record corrects the number on the next build.

Published quarterly reports are bound to a frozen snapshot and are deliberately not rewritten when later data changes. If a report contains an error of fact rather than a superseded figure, we correct it in place and note the correction on the page.