2.5k
GitHub Stars
4
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill paymentsdb- _meta.json272 B
- query.sh1.1 KB
- README.md380 B
- SKILL.md19.0 KB
Overview
This skill lets you query Stripe customer and billing data that is synced into a PostgreSQL database. It exposes the Stripe schema and tables so you can ask about customers, subscriptions, invoices, charges, and related objects. Use the provided query script to run SQL directly against the synced data store.
How this skill works
All Stripe data is stored under the stripe schema in a synced Postgres database. You run SQL via the included exec script (for example: ./query.sh "SELECT now();") to inspect tables such as customers, invoices, charges, subscriptions, payment_intents, checkout_sessions, and many more. Each table retains raw JSON (jsonb) plus denormalized columns for common fields to make queries straightforward.
When to use it
- Look up customer records, emails, payment methods, or balances.
- Investigate invoices, payments, refunds, disputes, and credit notes.
- Audit subscription and checkout session activity and line items.
- Reconcile Stripe balance transactions, payouts, and fees.
- Build reports that join customers, invoices, and charges for revenue analysis.
Best practices
- Filter by created (timestamp integer) or _last_synced_at to work with recent data only.
- Use the _raw_data jsonb column when you need fields not exposed as top-level columns.
- Protect API keys and account identifiers; queries can return sensitive billing info.
- Limit result sets and add indexes on frequently queried columns (customer, id, created).
- Prefer parameterized queries in integrations to avoid injection and accidental data exposure.
Example use cases
- Find a customer's latest invoice and payment status by joining stripe.customers to stripe.invoices.
- List recent failed charges and disputes to identify potential fraud or payment issues.
- Calculate monthly recurring revenue by aggregating stripe.invoices or subscription-related charges.
- Extract checkout session line items to reconcile order details with accounting records.
- Generate payout and balance reports using stripe.balance_transactions and stripe.payouts.
FAQ
Execute the provided script, for example: ./query.sh "SELECT now();" to verify connectivity and run SQL against the Postgres database.
Where are customer emails and names stored?
Customer emails and names are available in stripe.customers.email and stripe.customers.name; full payloads are in stripe.customers._raw_data.
Can I access subscription and invoice relationships?
Yes. Invoices include subscription and customer columns, and subscriptions and checkout_sessions tables link to customer and invoice identifiers for joins.