Wallet Wars
As AI agents gain the ability to make purchases on users' behalf, a battle is emerging over which companies will control those payments and how transactions will work. The article breaks down the competing interests between wallet providers, merchants, card networks, and agents themselves—and explains why the difference between "who processes the payment" and "who transacts as you" actually matters for your rewards, loyalty programs, and who fixes things when something goes wrong.
- Stripe, PayPal, and Shopify are racing to connect their existing wallets to agents, but solutions like Stripe Link's virtual cards create a two-transaction problem: the merchant sees a Stripe card instead of your actual card, breaking loyalty programs and merchant relationships (you lose your airline miles, Walmart can't recognize you for their rewards).
- The industry is moving away from "walled garden" approaches (where Stripe acts like AOL, controlling all transactions internally) toward open standards from card networks—Visa Intelligent Commerce, Mastercard's AgentPay, and Amex's ACE—that let agents use your card without holding it.
- Liability is fragmented across multiple parties: the agent, the wallet, the card issuer, and the merchant each have different responsibilities for authorization, execution, and purchase protection, leaving unclear who refunds you when an agent books the wrong hotel dates.
AI agents are about to handle payments on your behalf—ordering your kids' cleats, booking hotels, managing your schedule. That requires access to your payment credentials, which is triggering a scramble among wallet providers. The core issue isn't just who facilitates the payment, but who gets to act as you in the transaction. Stripe Link (300M users), Shopify Shop Pay (250M users), and PayPal (400M+ users) are the main players jockeying for position. They're moving fast to integrate with agent platforms like Meta's Muse and OpenAI's Instinct, but speed alone won't determine the winner. The real battle is about reach—which wallet works everywhere—and about something subtler: whether the agent can preserve your relationship with merchants while making the payment happen.
When a wallet like Link can't reach a merchant directly, it issues a virtual card to complete the purchase instead. This solves the merchant coverage problem but breaks things downstream. Say your agent books a flight using your Chase Mileage Plus card, but Link pays United with a Stripe-issued virtual card. The transaction goes through, but your airline miles don't post because United sees a different card. Stripe can reproduce the payment without reproducing the relationship. This matters because merchants offer benefits, loyalty programs, and rewards tied to the original card. A walled garden like Stripe's works fine inside its own ecosystem, but the moment your agent shops elsewhere, the customer relationship fragments.
The messier problem is routing. Once an agent can access multiple wallets and cards, which one should it use? You might want your airline card for flights, a different card for groceries, and a merchant's saved payment method for repeat purchases. Different cards offer different rewards, protections, and merchant relationships. Your agent needs payment instructions that go beyond "spend $500"—it needs to understand your preferences, the merchant's relationship to each card, and whose economics matter when those interests conflict. The article cuts off before addressing liability, but that's the final frontier: if your agent books the wrong dates and the hotel charges you correctly for what it ordered, who eats the cost? The rules are still being written.