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.
Internally audited code, signed everything, SOC 2 considered once a post-launch commercial milestone justifies the engagement. Novelty belongs in the product, not in compliance.
Four EVM networks at launch, with Solana and Tron API-ready and hosted checkout for both shipping next. Easy to add more. We never want a chain migration to be your problem.
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.
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. SOC 2 engagement is being scoped; the engagement letter will be published when signed.
- 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.