0.5% taken atomically →

Stablecoin checkout.
0.5% flat. Final on-chain in seconds.

USDC on Base, settled directly to your wallet. Every payment splits 99.5% to you and 0.5% to Settle in a single on-chain transaction. We don't shut you down for what you sell.

Fee
0.5%
flat, taken on-chain
Settlement
2s
on Base
Chargebacks
0
payments are final
Onboarding
OAuth
GitHub, ship today

Built for AI agents

One paste. Settle is wired into your project.

No SDK to install. No REST API to learn. Settle is MCP-only — point any AI coding agent at mcp.settle.xxx and it speaks JSON-RPC natively. Drop the prompt below into Cursor, Claude Code, v0, or Aider; the agent calls create_invoice, register_webhook, and the rest directly.

Set up Settle in this project. MCP: https://mcp.settle.xxx, my key: <PASTE>. Mint a $1 test invoice and show me the checkout link.

Replace <PASTE> with a test key from /dashboard/keys after signup. More prompts (build a checkout side-card, wire webhooks, …) at /docs/prompts. Agent-readable spec at /llms.txt.

What it is

A stablecoin payment rail. Nothing more.

Settle is not a wallet, not a custodian, not a fiat gateway. The user pays in USDC on Base; the router contract settles to your cold wallet on-chain in seconds.

Atomic on-chain settlement.

The router splits payment 99.5% to your cold wallet, 0.5% to Settle, in the same transaction. Non-custodial. Settle never holds your funds.

0.5% flat. Same token in, same out.

USDC stays USDC. No FX spread, no conversion. The fee is taken on-chain — there is no invoice from us at the end of the month.

Live on Base.

USDC on Base (~2s). The router contract is deployed and live; the same primitives extend to additional chains as we ship them.

Final by design.

Crypto payments don't reverse. No chargeback fees, no retrieval requests, no 540-day liability window. Disclosed loudly to the user before they sign.

Open-source contracts.

Router source is public and static-analysis-clean (Slither, Mythril, Aderyn — zero findings). 2-of-3 multisig + 48-hour public timelock on every admin action. Treasury keys never touch a hot machine.

Agent-first integration.

Point your AI at mcp.settle.xxx. Authorize once, then ask it to add checkout. Five minutes for Next.js, Hono, FastAPI, or Express.

Integration

Three steps. Five minutes.

  1. 01

    Sign in. Register a payout address.

    GitHub OAuth. One payout address per chain — Ledger, Trezor, Safe, Squads, whatever you already use. Sign once to prove control. OFAC-screened on submit.

  2. 02

    Your AI ships checkout.

    Authorize Claude, Cursor, or any MCP-capable agent. It calls create_invoice, gets a hosted checkout URL, and drops it into your app. No SDK to install.

  3. 03

    User pays. You settle.

    User signs a single off-chain authorization. Funds land in your cold wallet on the next block. Webhook fires the moment confirmation lands.

Questions

Honest answers.

How does Settle decide who can use it?

Settle doesn't underwrite based on industry. The only gate is OFAC screening on the payout address at signup and on the payer wallet at checkout. Same code path for everyone.

Is Settle custodial?

No. Funds settle directly to a payout address you control. The router splits 99.5% to you, 0.5% to Settle, in the same on-chain transaction. We never hold merchant funds.

What's the actual cost vs a high-risk processor?

0.5% flat. High-risk processors typically charge 3–5% for cannabis, 5–10% for adult, 4–8% for firearms — plus rolling reserves of 5–20% held for 6 months, plus chargeback fees of $15–50 per dispute. Settle has none of that.

Do users need crypto?

Yes. Settle is a stablecoin rail — it's a real trade-off. Most of our merchants' users already hold USDC on Coinbase, Binance, or MetaMask. If your buyers don't, Stripe is probably the better fit.

What about chargebacks?

There aren't any. Stablecoin payments are final once confirmed. Disclosed loudly on every checkout before the user signs.

Refunds?

None, ever. By the time we know about a payment, funds are already in your cold wallet. There is no clawback path. We tell the user before they pay.

What chains are supported?

USDC on Base.

Is there a transaction cap?

$500,000 USD-equivalent per transaction.

How do I integrate?

Settle is MCP-only — there is no REST API, no SDK to install, and no api.settle.xxx subdomain. Point your AI agent (Cursor, Claude Code, v0, Aider) at mcp.settle.xxx and it speaks the JSON-RPC tool surface natively. The agent-readable spec lives at settle.xxx/llms.txt; paste prompts at settle.xxx/docs/prompts. No human boilerplate to write.

Why MCP-only? No REST API?

Because integrations are written by AI agents now. JSON-RPC over HTTP with self-describing tool schemas (call tools/list — it returns the live shape) is the format agents handle without inventing. A REST API would just be one more thing for the agent to hallucinate the wrong shape of. Same protocol Anthropic, OpenAI, and Cursor agents already speak.