01 · Tokenize
Encrypt card details with Evervault. Create a short-lived Browser Token scoped to the payment destinations you need.
Payments · Browserbase × Evervault
From browsing to buying.
Secure checkout for AI agents.
Build payment workflows with Browserbase and Evervault Browser Tokens. Let agents complete checkout while keeping real card numbers and CVVs outside the browser.
The integration
Let your agent pay. Keep card data protected.
Browserbase runs your checkout workflow. Evervault gives it temporary, card-shaped tokens to enter into payment forms.
The browser works with tokens. Evervault’s proxy swaps them for the real card details as the request leaves the browser for the payment destination.
How it works
A browser that acts. A token that protects.
Three steps from encrypted card data to checkout.
02 · Automate
Run checkout on Browserbase through Evervault’s proxy. Your agent fills the payment form with token values.
03 · Complete
Evervault swaps tokens for real card details on requests to allowed hosts. The browser continues to work with tokens.
Payment use cases
From “find it” to “take care of it.”
Build agents that follow through on approved purchases.
Where agents can help
Take an approved trip through checkout.
Build a payment workflowHelp travelers compare options, fill passenger details, and complete an approved booking through a website. Use tokens for the payment fields while your application manages approval and confirmation.
Open Source
- Stagehand SDK
Primitives
- Browser APIs
Keep supplies moving.
Build a payment workflowReplenish office supplies and place approved orders through vendor storefronts. Let the browser handle the forms while your application controls the items, budget, and approval.
Open Source
Primitives
- Browser APIs
Make the next step a prepared checkout.
Build a payment workflowMove from a customer’s selection to a checkout ready for approval. Automate cart and form steps across storefronts, and verify the order result before reporting success.
Open Source
- Stagehand SDK
Primitives
- Browser APIs
Get started
Your first tokenized checkout
Connect Evervault to your Browserbase workflow in four steps.
01 · Encrypt the card
Collect and encrypt the card number and CVV with Evervault before they enter your automation. Your backend uses the encrypted values to request a Browser Token.
02 · Create a Browser Token
Create tokens just before checkout. Set a short TTL and allow only the merchant and payment-provider hostnames that receive the card fields. Evervault returns tokens and proxy credentials; tokens remain reusable until expiry.
03 · Connect Browserbase
Use Evervault’s returned credentials as an external proxy for your Browserbase session. Configure the runtime to trust Evervault’s CA certificate, without disabling certificate verification. Connect your automation and use only token values.
04 · Complete checkout
Fill payment fields with the tokenized card number and CVV. Evervault’s proxy replaces them with real values for allowed destinations. Your application confirms purchase approval and records the checkout result.
Will tokens work with existing checkout forms?
Card tokens retain the BIN, card length, and Luhn validity; CVV tokens retain their digit count. Merchants need no new protocol or integration. Use customers’ existing cards, including virtual cards. Some checkouts with client-side encryption require Evervault-managed, provider-specific handling.
How does this reduce PCI scope?
Evervault is a PCI DSS Level 1 service provider. Scope reduction depends on correct implementation: collect and encrypt card data before it reaches your automation, and pass only tokens to agents, browsers, and logs. Browser Tokens do not automatically make every part of your application compliant.
What is stored, and which controls are live?
Evervault stores no plaintext or server-side token mapping. Encrypted session data travels in time-bound proxy credentials. Live controls include destination allowlists, expiry, fixed permissions, and session reveal/refusal logs. Spend caps, approval thresholds, a session kill switch, and merchant-category blocks are listed as in progress.
Does this handle 3D Secure or purchase approval?
Frictionless 3D Secure works normally. Challenges and MFA may require user intervention. Your application handles purchase approval; transaction authorization remains with the issuer or processor. Browser Tokens protect submitted values, rather than orchestrating checkout.
Is this only for cards, and how is it priced?
Browser Tokens also support passwords, email, and phone values. An Evervault account is required. Sandbox use is free under fair-use limits; production card and credential sessions are billed separately, with residential proxy charges extra. Check Evervault’s product page for current pricing.
Browserbase × Evervault
Give your agent a way to pay.
Build the browser workflow. Keep card data outside it.
