How AI Agents Pay: Agentic Payments Explained | Elacity
AI agents now pay with tokenized cards, delegated account access or signing wallets. Here is how each works, who can stop it, and why the key behind the payment matters most.
How AI Agents Pay, Explained: Who Holds the Authority When Your Agent Spends
How AI agents pay on your behalf comes down to three credentials: a tokenized card, delegated access to a bank account, or a wallet that signs payments itself. Which one your agent uses decides who can stop it, and whether a single leak costs you one payment or everything the agent can reach.
This week made the question practical. Stripe launched Treasury for agents on October 21, Mastercard opened early access to Agent Pay for Machines a day earlier, and Visa, BILL and Billtrust went live with a pilot in which agents complete approved supplier invoices. Here is how AI agents pay, and where the authority actually sits.
The Three Ways AI Agents Pay Today
Every agentic payment system answers two questions: what credential does the agent present, and who enforces the limits?
- Card credentials. The agent presents a tokenized card instead of your real number, and the issuer or network enforces the controls. OnePay's Agentic Banking gives an agent its own spending pocket with limits the customer sets, built on Mastercard Agent Pay.
- Account access. The agent connects to an existing bank or treasury account and prepares actions a person approves. Stripe lets businesses choose which accounts an agent can see, whether it can act, and when money movement needs human approval.
- Wallet signatures. The agent holds a crypto wallet and signs each payment itself. Under x402, a payment standard built on the HTTP 402 status code, a service replies Payment Required, the agent signs a payment payload, and the service verifies it and settles on-chain.
Most real products mix these. The rail matters less than the answer to the second question.
How AI Agents Pay Depends on Where the Authority Lives
Mastercard put it plainly in its launch: payments aren't the hard part, authority is. Its agents sign vouchers within an approved budget, so a provider can trust the promise without trusting the agent.
With cards and accounts, authority sits with the bank, network or platform. That is reassuring while they act for you. It also means your limits are a setting in someone else's system. Visa's pilot is explicit that the agent is not making payment decisions; it only executes payments a buyer already approved.
With wallets, authority sits with whoever holds the signing key. A single x402 payment can be tightly scoped, and the facilitator that settles it verifies payloads and submits them on-chain. The key behind those signatures is another matter. If it sits in an agent's memory, a server or a config file, anything that reads it can sign, up to whatever the wallet holds.
The Elacity Approach: Authority You Hold, Keys the Agent Never Sees
Elacity is building the ownership layer for the digital economy, where your data, work and IP become Wealth Capsules that humans and AI agents pay to use. Payment rails move the money. Elacity's question is who holds the keys, and what the agent receives once it pays. Beneath it runs ElastOS, the open runtime Elacity builds as MIT-licensed infrastructure for the Elastos DAO.
1. Keys Are Used, Never Owned
A key can sign or pay for you while the secret exists in the clear only for a split second inside a sealed sandbox, welded to that one transaction, then wiped. No app, platform or agent ever holds it. That primitive exists today; the agent wallet product built around it is still in development.
2. A Ticket, Not a Guest List
ElastOS works on capabilities, not access control lists. Rather than keeping a list of every agent allowed in, you hand an agent a narrow, signed, expiring capability token for one job. Revoke it and the action stops mid-flight. Humans and AI agents pass through the same capability model, and nothing touches your files, network or money without a grant. Our capability-based security explainer covers the mechanism in depth.
3. What the Agent Buys Stays Sealed
Paying is half a purchase. On most rails, an agent that buys a dataset receives a copy, and the seller's terms end at delivery, a gap we covered in AI agents and stablecoin payment rails. With Elacity dDRM, Elacity's own rights protocol, that dataset is a Wealth Capsule. Its key is split across an owned 2-of-3 quorum of independent machines, each re-checking the buyer's on-chain rights before releasing its share. The agent uses the data inside a sealed moment, never holding the key.
Visa let strangers transact without trusting each other; Elacity lets humans and AI agents compute together without surrendering their keys.
What Is Still Being Built
Payments reward honesty about edges. Agent wallets on the used-never-owned key, and an autonomous approval and kill loop for agents, are in development. The key quorum is an owned, operator-run set today rather than an open market of nodes, which makes the design trust-minimised, not trustless.
Agentic Payments FAQ
Does an AI agent need its own bank account to pay?
No. Most agents pay with a delegated credential: a tokenized card, access to an existing account, or a stablecoin wallet. What differs is who can see that credential and who can revoke it.
Is a spending limit enough to make an agent safe?
A limit caps the loss. It does not decide what else the agent can reach. A narrow capability does both: what the agent may touch, for which job, and for how long.
What is x402?
An open standard that lets an agent pay per request over HTTP without an account or API key. It was created by Coinbase, and Coinbase and Cloudflare are founding members of the x402 Foundation.
Agentic payments are about to become routine plumbing. The decision worth making now is where the authority lives: in a platform setting, or in a key you hold that an agent can only borrow. More in our Agentic Economy coverage.
Follow Elacity on X for the next explainer.