Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Payment guard middleware for AI agents. Before any payment, it runs a preflight check against the user's policy, enforcing a master on/off switch, per-transaction limits, monthly caps, and merchant allow/block lists. Other payment-capable skills must route through it before proceeding and log payments after completion.
Centralizes payment policy enforcement so individual skills don't each need to implement their own limits, confirmation flows, or audit trails.
When to use it
- Blocking an agent from charging a card when payments are disabled
- Capping automated purchases at £20 per transaction
- Requiring explicit user confirmation before a large subscription renewal
- Tracking total monthly spend across multiple payment skills
- Auditing which skills initiated payments and why they were denied
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: 'Book a £15 subscription on shop.example.com'
- 1Call signet-preflight with amount 15, currency GBP, payee shop.example.com, purpose Subscription
- 2Receive ALLOW response confirming the payment is within policy
- 3Proceed with the payment through the payment-capable skill
- 4Call signet-record with the same parameters to log the transaction in the ledger
Subscription booked and £15 appended to the monthly ledger