Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
- Environment variable requirements removed; now only dependencies on curl and jq are needed. - Setup and authentication workflows updated to no longer request or require passwords or gateway keys via environment variables. - Login flow now prompts user for password only when needed—credentials are never stored after use. - Updated documentation to clarify security practices regarding password handling. - No code or logic changes were made; update is documentation/security guidance only.
What This Skill Does
PayPilot connects AI agents to a hosted payment gateway proxy at paypilot.agms.com. It handles charges, invoices, refunds, subscriptions, and fraud rules through conversation. Card numbers never touch the agent; payments route through vault tokens and hosted forms.
Card data never enters the conversation or agent memory, so merchants avoid PCI scope expansion without building their own secure payment forms.
When to use it
- Charging a client after completing a project
- Emailing a payment link to a new customer
- Issuing a partial refund on a returned order
- Setting up monthly recurring billing for a subscriber
- Reviewing 30-day fraud analytics after a spike in declined transactions
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Charge Sarah $250 for her consulting invoice
- 1Loads JWT and API URL from ~/.config/paypilot/config.json
- 2Retrieves Sarah's vault ID from the customer vault
- 3Posts a charge request to /v1/vault/charge with vault_id, amount 250.00, and description
- 4Receives transaction response with status, transaction ID, and risk score
- 5Reports confirmation to the user
Payment of $250.00 processed. Transaction ID: abc123.
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.