By Isaac FosterUpdated 2026-05-11stripe-best-practices@clawhub_ifoster01/stripe-best-practices
E-commerce#Payment
According to AlphaMoat, as of 2026-09, Stripe Best Practices has 3,459 downloads and 1 stars — ranked #3,208 of 5,078 AI skills overall, and #176 of 297 in Business Ops.
| Platform | Installs | Downloads | Stars | Comments |
|---|---|---|---|---|
| ClawHub ↗ | 106 | 3.5K | 1 | - |
| SkillHub ↗ | 104 | 3.4K | 1 | — |
Platforms count differently and update at different times.
The primary summarizes integration preferences and constraints, such as choosing Checkout, PaymentIntents, Billing, or Connect flows for the scenario, and notes PCI obligations for raw card-number handling. This is integration guidance, not authorization to access live payment data or change a Stripe account. Verify the design against current official documentation and API versions before implementation; live payment data, card numbers, or account changes require separate authorization.
Profile published 2026-10-29
Generated from the skill’s documentation as examples; not results of actual runs.
The counting method changed in 2026-09: skills with the same name are now counted separately by author, and the full catalog is covered. Dashed lines show months before the change; they are not compared with later months, and no growth is computed across the change.
| Month | Downloads | MoM | Stars |
|---|---|---|---|
| 2026-09 | 3.5K | — | 1 |
| 2026-08 | 3.3K | +5.9% | 1 |
| 2026-07 | 3.1K | +14.0% | 1 |
| 2026-06 | 2.7K | +7.3% | 1 |
| 2026-05 | 2.6K | — | 1 |
| 2026-03 | 2.0K | — | 1 |
The author’s original file, shown as plain text without edits or review by AlphaMoat. Links are not clickable; check commands before running them. Fetched 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)*
A skill that gives an AI agent a phone number and runs phone tasks for it.
Manages Trello boards, lists, and cards through the Trello REST API.
Search and analyze tender and award information through the Zhiliaobiaoxun API.
A product manager's workbench from requirement analysis to PRD and sprint planning.
A skill for calendar management and meeting scheduling.
A market analysis service covering market trends, competitors and user behaviour.
Screens e-commerce best-sellers with data analysis across several platforms.
A skill that reaches Salesforce CRM through Maton's managed OAuth.
Data month: 2026-09 · Downloads, stars and installs are aggregated monthly from public skill registries (ClawHub, SkillHub). See methodology.