stripe-payments
Best practices for Stripe payment integration. Use when implementing payments, subscriptions, checkout flows, or any monetization feature in games or web apps. Covers CheckoutSessions, Payment Element, subscriptions, and Connect.
Why use this skill?
Learn how to integrate secure Stripe payments, subscriptions, and checkout flows into your games and web apps using OpenClaw AI agent best practices.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/kjaylee/stripe-paymentsWhat This Skill Does
The stripe-payments skill is an essential toolkit for developers and game creators using the OpenClaw AI agent to manage monetization. It provides a standardized framework for integrating Stripe's modern payment infrastructure into your applications. This skill focuses on the latest best practices, ensuring you utilize the most secure and efficient APIs such as CheckoutSessions and Payment Elements, while strictly avoiding deprecated legacy endpoints like the Charges or Sources APIs. It helps bridge the gap between complex financial documentation and practical, clean code implementation for payment workflows, subscriptions, and platform-level marketplace architectures.
Installation
To integrate this skill into your environment, use the OpenClaw CLI tool. Run the following command in your terminal:
clawhub install openclaw/skills/skills/kjaylee/stripe-payments
Ensure you have your Stripe secret keys configured in your environment variables before invoking any payment-related functions through your AI agent.
Use Cases
This skill is designed for several key financial scenarios:
- One-time Purchases: Perfect for individual game items, level unlocks, or digital assets.
- Subscription Services: Ideal for monthly recurring membership models or SaaS-style game services, utilizing the Billing API.
- Marketplace Platforms: If your application supports multiple developers or creators, this skill guides you through the complexities of Stripe Connect and destination charges.
- Simple Monetization: Quick implementation of donation or sponsorship links using Stripe's pre-built Payment Links.
Example Prompts
- "OpenClaw, help me set up a CheckoutSession for a one-time game purchase of $9.99, using the best current practices and ensuring I handle the session URL correctly."
- "I need to implement a monthly subscription for my app. Can you generate the Node.js server-side code for a subscription CheckoutSession and explain how to verify the webhook signature?"
- "My game has a marketplace component. What are the key architectural requirements when implementing Stripe Connect to ensure the 'merchant of record' is correctly configured?"
Tips & Limitations
- Security First: Never expose your Stripe Secret Key on the client side. Always perform payment creation logic on your backend.
- Dynamic Pricing: Avoid hardcoding amounts in your frontend. Fetch pricing details from the server to prevent client-side manipulation.
- Webhooks: Always implement webhook signature verification to handle asynchronous events like payment success or subscription cancellations securely.
- Legacy Avoidance: The skill strictly advises against using the Charges or Tokens API. Always favor the PaymentIntents or SetupIntents flows for compliance and security.
- Compliance: Ensure your server is running on HTTPS and that you have completed the Stripe Go-live checklist to avoid production deployment issues.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-kjaylee-stripe-payments": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: external-api, code-execution
Related Skills
ui-ux-pro-max
UI/UX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, information architecture, visual style direction, design systems/tokens, component specs, copy/microcopy, accessibility, or to generate/critique/refine frontend UI (HTML/CSS/JS, React, Next.js, Vue, Svelte, Tailwind). Includes workflows for (1) generating new UI layouts and styling, (2) improving existing UI/UX, (3) producing design-system tokens and component guidelines, and (4) turning UX recommendations into concrete code changes.
ralph-loop
AI 자율 구현 방법론. 구현/개발/코딩 요청 시 자동 적용. 메인은 마더 서브에이전트를 spawn하고, 마더가 워커들을 관리. specs/ → IMPLEMENTATION_PLAN.md → 1태스크씩 구현 → 2단계 리뷰 → 테스트 → 반복.
game-dev-rust-godot
Game development workflow using Rust+WASM or Godot 4.x for HTML5 games. Use when creating new games, implementing game mechanics, or porting existing games. Follows TDD-based production pipeline v3.1 with asset-first approach. Covers Rust(Macroquad/Bevy), Godot HTML5 Export, asset acquisition, test case writing, and QA automation. Master directive (2026-02-06) - ONLY Rust+WASM or Godot allowed, JS/TS frameworks prohibited.
subagent-dev
Execute implementation plans using fresh subagents per task with two-stage review (spec compliance + code quality). Use when executing multi-task plans with independent work units. Enhances ralph-loop methodology.
systematic-debugging
Root-cause-first debugging methodology. Use when encountering any bug, test failure, or unexpected behavior BEFORE proposing fixes. Prevents random fix attempts that waste time and create new bugs.