Build Data Studio dashboards from Stripe charges
Success rates, declines and refunds by day, from the charges themselves. Stripe goes into your data warehouse first, where charges are joined to payment intents and refunds, and Data Studio charts the result.
%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
Data StudioIdAccou…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 Stripe charges do not go straight to a Data Studio dashboard
A dashboard on the Stripe account shows what Stripe counts, for the windows Stripe offers. To chart declines against attempts, and refunds against what was kept, the charges, payment intents and refunds meet in a warehouse first.
- A charge shows its outcome, not how many attempts preceded it
- The data analyst joins charges, payment intents and refunds on payment_intent
- Dashboard viewers read one definition of a successful payment
StripeCharges, outcomeData Studio
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.
- Charges and Payment intents are two of the 14 endpoints
- 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.chargesStep 2: Link Stripe charges to payment intents and refunds
In your data warehouse the model joins Charges and Refunds on payment_intent, so a decline can be read as part of an attempt, and a refund against the charge it reverses.
- Charges, payment intents and refunds join on payment_intent
- amount_refunded sits on the charge, so partial refunds show
- Store orders join on the keys your checkout carries
Step 3: Feed Data Studio dashboards with Stripe data
Add Data Studio as a destination of the Stripe Data Mart and build the on it. Fields such as created, status, amount, currency and amount_refunded come from your data warehouse.
- Outcomes by day read the Data Mart, not the Stripe API
- Turn on Available in Data Studio for the published Data Mart, then add the OWOX connector in Data Studio
Data StudioCharges
Google SheetsSame Data Mart
ClaudeSame Data MartStep 4: Use the same Stripe Data Mart in a sheet or an assistant
The Charges Data Mart is not locked to one dashboard. Open the same rows in a spreadsheet or ask about them in an AI assistant, with the same definitions.
- Support sorts failed charges by amount in a spreadsheet without a new export
- An assistant reads the same Data Mart, so status counts agree with the dashboard
Data StudioDashboardGoogle SheetsSame Data MartClaudeSame Data MartStep 5: Reuse Stripe charge outcomes
The same Data Mart works in OWOX, where your assistant for data can read it. Ask about any report, then get the result in Google Sheets or Excel in one click.
- Ask on which day declines peaked, then export the answer
- paid is defined once and every report reads it
Google SheetsOpen
ExcelOpen
- 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 Data Studio
A dashboard on the Stripe account shows what Stripe reports. OWOX loads the charges into your data warehouse so Data Studio can set them beside attempts, refunds and orders.
- You own the data. Stripe lands in your own data warehouse, in tables you control.
- Attempts beside outcomes. Charges join payment intents, so a decline is part of a story.
- Refunds in the same chart. amount_refunded and the Refunds table agree in one Data Mart.
- One place to fix. When Stripe changes its API, you publish a new connector version and charge reports keep reading the same tables.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.