Ask Claude about Stripe disputes
Load Stripe into your data warehouse first, tie every dispute to its charge and any refund, then ask Claude where chargebacks come from. Claude reads a Data Mart you published through OWOX, not the Stripe account.
%20scale(1.25)%22%20fill%3D%22%23fff%22%20d%3D%22M13.976%209.15c-2.172-.806-3.356-1.426-3.356-2.409%200-.831.683-1.305%201.901-1.305%202.227%200%204.515.858%206.09%201.631l.89-5.494C18.252.975%2015.697%200%2012.165%200%209.667%200%207.589.654%206.104%201.872%204.56%203.147%203.757%204.992%203.757%207.218c0%204.039%202.467%205.76%206.476%207.219%202.585.92%203.445%201.574%203.445%202.583%200%20.98-.84%201.545-2.354%201.545-1.875%200-4.965-.921-6.99-2.109l-.9%205.555C5.175%2022.99%208.385%2024%2011.714%2024c2.641%200%204.843-.624%206.328-1.813%201.664-1.305%202.525-3.236%202.525-5.732%200-4.128-2.524-5.851-6.594-7.305h.003z%22%2F%3E%0A%3C%2Fsvg%3E%0A)
StripeConnectedBalance transact…ChargesCustomersDisputes
ClaudeIdAccou…Livem…Daily 09:00Stripe Endpoints
14 Stripe endpoints you can import. Each lands in its own table in your data warehouse.
Balance transactions
Every movement of money through the Stripe balance: charges, refunds, disputes, fees, payouts, adjustments.
16 fieldsTime seriesCharges
One row per charge attempt: amount, outcome, card details, who paid and which invoice or payment intent it belongs to.
33 fieldsTime seriesCustomers
Every customer object: identity, billing country, delinquency and balance.
17 fieldsDisputes
One row per dispute (chargeback) with its status and evidence deadline.
14 fieldsTime seriesEvents
The audit trail: every change Stripe recorded (invoice.paid, customer.subscription.updated, charge.refunded, …) with the id of the object it concerns.
11 fieldsTime seriesInvoice line items
Every line on every invoice: what was billed, for which price and product, for which period.
19 fieldsInvoices
One row per invoice with amounts, status and period.
31 fieldsTime seriesPayment intents
One row per payment attempt lifecycle: how much was asked for, how much was received, and where it stands.
22 fieldsTime seriesPayouts
One row per transfer from the Stripe balance to the bank account: amount, arrival date, status.
18 fieldsTime seriesPrices
Every price (plan) of every product, active or not, with amount, currency and billing interval.
17 fieldsProducts
The catalogue: every product, active or not.
13 fieldsRefunds
One row per refund: how much was returned on which charge, why, and the balance transaction that reversed the money.
13 fieldsTime seriesSubscription items
The lines of every subscription: which price, how many units.
14 fieldsSubscriptions
One row per subscription in any status (status=all), full refresh every run so cancellations and past-due states are current.
23 fields
Why Claude needs your data warehouse, not the Stripe account
A dispute record names a reason and a deadline. Whether the money was already refunded, and what else that customer bought, sits in other tables, and those are joined in a warehouse by the data analyst before Claude is asked anything.
- A dispute shows a reason and a due date, not the customer's history
- evidence_due_by only helps when the open disputes are listed first
- Claude answers from a published Data Mart, so two askers get the same number
StripeDisputes, reasonsClaude
Data warehouseJoined by idStep 1: Load Stripe into your data warehouse first
Create a Data Mart with Stripe as the source and choose where the data lands. The Stripe connector is a custom connector built in OWOX Data Marts, and the data goes into any popular data warehouse.
- Disputes is one of 14 endpoints; each dispute names its charge
- Authorize with a restricted Stripe API key that has read access
- Open the Stripe connector for your data warehouse below
StripeData MartGoogle BigQuery
AWS Athena
Snowflake
AWS Redshift
Databricksstripe.disputesStep 2: Link Stripe disputes to charges and refunds
In your data warehouse the model joins Disputes and Refunds on charge, so a dispute can be read against the charge it contests and any refund already paid.
- Disputes, charges and refunds join on charge
- A refunded charge is visible before it is fought
- amount means the same in every report
Step 3: Connect Claude to your Stripe data through OWOX
In Claude, open Settings, then Connectors, and add OWOX. Claude then sees the Data Marts you published, and only those.
- Claude sees only the Data Marts you published
- The Data Mart you published is the one it reads
ClaudeConnectorsOWOX MCPAddConnectedStep 4: Ask Claude about where chargebacks come from
Ask in plain words, for example which dispute reason costs the most. Claude finds the Data Mart that answers it, runs the query and answers from your data warehouse.
- The answer reads Disputes in your data warehouse, not the Stripe API
- Disputes can be read next to the charges and refunds
ClaudeShow amount by reasonget_relevant_data_marts_by_promptquery_data_martreasonamountstatusStep 5: Reuse Stripe dispute answers as files
Optional: in one click, export the answer or its source data to Google Sheets, CSV or XLS to check it or share it.
- The export carries the same numbers as the answer
- Share it with a colleague who does not use Claude
Google SheetsCSVXLSOne click
- 0.41.0Dates from Google Sheets arrive as dates, not text
- 0.41.0Rotating a connector key is one change: Sources share reusable Credentials
- 0.40.0Connecting a plan from Google Sheets takes fewer guesses
- 0.39.0Reload a year of history in one backfill, not twelve
- 0.39.0Long Facebook Ads imports no longer fail on a corrupted response
Why OWOX for Stripe in Claude
Pointing Claude at the Stripe API returns disputes without the charge and refund around them. OWOX gives it the full picture around each one, defined once.
- Disputes with context. Each dispute joins its charge and any refund, so a reason can be weighed.
- You own the data. Stripe lands in your own data warehouse, in tables you control.
- Answers you can trace. You can see which Data Mart an answer came from, and one click exports its source data.
- Versioned, with rollback. The manifest is open in the connector builder, and every change is a saved version you can roll back.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.