作者:Isaac Foster更新於 2026-05-11stripe-best-practices@clawhub_ifoster01/stripe-best-practices
電商營運#Payment
據 AlphaMoat 統計,截至 2026-09,Stripe Best Practices 累計下載 3,459 次、獲 1 個星標,在全部 5,078 個 AI 技能中排名第 3,208 位,在「商業營運」分類(297 個)中排名第 176 位。
| 平台 | 累計安裝 | 累計下載 | 星標 | 評論 |
|---|---|---|---|---|
| ClawHub ↗ | 106 | 3459 | 1 | - |
| SkillHub ↗ | 104 | 3369 | 1 | — |
各平台的計數口徑不同,統計時間不一致。
主文彙總了整合選型偏好與限制，例如按場景選擇 Checkout、PaymentIntents、Billing 或 Connect 流程，並提醒原始卡號處理涉及 PCI 合規要求。該內容屬於整合指導，不代表獲准訪問真實支付資料或修改 Stripe 帳戶。實施前應依據官方文件和當前 API 版本複核方案；涉及即時資金、卡號或帳戶變更時須另行取得相應授權。
資料釋出於 2026-10-29
以下是根據技能文件生成的示例,不代表實際執行結果。
2026-09 起統計方法調整:同名技能按作者分別統計,並覆蓋全部技能。圖中虛線為調整前的月份,與之後的資料不直接比較,也不計算跨越調整的增長。
| 月份 | 累計下載 | 環比 | 星標 |
|---|---|---|---|
| 2026-09 | 3459 | — | 1 |
| 2026-08 | 3313 | +5.9% | 1 |
| 2026-07 | 3127 | +14.0% | 1 |
| 2026-06 | 2742 | +7.3% | 1 |
| 2026-05 | 2556 | — | 1 |
| 2026-03 | 2019 | — | 1 |
以下是作者釋出的原始檔案,按純文字顯示,本站未做修改或稽核;其中的連結不可點選,命令請核實後再執行。抓取於 2026-10-23。
--- name: stripe-best-practices description: Best practices for building Stripe payment integrations metadata: version: "245b3bbb" type: knowledge format: uasp --- # 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](https://docs.stripe.com/payments/payment-methods/integration-options) - primary integration design reference - [stripe:api-tour](https://docs.stripe.com/payments-api/tour) - API overview - [stripe:go-live](https://docs.stripe.com/get-started/checklist/go-live) - pre-launch checklist - [stripe:migration/charges](https://docs.stripe.com/payments/payment-intents/migration/charges) - Charges to PaymentIntents migration - [stripe:migration/payment-element](https://docs.stripe.com/payments/payment-element/migration) - Card Element to Payment Element migration - [stripe:billing/design-integration](https://docs.stripe.com/billing/subscriptions/designing-integration) - subscription integration planning - [stripe:connect/recommendations](https://docs.stripe.com/connect/integration-recommendations) - Connect charge type selection - [stripe:pan-import](https://docs.stripe.com/get-started/data-migrations/pan-import) - PAN data migration --- *Converted from UASP format (knowledge skill)*
為 AI agent 提供電話號碼並代辦電話事務的技能。
透過 Trello REST API 管理看板、列表與卡片。
透過知了標訊介面查詢和分析招投標相關資訊。
產品經理工作臺：從需求分析到 PRD 與迭代規劃。
面向日曆管理與會議排期的技能。
提供市場趨勢、競品與使用者行為分析的市場分析服務。
按資料分析篩電商爆款，覆蓋多個平台的品類。
透過 Maton 託管 OAuth 訪問 Salesforce CRM 的技能。
資料月份:2026-09 · 下載/星標/安裝數聚合自公開技能註冊庫(ClawHub、SkillHub),按月更新。口徑說明見資料方法。