checkout-implementation
Implements Stripe payment flows -- Checkout Sessions, Payment Element, subscription signup, and customer reuse. Use when the user wants to "add checkout", "build a payment flow", "integrate Stripe payments", "add a paywall", or "subscription signup". For conversion analysis, see checkout-conversion.
来源信息
- 仓库
- appeeky/stripe-skills
- 最近来源活动
- 2026年7月19日 10:10
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 5
- 分支
- 1
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- checkout-implementation
- description
- Implements Stripe payment flows -- Checkout Sessions, Payment Element, subscription signup, and customer reuse. Use when the user wants to "add checkout", "build a payment flow", "integrate Stripe payments", "add a paywall", or "subscription signup". For conversion analysis, see checkout-conversion.
- metadata
- {"version":"1.0.0"}
# Checkout Implementation
Builds Stripe payment flows matched to the project stack.
## Choose the approach
| Need | Use |
|------|-----|
| Fastest, hosted | Stripe Checkout (`checkout.sessions.create`) |
| Embedded, custom UI | Payment Element + PaymentIntent/SetupIntent |
| Recurring | subscription mode |
## Checkout Session essentials
- mode: subscription
- line_items: price + quantity
- customer OR customer_email (reuse existing customer to avoid dupes)
- success_url / cancel_url
- allow_promotion_codes: true
- subscription_data metadata: user_id
- automatic_tax enabled (if using Stripe Tax)
## Critical rules
- **Reuse customer**: check for existing `stripe_customer_id`; for plan changes use `subscriptions.update` (proration), never a 2nd subscription
- Pass `user_id` in metadata for webhook provisioning
- Server-side price validation (whitelist price IDs)
## Verify
`stripe_implementation_planner` (MCP) for architecture; test with test cards; confirm via `webhook-implementation`.
在 GitHub 查看