privacy-cards

What This Skill Does

The privacy-cards skill enables your OpenClaw agent to programmatically create and manage virtual credit cards via the Privacy.com API. It provides a secure interface to generate virtual card numbers (VCNs) for online transactions, offering enhanced security by masking your real financial information. Users can issue single-use cards for one-time purchases, merchant-locked cards to prevent unauthorized re-billing, or standard unlocked cards. Beyond creation, the skill provides granular control over card lifecycle management, including setting spending limits, pausing active cards, or closing them entirely. The skill also facilitates detailed financial oversight by allowing the agent to query transaction history, filter results by status or date range, and audit spending patterns directly from the command line or agent interface.

Installation

To install this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/johnielee/privacy-cards

Ensure you have a registered Privacy.com account and have obtained your API key from their support team. Once you have the key, configure your environment by adding export PRIVACY_API_KEY="your-api-key" to your .bashrc or .zshrc file.

Use Cases

• Subscription Management: Generate merchant-locked cards for specific subscriptions to ensure a service can only charge exactly what you authorized.
• One-time Purchases: Use single-use cards for untrusted merchants to prevent potential data breaches from exposing your primary funding source.
• Budgeting: Implement strict monthly spending limits on virtual cards to prevent overspending on specific categories.
• Transaction Auditing: Quickly search through transaction logs to reconcile statements or investigate declined charges.

Example Prompts

1. "Create a new single-use card with a $50 limit for my purchase at store.example.com and tell me the card number."
2. "Pause my current 'Streaming Services' card until I decide to resume it."
3. "Show me all declined transactions from the past month for my primary shopping card."

Tips & Limitations

• Security: Always use the sandbox environment (https://sandbox.privacy.com/v1) for testing your logic before executing real transactions.
• Enterprise Requirements: Note that sensitive card details (PAN, CVV) are only returned in production for accounts with specific enterprise-level access; otherwise, rely on card tokens for management.
• API Limits: Keep in mind that the Privacy.com API has rate limits; verify your account tier if you plan on automating high-frequency card generation.