10.15
±0.00
Stablecoin payments for businesses and AI agents
Accept supported stablecoins, verify exact assets, and reconcile every payment—whether it starts in a checkout or a programmatic agent workflow.
Acme Supply
Order #1048
Amount due
$10.15
pay_•••f1b
USDC
Base network
Live payment state
01/03Transfer detected
10.15 USDC · Base
The payment rail / 01—04
Follow the same resource from merchant intent to independently verified payment and durable accounting.
$10.15
asset
USDC · Base
order
#1048
Current event
Processingcheckout_session.created
10.15 USD · USDC on Base
Network-aware by design
A symbol is not an asset. Paybytoken binds each supported token to its network identity, contract or mint, decimal rules, and confirmation policy.
Accept $10.15
currency "usd"
ui_mode "embedded"
supported_tokens
USDC / base
USDC / ethereum
USDT / ethereum
USDC / solana
The merchant defines eligibility once. No chain credentials enter the browser.
USDC
USDC / Base
Allowlisted contract
USDC / Ethereum
Allowlisted contract
USDT / Ethereum
Allowlisted contract
USDC / Solana
Allowlisted mint
Checkout surfaces / 03
Hosted by Paybytoken
$10.15
USDC · Base
Exact asset selected
Optional checkout accelerator
Paybytoken Pay lets eligible returning customers use a balance.
Reconciliation is the product
Transfers can arrive short, over, late, or more than once. Paybytoken records what actually happened and applies an explicit policy instead of flattening every case into success or failure.
10.15
±0.00
9.50
−0.65
11.00
+0.85
—
closed
Built for software and teams
The same payment contract can power a human checkout and a programmatic agent flow. Businesses retain policy control while agents receive bounded actions and verifiable outcomes.
One payment contract
Policy controlledThe merchant defines the amount, eligible assets, expiry, and business context before any actor can pay.
Short-lived scopes and idempotent operations give an agent a narrow action instead of an open-ended credential.
Machine-readable state and signed events let both merchant systems and agents confirm what actually happened.
Agent-authorized payment
250.00 USDC
agent budget
250.00 USDC
scope · procurement
merchant payment
Order #AX-204
USDC · Base
Human and agent flows share exact asset validation, payment state, and reconciliation.
Delegated agent authorization remains a controlled design-partner capability.
Server-side first
Secret credentials never enter the storefront
Short-lived client secrets scope browser access
Webhooks and retrieval—not redirects—confirm success
const session = await paybytoken.checkoutSessions.create({
currency: "usd",
line_items: order.items,
supported_tokens: [
{ currency: "USDC", chain: "base" }
],
ui_mode: "embedded",
allowed_origin: "https://shop.example.com"
});
return {
client_secret: session.client_secret,
url: session.url
};Operations after checkout
Operational guarantees
Idempotent creation
Safe retries never create an ambiguous order.
Authenticated retrieval
Current payment state remains available on demand.
Signed delivery
Webhook evidence is verifiable and replayable.
Ledger boundary
Merchant balances update from durable accounting entries.
The payment resolves here
Take the same object from creation to durable accounting and a signed merchant event. The browser never decides whether the payment succeeded.
Payment receipt
10.15 USDC