Mints Banking · Checkout
Sell to agents the way you sell to humans.
Sell to agents the way you sell to humans — except checkout takes milliseconds, customers verify cryptographically, and every sale carries a receipt both sides can prove.
Customer
atlas-research
did:oas:l1fe:agent:7f3a…c9e2
Order
Checkout is not a page. For agents, it's a round trip — price, sign, settle.
Merchant flow
Quote, authorize, capture.
The complete checkout lifecycle from session creation to reconciled receipt — no human-shaped checkout page required.
Create session
Merchant creates a checkout session with amount, currency, and description. Returns a session token.
Agent quotes
Agent receives price in the session or via HTTP 402. Verifies the merchant's identity against their lineage.
Authorize
Agent signs an authorization locally with its private key. Signature proves identity and intent — no password, no redirect.
Capture
Mints verifies the signature, confirms lineage, and settles funds. Merchant receives a structured receipt.
Reconcile
Both sides hold a signed, replayable event. Merchant's ledger updates atomically. No manual reconciliation.
Create session
Merchant creates a checkout session with amount, currency, and description. Returns a session token.
Agent quotes
Agent receives price in the session or via HTTP 402. Verifies the merchant's identity against their lineage.
Authorize
Agent signs an authorization locally with its private key. Signature proves identity and intent — no password, no redirect.
Capture
Mints verifies the signature, confirms lineage, and settles funds. Merchant receives a structured receipt.
Reconcile
Both sides hold a signed, replayable event. Merchant's ledger updates atomically. No manual reconciliation.
POST /v1/checkout/sessions
{ "amount": "149.00", "currency": "USDC",
"description": "API access — June + Inference Pro",
"merchant": "did:oas:l1fe:mhr:a3f1…" }# Agent receives HTTP 402 with session token
# Signs locally and retries — no redirect
$ mints pay --session cs_01JXF8… 149.00
✓ payment settled in 138ms tx_01JXF8…4a9cCustomer verification
Every buyer is cryptographically proven.
An agent customer is not an account number or an email address. It is a DID with a verifiable lineage rooted at a human. You know exactly who is buying — and their organization cannot dispute the charge.
Identity without a username
Agent customers authenticate with their OAS DID and an Ed25519 signature — not a password, not an OAuth token. You verify the signature server-side. No shared secret, no session to steal.
Lineage as credit history
Every buyer's DID traces back through their organization to a human root. You can verify the lineage at checkout time — and optionally gate access by lineage depth, organization, or spending history.
Non-repudiable purchase
The agent's private key signs the authorization. The signature is recorded in the immutable event log. Neither the merchant nor the buyer can later dispute what was agreed — the proof is in the ledger.
Buyer lineage
The purchasing agent is a leaf in a lineage you can verify before settlement.
Cross-lineage requests are rejected at the protocol layer — no configuration required.
Capabilities
What Mints Checkout does.
A checkout that completes in the same HTTP round trip as a payment. No redirect. No session. No waiting.
Agent-verified customers
Every buyer presents a DID with a human-rooted lineage. You get identity proof, not just a payment token.
Programmatic checkout
Create sessions via API. Agents quote, authorize, and capture without leaving the HTTP request cycle.
Provable receipts
Structured, Ed25519-signed receipts for every sale. Both merchant and buyer hold independent proof.
x402 compatible
Serve a checkout session as an HTTP 402. Any x402-capable agent pays in a single retry — zero integration overhead.
Lineage-gated access
Optionally restrict purchases to specific lineage depths, organizations, or verified history. Your rules, enforced at the protocol layer.
Session
cs_01JXF8…
Receipt
tx_01JXF8…4a9c
Merchant
did:oas:…:mhr:a3f1…
Customer
did:oas:…:agent:7f3a…
Amount
149.00 USDC
Settled
2026-06-13T14:22:07Z
Signature
sig_ed25519_3c9f2a01d84b…f19e7c (agent key) · verified by Mints
Why not traditional checkout?
Agents are not humans in a browser.
Conventional checkout flows — redirects, sessions, OAuth, email confirmation — were designed for humans navigating UI. Agents operate at machine speed and need cryptographic proof, not a login form.
Mints Checkout
Programmatic, cryptographic, milliseconds
Traditional checkout
Manual, credential-based, seconds to minutes
Related primitives
Checkout connects everything.
Payments
Checkout is built on the same x402 payment primitive. Any payment-capable agent is already checkout-capable.
Escrow
Gate checkout completion behind a milestone or condition. Release funds only when delivery is verified.
Mints Identity
Buyer verification is powered by OAS DID identity. Mints Identity manages key ceremonies and lineage proofs at scale.
Start accepting agent payments.
Mints is in early access. Tell us what you're selling — we'll help you wire up your first checkout session.