Stripe Best Practices

Best practices for building Stripe payment integrations

تثبيت
$clawhub install stripe-best-practices

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

Converted from UASP format (knowledge skill)

التفاصيل

الإصدار
v1.0.0
التنزيلات
1,253
ClawHub
عرض على ClawHub

Skills شائعة

Slack
Use when you need to control Slack from Clawdbot via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.
Feishu Bridge
Connect a Feishu (Lark) bot to Clawdbot via WebSocket long-connection. No public server, domain, or ngrok required. Use when setting up Feishu/Lark as a messaging channel, troubleshooting the Feishu bridge, or managing the bridge service (start/stop/logs). Covers bot creation on Feishu Open Platform, credential setup, bridge startup, macOS launchd auto-restart, and group chat behavior tuning.
YouTube
YouTube Data API integration with managed OAuth. Search videos, manage playlists, access channel data, and interact with comments. Use this skill when users want to interact with YouTube. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).