stripe-integration

What This Skill Does

The Stripe Integration skill provides a comprehensive toolkit for managing payment lifecycles within your application using the OpenClaw AI agent. It abstracts the complexity of Stripe's API, enabling developers and business operators to implement secure, PCI-compliant payment flows ranging from simple checkout pages to complex marketplace architectures with Stripe Connect. The skill handles the critical heavy lifting of payment intent lifecycle management, webhook verification, subscription recurring billing logic, and customer data synchronization. It is specifically designed to enforce idempotent operations, ensuring that network retries or duplicate webhooks do not result in double-charging or inconsistent database states.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/anton-abyzov/sw-stripe-integration Ensure your Stripe Secret API keys and Webhook signing secrets are properly configured in your agent environment variables before executing the first transaction.

Use Cases

• SaaS Subscription Billing: Automate user upgrades, downgrades, and cancellations, ensuring billing cycles align with product changes.
• Marketplace Platforms: Utilize Stripe Connect to facilitate transactions between third-party sellers and buyers, handling destination charges and complex payout structures.
• E-commerce Checkout: Rapid deployment of Stripe-hosted Checkout sessions for rapid time-to-market, or custom UI implementations for brand-aligned checkout experiences.
• B2B Service Payments: Utilizing Setup Intents to capture customer payment methods for future invoicing or automated recurring service charges.

Example Prompts

1. "Analyze my current webhook logs and implement a verification handler for checkout.session.completed events to ensure our database reflects paid status correctly."
2. "Create a new subscription billing tier for our professional plan with a 14-day trial period and automated email follow-ups for failed payments."
3. "Set up a Destination Charge flow using Stripe Connect where the platform takes a 10% commission on every transaction processed by our sellers."

Tips & Limitations

• Security: Always rely on webhooks for the source of truth regarding payment status rather than frontend callback URLs, which are easily spoofed.
• Idempotency: Always use idempotency keys when making API requests to Stripe to prevent duplicate charges during transient network failures.
• SCA Compliance: If your users are in Europe, ensure your implementation handles Strong Customer Authentication by correctly using the Payment Intents API to trigger 3D Secure challenges when required.
• Connect Limitation: Be aware of the 'Direct Charge Webhook Gap'—ensure you are listening to the correct account endpoints depending on whether you are using Direct or Destination charges to avoid missing critical payment events.