Card Management

What This Skill Does

The Card Management skill is a powerful extension for the OpenClaw AI agent, enabling secure interaction with MasterPay Global virtual payment systems. This tool provides a comprehensive suite of functionalities to create, monitor, and manage virtual cards directly within your workflow. Whether you need to generate a single-use virtual card for a one-time subscription or a multi-use card for recurring vendor payments, this skill handles the lifecycle management from creation to secure cancellation. By integrating these API endpoints, users can list wallets, check balances, retrieve sensitive card details (CVV, full number) via secure transaction PIN verification, and implement card-level security controls like locking or unlocking cards to mitigate fraudulent risk.

Installation

To install this skill, use the following command in your OpenClaw terminal: clawhub install openclaw/skills/skills/d9m1n1c/aiotnetwork-card-management

The skill is sourced from the openclaw/skills repository. Once installed, ensure you have configured your environment by setting the AIOT_API_BASE_URL if you are targeting a specific development environment. If unset, it defaults to the secure production-ready staging environment at https://payment-api-dev.aiotnetwork.io.

Use Cases

• Security-First Transactions: Generate unique single-use virtual cards for high-risk online purchases to prevent credential theft.
• Vendor Management: Create distinct multi-use cards for different service providers to track spending and manage recurring subscriptions efficiently.
• Emergency Control: Instantly lock or cancel a virtual card if suspicious activity is detected, providing an immediate layer of defense without needing to access a web dashboard.
• Automated Reconciliation: Programmatically list cards by wallet to audit spending across various projects or departments.

Example Prompts

1. "OpenClaw, check my current wallet balances and tell me which wallet has the most funds available."
2. "Create a single-use virtual card for $50.00 from my primary wallet to pay for a subscription."
3. "I suspect unauthorized activity on my last generated card. Please lock the card with UUID ending in 45a1 immediately."

Tips & Limitations

• Authentication is mandatory: Every tool call requires a valid authentication token. Ensure your session is active before running commands.
• Secure Data Handling: Methods like get_card_details that return unmasked numbers and CVVs require a transaction PIN. Handle this sensitive information with care and never store it in insecure logs.
• Pre-check required: Always execute list_card_wallets before attempting card creation to ensure you are targeting the correct wallet UUID.
• Locking vs. Canceling: Use lock_card for temporary pauses and cancel_card for permanent suspension, as canceled cards cannot be reactivated.