x402 vs Stripe Issuing for AI agents
Last reviewed: August 2026
Choose Stripe Issuing if you are a company building an agent product: once your business is onboarded, you can programmatically issue cards with per-card spending controls, fund them from a bank account, and earn interchange, all with no crypto anywhere. Choose x402 card issuance (Laso) if the agent itself must acquire the card: there is no business onboarding, no bank account, and no API key application; the agent pays one x402 request in USDC and holds a card about a minute later. The dividing line is who does the onboarding: Stripe onboards your company, x402 onboards nobody.
These solve different problems
Stripe Issuing is infrastructure for businesses: your company passes business verification, connects funding, and then your backend creates cardholders and virtual cards by API. It is mature, well documented, and battle-tested. x402 card issuance is infrastructure for agents: any wallet-holding process can buy a card the way it buys any API call, by paying an HTTP 402 challenge. Comparing them is still useful because agent builders genuinely face this choice, usually without realizing the onboarding difference is the whole decision.
Side by side
| Laso over x402 | Stripe Issuing | |
|---|---|---|
| Who onboards | Nobody. A wallet signature is the only identity; the first card can exist a minute after the agent first learns the API exists | Your business: entity verification, review, and an approved Issuing account before the first card |
| Who can use it | Any agent or person with USDC on Base or Solana, including individuals and agents with no company behind them | Companies in supported countries (U.S. first, parts of Europe), building on their own Stripe account |
| Funding | Per card, in USDC, at order time; the 402 challenge quotes the exact total before payment | A pre-funded balance or bank connection your company maintains |
| Card model | Non-reloadable prepaid, $5–$1,000 per card, U.S. merchants; international cards $100–$1,000 with a 3.8% fee, fulfilled within ~24h | Reloadable or single-use virtual cards with rich per-card spending controls (merchant category locks, per-authorization limits), plus physical cards |
| Spending control | The card amount is the control: it holds the checkout total and nothing more | Real-time authorization webhooks: your code can approve or decline each transaction as it happens, which is genuinely stronger |
| Economics | 0% fee on U.S. cards (you pay face value); no interchange share | Per-card and platform fees, offset by interchange revenue share on spend, which at scale can make issuing a profit center |
| Disputes and support | Consumer-grade: refund requests and support through Laso | Full program-level dispute tooling |
| Agent autonomy | Complete: discovery (SKILL.md, llms.txt, ai-plugin.json), pricing, payment, and issuance are all machine-readable and machine-executable | High after setup, zero before it: API keys exist only once a human has onboarded a business |
The case for Stripe Issuing, made properly
If you are building a product where your agents spend your users’ money at scale, Stripe Issuing is probably what you want. Real-time authorization control is the killer feature: your server sees every authorization before it is approved and can enforce policy per merchant, per category, per amount, per agent, live. Interchange share means volume pays you back. Cards are reloadable, physical cards exist, and the compliance burden of running a card program is Stripe’s specialty. None of this is available in the x402 model today, and pretending otherwise would be dishonest.
The case for x402 issuance
Everything above assumes a company is standing behind the agent, willing to onboard, and in a supported country. Remove any of those assumptions and Stripe Issuing stops being reachable. An individual’s personal agent has no business entity. An open-source agent a thousand people run cannot share one Issuing account. An agent that discovers mid-task that it needs a card cannot pause for onboarding. For all of these, x402 issuance is not merely more convenient; it is the only working path: the agent reads SKILL.md, pays a 402 challenge in USDC, and polls for the card number. Setup time is however long one HTTP request takes.
# The entire "onboarding": pay the challenge, poll for the card.
curl "https://laso.finance/get-card?amount=120" # 402 challenge -> pay -> card_id
curl "https://laso.finance/get-card-data?card_id=card_abc123" \
-H "Authorization: Bearer eyJ..." # -> card_number, expiry, cvvThe spending-control story also differs in kind, not just strength. Stripe gives you programmable control over a long-lived card. The x402 model gives you a card that is its own control: it holds exactly the checkout total, so the blast radius of a leaked card number is the leftover balance on a card that was sized to a single purchase. Weaker for a fleet with a treasury; entirely adequate for an agent buying one thing at a time.
A note on Stripe and x402 together
These are not opposing camps. Stripe is an x402 Foundation member and settles x402 payments on Base, so the protocol the agent pays with here is one Stripe itself supports. A plausible future has business-backed agents on Issuing and unaffiliated agents on x402 cards, with both paying x402-native services directly. Choosing today is choosing for your situation, not picking a winner.
Frequently asked questions
Can an AI agent sign up for Stripe Issuing by itself?
No. Issuing requires an approved business account: entity verification and review that a human completes for a company. After that, the company’s backend can issue cards programmatically, including for agent use. The agent operates the cards; it cannot bootstrap the program.
Is Stripe Issuing available to individuals?
No, it is a business product in supported countries. An individual who wants their personal agent to hold a card is outside its model, which is exactly the population x402 card issuance serves: a wallet signature is the whole sign-up.
Which is cheaper for an agent that buys occasionally?
x402 issuance: a $50 U.S. card costs $50 in USDC with a 0% Laso fee, and there are no platform or monthly fees. Stripe Issuing’s economics (platform fees offset by interchange share) reward sustained volume, so it gets cheaper, and eventually profitable, at scale.
Does Stripe support x402?
Yes, on the payments side: Stripe settles x402 payments on Base and joined the x402 Foundation. That is separate from Stripe Issuing, which creates cards; there is no way to obtain a Stripe-issued card by paying an x402 challenge as of August 2026.
Can I get real-time control over what a Laso card is spent on?
Not per-authorization: there is no live approve/decline hook, and this is a real gap versus Stripe Issuing. The available controls are structural: size each card to the exact checkout total, keep the funding wallet lean, use the managed wallet’s per-call spend cap, and receive webhooks for account events.
More guides
- How to give your AI agent a credit card — An AI agent cannot pass credit underwriting, but it can issue itself a virtual prepaid card over an API in about a minute. The working pattern, with real requests: x402 payment in, card number out.
- x402 vs AP2 vs ACP vs MPP vs UCP: which should your agent use? — All five agent payment protocols compared honestly: x402 and MPP for machine-to-machine HTTP payments, ACP for ChatGPT checkout, UCP for Google surfaces, AP2 for authorization. Which layer each one is, when to use each, and a worked x402 example.
- Issue a virtual card with one x402 call — A complete, runnable walkthrough: pay one x402 request in USDC and receive a virtual prepaid card with number, expiry, and CVV. Real endpoints, real response shapes, error handling included.
- All agent guides, or how Laso compares to the alternatives
Try it: connect a wallet at laso.finance and you'll have a card, gift card, or payout in minutes.
Building an agent? Point it at laso.finance/SKILL.md — it can set itself up.