Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
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
Here's how your AI assistant might use this skill in practice.
User asks: how do I add a $9.99 one-time purchase to my game
- 1Create a CheckoutSession on the server with mode set to 'payment'
- 2Define line_items using price_data with unit_amount in cents
- 3Set success_url and cancel_url pointing to game domain
- 4Return session.url to the client and redirect the user
- 5Verify payment via webhook signature on the server
A working Stripe-hosted checkout flow for a one-time game purchase
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.