Compliance for stablecoin payments
Stablecoins move money without saying anything about it.
Mersane scores every stablecoin payment before it settles, and produces the record your bank will accept afterwards. One API call.
- $33T
- stablecoin transfer volume in 2025
- 733%
- growth in B2B stablecoin payments, year on year
- $950B
- of 2025 flow that could not be classified at all
The gap
What the rail carries, and what your bank asks for.
A stablecoin transfer carries
- Sender address
- Receiver address
- Amount
- Token and chain
- Timestamp
A bank wire has carried, by law, since November 2025
- Verified payer identity
- Verified beneficiary identity
- Structured remittance information
- Invoice references and line-item detail
- Standardised purpose codes
- Ultimate debtor and creditor across every hop
- Regulatory and compliance data
The banking system spent a decade making sure that information travels with every payment. It finished the job in November 2025. Stablecoin rails carry none of it.
Why it matters
Your bank should never be the one who finds it first.
Crypto neobanks, payroll platforms and remittance apps all depend on a sponsor bank or an off-ramp partner to turn stablecoins into money in someone's account. When something bad gets through, the bank catches it, and there is nothing to explain it with.
Lose that relationship and the company usually ends. The tools built for this problem are enterprise platforms sold to banks with two hundred analysts. Our customers have none.
How it works
One call, before the money moves.
You send us a pending payment
Wallet, amount, chain, your customer ID, and whatever context you have.
We reconstruct what the rail discarded
We walk the funds backwards on chain, build a behavioural baseline from your own ledger, and work out the payer, the purpose and the matching invoice.
You get a verdict and a record
Allow, review or block, with the reasoning. Plus a signed, timestamped record you can hand to your bank.
The integration
Hours, not weeks.
No SDK required. No dashboard to learn. No analyst to hire.
const verdict = await mersane.screen({
from: "0x7a3f...c91d",
to: "0x1c88...4b02",
amount: "5000.00",
token: "USDC",
chain: "base",
customer_id: "cus_8812"
});
if (verdict.action === "block") {
return holdPayout(verdict.reason);
}What we look at
Two signals nobody else joins together.
On-chain provenance
We trace funds backwards across hops and flag exposure to mixers, sanctioned addresses, high-risk exchanges, bridges and known fraud clusters. Not a single score, a chain of custody.
Account behaviour
We build a baseline for each of your customers from your own transaction history: typical size, counterparties, corridors, timing. Then we catch what is wrong for that account, not just wrong in general.
Chain analytics have the chain and not the account. Fraud platforms have the account and not the chain. The signal lives in the overlap.
Start without integrating
Send us last month. We'll show you what we'd have caught.
Export your historical transactions. We score them offline, with no integration and nothing touching production, and come back with what we would have flagged and why. Then you decide whether to turn it on.
Built for
Companies moving stablecoins on behalf of other people.
- Crypto neobanks
- Payroll platforms
- Remittance apps
- B2B payment startups
- Contractor payment platforms
- PSPs adding stablecoin rails
Typically ten to fifty people. Running on Bridge, BVNK, Conduit or Circle. No compliance team. A banking relationship they cannot afford to lose.