stripe-payments
Add Stripe payments to a web app — Checkout Sessions, Payment Intents, subscriptions, webhooks, customer portal, and pricing pages. Covers the decision of which Stripe API to use, produces working integration code, and handles webhook verification. No MCP server needed — uses Stripe npm package directly. Triggers: 'add payments', 'stripe', 'checkout', 'subscription', 'payment form', 'pricing page', 'billing', 'accept payments', 'stripe webhook', 'customer portal'.
npx skills add jezweb/claude-skills --skill stripe-payments --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Stripe Payments Add Stripe payments to a web app. Covers the common patterns — one-time payments, subscriptions, webhooks, customer portal — with working code. No MCP server needed. ## Which Stripe API Do I Need? | You want to... | Use | Complexity | |----------------|-----|-----------| | Accept a one-time payment | Checkout Sessions | Low — Stripe hosts the payment page | | Embed a payment form in your UI | Payment Element + Payment Intents | Medium — you build the form, Stripe handles the card | | Recurring billing / subscriptions | Checkout Sessions (subscription mode) | Low-Medium | | Save a card for later | Setup Intents | Low | | Marketplace / platform payments | Stripe Connect | High | | Let customers manage billing | Customer Portal | Low — Stripe hosts it | **Default recommendation**: Start with Checkout Sessions. It's the fastest path to accepting money. You can always add embedded forms later. ## Setup ### Install ```bash npm install stripe @stripe/stripe-js ``` ### API Keys ```bash # Get keys from: https://dashboard.stripe.com/apikeys # Test keys start with sk_test_ and pk_test_ # Live keys start with sk_live_ and pk_live_ # For Cloudflare Workers — store as secrets:
- Which Stripe API Do I Need?
- Setup
- Install
- API Keys
- Server-Side Client
- One-Time Payment (Checkout Sessions)
- Create a Checkout Session (Server)
- Redirect to Checkout (Client)
- Create Products and Prices
- Subscriptions
- Check Subscription Status
- Webhooks
- Webhook Handler (Cloudflare Workers / Hono)
- Register Webhook
npm install stripe @stripe/stripe-js Get keys from: https://dashboard.stripe.com/apikeys Test keys start with sk_test_ and pk_test_ Live keys start with sk_live_ and pk_live_ For Cloudflare Workers — store as secrets: npx wrangler secret put STRIPE_SECRET_KEY npx wrangler secret put STRIPE_WEBHOOK_SECRET For local dev — .dev.vars: Via Stripe CLI (recommended for setup) stripe products create --name="Pro Plan" --description="Full access"
What does the stripe-payments skill do?
Add Stripe payments to a web app — Checkout Sessions, Payment Intents, subscriptions, webhooks, customer portal, and pricing pages. Covers the decision of which Stripe API to use, produces working integration code, and handles webhook verification. No MCP server needed — uses Stripe npm package directly. Triggers: 'add payments', 'stripe', 'checkout', 'subscription', 'payment form', 'pricing page', 'billing', 'accept payments', 'stripe webhook', 'customer portal'.
How do I install it?
Run `npx skills add jezweb/claude-skills --skill stripe-payments --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jezweb/claude-skills, a repository with 954 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.