payment-integration

What This Skill Does

The Payment Integration skill is a robust toolkit designed for OpenClaw agents to architect secure, scalable, and reliable payment systems. It goes beyond simple API calls by enforcing industry-standard patterns for financial transactions. Whether you are building a SaaS subscription platform, a B2B marketplace using Stripe Connect, or a custom checkout flow, this skill ensures you handle the complexities of asynchronous events, idempotency, and data integrity.

This skill specializes in the "Dual Confirmation" pattern, ensuring that your application state remains consistent even if a user closes their browser mid-payment or if network latency affects frontend callbacks. It provides strict guidelines on how to handle Stripe Connect webhooks, particularly the nuanced difference between platform-level and connected-account events. By automating the implementation of idempotent database updates, it prevents double-processing of payments and ensures that critical operations, such as inventory allocation or digital asset delivery, only occur exactly once.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/anton-abyzov/sw-payment-integration

Use Cases

• SaaS Subscriptions: Implementing recurring billing cycles with automated trial handling and dunning management.
• Marketplace Platforms: Building multi-vendor ecosystems using Stripe Connect, including destination charges and platform fee splitting.
• E-commerce Workflows: Creating high-conversion checkout pages with support for 100% promo codes, complex taxes, and guest checkout scenarios.
• Async Event Handling: Setting up resilient webhook listeners that correctly distinguish between standard platform events and account-specific Connect events.

Example Prompts

1. "Implement a Stripe Connect checkout flow for my marketplace that calculates a 10% platform fee and triggers an idempotent order update upon webhook receipt."
2. "How should I structure my database schema and webhook handler to correctly identify 100% discount codes without a payment intent object?"
3. "Write a secure webhook listener for Stripe in Node.js that processes subscription upgrades and handles retry logic for database record updates."

Tips & Limitations

• Security: Never log raw credit card numbers or CVCs. Always use Stripe Elements or equivalent hosted fields to maintain PCI compliance by keeping sensitive data out of your server logs.
• Idempotency: Always treat every webhook event as potentially redundant. Your database layer must perform atomic updates (e.g., UPDATE status = 'paid' WHERE status = 'pending') rather than simple overwrites.
• Edge Cases: Always define a fallback logic for failed payments or expired payment sessions. Ensure your webhook handler acknowledges receipts within the required timeframe to avoid event repetition by the payment processor.