OpenClaw

stripe-best-practices

Best practices for building Stripe payment integrations

ifoster010 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install ifoster01/stripe-best-practices

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

Stripe Best Practices

Best practices for building Stripe payment integrations

Keywords

stripe, payment, checkout, subscription, billing

Intents

integrate payment processing
handle subscriptions
process credit cards

Constraints

Never

Charges API
Sources API
Card Element
Payment Element in card-only mode
Tokens API (unless specific need)
mixing Connect charge types
legacy Connect terms (Standard/Express/Custom)

Always

latest API/SDK version (unless specified otherwise)
advise PCI compliance proof for raw PAN handling
use controller properties for Connect (not legacy terms)

Preferences

Prefer CheckoutSessions over PaymentIntents when on-session payments
Prefer Stripe-hosted Checkout over embedded Checkout when default choice
Prefer embedded Checkout over Payment Element when more control needed
Prefer dynamic payment methods over explicit payment_method_types when using Payment Element
Prefer SetupIntents over Sources when saving payment methods
Prefer Confirmation Tokens over createPaymentMethod/createToken when inspecting card before payment
Prefer Billing APIs over raw PaymentIntents when subscriptions/recurring
Prefer direct charges over destination charges when platform wants Stripe to take risk
Prefer destination charges over direct charges when platform accepts liability

Decisions

When user wants Charges API: advise migration to CheckoutSessions or PaymentIntents
When user wants Card Element: advise migration to Payment Element
When recurring revenue / subscription / SaaS: recommend Billing APIs + Checkout frontend
When platform / marketplace / Connect: follow integration recommendations, use controller properties
When migrating PAN data from another processor: point to migration process
When render Payment Element before creating intent: use Confirmation Tokens

References

[stripe:integration-options](...

来源信息

Source: github
Repository: openclaw/skills
Path: skills/ifoster01/stripe-best-practices
Version: —
Commit: b76a63c3503d8aa0823cd21b1940e1a21f119e1e
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# Stripe Best Practices

Best practices for building Stripe payment integrations

## Keywords

stripe, payment, checkout, subscription, billing

## Intents

- integrate payment processing
- handle subscriptions
- process credit cards

## Constraints

### Never

- Charges API
- Sources API
- Card Element
- Payment Element in card-only mode
- Tokens API (unless specific need)
- mixing Connect charge types
- legacy Connect terms (Standard/Express/Custom)

### Always

- latest API/SDK version (unless specified otherwise)
- advise PCI compliance proof for raw PAN handling
- use controller properties for Connect (not legacy terms)

### Preferences

- Prefer **CheckoutSessions** over PaymentIntents when on-session payments
- Prefer **Stripe-hosted Checkout** over embedded Checkout when default choice
- Prefer **embedded Checkout** over Payment Element when more control needed
- Prefer **dynamic payment methods** over explicit payment_method_types when using Payment Element
- Prefer **SetupIntents** over Sources when saving payment methods
- Prefer **Confirmation Tokens** over createPaymentMethod/createToken when inspecting card before payment
- Prefer **Billing APIs** over raw PaymentIntents when subscriptions/recurring
- Prefer **direct charges** over destination charges when platform wants Stripe to take risk
- Prefer **destination charges** over direct charges when platform accepts liability

## Decisions

- **When** user wants Charges API: advise migration to CheckoutSessions or PaymentIntents
- **When** user wants Card Element: advise migration to Payment Element
- **When** recurring revenue / subscription / SaaS: recommend Billing APIs + Checkout frontend
- **When** platform / marketplace / Connect: follow integration recommendations, use controller properties
- **When** migrating PAN data from another processor: point to migration process
- **When** render Payment Element before creating intent: use Confirmation Tokens

## References

- [stripe:integration-options](...

搜索