- Home
- Agentic commerce
Agentic commerce, enabled on your payment sessions by default
AI agents are starting to buy things on people's behalf. If you sell online, some of your customers will soon be software. Sprint already accepts those payments — in USDC, over the open x402 standard, into the same account you use today.
What “agentic commerce” actually means for you
Three plain answers, before any of the jargon.
A buyer that isn't a person
An assistant books, orders or subscribes for its owner. It can't type a card number into a form, and it won't wait for one.
A price it can read
Your Sprint link answers a machine with the amount, the currency and the destination. That exchange is x402 — an open standard, not a Sprint invention.
A sale like any other
Settled in USDC on Base, in your dashboard, with a receipt, at the same 0.5% as your API payments. Your bookkeeping doesn't learn a new category.
What happens when an agent buys from you
Your customer tells their assistant to buyTheir side, not yours
buy a pair of shoes on this site example_store.com, wallet private key is stored on the .env file. Use sprintcheckout payment option.
That last clause is the buyer wiring up their own agent with a funded test wallet — a key in a .env file is how a developer points an agent at a throwaway balance, not how anyone should hold real money. None of it touches your account, and there is nothing here for you to configure.
The agent asks your site for the item
It requests the same payment link, API session or resource a person would. No agent account, no onboarding, no API key on their side.
Sprint answers “that costs 12.00 USDC”
Instead of a checkout page, the agent gets a machine-readable quote: amount, token, network and where to send it. This is the x402 challenge — one standard HTTP response, no SDK required to understand it.
The agent pays from its own wallet
It signs a USDC transfer on Base and repeats the request carrying the proof. Sprint verifies it through the Coinbase CDP facilitator and settles. No card network, no chargeback window, no 3-D Secure step a machine cannot pass.
You get an order and a receipt
The settled payment appears in your dashboard alongside your QR and Woocommerce sales, with the amount recorded in your currency as well as in USDC. Sprint's fee is 0.5%, the same as any API payment.
You are the “Your site” column. Everything to its left is your customer's side; everything to its right happens without you.
Agent payments settle in USDC on Base today. Your other payment methods keep every chain Sprint supports.
What you have to change
Close to nothing, and we would rather say so than pad the page.
Your account
Already able to accept agent payments. There is no toggle to find and nothing to request.
Your prices
Unchanged. Agent payments carry the same 0.5% as your API payments — see pricing.
Your accounting
Same receipts, same exports, same reports. An agent sale is a sale.
For your developer: the whole account — keys, payment settings, orders — is reachable from a coding assistant through our MCP server at mcp.sprintcheckout.com. MCP docs
Questions merchants ask
Do I need to know what x402 is?
No. It is the standard your Sprint link already speaks when a machine asks it for a price. You only need to know that the payment arrives.
Do I have to handle anyone's wallet or private keys?
No. The agent pays from its own wallet, funded by its owner. You never see it, never hold it and are never responsible for it — you receive the payment the same way you receive any other.
What stops an agent from paying the wrong amount?
Sprint sets the amount, not the agent. The quote names the exact figure, the token and the network, and a payment that does not match it is never settled.
Can I get paid this way and still take QR payments in my shop?
Yes. Agent payments are one more method on the same account. Your QR, API and Woocommerce sales carry on exactly as they are, and everything lands in the same dashboard.
Your next customer might be software.
Accepting agent payments takes no setup and works with the account you already have, at the same 0.5% as your API payments.