Spotlight
Stablecoin payouts for marketplaces
Paying sellers in hard-currency stablecoins can solve corridors that correspondent banking handles badly — and introduces a compliance stack most marketplaces have not built.
The problem
A marketplace with sellers outside its home region eventually hits corridors where conventional payouts work badly: transfers that take days, deductions applied somewhere in the correspondent chain that nobody can itemise, and recipients whose local banking access is limited. Seller churn in those corridors is a payments problem presented as a product problem.
What the approach looks like
Settlement to sellers in a hard-currency stablecoin, with the seller choosing whether to hold it or convert locally. In practice this means a payout provider with stablecoin rails, a conversion path at both ends, and — critically — a compliance stack that treats these as the regulated transfers they are.
The stack you actually need
Four categories, not one:
- Crypto & stablecoin infrastructure — custody or wallet infrastructure, on/off ramps, and the transfer rails themselves.
- FX & cross-border — conversion into and out of the stablecoin, and the corridors where a local rail still beats a token.
- KYC & KYB — the seller onboarding standard required for this kind of transfer, which is higher than for a domestic payout.
- Fraud & AML monitoring — travel-rule compliance, wallet screening and transaction monitoring built for on-chain flows.
What makes it hard
The compliance load is the real cost. Stablecoin transfers attract requirements that conventional payouts do not — counterparty information rules, wallet screening against sanctioned addresses, and treatment that varies by jurisdiction and is still moving. Several markets have adopted or are adopting specific regimes for this, and the answer differs per corridor.
The second difficulty is the last mile. A stablecoin payout is only useful if the seller can turn it into local spendable money at a sane cost. If off-ramp coverage in your corridors is thin, you have replaced one bad experience with another.
Questions to put to providers
- Which corridors do you cover for both payout and off-ramp, and what is the all-in cost per corridor?
- Who holds custody, under what arrangement, and what happens in your insolvency?
- How is travel-rule compliance handled, and with which counterparties?
- What wallet screening is applied, against which lists, and what happens to a hit?
- What is the reconciliation model — how do on-chain settlements land in my ledger?
- What licences do you hold in each market where I would be paying sellers?
Honest assessment
This is a high-regulatory-load approach that solves a specific, real problem. It is a poor fit for a marketplace whose corridors are well served by local rails, and a strong fit for one whose sellers are repeatedly complaining about payouts that arrive late and short. Decide by corridor, not by category.
Several of the categories above are still onboarding providers on Finlane — you can publish an RFP in them, but expect fewer responses than in banking-as-a-service or card issuing today.
- When this applies
- Sellers in corridors where bank payouts are slow, expensive or unreliable
- Build difficulty
- High
- Regulatory load
- High
Categories involved
Take this to providers
Describe the requirement once and let matching providers in each category respond. You stay anonymous until you accept one.
Related reading
- Seven reasons BaaS providers reject applicantsRejection from a banking-as-a-service provider is usually a risk decision made early and rarely explained. Here are the seven reasons it happens — and what to change before you apply again.
- Paying marketplace sellers across bordersSeller payouts across corridors: what breaks, which provider categories are involved, and the questions that separate a payout provider that works from one that looks like it does.
- Launching a business account inside a SaaS platformWhat a vertical SaaS platform needs to offer its customers a branded business account: the licence question, the stack, the onboarding reality and the sequence to procure in.