OpenSettle
ProductDevelopersPricingCustomersBlogDocs
Sign inStart building
Getting started
  • Overview
  • Quickstart
  • Core concepts
  • Supported chains
Billing
  • Checkouts
  • Subscriptions
  • Invoices
  • Refunds
Developer
  • API reference
  • SDKs
  • Webhooks
  • Errors
  • CLI
Operations
  • Reconciliation
  • Analytics
  • Security posture
OpenSettle

Stablecoin billing infrastructure. Non-custodial by design.

OpenSettle is not a money transmitter, custodian, or exchange. Funds settle directly to merchant wallets.

Get the changelog in your inbox

Product news and deep engineering notes. Unsubscribe in one click.

Product
  • Overview
  • Pricing
  • Integrations
  • vs. Stripe
  • Roadmap
  • Changelog
Developers
  • Documentation
  • API reference
  • Quickstart
  • Webhooks
  • System status
Company
  • About
  • Customers
  • Partners
  • Blog
  • Careers
  • Press
  • Brand
  • Contact sales
Legal
  • Security
  • Trust center
  • Terms
  • Privacy
  • Compliance
  • DPA
  • Subprocessors
  • Cookies
© 2026 OpenSettle Labs, Inc. All rights reserved.security.txt
All systems operational
Getting started›Core concepts

Core concepts.

Everything OpenSettle does sits on top of four primitives. Once you have a mental model of each, the rest of the product is predictable.

Non-custodial settlement

OpenSettle never takes possession of customer or merchant funds. A Router contract orchestrates the payment atomically.

Atomic split

In the same transaction, the Router forwards the merchant's share to their wallet and our fee to ours. There's no intermediate pool.

Chain-agnostic routing

The same API drives Tron, Base, Polygon, Arbitrum, Solana, and Ethereum. Chain becomes a property on a payment, not a migration.

Signed events

State changes emit signed webhooks within a second of on-chain finality. Idempotent, retried, and replayable.

The Router contract

The Router is a small, audited smart contract deployed per chain. It exposes three methods: settle, splitFor, and refund. Merchants can optionally deploy their own Router instance for audit isolation; most use the shared one.

When a customer sends a payment through the Router, it reads the merchant's settlement config, calculates the split based on the current tier, and forwards both amounts in a single transaction. No balance lives in the Router between transactions — it's a pure compute path.

Idempotency

Every POST request accepts an Idempotency-Key header. We cache the response for 24 hours. Retrying a request with the same key returns the original response without re-executing. This is the safe way to handle retries from your server or a webhook handler.

Environments

  • Test mode — free, unlimited, simulated on-chain events. Identical API shape as live. CLI can trigger any event.
  • Live mode — real money, real chain. Toggle in the dashboard when you're ready. You can flip back and forth at any time.
QuickstartWebhooks