Skip to content
Live
Browser Use·· yesterday

Browser Use agents can now check out without ever seeing your card, with Evervault

Browser Use agents can now check out without ever seeing your card, with Evervault

Brief overview

Browser Use The intelligent entity completes payment via Evervault token, the real card number is never touched. The token is the same length as the real card number, the check code is valid, and it is replaced by Evervault as the real card number during the payment process. The enterprise version supports custom agents, and the EU version API is available in the EU region.

Article

Browser Use x Evervault

Agents that buy things need a card. Giving a model your real card number is a bad idea. Evervault fixes that.

With Evervault in front of a Browser Use browser, the agent types a token that looks exactly like a card: Luhn-valid, same length, same BIN, a CVV with the same number of digits. The checkout form accepts it. When the browser sends it to a host you allowed, Evervault swaps in the real card on the way out. The real number never reaches the model, the agent, or the browser.

How it works

  1. Create tokens on your server. Call Evervault's Browser Tokens API with the card and the hosts allowed to receive it. You get tokens plus a proxy login.
  2. Start a Browser Use browser on that proxy. Pass the proxy login as customProxy and trust the Evervault CA. Every other site keeps full certificate checks.
  3. Give the agent the tokens. It fills the checkout like a person would.
  4. Evervault swaps the real values only in requests to the hosts you allowed. Tokens expire with their TTL.
curl https://api.browser-use.com/api/v4/browsers \
  -H "X-Browser-Use-API-Key: $BROWSER_USE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "customProxy": {
      "host": "us-va.browser.relay.evervault.app",
      "port": 443,
      "username": "PROXY_USERNAME",
      "password": "PROXY_PASSWORD",
      "caBundleUrl": "https://ca.evervault.com"
    }
  }'

Built for real checkouts

  • Residential IPs still work. Evervault can forward to the Browser Use residential proxy, so the merchant sees a normal residential exit: browser → Evervault → Browser Use proxy → merchant.
  • Switch only at the payment step. Shop on the residential proxy, then change a running browser to Evervault when the agent reaches the payment form. Tabs and cookies stay.
  • EU too. EU accounts use the EU Browser Use API and Evervault's EU relay.

Try it

Read the Evervault guide in our docs. Custom proxies are an enterprise feature: email [email protected]. Browser Tokens are in preview at Evervault, so ask Evervault for access.

Also see: passwords with 1Password and paying with Stripe Link.

Source: Browser Use · browser-use.com