by 100xPercent
Pop Pay is a CLI and MCP server that lets AI agents complete checkouts without ever seeing card details. Credentials are injected into the browser page over the Chrome DevTools Protocol, outside the agent's context.
PluginContact for pricing
Step 1: Install with Homebrew, the curl script, or npm install -g pop-pay.
Step 2: Run pop-pay init-vault to encrypt your card credentials, optionally with --passphrase.
Step 3: Run pop-pay launch to open Chromium with remote debugging on port 9222.
Step 4: Add the MCP server to your client, for example claude mcp add --scope user pop-pay -- npx -y pop-pay launch-mcp.
Step 5: Set limits and allowed categories in ~/.config/pop-pay/.env.
Step 6: Let the agent call request_virtual_card when it reaches a checkout page.
No. Credentials are injected into the browser page over CDP and are masked in all MCP responses and logs.
The README gives setup for Claude Code, Cursor, Windsurf, VS Code and OpenClaw. Any MCP-compatible client can use the standard config.
Yes. A separate pop-pay-python package is installed with pip and uses the same security model and vault format.
The project is MIT licensed. Using Stripe Issuing as the card provider requires your own Stripe key.
Requirements
Churnkey MCPChurnkey MCP connects AI agents to a Churnkey workspace so they can read retention data, edit Cancel Flows and dunning campaigns, run experiments and publish changes. Access follows the signed-in user's own permissions.MCP AirlockMCP Airlock is a proxy placed between an AI agent and an MCP server. It adds per-caller tool permissions, dry runs, human confirmation for risky calls, and an audit trail.