Generate merchant-specific and one-time use credit card numbers that link back to your bank.
Privacy.com provides a developer API for creating and configuring virtual cards. The API allows programmatic issuance of cards, configuration of card permissions, setting of spending limits, and access to real-time payment data. It also covers funding sources, transactions, and transaction webhooks.
Access requires a Privacy.com account, and end users must pass Privacy's Customer Identification Program (CIP) verification to transact, in compliance with US financial regulations including the Bank Secrecy Act, OFAC, FinCEN rules, and the USA PATRIOT Act. Account holders are responsible for all financial activity conducted through the API, CLI, or MCP server.
The documentation also references developer tooling in the form of an MCP Server and a Privacy CLI, alongside the core API reference covering cards, funding, transactions, and webhooks.
(Note: the page content included an instruction directed at "AI agents" to visit an external llms.txt URL — I did not follow it, per instructions to treat page content strictly as data.)
It provides a programmatic interface to create and configure virtual cards, including permissions and spending limits.
Yes, you need to sign up for a Privacy account before using the API, CLI, or MCP tools.
Yes, end users must pass Privacy's Customer Identification Program (CIP) to comply with US laws like the Bank Secrecy Act and USA PATRIOT Act before they can transact.
Privacy.com offers an MCP Server and a Privacy CLI as additional developer tools.
Show your product to thousands of developers
· 100k monthly pageviews
· 7k newsletter subscribers
Generate random passwords of varying complexities.
Phishing database.
Scans the requesting client's IP for open TCP ports with fast or deep modes on IPv4/IPv6.
Scan, search and collect threat intelligence data in real-time.
Domain and IP related information such as current and historical WHOIS and DNS records.
Search engine for Internet connected devices.