How Payment Processors Can Run Their Own Stablecoin Settlement Rails
At $1M a month, a 1.5% stablecoin processing fee is a line item. At $100M a month, it is $1.5M. The on-chain transfer underneath that fee costs a fraction of a cent on most chains; the rest pays for everything around it. Payment processors can reduce the variable cost of stablecoin settlement by owning more of that underlying infrastructure: custody, deposit and sweep logic, and liquidity. The question is when the fixed cost of owning it becomes lower than the variable cost of outsourcing it.
Key takeaways
- Per-transaction fees grow with volume. Self-hosted rails are mostly fixed cost plus a thin layer of gas and conversion spread.
- Against 1.5% checkout pricing, the Fee Crossover Point in our model sits around $3M to $4.3M in monthly GMV.
- Against negotiated orchestration pricing, the fee case is thinner, and control becomes the stronger argument.
- Running your own rails does not remove float. It moves float onto your balance sheet.
What Per-Transaction Stablecoin Fees Actually Pay For
A stablecoin processing fee is not a charge for moving tokens. It is a charge for everything around the transfer.
Stripe charges 1.5% of the transaction amount for stablecoin payments, against 2.9% + $0.30 for a US domestic card (Stripe pricing). The merchant never handles a wallet or converts crypto. Completed payments land in the Stripe balance in local currency (Stripe docs).
The transfer underneath is cheap. BVNK's published network fee data puts the average transfer on Solana, Base or Polygon below one euro cent in recent weeks, with Ethereum near €0.18 (BVNK network fees).
So the 1.5% pays for abstraction. That abstraction is worth it at low volume. At high volume, that percentage becomes a meaningful operating cost.
Not all of that bundle is something a payment processor needs to buy. A PSP already runs acceptance, merchant onboarding and reconciliation. What it rents is the settlement layer underneath: custody, conversion and payout. That layer is the part this article prices.
Infrastructure providers price differently. Orchestration APIs usually quote in basis points per customer, often with a monthly minimum. BVNK, for example, lists pricing from $5,000 a month that scales with flow (BVNK).
How Can I Replace My Processor's Per-Transaction Stablecoin Fees?
You replace the settlement part of a per-transaction fee by owning the infrastructure underneath it: custody, deposit detection, sweeping, compliance checks and liquidity. Each part becomes a cost you run instead of a percentage you rent.
The cost does not go to zero. It changes shape:
- Custody and signing: a self-hosted custody platform in your own cloud or data center.
- Nodes and monitoring: RPC access, deposit listeners and alerting.
- Compliance: KYT and sanctions screening before funds move.
- People: engineers and treasury operators who own the rail day to day.
- Gas: still paid per transaction, but in cents, not percent.
- Liquidity: OTC or exchange spread when converting to fiat, plus banking partners for payouts.
The last line is the one teams underestimate. In our off-ramp rail walkthrough, the fiat payout runs on the platform's own inventory, which has to be funded and rebalanced. For the full cash-out pipeline, see How Crypto Off-Ramps Work.
The Fee Crossover Point: Cost Model at $10M to $100M GMV
The Fee Crossover Point is the monthly GMV at which a fixed self-hosted cost falls below the fees you would otherwise pay. Below it, renting is cheaper. Above it, every extra dollar of volume widens the gap.
Our model uses illustrative monthly assumptions. Self-hosted fixed cost is $40K to $60K, covering infrastructure, two to three engineers and operators, compliance tooling and a custody license. Variable cost is 0.10% for gas and conversion spread. Checkout pricing is Stripe's published 1.5%. Orchestration pricing is an assumed negotiated range of 0.25% to 0.50%, not a published price.
| Monthly GMV | Checkout pricing (1.5%) | Orchestration (0.25% to 0.50%, assumed) | Self-hosted rails (illustrative) | Self-hosted saving vs checkout |
| $10M | $150K | $25K to $50K | $50K to $70K | 53% to 67% |
| $50M | $750K | $125K to $250K | $90K to $110K | 85% to 88% |
| $100M | $1.5M | $250K to $500K | $140K to $160K | 89% to 91% |
Two readings stand out. Against checkout pricing, the crossover arrives early, at about $3M to $4.3M a month, and savings pass 85% from $50M. In our illustrative model, that is the scenario where an 80%+ reduction holds, and it assumes the processor already owns acceptance and reconciliation.
Against orchestration pricing, the crossover sits between $10M and $40M a month. At $100M, the saving is closer to 36% to 72%. That still matters, but the stronger case there is control over keys, policy and settlement timing.
Settlement Speed and Float: T+0 On-Chain Is Not Free Liquidity
On-chain, a stablecoin transfer settles in seconds, any day of the week. Fiat does not.
Processors pay out on banking schedules. Stripe's default settlement timing is two business days in the US and three in most of Europe, while the UAE starts at five business days and Singapore at seven calendar days (Stripe payouts). Weekends and holidays do not count as business days.
When you rent rails, the processor holds that float and you wait. When you run your own, stablecoins reach your treasury at T+0. But most merchants still want fiat, often the same day, and someone has to pre-fund that payout.
That someone is now you. A PSP paying out $3M a day on a two-day rebalancing cycle needs roughly $6M of fiat inventory, plus a weekend buffer. Running your own rails does not remove float. It moves float onto your balance sheet.
The trade-off is different: you decide when to convert, which venue to use and how much buffer to hold. You also stop depending on one provider's uptime and risk reviews to reach your own settlement funds. Add the cost of capital on that inventory to your Fee Crossover Point.
How Payment Processors Can Run Their Own Stablecoin Rails: A 4-Step Plan
Payment processors run their own stablecoin rails by moving one layer at a time from rented to owned, starting with custody and ending with liquidity. A hybrid phase is normal.
- Keep the fiat leg, own the stablecoin balance. Keep your current provider for conversion and payouts, but receive stablecoins into wallets you control. You cut custody and movement fees first and learn your real flow patterns.
- Deploy self-hosted custody with deposit and sweep automation. Give each merchant or order its own deposit address, confirm deposits through webhooks and sweep balances into a central treasury on a schedule. Our guide to non-custodial solutions compares the main platforms. For multi-chain address strategy across EVM, Solana and Tron, see [Dev #3 link, add when published].
- Put policy in front of every withdrawal. Set approval rules by amount, whitelisted destination and network, and screen counterparties before funds move (policy rules example). This lets volume grow without manual approvals growing with it.
- Bring liquidity in-house. Add OTC and exchange relationships, set rebalancing thresholds and size your fiat inventory. Only at this step do you replace the provider's conversion spread with your own.
When Not to Build Your Own Rails
Self-hosted rails are not the right answer for every processor. Stay with a provider if your stablecoin volume sits below the crossover, if you lack licenses in your payout markets, or if no one will own treasury operations day to day.
Licensing alone can decide it. Each new payout market can introduce local licensing, entity and liquidity requirements, as we covered in Emerging Market Crypto Ramps.
Who Owns the Rails Next
Stablecoin settlement is becoming infrastructure that the largest networks want to own. Mastercard completed its acquisition of BVNK in August 2026, bringing stablecoin settlement capability in-house. Processors that only resell these rails will compete on whatever margin the owners leave them.
The processors with the most room to move will know their own Fee Crossover Point, and will own their keys, policy and treasury by the time volume crosses it.
If you are mapping your own crossover, Fystack builds self-hosted custody infrastructure with deposit sweeps and a policy engine that enforces approval rules before signing: talk to the team.
About Fystack: Fystack is a self-hosted custody platform for fintech teams. Its core signing infrastructure, mpcium, is open-source on GitHub. Fystack supports TRON, Ethereum, BNB Chain, Solana, Polygon and more.
FAQ
How can I replace my processor's per-transaction stablecoin fees?
Run your own custody, deposit, sweep and compliance stack, and pay fixed infrastructure costs instead of a percentage. Most processors keep a provider for fiat conversion at first.
How can payment processors run their own stablecoin rails?
Move one layer at a time: own the stablecoin balance, deploy self-hosted custody with sweep automation, add policy controls, then bring liquidity in-house.
How much does it cost to run self-hosted stablecoin rails?
In our illustrative model, about $40K to $60K a month in fixed costs plus around 0.10% in gas and conversion spread. Team size, chains and payout markets move that number.
At what volume do self-hosted stablecoin rails pay off?
Against 1.5% checkout pricing, at about $3M to $4.3M in monthly GMV in our model. Against negotiated orchestration pricing, between $10M and $40M.
