The new technology lets AI agents use temporary card and password values during checkout, while Evervault replaces those values with real credentials before requests reach authorized merchant systems.

AI agents can search for flights, compare prices, and fill in passenger details. But when a task reaches the payment page, a critical problem remains: how can an agent pay without exposing a user's sensitive financial information?

Evervault is addressing that challenge with Browser Tokens, a new product designed to let AI agents complete online checkouts without handling real card numbers or security codes.

Announced by Evervault founder and CEO Shane Curran, Browser Tokens use temporary stand-in values for card numbers, CVVs, and passwords. The agent enters these values into a merchant's existing checkout form. Evervault then replaces them with the real credentials as the relevant request travels to an authorized destination.

The merchant can continue processing a conventional payment without adopting a new payment protocol. Meanwhile, the agent does not need direct access to the underlying card details.

The product targets a growing barrier to agentic commerce: AI systems need enough authority to complete tasks, but they should not receive unrestricted access to the user's financial credentials.

Evervault says Browser Tokens are available for Chromium-based headless browsers, including Browserbase. The company also names Ramp and Natural among organizations using or adopting the technology.

Why AI Agents Need a Safer Way to Pay

AI agents are moving beyond conversation and into tasks that involve multiple websites and services. They can help users book travel, purchase products, manage accounts, and complete other digital workflows.

However, online payments introduce a sensitive security problem.

To complete a purchase, an agent may need to interact with a form containing a card number, CVV, billing details, or login credentials. Giving an agent direct access to these values creates additional risks.

Sensitive information could appear in logs, browser sessions, debugging tools, or other systems involved in the workflow. A malicious webpage could also attempt to manipulate an agent into revealing information or sending it to an unintended destination.

These risks create a difficult trade-off. If users must approve every payment step, agents lose some of their ability to operate independently. If developers give agents unrestricted access to payment credentials, they increase the potential impact of a security failure.

Existing alternatives also have limitations. Virtual cards can require additional setup and may change how transactions appear on statements. Network-based agentic payment solutions depend on their supported payment arrangements and participating parties.

Evervault's approach is to keep the agent working with substitute values while a separate system controls when the underlying credentials can be revealed.

The objective is not to eliminate every risk associated with autonomous purchasing. Instead, Browser Tokens aim to reduce the exposure of sensitive data while allowing agents to use existing online checkout systems.

What Are Evervault Browser Tokens?

Browser tokens are temporary stand-in values that represent sensitive information. They can replace card numbers, CVVs, and passwords during an agent's interaction with a website.

Evervault generates the tokens in a format that the relevant input field can accept. For example, a card token can be formatted to pass the basic checks that a checkout form applies to card numbers.

When the agent submits the form, Evervault's proxy replaces the token with the corresponding real value before the request reaches an authorized destination.

This creates a separation between the information the agent handles and the credentials required to complete the transaction.

The agent fills out the form using the token. The merchant or payment processor receives the underlying payment information through the configured flow.

According to Evervault, this means merchants can continue using their existing checkout pages. They do not need to adopt a new payment protocol or redesign their payment systems specifically for browser tokens.

That compatibility is central to the product's pitch. Rather than waiting for every merchant to support a new agentic payment standard, developers can build around the checkout infrastructure already in use.

However, compatibility does not mean every checkout will necessarily work without additional configuration. Browser setup, merchant security controls, payment verification, and other site-specific requirements can still affect a transaction.

How Browser Tokens Work

Evervault describes a setup process that connects credential collection, token creation, and browser traffic routing.

1. Collect and encrypt the sensitive data.

The developer first collects and encrypts the relevant card details through Evervault's card collection infrastructure.

The process can also cover passwords when an agent needs to sign in to an existing merchant account.

2. Create tokens for the task.

The developer creates browser tokens using the encrypted values. The tokens act as substitutes for the credentials that the agent would otherwise need to enter.

Developers can limit which types of data are available. For example, a purchase might require a card number and CVV, while another workflow may need a password to access an account.

3. Give the agent the tokens.

The agent receives the stand-in values and enters them into the relevant checkout or login fields.

The agent can continue working through the browser without directly receiving the real card number or password through this mechanism.

4. Route browser traffic through Evervault

The browser's traffic passes through Evervault's proxy. Developers configure the environment so that the proxy can identify the relevant tokens and replace them where the rules permit.

Evervault says the browser needs its certificate authority certificate installed in the trust store. This is a required setup step for the described proxy architecture.

5. Replace tokens at authorized destinations.

When a request reaches a permitted hostname, Evervault replaces the relevant token with the real value.

If the destination is not authorized, the proxy is designed to forward the request without revealing the underlying credential. The recipient would therefore receive the stand-in value rather than the real card details.

This destination-based control is important because an agent may encounter misleading content or malicious pages while browsing. The objective is to prevent a token from becoming a route for disclosing the actual credential to an unapproved host.

Four Controls Designed to Limit Credential Exposure

Browser tokens include several controls that developers can set before an agent starts its task.

Hostname allowlists: Developers specify which merchant, payment processor, or gateway hosts can receive the real values. This is intended to prevent credential disclosure to unrelated destinations.

Time limits: Tokens expire after a defined period. Evervault says the default time to live is 15 minutes, although developers can choose a different window to accommodate the task.

Data categories: Developers can restrict tokens to the information required for a workflow, such as card details for checkout or passwords for sign-in.

Egress type and region: Developers can use their own residential proxy to make browser traffic originate from a location that suits the merchant's requirements. Evervault-managed residential IPs are listed as a future offering.

Evervault says these permissions become fixed after token creation. Neither the agent nor the application code can expand them later. The company also says it logs credential reveals and refusals for each session, allowing developers to review which values were released to which hosts.

These controls can support more restrictive payment workflows. However, they do not remove the need to secure browser infrastructure, protect account access, validate transactions, and monitor agent behavior.

The quality of the overall implementation will still depend on how developers configure the system and manage the wider agent environment.

Do Merchants Need to Change Their Checkout?

One of Browser Tokens' main selling points is that merchants can continue using their existing checkout forms.

Evervault says its card tokens retain the first six digits of the underlying card number and pass the Luhn checksum used to validate card-number formats. This helps a checkout form recognize the expected card brand and accept the token as an input value.

The token itself is not the payment card. It is a stand-in that Evervault replaces when the configured request reaches an authorized destination.

This distinction could make the technology useful for agent developers working with established online merchants. They would not necessarily need to persuade every merchant to implement a dedicated agentic payment protocol.

The company also says its proxy can match the network fingerprint of a regular Chrome browser. Developers can combine it with a residential proxy when a merchant expects traffic from a residential connection.

These capabilities are intended to help automated browsing work with existing checkout systems. They should not be interpreted as a guarantee that merchants' fraud systems will accept every agent-driven transaction.

Merchant protections can use several signals beyond card format or network fingerprint. A checkout may also require additional verification, account checks, or user confirmation.

What about 3D Secure and multi-factor authentication?

Browser Tokens do not remove every user interaction from the payment process.

Evervault says frictionless 3D Secure can continue to work normally. However, a 3D Secure challenge or multi-factor authentication prompt may still require the user to participate, often through a session takeover provided by the browser platform.

This is an important limitation for fully autonomous purchasing. A system may be able to complete most of a checkout automatically yet still need a person to approve a security challenge or confirm a sensitive action.

For developers, the practical goal is therefore controlled automation rather than a guarantee that every transaction will be completed without human involvement.

Browser Tokens vs Network Tokens and Virtual Cards

Browser Tokens take a different route from several other approaches to agentic payments.

Network-based agentic payment products, including Visa Intelligent Commerce and Mastercard Agent Pay, use payment-network infrastructure to support authorised agent transactions. Their coverage depends on the applicable network, issuer, merchant and product arrangements.

Virtual cards provide a separate card number for a transaction or spending arrangement. They can help limit exposure of a primary card number, but may require another provider, onboarding process or supported region.

Browser-based secret vaults let a browser platform store credentials and fill them into a session. While that can keep values out of the agent's prompt, sensitive data may still enter the browser environment or related debugging interfaces, depending on the implementation.

Evervault's approach is different: the agent enters a token, and a proxy replaces it with the real value at a hostname approved by the developer.

This could help developers work with existing merchant checkout pages. It also creates a dependency on Evervault's proxy, token configuration and browser setup.

No single approach automatically solves every agentic payment problem. Developers need to consider the payment methods they support, geographic coverage, credential security, user authorisation and how they will handle failed or disputed transactions.

Browser Tokens should therefore be viewed as one approach to securing credential use in agent-driven checkout—not a universal replacement for card-network tokenisation, virtual cards or other payment controls.

What This Means for PCI DSS and Payment Security

Handling card data can bring systems and service providers within the scope of the Payment Card Industry Data Security Standard (PCI DSS). This is one reason developers are looking for ways to limit the exposure of sensitive payment information in agent workflows.

Evervault argues that Browser Tokens can help reduce the systems that handle real card data. Instead of giving an agent the underlying card number, the developer supplies a token and uses the proxy to replace it at the permitted destination.

That design may help reduce data exposure. However, using Browser Tokens does not automatically remove an organisation from PCI DSS scope.

The actual scope depends on the full payment architecture, the systems that can affect the security of the cardholder data environment, the integration design and the applicable assessment requirements. Businesses should validate their implementation with their qualified security assessors or other appropriate compliance advisers.

The same caution applies to broader security claims. Tokenisation can reduce the amount of sensitive information an agent handles, but it does not eliminate risks involving compromised accounts, malicious browser extensions, misconfigured allowlists or unauthorised purchases.

For fintech companies and merchants, the key question is whether the system's technical controls, operational practices and compliance position match the risks of the intended use case.

Availability and Pricing

Evervault says Browser Tokens are available for Chromium-based headless browsers, including Browserbase. Developers can use the product alongside Evervault's card-data infrastructure.

The company lists free sandbox apps for testing. Production apps are available through its Pro plan, with published starting prices of:

  • $0.25 per card session, covering the card number and CVV.
  • $0.05 for non-card data, such as passwords and personal details.

Evervault says production usage is backed by a service-level agreement (SLA). Developers should consult the company's current documentation and commercial terms for eligibility, limits and implementation requirements.

For teams building autonomous shopping, booking or account-management agents, the pricing provides an initial way to assess the cost of adding a credential-protection layer. The total operating cost will also depend on browser infrastructure, proxy requirements and the wider agent workflow.

Why Browser Tokens Matter for Fintech

The launch highlights a central issue in agentic commerce: AI systems need a safe way to act on behalf of users without gaining unrestricted access to sensitive credentials.

Payment networks are developing agentic payment products. Wallet providers are exploring new ways to authorise machine-initiated transactions. Meanwhile, infrastructure providers such as Evervault are working on how agents can use today's websites and checkout forms.

Browser Tokens focus on that last problem. They aim to make it possible for an agent to interact with existing payment forms while limiting exposure of the actual credentials.

If the model proves reliable across real-world implementations, this approach could support travel booking, online shopping and other workflows where agents need to sign in and pay for services.

Yet the larger market will require more than a secure substitute for a card number. Businesses will also need spending controls, user consent, transaction records, fraud monitoring, dispute processes and clear responsibility when an agent makes a mistake.

The key measure of success will be whether these systems make agentic transactions safer and easier to manage without adding unacceptable operational or compliance risks.

The Bottom Line

Evervault's Browser Tokens are designed to help AI agents complete online payments without directly handling users' real card numbers, CVVs or passwords.

The system uses temporary stand-in values, a configured proxy and hostname restrictions to control where the underlying credentials are revealed. Its compatibility with existing checkout forms could make it attractive to developers who want to automate purchases without waiting for every merchant to adopt a new payment protocol.

However, Browser Tokens do not guarantee that every checkout will work, remove every human verification step or automatically eliminate PCI DSS obligations.

The broader significance is clear: as AI agents move from recommendations to real-world transactions, credential security and spending authority will become critical parts of payment infrastructure.

The next stage of agentic commerce will depend not only on what AI agents can do, but on whether they can act with tightly controlled access to money and personal data.


Sources and further reading

Editorial note: Product capabilities, pricing and security statements are attributed to Evervault's supplied announcement. Confirm the latest technical documentation and compliance guidance before publication.