stripe-payments
by kjaylee
Web & Frontend DevelopmentBrief
Best practices for Stripe payment integration.
Description
What This Skill Does
Best practices guide for integrating Stripe payments into games and web apps. Covers CheckoutSessions, subscriptions via Billing API, embedded checkout, and multi-party payments with Connect. Includes a list of deprecated APIs to avoid.
Codifies which Stripe APIs are current versus deprecated, preventing teams from accidentally building on legacy endpoints like Charges or Sources.
When to Use It
- Adding a one-time purchase flow to a web game
- Setting up monthly subscriptions for a SaaS app
- Selling in-app items with metadata tracking
- Building a marketplace that pays out to multiple developers
- Accepting donations with Payment Links
Example Workflow
User asks: how do I add a $9.99 one-time purchase to my game
- 1
Create a CheckoutSession on the server with mode set to 'payment'
- 2
Define line_items using price_data with unit_amount in cents
- 3
Set success_url and cancel_url pointing to game domain
- 4
Return session.url to the client and redirect the user
- 5
Verify payment via webhook signature on the server
A working Stripe-hosted checkout flow for a one-time game purchase
Requirements
- Stripe account
- STRIPE_SECRET_KEY environment variable
- Stripe webhook secret for signature verification
Installation
clawhub install kjaylee/stripe-paymentsRun the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.