Stablecoin billing, built for developers.
Custody creates regulatory, operational, and reputational cost — for the platform and for the businesses on it. Direct-to-wallet stablecoin settlement gives developers a billing rail that doesn't depend on an issuer's appetite for their business model, and gives their customers a payment that lands in seconds, not days. OpenSettle is that rail, with the typed SDKs, idempotent webhooks, and on-chain audit trail an engineering team will actually ship against.
Why we built it this way.
Custody is a regulatory, operational, and reputational cost. We opted out, by architecture.
Typed SDKs, idempotent webhooks, a deterministic test mode. If it takes an afternoon to integrate, we did it right.
A single fee on volume, paid in the same transaction. No reserves, no minimums, no rent-seeking.
Code is internally reviewed and externally auditable, signed everything, SOC 2 considered once a post-launch commercial milestone justifies the engagement. Novelty belongs in the product, not in compliance.
Hosted checkout is live on four EVM networks — Base, Ethereum, Polygon, and Arbitrum — with Solana and Tron API-ready for detection and hosted checkout for both shipping next. Base is USDC-only, Tron is USDT-only. The full matrix is on one canonical page so it never drifts.
Self-custody is a real constraint, not a reason to fall back on cards. One-click email-renewal links work on every wallet today; allowance-based autopay is live on Base, Polygon, and Arbitrum.
Who's behind this.
Solo founder. Built OpenSettle from the ground up — non-custodial by architecture, not as a marketing claim. Anonymous by design: happy to do real diligence conversations under NDA, but the public record is the code, the audit pack, and the merchants we settle for.
Full KYB available to enterprise prospects on request — founder identity and verification documents are shared directly under NDA. The public record is the code, the chain, and the merchants we settle for.
Trust is built on what you can verify.
Money infrastructure is not a place for marketing claims. Everything we say about OpenSettle should be something a merchant, auditor, or regulator can check for themselves — in the code, in the chain, or in a published report.
- Non-custodial by architecture. Funds settle wallet-to-wallet on-chain. OpenSettle never holds a balance, so there is nothing for us to lose, freeze, or rehypothecate.
- Open SDKs, public history. Node, Python, Go, and Rust clients are published to their respective registries with reproducible builds and a public commit history. Pin any version, audit any line.
- Security work is published. Threat models follow OWASP guidance, findings and fixes are tracked in versioned audit reports, and a coordinated vulnerability disclosure programme is open to outside researchers. A SOC 2 engagement is considered post-launch, gated by a commercial milestone; no date is committed until the engagement letter is signed and published. Current certification status and roadmap dates live in the trust center.
- One canonical chain matrix. Mainnet hosted checkout is live on Base, Ethereum, Polygon, and Arbitrum (Base is USDC-only); detection also covers Solana and Tron (Tron is USDT-only), with hosted checkout for both shipping next. The authoritative per-chain breakdown lives in the supported chains reference so it never drifts between pages.
- Pricing in the docs, not in a sales call. A cascading rate on volume, accrued at confirmation and billed monthly. No reserves, no minimums, no “contact us” tier.
Press, partnership, or due-diligence questions? Get in touch.