Notes from the layer.
Engineering, product, and compliance writing from the people building OpenSettle.
Your payment processor is holding your money right now. We built one that can't.
Card processors hold your revenue for days; some balances freeze for months. We built a wallet-to-wallet rail the processor never touches.
How protocols are billing in 2026 (and why it's not what you think)
The quiet shift: protocols bill in USDC, route to a multisig, and skip the token entirely. Why it's happening — and the patterns we keep seeing.
The one line of code that prevents fake payment notifications (and the seven that make it bulletproof)
An attacker who knows your webhook URL can fake payment.confirmed events. The defense is constant-time HMAC — and the four ways it goes wrong.
Accepting USDT on Polygon: the cheapest stablecoin rail for emerging-market SaaS
USDT on Polygon is the rail your emerging-market customers already use: gas typically sub-cent, settlement in seconds, zero card-network FX margin.
Stripe vs OpenSettle for stablecoin billing on a crypto SaaS
Stripe added USDC settlement. We never left. A side-by-side for engineers — what each does well, what each doesn't, and when to run both.
The claims we removed from our marketing (and why)
We overstated chain support and quoted an unmeasured settlement time. Here's the audit, the corrections, and the guard script that prevents a repeat.
What "confirmed" actually means for stablecoin payments: a chain finality field guide
Block confirmation, probabilistic finality, and re-org risk across the four EVM chains where OpenSettle settles. Pick the right wait for your risk.
Reorg-safe payment confirmation: the failure mode nobody puts in their docs
Your dashboard says confirmed, then the chain re-organizes and the deposit is gone. How OpenSettle detects it, flips the state machine, and tells you.
Why we bill off-chain instead of running an on-chain splitter
Platform-fee architecture is load-bearing. Why we bill off-chain instead of an on-chain splitter — and why the splitter stays on the roadmap as opt-in.
Verifying wallet signatures across EVM, Solana, and Tron
Three signature schemes, three wire formats, one product surface. How we cryptographically verify a merchant owns the wallet they claim.
Worker heartbeats and a production preflight that fails fast
When a worker silently stops ticking, payments stop confirming. How we use Postgres heartbeat rows and one preflight endpoint to catch it first.