stripe-best-practicesBest practices for building Stripe payment integrations
Install via ClawdBot CLI:
clawdbot install ifoster01/stripe-best-practicesBest practices for building Stripe payment integrations
stripe, payment, checkout, subscription, billing
Converted from UASP format (knowledge skill)
Generated Mar 1, 2026
A retail business wants to implement a secure online payment system for one-time purchases. They need to handle various payment methods and ensure PCI compliance without storing raw card data. This scenario involves using Stripe-hosted Checkout for simplicity and security.
A software-as-a-service company needs to manage recurring billing for monthly or annual subscriptions. They require automated invoicing, trial periods, and handling upgrades/downgrades. This scenario recommends using Billing APIs with Checkout for frontend integration to streamline recurring payments.
A marketplace platform connecting buyers and sellers needs to process payments while managing funds distribution and compliance. This involves using Stripe Connect with controller properties to handle direct or destination charges based on risk acceptance, ensuring proper integration for multi-party transactions.
A business is transitioning from an older payment processor to Stripe and needs to migrate existing customer payment data. This scenario focuses on using PAN import tools and migrating from Charges API to PaymentIntents or CheckoutSessions, ensuring a smooth transition without disrupting service.
A company requires more control over the payment UI than Stripe-hosted Checkout offers, such as integrating payments into a custom app interface. This scenario involves using embedded Checkout or Payment Element with dynamic payment methods to provide flexibility while maintaining security and best practices.
This model involves offering software services with recurring revenue through monthly or annual subscriptions. It leverages Stripe's Billing APIs for automated payments, invoicing, and managing customer lifecycles, ensuring predictable revenue streams and scalability.
A platform that facilitates transactions between multiple buyers and sellers, taking a commission on sales. It uses Stripe Connect to handle payment routing, compliance, and fund disbursement, with revenue generated from transaction fees or percentage cuts.
Businesses selling physical or digital goods with single, non-recurring payments. This model focuses on secure checkout processes using Stripe-hosted or embedded Checkout to process payments efficiently, with revenue coming from direct sales.
💬 Integration Tip
Always use the latest Stripe API versions and prefer CheckoutSessions for on-session payments to simplify integration and enhance security. For subscriptions, leverage Billing APIs instead of raw PaymentIntents to manage recurring billing effectively.
Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.
Connect to 100+ APIs (Google Workspace, Microsoft 365, GitHub, Notion, Slack, Airtable, HubSpot, etc.) with managed OAuth. Use this skill when users want to...
Build, debug, and deploy websites using HTML, CSS, JavaScript, and modern frameworks following production best practices.
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).
Scaffold, test, document, and debug REST and GraphQL APIs. Use when the user needs to create API endpoints, write integration tests, generate OpenAPI specs, test with curl, mock APIs, or troubleshoot HTTP issues.
Search for jobs across LinkedIn, Indeed, Glassdoor, ZipRecruiter, Google Jobs, Bayt, Naukri, and BDJobs using the JobSpy MCP server.