Privacy Cards for Openclaw

A powerful programmatic interface for creating and managing Privacy.com virtual payment cards through Openclaw Skills.

johnielee
v1.0.0
Feb 5, 2026
1
2.5k
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install privacy-cards

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install privacy-cards using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Privacy Cards?

The Privacy Cards skill enables developers to integrate Privacy.com's robust virtual card infrastructure into their automated workflows via Openclaw Skills. It allows for the generation of single-use, merchant-locked, or unlocked virtual cards, providing a secure layer for online payments that protects your primary funding sources.

By leveraging this skill, users can programmatically control card states, update spending limits in real-time, and monitor transaction histories. It is designed for those who need a high level of security and automation in their digital purchasing and subscription management, all handled within the Openclaw Skills ecosystem.

Privacy Cards Use Cases

  • Automated creation of single-use cards for one-time online purchases to prevent recurring billing.
  • Generating merchant-locked cards to restrict spending to specific vendors and prevent overcharging.
  • Programmatic auditing of transaction history for business expense management.
  • Dynamic adjustment of spending limits based on budget thresholds or project requirements.
  • Rapid response security scripts to pause or close cards automatically during suspicious activity.

How Privacy Cards Works

  1. The skill authenticates with the Privacy.com API using a securely stored API key within the Openclaw Skills configuration.
  2. A request is initiated to create a card with specific parameters, such as card type (SINGLE_USE, MERCHANT_LOCKED, or UNLOCKED) and a defined spend limit.
  3. The Privacy.com API processes the request and returns a JSON object containing the card token and sensitive card data like PAN, CVV, and expiry (subject to account permissions).
  4. Users can then perform management actions such as listing all active cards, retrieving specific card details, or patching card states to PAUSED or CLOSED.
  5. Transaction data is retrieved via the transactions endpoint, allowing for detailed filtering by date, card token, or approval result.

Privacy Cards Setup

To begin using this skill within Openclaw Skills, follow these installation steps:

  1. Sign up for a Privacy.com account.
  2. Email support@privacy.com to request API access specifically for your account.
  3. Once approved, obtain your API key from your account dashboard.
  4. Configure your environment variable to authenticate requests:
export PRIVACY_API_KEY="your-api-key"

Note: For testing, you can use the sandbox environment at https://sandbox.privacy.com/v1 before moving to production.

Privacy Cards Data Schema & Taxonomy

The Privacy Cards skill utilizes a structured JSON schema for card and transaction management. Below is the primary data organization:

Card Object Schema

Field Type Description
token String Unique UUID for the card
type String SINGLE_USE, MERCHANT_LOCKED, or UNLOCKED
state String OPEN, PAUSED, or CLOSED
spend_limit Integer Limit in cents
spend_limit_duration String TRANSACTION, MONTHLY, ANNUALLY, or FOREVER

Transaction Object Schema

Field Type Description
token String Unique UUID for the transaction
amount Integer Transaction amount in cents (negative for debits)
result String APPROVED or DECLINED
status String PENDING, SETTLING, or SETTLED

Privacy Cards Advanced Features

  • Support for merchant-locked cards that automatically bind to the first merchant that processes a transaction.
  • Granular transaction filtering including date ranges, specific card tokens, and success/failure results.
  • Real-time patching of card metadata, allowing users to update memos and spend limits without issuing new cards.
  • Comprehensive decline reason reporting to help debug payment issues within Openclaw Skills scripts.
  • Sandbox environment compatibility for safe testing of automated payment workflows without using real funds.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*