Your AI agent found the flight, picked the seat, and filled in the passenger details. Then it reached the payment form and stopped.

To finish the job, it needed a card number, and you’d be right not to give it one, despite what Elon says:

Anything you give a model may end up in a log, on someone else's server, or in the hands of a webpage built to trick it.

Every team building agents hits this wall, and every workaround costs something. Hand the agent the card and you, your model provider, and your browser platform all fall into PCI DSS scope. Keep the user in the loop and nobody’s awake to approve the overnight fare drop. Virtual cards cost users their rewards, and agentic payment protocols could take years to adopt.

Today, we’re launching Browser Tokens, so your agent can finish what it started. The agent checks out with a stand-in card number, and Evervault swaps in the user’s real card on the way to the merchant. The merchant sees a normal payment, and the real number never reaches the agent, its logs, or your model provider.

Browser Tokens are available with Chromium-based headless browsers like Browserbase. Join companies like Ramp and Natural and start using Browser Tokens today.

"Agents complete checkout with tokenized data, and the real card is only swapped in when it reaches the merchant. That's what lets agentic commerce scale on today's web, without waiting for every merchant to adopt new protocols."

Walt Leung, Co-founder and CPO at Natural

What are Browser Tokens?

Browser Tokens are stand-in values for a card number, CVV, or password. Each token is randomly generated in the same format as the value it replaces, so the agent can type it into a checkout form like a real card.

When the agent submits the form, Evervault's proxy swaps the token for the real value on the way to the merchant, and only until your set time limit runs out.

How do Browser Tokens work?

Browser Tokens sit between your agent browser and the merchant, and setup takes minutes:

1. Collect and encrypt card data via Evervault card collection.

2. Create a Browser Token for your agent with the encrypted values.

3. Give the agent the Browser Tokens.

4. Route the browser’s traffic through Evervault. You can add a downstream proxy for cases where you need a residential IP. 

5. Evervault swaps the tokens for the real values on the way to the merchant.

Browser Tokens also work for passwords. You can give your agent a stand-in password to log in to the user's account on the merchant site, so it can pay with the card already saved there.

Do merchants need to make any changes?

The merchant sees a normal sign-in and a normal card payment. They don't have to adopt a protocol or rebuild their checkout.

Each token passes the checks a checkout page runs on a card number. It's Luhn-valid and keeps the card's first six digits, so the form shows the right card brand and accepts it. When the agent submits the form, Evervault swaps the token for the real card on the way out, and the merchant or its payment processor receives the original card number. The merchant never knows that Evervault was involved.

The traffic looks like a person shopping, too. Evervault's proxy matches the network fingerprint of a regular Chrome browser, and with a residential proxy the request comes from a home connection instead of a data center, so the merchant's fraud checks don't turn the agent away.

Frictionless 3D Secure works as normal. A 3DS challenge or MFA prompt still needs the user, usually through your browser platform's session takeover.

How do Browser Tokens compare to alternative agentic payment solutions?

One integration covers any card that already pays online, debit or credit, issued in the US or anywhere else. Here's how the alternatives compare:

How do you control where an agent’s card data goes?

You set the rules when you create the token, before the agent starts. Four controls are live today:

• Hostname allowlist. Only the merchant, payment processor, or gateway hosts you name can see the real card. If a page built to trick the agent sends the token somewhere else, Evervault forwards the request untouched, and that site receives a worthless stand-in.

• Time to live. Tokens stop working after a window you choose, fifteen minutes by default. Set it long enough to cover a login or MFA step, and no longer.

• Data categories. Tokenize only what the task needs: card number and CVV for a checkout, a password for a sign-in.

• Egress type and region. Bring your own residential proxy so traffic comes from the country or city the merchant expects. Evervault-managed residential IPs are coming.

Those permissions are locked once the token exists. Neither your code nor the agent can widen them later. Evervault logs each reveal and refusal per session, so you can see which values went to which hosts.

Getting started with Browser Tokens

You can start building today. Sandbox apps are free for testing purposes. Production apps are available with the pro plan and start at $0.25 per card session, covering the card number and CVV, and $0.05 for non-card data such as passwords and personal details, all backed by an SLA.

Alongside Evervault, you'll need a headless Chromium browser, like Browserbase. The docs below walk through both:

• Browser Tokens documentation

• Browserbase integration documentation

If you're new to Evervault and want to explore our complete card data infrastructure platform, contact our team to learn how we can help you reduce your PCI scope and optimize your payments.

Frequently Asked Questions

1. What are agentic payments?

Any purchase completed by an agent. The end user authorizes the purchase and shares a card, and the agent handles everything else automatically.

2. How can an AI agent pay without seeing card data?

With Browser Tokens, your agent gets a stand-in card number that looks like a valid card number to use in checkout forms. Evervault sits between your agent and the merchant and replaces the stand-in value with the real one. The swap only happens for sites you’ve approved, so the agent and its logs only ever see the stand-in.

3. Do Browser Tokens keep me out of PCI DSS scope?

Yes. Your agent and browser never touch real card data, so they stay out of Payment Card Industry (PCI) compliance scope. Evervault handles the real card data in its own PCI-certified environment.

4. Do Browser Tokens store card data?

Evervault doesn’t store real card numbers or a list matching tokens to cards. Your systems store only encrypted card data, which is useless without Evervault’s keys.