Evervault’s Browser Tokens Solve Credential Theft. The Banks Weren’t Worried About Credential Theft.

Evervault launched Browser Tokens at Money20/20 Las Vegas on October 20, 2026, a product that swaps card numbers, CVVs and passwords for short-lived, Luhn-valid, BIN-preserving stand-ins injected only at allowlisted hosts, priced at $0.25 per card session and $0.05 per credential session, with Ramp and Natural named as launch users. The launch lands amid hard blocks on third-party agents imposed between October 13 and 16, 2026 by JPMorgan, Schwab, BofA and Citi, and a Wells Fargo Online Access Agreement update shifting liability for agent transactions to the customer, because Browser Tokens ships without the spend caps, human-approval thresholds, kill switch and merchant-category blocks banks want and instead markets residential IPs and anti-bot avoidance. Evervault founder Shane Curran's company argues the product needs no bank or merchant protocol adoption, unlike Visa Intelligent Commerce and Mastercard Agent Pay, but the missing governance controls leave the liability and agent-verification questions banks are raising unresolved.

Evervault launched Browser Tokens at Money20/20 Las Vegas on October 20, 2026, positioning the product as a technical workaround for the friction currently stalling agentic commerce https://forkast.news/glossary/agentic-commerce/ . The core promise is simple: by replacing sensitive card numbers, CVVs, and passwords with format-preserving stand-ins, the company aims to prevent credential exposure. However, the product arrives at a moment when the primary barrier to adoption is not just data security, but the fundamental question of agent identity https://forkast.news/learn/what-is-agent-identity/ . The mechanics of the stand-in The mechanism relies on short-lived, Luhn-valid, and BIN-preserving values that allow merchant forms to process data without modification. When a developer integrates the service, Evervault’s browser proxy swaps the real value into the transaction only at allowlisted hosts – and nowhere else. These permissions, including the host allowlist and a default 15-minute time-to-live, are locked at the moment of token creation and cannot be expanded. Because no token-to-value mapping is stored, the agent, the browser, and the logs remain outside of PCI scope, with the compliance burden resting on Evervault. Pricing is set at $0.25 per card session and $0.05 per credential session, with Ramp and Natural named as launch users. The product is designed to bypass the slow-moving consensus required by traditional card networks. As the company notes, Visa Intelligent Commerce and Mastercard Agent Pay require both the bank and the merchant to support the protocols, a hurdle that remains significant. Browser Tokens, by contrast, require no such adoption. As the product page states, the merchant sees a normal sign-in and a normal card payment. Anti-detection versus verification This ease of integration creates a distinct tension. While the product shields credentials, it also markets features such as residential IPs, standard Chrome network fingerprints, and anti-bot avoidance tools. These features are intended to ensure an agent is not turned away by merchant fraud checks. Yet, this is the exact behavior that triggered the recent wave of bank lockouts https://forkast.news/the-access-tax-amazon-imposed-on-shopping-agents-just-arrived-at-your-bank/ . Between October 13 and 16, 2026, institutions including JPMorgan, Schwab, BofA, and Citi implemented hard blocks against third-party agents. Wells Fargo even updated its Online Access Agreement to shift liability for agent transactions directly to the customer. The banks are not merely concerned with credential theft; they are concerned with the lack of verifiable intent. Jamie Dimon has publicly cited the risk of rogue agents, stating: “You don’t want rogue agents, and it could be thousands of them,” and “There’s a liability transfer.” Schwab’s executive team has noted the necessity of blocking unauthorized tools, reporting that they block agents “in the tens and twenties” each week, while asking the question: “who’s liable?” The industry is currently moving toward a verification-first model, exemplified by the Visa Trusted Agent Protocol https://forkast.news/the-banks-locked-agents-out-this-week-an-agent-paid-an-invoice-through-the-front-door/ , which emphasizes directory registration and buyer-approved execution. Evervault’s anti-detection features effectively help agents mimic human behavior to bypass the very security gates that banks are currently reinforcing. Roadmap versus immediate governance The current iteration of Browser Tokens focuses on the mechanics of the transaction rather than the governance of the agent. Features that would provide the guardrails banks demand – such as spend caps, human-approval thresholds, a kill switch, and merchant-category blocks – are marked as upcoming on the roadmap rather than available at launch. Without these controls, the product solves the problem of credential exposure while leaving the underlying liability and verification issues unresolved. Shane Curran, founder of Evervault, has stated that “Agentic payments are just payments.” But for the institutions holding the capital, the distinction between a human and an agent remains the defining risk of the current cycle. Until the infrastructure can prove who is initiating the transaction, the ability to hide an agent’s identity may prove to be a liability rather than a feature.