Evervault Browser Tokens AI agents Review 2026: Features, Security Limits and Use Cases

Evervault Browser Tokens AI agents allow automated systems to finish checkouts and logins on existing websites without handing over real card numbers or passwords. The product launched on October 19–20, 2026 at Money20/20 and targets headless browser setups such as Playwright and Browserbase. Merchants see ordinary payment requests and require no changes to their checkout flows.

Evervault Browser Tokens AI agents Core Features and Mechanics

Tokens preserve format so card numbers remain Luhn-valid and keep the original BIN. CVV tokens match length, and password tokens keep compatible string formats. The agent works only with these tokens. Evervault’s proxy swaps them for plaintext at the exact moment the request leaves the browser, but only for hostnames on the allowlist set at token creation.

Controls are locked when the token is issued and cannot be widened later. Options include exact hostnames or subdomain wildcards, TTL values that default to fifteen minutes, data categories such as card number plus CVV, and egress through residential or data-center proxies. Residential IPs managed by Evervault are scheduled for later release. Logging records every reveal or refusal tied to the session.

The service supports both card checkout and credential flows, including logins that unlock saved payment methods. 3DS and MFA steps stay under user control. No plaintext values or mapping tables are stored by Evervault at any point.

Security Limits, Compliance, and Pricing

When card data is collected and encrypted through Evervault surfaces before token creation, the agent, browser platform, and automation code fall outside PCI scope. Evervault holds PCI DSS Level 1 and SOC 2 Type II certifications. A dual-custody encryption model keeps the merchant unaware of any intermediary involvement, so the payment appears as a standard transaction.

Current per-token restrictions cover hostname allowlists, TTL, and data categories. Spend caps, human-approval gates, kill switches, and merchant-category blocks remain on the roadmap. Early users include Ramp and Natural, which run agentic checkout on unmodified merchant sites.

Production pricing on the Pro plan charges $0.25 per card session, covering number and CVV. Credential sessions cost $0.05 each and are free when paired with a card session. Bandwidth is $1 per GB after the first 25 MB per session. The sandbox remains free for testing.

Practical Use Cases and Remaining Constraints

Teams use the tokens for agent-driven checkout on any merchant site without waiting for new payment protocols. The same mechanism supports login to accounts holding saved cards. Broader credential automation covers passwords and API keys while limiting exposure to models and logs.

Limitations include the short default TTL, the need to predefine allowlists, and the absence of spend caps or approval workflows until roadmap items ship. No major updates appeared in the changelog through early November 2026. Continued integration with platforms such as Browserbase is expected, along with the listed control features.