stripe

What This Skill Does

The Stripe skill for OpenClaw provides a powerful interface for querying your synced Stripe billing data directly from a PostgreSQL database. Rather than relying on live API calls that can be slow or rate-limited, this skill leverages a high-performance local database sync. It exposes schemas related to accounts, active entitlements, balance transactions, and individual charges, allowing for deep financial reporting, customer subscription auditing, and real-time revenue analysis using standard SQL syntax. By utilizing the provided ./query.sh interface, you can perform complex joins, aggregations, and filtering across your financial data infrastructure.

Installation

To integrate this skill into your environment, execute the following command in your OpenClaw terminal:

clawhub install openclaw/skills/skills/ramonverse/paymentsdb

Ensure that your environment is properly connected to the target PostgreSQL instance where the Stripe schema has been provisioned.

Use Cases

This skill is ideal for financial operations, customer success teams, and technical analysis. Use it to:

• Analyze revenue streams by aggregating data from the stripe.charges table.
• Audit customer entitlements by querying stripe.active_entitlements to see which features are currently assigned.
• Track financial health by calculating net revenue from stripe.balance_transactions.
• Debug customer issues by looking up transaction statuses, refund details, and payment intent outcomes.
• Generate custom reports on business performance without needing to log into the Stripe Dashboard.

Example Prompts

1. "What is our total revenue collected from successful charges over the last 30 days?"
2. "List all active entitlements for the customer with the email address [email protected]."
3. "Show me the last 10 balance transactions, specifically highlighting any fees or net amounts that seem unusual."

Tips & Limitations

• Performance: Since this skill queries a local database, ensure your indices on the stripe schema are optimized for your most frequent query patterns to maintain sub-second response times.
• Data Freshness: Remember that this skill accesses synced data; verify the _last_synced_at column in any table to ensure your report is based on current information.
• Schema Structure: All relevant data is namespaced under the "stripe" schema. Always prefix your table references with stripe. to avoid ambiguity. If you require complex raw data analysis, utilize the JSONB operators supported by PostgreSQL to traverse the _raw_data columns effectively.