Stablecoin settlement layer · costs side by side
63% less to settle the same volume.
Move the volume to yours. The gap between the two bars is money that currently leaves your business as processing cost.
Card and correspondent-banking rates fall in a 2 to 6% band (World Bank, BIS 2026), and the incumbent figure used here sits at the conservative end of it at every volume. That is deliberate: a head of payments knows their own effective rate precisely, so widening the gap with a flattering anchor would only cost us the meeting. Cross-border adds an FX leg to the incumbent, against the 1 to 4% typically hidden in the exchange rate. It adds nothing to our side: the tiered rate is what you pay us all in, and our own FX spread is a cost we carry rather than a line we charge. Both sides tier down with settled volume, because incumbent pricing does too; holding theirs flat while ours falls would inflate the gap. Our own rate at any volume is set by the tiered table in Pricing. The licence is charged at cost.
How it works
Fiat in. Stablecoin speed.
Fiat out. Under your brand.
A whitelabelled settlement rail: any payment in, settled in stablecoin on Base (EURC and USDC live) in seconds, split atomically, and your customers only ever see your brand.
Cards, Apple Pay, bank transfer. Your customer sees your brand, never ours.
EURC on Base, final in seconds.
Programmable, API-defined per customer: check-in, proof of delivery, milestone.
Atomic: payout, margin, budgets. No reconciliation.
Near-instant, with native on and off ramps.
One engine, every currency.
The engine is coin-agnostic. The currency is a corridor decision.
- EURC live
- USDC live
- GBP and other local-currency stablecoins integration-ready
- A new coin is configuration, not a rebuild
What you would otherwise be choosing between.
Orchestrates legacy rails. Payouts still ride T+2 banking and banking-hours cut-offs, and the cost is a percentage of every transaction.
Moves the transfer leg. Escrow, conditional release, atomic splits and compliance hooks are left to you to build and operate.
The usual default. That means the escrow contracts, the trigger library, the dispute edge cases, the compliance wiring, the ramps and the reconciliation, then maintaining all of it.
All of it, under your brand, on one rail. You define the release condition; we settle against it and split the payout in the same transaction.
Chargebacks are buyer protection by lawsuit. Escrow is buyer protection by design.
Proof
The rail is built
and tested.
Setlz is not a concept. The rail, escrow, delivery triggers and integrations are built and tested end to end across repeated runs. We built this underneath a working marketplace rather than from a specification, which is why the trigger and dispute logic covers the cases it does.
Open any settlement below: capture, escrow, the rule that held it, and the split that fired the moment the condition was met.
| Capability | Setlz | Cards + bank payouts |
|---|---|---|
| Settlement | Seconds | T+2 or worse |
| What you pay | Tiered basis points, falling with settled volume. See Pricing. | 2 to 6% plus FX spread |
| FX | Transparent on-chain swap, basis-point spreads on deep pools | 1 to 4% margin hidden in the exchange rate |
| Cross-border | Native | Correspondent banking |
| Splits | Atomic and programmable | Manual reconciliation |
| Chargebacks | None on-chain | Weeks of exposure |
| Uptime | 24/7 | Banking hours |
Every row above is money. Faster settlement is working capital. Lower cost is margin. No chargebacks is fewer write-offs.
Safety and custody
Holding other people's money,
for a moment.
Compliance: obligation yours, tooling ours.
Your policy, executable on our rails.
- Pluggable KYC: bring your provider or use the pre-wired integration
- AML screening hooks
- Jurisdiction geo-fencing
- Transaction-level reporting
Screening as a release condition: an escrow can be programmed not to release until your own checks pass.
Who can move the money.
The question behind every other question on this page.
Custody today: client-owned accounts at regulated bank and PSP partners. We hold no customer funds, so a failure on our side is not a loss of your money. Release is executed by the settlement contract against the condition you defined, not by someone at Setlz deciding to send it.
Reserves: escrowed balances are held one for one in fully-reserved stablecoin. They are not lent, rehypothecated, or used for treasury yield. Idle-balance routing exists for our own operating float and never touches escrowed funds.
Audit: the settlement contracts have been audited by Hacken.
Disputes: outcomes are rule-based and resolve inside a defined window. Funds stay in escrow until the rule fires, so a dispute delays a release rather than clawing back a completed one.
Where you stand, and where we do.
Stated plainly, because it decides who carries what.
Today: settlement runs on regulated bank and PSP partners with client-owned accounts. The funds stay in your name and we never take possession of them, so your merchant-of-record posture does not change.
Next: we are acquiring an authorised EU electronic money institution. That makes us the regulated principal and lets us settle as merchant of record on your behalf, which moves liability for the settlement leg from you to us. That is why the licence matters to you and not only to us.
Either way: escrowed balances are held one for one, fully reserved, and are not lent to anyone.
Pricing
Two lines. One rail.
Licence at cost. Transactions for profit. The licence covers onboarding, integration and support, and is priced to cover cost rather than to earn: we make money only when you transact.
Transaction fee · by settled volume
Where the 40% comes from. Card processors charge roughly 2 to 6% of every transaction for less, on published rates that vary by acquirer, region and card mix. The transaction fee is set 40% below what a card processor would charge on the same settlement, and the gap widens as settled volume rises. Every tier above sits under the card range.
What you are paying for. Not the rail, which costs cents, but the whitelabelled vertical product on top: the escrow, the delivery triggers and the structure you would otherwise build yourself.
Indicative. Priced per corridor and settled volume, and confirmed in writing before onboarding.
Team
Who you would be
working with.
What each of them has shipped.
Samuel Dreier
Serial entrepreneur: three ventures across fintech, commodities and logistics, the first at 18. Cross-jurisdiction operations and deal-closing.
Jake Crocker
Built the settlement rail, escrow system, Experience Wallet and live PMS integrations. Shipped and in production.
Adam Bates
Ran global marketing for Cardano (IOHK), one of the largest blockchain networks by market cap. Ex-BBDO partner: Virgin, Emirates, London 2012.
Andrew Deighan
Co-founder and product lead. Fintech founder and marketplace operator, which is where the trigger and dispute requirements came from.
Edison Dalani
Ex-Expedia finance leader: treasury, controls and the numbers behind a regulated payments business.
Mark Mosley
Scales onboarding, operations and the integration pipeline that brings each new client live.
Onboarding is run by the same people who built the rail, not handed to a separate implementation team.