Integrate Paddle payments with subscriptions, webhooks, checkout, and tax compliance.
On first use, read setup.md for integration guidelines.
User needs to integrate Paddle for SaaS payments. Agent handles API calls, webhook verification, checkout setup, subscription management, and tax compliance configuration.
Memory lives in ~/paddle/. See memory-template.md for structure.
~/paddle/
├── memory.md # API keys, environment, product IDs
└── webhooks.md # Webhook endpoints and event handling
| Topic | File |
|---|---|
| Setup process | setup.md |
| Memory template |
memory-template.md |
| API endpoints | api.md |
| Webhook handling | webhooks.md |
https://sandbox-api.paddle.comhttps://api.paddle.com| State | Meaning | Action |
|---|---|---|
active | Paying customer | Grant access |
trialing | In trial period | Grant access, remind before end |
past_due | Payment failed | Retry period, warn user |
paused | User paused | Restrict access, allow resume |
canceled | Subscription ended | Revoke access at period end |
customer_id (ctm_xxx) — unique per customersubscription_id (sub_xxx) — unique per subscriptiontransaction_id (txn_xxx) — unique per paymentprice_id (pri_xxx) — your pricing configurationsubscription.past_due events but let Paddle retry firstsubscription.canceled from failed paymentspast_due state → User loses access during retry window, bad UX| Endpoint | Data Sent | Purpose |
|---|---|---|
| https://api.paddle.com | Customer data, subscription info | Payment processing |
| https://sandbox-api.paddle.com | Test customer data | Sandbox testing |
No other data is sent externally.
Data that leaves your machine:
Data that stays local:
This skill does NOT:
By using this skill, customer and payment data is sent to Paddle. Only install if you trust Paddle with your billing data.
Install with clawhub install <slug> if user confirms:
billing — General billing patternspayments — Payment processingsubscriptions — Subscription managementclawhub star paddleclawhub sync