Browser Use gives web agents single-use cards for checkout

Why it matters

Browser agents can already search, compare and fill carts. Single-use Link cards let them finish purchases on existing websites while limiting access to the user's real payment credentials.

Browser Use added Stripe's Link wallet to its web-agent stack on September 3rd, letting an AI agent request a single-use card, enter it at checkout and complete an online purchase without receiving the user's underlying payment credentials.

https://x.com/browser_use/status/2095532489150537802

The company announced the integration in a post on X. A user connects a card to Link once. When a Browser Use agent needs to pay, it sends a spend request. Link then issues a temporary card for the approved transaction, and the agent uses that credential on the merchant's checkout page. The card stops working after the purchase.

Link still requires the user to approve each request before releasing a payment credential. Stripe's documentation for its agent wallet says the request can include the merchant, amount, currency and an explanation of the purchase. Users can review requests and track agent spending through Link's web interface or mobile apps.

That approval step puts a human between an agent's shopping decision and the movement of money. The agent receives enough information to finish checkout, while the card stored in the user's Link wallet remains hidden. A compromised browser session could expose the temporary credential, but the single-use design narrows its value beyond the authorized transaction.

A payment layer for the existing web

The integration gives Browser Use agents a path through ordinary card checkouts. That is important because most merchants have not rebuilt their stores around machine-payment protocols or AI-specific checkout APIs. A disposable card lets an agent use payment forms already designed for human shoppers.

Stripe launched Link's wallet for agents on April 29th. The product runs on Stripe Issuing and can provide either a one-time-use card or a Shared Payment Token, a credential designed for machine-native transactions. Browser Use's announcement centers on the card route, which gives its agents a way to pay on sites that still expect a card number.

The result extends browser agents from researching products and filling carts into completing the transaction. Browser Use already lets agents open pages, click controls, type into forms and run longer web workflows through its open-source Python library and hosted service. Its GitHub repository had more than 112,000 stars as of September 3rd.

Payments raise the stakes for the same automation. A failed research task wastes time. A failed purchase can move money, order the wrong item or send goods to the wrong address. Browser Use and Link are handling the credential problem through temporary cards and mandatory approval, while the browser agent remains responsible for navigating the merchant's interface and entering the correct order details.

Browser Use moves closer to transaction infrastructure

Browser Use was founded in 2024 by Magnus Muller (@mamagnus00) and Gregor Zunic (@gregpr07), who met while studying data science at ETH Zurich. The pair began working on Browser Use after encountering the limits of conventional browser automation, then released the project as open source in November 2024.

Browser Use joined Y Combinator's Winter 2025 batch. In March 2025, it raised a $17 million seed round led by Felicis, with participation from A Capital, Nexus Venture Partners, Y Combinator, Paul Graham, Liquid 2, SV Angel and Pioneer Fund.

Muller and Zunic initially built Browser Use to translate websites into structures that language models could interpret and operate. The Link integration pushes that thesis into commerce: Browser Use supplies the hands that operate the site, while Stripe supplies a narrowly scoped payment credential.

Stripe has been building several routes for agents to transact. Its Agentic Commerce Protocol with OpenAI supports merchant integrations and Shared Payment Tokens, while Link's wallet for agents addresses purchases on the card-based web. Browser Use is adopting the second route, giving developers a way to add purchasing without building a wallet, card-issuing system and approval interface themselves.

The product remains dependent on a human authorization for every payment. Stripe has said it plans to add controls that could permit purchases within preset limits without separate approval. For now, Browser Use agents can reach the final checkout button, but Link keeps the last financial decision with the cardholder.