Billing

What This Skill Does

The Billing skill provides a comprehensive framework for managing complex financial operations within your software applications. It acts as a specialized assistant for integrating payment service providers (PSPs) like Stripe and Paddle, handling the entire lifecycle of revenue collection. The skill focuses on critical financial infrastructure, including subscription management, recurring billing, invoice generation, tax compliance, and revenue recognition. By leveraging OpenClaw's Billing skill, developers can offload the complexities of idempotent webhook processing, currency normalization, and the subtle nuances of subscription state transitions.

Installation

To integrate this skill into your environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/ivangdavila/billing

Use Cases

• Subscription Engines: Designing multi-tier SaaS platforms with trial periods, grace periods, and automated renewal logic.
• Marketplace Architectures: Implementing split payments where a platform takes a percentage of a transaction between two external parties.
• Usage-Based Scaling: Creating dynamic billing models where customers are charged based on metered consumption (e.g., API hits, storage capacity).
• Regulatory Compliance: Automating tax calculation based on user geography and handling the complex state transitions of chargebacks and refund disputes.
• Revenue Operations: Setting up revenue recognition workflows to ensure financial reporting aligns with accounting standards (e.g., ASC 606).

Example Prompts

1. "I need to implement a webhook listener for Stripe that handles subscription cancellations. Ensure it manages the state transition from 'active' to 'canceled' without losing access until the period end."
2. "Help me configure my billing model for a usage-based product. I need to track consumption in my database and trigger an invoice at the end of each month based on those integer values."
3. "Our customer billing logic is failing due to race conditions where the 'invoice.paid' event arrives before the 'subscription.updated' event. How can I architect my database to ensure eventual consistency?"

Tips & Limitations

Always treat money as integers in smallest units; never use floats to avoid rounding errors. When dealing with webhooks, prioritize idempotency by storing event IDs. Do not rely on sequential execution—assume events will arrive out of order and build state machines accordingly. The billing skill is a powerful tool for financial integrity but requires strict adherence to security protocols, particularly when verifying webhook signatures to prevent unauthorized event spoofing. Remember that 'deleting' a subscription is destructive; always prefer 'canceling' unless a refund or immediate termination is explicitly required by the business logic.