Browser Use added credit card payments for its hosted browser agents. The feature uses Link, Stripe's payment service, connected once under Integrations. When an agent reaches a checkout, it requests approval and names the amount, merchant and item. The user approves in the Link app, and nothing is charged before that. Link then issues a single-use virtual card valid for hours and one purchase. The agent fills the form, pays, and reports back. Browser Use says the agent never holds the Link token and cannot approve payments for itself. Real card numbers stay inside Link. On Stripe checkouts that advertise agent payments, the agent can use a Link Pay Token instead of a card number.
What changed
Hosted browser agents could not complete card checkouts without exposing a real card number.
What it unlocks
Letting a hosted browser agent complete a checkout after a human approves the exact amount and merchant.
- one-time card valid for hours
- one purchase per card
What you need to act on it
- Browser Use Cloud account
- Link account connected under Integrations
- Pay with Link enabled on the task
- approval in the Link app for each purchase
Sources