Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
A knowledge skill that encodes Stripe's recommended integration patterns, deprecated API warnings, and decision rules for payments, subscriptions, and Connect platforms. It guides agents toward current Stripe APIs and away from legacy ones like Charges API, Card Element, and Sources API.
Encoding these rules in a skill prevents agents from defaulting to outdated Stripe APIs that Stripe itself recommends against, which can cause compliance issues and integration debt.
When to use it
- Choosing between CheckoutSessions and PaymentIntents for a new checkout flow
- Setting up recurring billing for a SaaS product
- Migrating an existing integration off the deprecated Charges API
- Building a marketplace with Connect and selecting the right charge type
- Saving a customer payment method without an immediate charge
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: I want to add subscription billing to my SaaS app
- 1Identifies recurring revenue use case and applies Billing APIs preference
- 2Recommends Stripe Billing APIs combined with Checkout frontend
- 3Advises against raw PaymentIntents for subscription management
- 4Suggests Stripe-hosted Checkout as the default frontend unless more control is needed
- 5References stripe:billing/design-integration for integration planning
A recommended integration approach using Stripe Billing APIs and Checkout, with links to relevant Stripe docs
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.