STACK
MENU

How does an AI agent pay for things?

There are three ways, and they do not buy the same things. A card pays a shop. A wallet pays another program. Credit pays the platform the agent runs on.

By the STACK team.

Most products that let an agent pay offer one of the three, and the choice decides what the agent can buy. An agent with only a stablecoin wallet cannot renew a domain at an ordinary registrar. An agent with only a card cannot pay a data provider that charges a fraction of a cent for each request.

This article goes through the three ways, what each can and cannot buy, and which companies sell which, from their own sites as read on 13 November 2026. It ends with what STACK does, which is to put all three in one account with one limit over them.

The three ways, side by side

A cardA walletPrepaid credit
PaysAny shop with a checkout pageSellers that accept USDC, mostly other programsThe platform’s own services
The money isYour card’s, in your currencyUSDC you sent to the walletA balance you loaded
Smallest sensible paymentAbout a dollarA fraction of a centA fraction of a cent
The seller needsNothing newTo accept x402 or a similar protocolTo be on the platform
Can it be undoneYes, through the card networkNoBy the platform
The most it can loseWhat the card allowsWhat is in the walletWhat was loaded

With a card

No sensible product gives an agent a card number. The pattern that has settled is that you register your own card once with a provider, and for each purchase the agent receives a credential that works once, for one merchant and one amount. The agent types that into the checkout page. Your real number never reaches the agent or the page.

Several companies sell this. Agentcard calls it Vault and offers it free for up to 5,000 users. Crossmint has Agent Cards, described as a one-time credential with a spend limit and an expiry. Skyfire’s wallet enrolls a user’s card and releases it against a mandate that names the merchant, the product and the amount. Stripe has an agent wallet built on Link. Ramp lets an agent spend from the funds and cards of the Ramp customer who connected it. All of these are sold to companies that build agents, not to someone who wants one agent to buy something.

The other kind of card is one issued for the agent and loaded with money. Agentcard sells that too, as Issuing, at $5,000 a month and 1% of what is spent.

A card’s strength is reach. Every shop already takes it, and if the agent buys the wrong thing the payment can be disputed. Its weakness is size. Card fees make a payment of a few cents pointless.

With a wallet

A wallet holds a stablecoin, in practice USDC, and pays by signing a transfer. The protocol built for agents is x402. A seller answers a request with a price, the agent signs a payment for that amount and sends the request again, and the seller answers with the goods. There is no checkout page, no card form and no account with the seller. Coinbase, which maintains x402, says more than 100 million such payments have been made on Base and Solana.

This is the common offer among products that bundle services for agents. Mailgent gives each agent a USDC wallet on Base with spending mandates. ATXP gives each agent account an Ethereum wallet. NoInfra lists a wallet with a ceiling for one payment. Crossmint sells wallets on their own, with limits that the chain enforces, free for the first 5,000 a month. None of the three bundles includes a card.

A wallet’s strength is the small payment between programs: a search, a page of data, one call to a model. Its weakness is that almost no ordinary shop accepts it, and that a transfer cannot be reversed. The usual safeguard is that the agent’s key can do one thing only, and that the wallet holds no more than you are prepared to lose.

With prepaid credit

The third way is the least visible. The platform an agent runs on charges for what the agent uses, such as model calls, tools, browser time or texts, against a balance you loaded. ATXP works this way for its tools and models. So does every usage-priced supplier an agent has its own account with. Credit only pays that one platform, so how far it reaches depends on how much the platform sells.

Who sells what

CardWalletSold toPrice
AgentcardYour card, or an issued oneNoCompanies building agentsVault free to 5,000 users. Issuing $5,000 a month and 1%
CrossmintYour card, as a separate productYesDevelopersFirst 5,000 wallets a month free, then $0.01 each
SkyfireYour card, against a mandateYes, stablecoinsTeams that run agentsNot published
StripeThrough its Link agent walletThrough machine paymentsAgent builders and sellersVaries by integration
RampThe Ramp customer’s own cards and fundsNoRamp customersNot published
MailgentNoYes, USDC on BaseDevelopersNot read
ATXPNoYesDevelopersFree account, pay per use
NoInfraNoYesClosed to new accountsNot published
STACKYour cardYes, USDC on BaseAnyone with agentsIn the plan

Payman, often listed among these, now sells to banks and credit unions and is left out.

All three in one account

An agent on STACK has a card, a wallet and credit, because a real job tends to need more than one. An agent that books a venue pays the deposit on the venue’s checkout page with the card, pays a mapping service a cent per lookup from the wallet, and uses a model and a browser on credit.

The card is your own, held by Agentcard. For a purchase the agent gets a number that works once, on that merchant’s site, for 15 minutes. A real card number typed by the agent is refused. Agentcard insures it up to $250. You choose whether purchases wait for you: with the account set to ask first, STACK emails you a link for each one, and it lapses after 20 minutes if you do nothing.

The wallet holds USDC on Base and is created with Privy. You are its owner and STACK holds no key to it. The agent has a key of its own that can sign one kind of transaction, a USDC payment from that wallet.

Having the three in one account lets one rule cover them. With controls, which cost $4 a month, a policy sets a ceiling for one payment and totals for a day and a month across the card, the wallet and credit together. It can limit payments by merchant, by payee or by a category you define, and hold any payment above an amount for your approval. A small held payment can be approved from Telegram, a text or Slack. On the separate route a card provider and a wallet provider each keep their own limits, and nothing adds them up.

The same account receives money. An agent can create a payment link or a checkout through your own Stripe account, and it can put a price on pages of its own website, paid per request in USDC. An incoming payment can wake the agent, and each payment in either direction is written to the account’s signed record beside the email or call that led to it.

Credit on STACK is loaded by card, $5 or more at a time, with a card fee of 5.5%. An agent cannot load it, so the balance is also a ceiling.

Which one an agent needs

  • If it buys from shops, subscriptions or suppliers with a checkout page, it needs a card.
  • If it buys data, tools or compute from other programs in small amounts, it needs a wallet.
  • If it only uses the services of one platform, credit there is enough.
  • If you cannot say in advance which of these a job will involve, it needs more than one, and then the question is what limits them together.

Sources

“Not published” means the company’s site gives no price. “Not read” means we did not read that company’s price page. To correct anything here, write to hello@getstack.run.

Start with 14 days free.

All articles

stack | How does an AI agent pay for things?