Browser Use agents can now check out without ever seeing your card, with Evervault
Browser Use added a way to run agent checkouts without the agent ever seeing your card. It works with Evervault Browser Tokens, which hand the agent stand-in card values instead of the real ones.
You create the tokens on your server by calling Evervault's Browser Tokens API with the card and the hosts allowed to receive it. That returns the tokens plus a proxy login. Start a Browser Use browser with that login as customProxy and trust the Evervault CA. Every other site keeps full certificate checks. The agent then fills the checkout form with the tokens. They are Luhn-valid, with the same length and BIN as the real card, and the CVV has the same number of digits. When the browser sends them to an allowed payment host, Evervault swaps in the real card on the way out. The real number never reaches the model, the agent, or the browser. Tokens expire with their TTL.
A few details matter for real stores. Evervault can forward to the Browser Use residential proxy, so the merchant still sees a residential exit. You can shop on the residential proxy and switch a running browser to Evervault when the agent reaches the payment form, and tabs and cookies stay. EU accounts use the EU Browser Use API and Evervault's EU relay.
Custom proxies are an enterprise feature on Browser Use, so you'd email sales@browser-use.com. Browser Tokens are still in preview at Evervault, so you'll also need to ask Evervault for access.