Non-custodial · recurring + one-time · multi-chain
Recurring stablecoin billing without custody.
Customers approve a USDC or USDT subscription once; every renewal settles straight from their wallet to yours. One-time charges settle the same way. OpenSettle never holds the money. Typed SDKs for Node, Python, Go, and Rust.
Sanctions screening · Audit-pack export
Interactive preview · no real payment.
From the buyer’s wallet to yours — nothing in between.
pays from any wallet
final — no chargebacks
settles to you, never escrowed
Trigger it however you sell — a hosted checkout, a shareable payment link, an emailed invoice, or one API call. One-time or recurring, the path above never changes.
The billing stack you'd otherwise build yourself. Shipped — and we mark what's still on the roadmap.
Direct-to-wallet settlement, signed webhooks, and audit-ready reconciliation across four EVM chains — without the custody, reserves, or money-transmitter licensing of a PSP.
Checkout — one-time or recurring
Charge once or bill on a schedule — hosted checkout or a shareable link, same direct settlement. Funds land 100% in your wallet, not ours; confirmed on-chain, never escrowed. Our fee accrues separately and is billed once a month.
Non-custodial by design
We never hold your funds — or your customers'. No reserves, no payout delays, no custody risk, and a much smaller regulatory surface.
Reconciliation that actually balances
Every payment with tx hash, block height, chain fee, platform fee, and customer reference — exportable in your GL's exact schema.
Webhooks that don't lie
Signed, idempotent, with exponential retries and a full delivery log. If your API takes a breath, ours waits.
One API across four EVM chains
USDC on Base, Ethereum, Polygon, and Arbitrum. Solana (USDC/USDT) and Tron (USDT) are API-ready (wallet verification + ingest); hosted checkout for both ships next.
A boring, well-shaped REST API — with the on-chain parts handled.
Conventional resource model, idempotency keys on every mutation, HMAC-signed webhooks with replay protection, typed SDKs in four languages. Plus the on-chain pieces a regulated merchant needs: chains, tokens, wallet authorization, sanctions screening, and a regulator-readable audit pack.
- Typed SDKs in Node, Python, Go, and Rust
- Signed webhooks with idempotency keys
- Isolated test mode — same endpoints, sk_test_ keys
- OpenAPI 3.0 spec and hosted dashboard
import { OpenSettle } from "@opensettle/sdk";
const os = new OpenSettle({
apiKey: process.env.OPENSETTLE_KEY!,
workspaceId: process.env.OPENSETTLE_WORKSPACE!,
});
// Hosted subscription checkout — buyer pays in USDC on Base
const checkout = await os.checkouts.create({
mode: "subscription",
customerEmail: "buyer@example.com",
priceId: "price_01jt…",
chain: "base",
token: "USDC",
successUrl: "https://your-domain.com/billing?ok=1",
cancelUrl: "https://your-domain.com/billing?ok=0",
metadata: { userId: "usr_123", planId: "pro" },
});
// Redirect the buyer — webhook (subscription.created) is the source of truth
return Response.redirect(`https://opensettle.io${checkout.hostedUrl}`, 303);The card-on-file problem, solved three ways.
Crypto wallets don't auto-charge like cards. So we built the whole spectrum — meet every customer where their wallet is, and stop losing renewals.
Invoice & pay
Each renewal issues an invoice and emails the customer a one-click pay link. One click, one signature, renewed. Works with any wallet the buyer already holds, on every chain we support.
ERC-20 allowance
Customer approves a spending cap once, straight from their own wallet. Each renewal pulls on-chain automatically — no prepaid balance to top up, no invoice to re-pay, revocable any time. The card-on-file of crypto, fully self-custodied.
Smart-wallet autopay
Session keys with time and spend caps. Completely hands-off for the customer, ERC-4337 native. Next up after the live allowance autopay.
Once they're subscribed, entitlements gate access with one check — an active subscription (or a manual grant) maps straight to what a customer can use.
How we settle vs. how everyone else holds your money.
Stripe now ships stablecoin payments and recurring billing too — but balances run through a processor and settle custodially. OpenSettle is the direct-to-wallet alternative: neither we nor a PSP ever hold your funds. Side-by-side, tradeoffs included.
| Capability | OpenSettle | Stripe | Coinbase Commerce | Wise Business |
|---|---|---|---|---|
| Non-custodial settlement | Yes | No | No | No |
| Direct-to-wallet payouts | Yes | No | No | No |
| Multi-chain on one API | Yes | No | Yes | No |
| Recurring stablecoin billing | Direct-to-wallet auto-pull* | Yes, via custodial balance | No | No |
| Stablecoin acceptance availability | Any self-custody wallet | Select merchant regions | Select regions (custodial) | n/a |
| Chargebacks | None | Yes | None | None |
| Settlement time | ~Seconds to minutes (on-chain) | 2–7 days | ~Seconds to minutes (on-chain) | 1–2 business days |
| Reserves or holdbacks | No | Yes | No | No |
| KYC on end customers | No | Limited | No | Yes |
| Regulatory footprint | Non-custodial software† | Money transmitter | MSB | EMI / MSB |
| Fees | 1% → 0.65% | 2.9% + 30¢ | 1% flat | 0.5–1% + FX |
| Card acceptance | No | Yes | No | Yes |
| Tax automation | No | Yes | No | No |
| SOC 2 attestation | Exploratory · gated by milestone | Published | Published | Published |
| Typed SDK languages | Node · Python · Go · Rust | 7 languages | 3 languages | 3 languages |
- Non-custodial settlement
- Yes
- Direct-to-wallet payouts
- Yes
- Multi-chain on one API
- Yes
- Recurring stablecoin billing
- Direct-to-wallet auto-pull*
- Stablecoin acceptance availability
- Any self-custody wallet
- Chargebacks
- None
- Settlement time
- ~Seconds to minutes (on-chain)
- Reserves or holdbacks
- No
- KYC on end customers
- No
- Regulatory footprint
- Non-custodial software†
- Fees
- 1% → 0.65%
- Card acceptance
- No
- Tax automation
- No
- SOC 2 attestation
- Exploratory · gated by milestone
- Typed SDK languages
- Node · Python · Go · Rust
- Non-custodial settlement
- No
- Direct-to-wallet payouts
- No
- Multi-chain on one API
- No
- Recurring stablecoin billing
- Yes, via custodial balance
- Stablecoin acceptance availability
- Select merchant regions
- Chargebacks
- Yes
- Settlement time
- 2–7 days
- Reserves or holdbacks
- Yes
- KYC on end customers
- Limited
- Regulatory footprint
- Money transmitter
- Fees
- 2.9% + 30¢
- Card acceptance
- Yes
- Tax automation
- Yes
- SOC 2 attestation
- Published
- Typed SDK languages
- 7 languages
- Non-custodial settlement
- No
- Direct-to-wallet payouts
- No
- Multi-chain on one API
- Yes
- Recurring stablecoin billing
- No
- Stablecoin acceptance availability
- Select regions (custodial)
- Chargebacks
- None
- Settlement time
- ~Seconds to minutes (on-chain)
- Reserves or holdbacks
- No
- KYC on end customers
- No
- Regulatory footprint
- MSB
- Fees
- 1% flat
- Card acceptance
- No
- Tax automation
- No
- SOC 2 attestation
- Published
- Typed SDK languages
- 3 languages
- Non-custodial settlement
- No
- Direct-to-wallet payouts
- No
- Multi-chain on one API
- No
- Recurring stablecoin billing
- No
- Stablecoin acceptance availability
- n/a
- Chargebacks
- None
- Settlement time
- 1–2 business days
- Reserves or holdbacks
- No
- KYC on end customers
- Yes
- Regulatory footprint
- EMI / MSB
- Fees
- 0.5–1% + FX
- Card acceptance
- Yes
- Tax automation
- No
- SOC 2 attestation
- Published
- Typed SDK languages
- 3 languages
Competitor fees, capabilities, and attestation status as of June 2026, compiled from each provider’s public pricing and documentation. Third-party terms change — check each provider’s own site for current details. Only the OpenSettle column reflects our own product. Recurring auto-pull is live on Base, Polygon, and Arbitrum; on every other chain renewals bill with a one-click invoice, so subscriptions work wallet-agnostically everywhere. Stripe does support stablecoin payments and recurring billing (via its Bridge acquisition), but those balances are held and settled by Stripe rather than sent direct to your wallet, and the stablecoin program rolls out to select merchant regions; check Stripe’s docs for current availability where you operate. † “Non-custodial software” describes how OpenSettle is built, not a completed regulatory determination: funds settle wallet-to-wallet and never pass through us, which is the basis for our position that we sit outside money-transmission and custody scope. Outside-counsel review of that position is in progress, and each merchant remains responsible for its own licensing where it operates.
Should you use OpenSettle?
We'd rather you know up front. OpenSettle is sharp for some businesses and the wrong tool for others — here's where it fits and where it doesn't.
Best for
- Crypto-native SaaS billing in USDC or USDT
- AI and API tools metering usage or selling credits
- Global and offshore B2B services that banks underserve
- Marketplaces paying out directly to seller wallets
- Protocol and on-chain tooling that already lives in wallets
Not for
- Paying out in fiat or moving money to bank accounts
- Accepting cards — there's no card rail here
- Broad altcoin checkout; we settle USDC and USDT only
- Teams that need a signed SOC 2 report to buy today
On the fence? If your customers already hold a stablecoin wallet, you're in the right place. If they expect to tap a card, you're not.
Volume pricing. No reserves. No payout delay.
You pay a percentage of monthly settled volume — accrued per payment, billed monthly, never deducted from what lands in your wallet. The rate drops as you grow. No setup fee, no minimum, no reserves, no "contact us" tier.
- Every chain we support
- Hosted checkout + SDKs
- Sanctions screening
- Audit-pack export
We're the infrastructure layer — not the bank.
OpenSettle is deliberately structured as a software platform — not a payment processor. The difference shows up in every part of your experience, from day-one onboarding to the legal review your counsel will run.
We don't hold your money.
OpenSettle is built non-custodial by architecture — your customers pay directly to your wallet, and we never take possession of funds. That structure is designed to keep us out of custody and money-transmission scope; outside-counsel review of that position is in progress.
Cryptographic wallet ownership.
Every settlement wallet must sign a one-time EIP-191 / TIP-191 / Ed25519 ownership challenge before it can receive funds. In-house OFAC SDN screening runs on every inbound payment; travel-rule integration is on the roadmap.
Internal audit live, SOC 2 exploratory.
Latest internal platform audit (May 2026) available on request — email security@opensettle.io. SOC 2 Type I pursuit is gated by a post-launch commercial milestone; the engagement letter will be published when signed.
You stay the merchant of record.
Because the architecture is non-custodial, funds never pass through OpenSettle on their way from buyer to seller — the basis for our position that we sit outside money-transmission scope. Each merchant remains responsible for its own licensing and compliance in the jurisdictions where it operates.
The questions
every team asks.
And the ones your counsel will. Nothing buried, nothing hedged.