Browser Use agent payment does not expose card numbers
The story so far
Browser Use agent completes payment via Evervault tokens, real card numbers never touch the model. Tokens are the same length as real card numbers, have valid checksums, and are replaced by real card numbers by Evervault during the payment process. Enterprise version supports custom proxies, EU version API available for EU regions. Browser Use agent uses Evervault tokens for payment, tokens appear identical to real card numbers including checksum, length, and BIN. When the browser sends the token to the authorized host, Evervault replaces it with the real card number during transmission, ensuring the real card number is never touched by the model, agent, or browser. Tokens have a TTL limit, and Browser Tokens are currently in Evervault's preview phase, requiring access permission from Evervault.
AI-written from the reports · Updated 1 hour ago
Coverage timeline
Follow the coverage to see every side of the story.
- Browser UseBrowser Use agent can complete payment using Evervault tokens without exposing real card numbers
Browser Use The intelligent entity completes payment via Evervault token, the real card number is never touched. The token is the same length as the real card number, the check code is valid, and it is replaced by Evervault as the real card number during the payment process. The enterprise version supports custom agents, and the EU version API is available in the EU region.
Heat over time
Not enough data yet to draw a trend.