Export guide · Checked against Stripe documentation 2026-11-17
How to export all your data from Stripe
Stripe data comes out through the Dashboard and through its data products. Team members export payments from the Transactions page and customers from the Customers page as CSV, and download financial reports such as the Balance summary as CSV. Sigma returns SQL query results as CSV, and Data Pipeline sends Parquet files to your own cloud storage.
Who can export from Stripe
The Dashboard exports are run by a team member signed in to the Stripe account. The Stripe support articles on exporting payments and customers do not name the role required, so check the role of the person you plan to ask. For Sigma, Stripe is specific: anyone on the account with permission to view reports can use the Sigma query editor.
Sigma and Data Pipeline are separate products from the basic Dashboard. At the time of checking, Stripe describes Sigma as free in sandboxes and offered on a paid plan for live data, and it has a Queries API in public preview that does not require a Sigma subscription. Data Pipeline is configured from the Dashboard settings and writes to storage that your company owns.
One export is not self-service. A customer export that includes payment method details is handled by Stripe's data migration team. The Dashboard export covers customer data without those details.
How to export, step by step
Route 1 of 5
Export payments from the Transactions page
Team member with Dashboard access to payments
- 01Open the Transactions page in the Stripe Dashboard.
- 02Filter by date range, payment method and payment type, such as successful, refunded, uncaptured or all payments.
- 03Click Export.
- 04Choose your settings and the columns to include.
- 05Save the CSV file that downloads to your device.
Stripe points finance teams to the Balance summary report for reconciliation, and to the Fees report for a list of all fees incurred.
Route 2 of 5
Export customers from the Customers page
Team member with Dashboard access to customers
- 01Open the Customers page in the Stripe Dashboard.
- 02Use the Filter button to narrow the customer list if needed.
- 03Click the export button in the upper-right corner.
- 04In the pop-up, choose the time zone, the date range and the columns to include.
- 05Run the export.
Route 3 of 5
Download the Balance summary report as CSV
Team member who can view financial reports
- 01In the Dashboard, go to the Reports page and open the Balance summary report.
- 02Set the date range, currency and time zone with the report controls.
- 03In the Balance change from activity section, click Export in the upper-right corner.
- 04Select CSV, choose the itemized format and pick the columns you want.
- 05Repeat from the Payouts section to download the list of individual payouts.
To get the same file on a schedule, open the report, click Schedule, choose daily, weekly or monthly with the columns and currency, and download each run when the email notification arrives. The same reports are available through the Reports API under types such as balance_change_from_activity.itemized.7 and payouts.itemized.5.
Route 4 of 5
Query everything with Sigma
Anyone on the account with permission to view reports, where Sigma is active
- 01Open the Sigma query editor in the Dashboard.
- 02Write a query in standard ANSI SQL, or load a saved query or a Stripe template.
- 03Click Run.
- 04Click Download CSV.
Queries can be scheduled daily, weekly or monthly, with results sent by email or as a webhook event. Sigma data is read-only.
Route 5 of 5
Sync full tables with Data Pipeline
Account with Data Pipeline and access to the destination storage
- 01Open Data Pipeline in the Dashboard settings.
- 02Choose a destination: Snowflake, Amazon Redshift, Databricks, BigQuery, Amazon S3, Google Cloud Storage or Azure Blob Storage.
- 03Complete Stripe's setup guide for that destination.
- 04Before reading a load, confirm the SUCCESS file for that run date exists.
After the initial load, Stripe delivers a new full load of your data on a regular basis, so this is a standing feed and not a one-time download.
What comes out
Dashboard exports are CSV files with the columns you ticked. The itemized Balance change from activity report has one row per balance transaction. Its default columns are balance_transaction_id, created, available_on, currency, gross, fee, net, reporting_category and description. Optional columns add customer_id, customer_email, customer_name, card and customer address fields, shipping address fields, charge_id, payment_intent_id, invoice_id, subscription_id and metadata keys. Those ID columns are how rows link back to charges, customers, invoices and subscriptions.
Sigma results are a table of whatever your SQL selects, downloaded as CSV. Tables join on primary and foreign keys: the charge_id column of the disputes table, for instance, joins to the id column of the charges table. One trap: Sigma expresses amounts in the lowest currency unit, such as cents, while the financial reports express gross, fee and net in major units, such as dollars.
Data Pipeline to cloud storage delivers Parquet files. Live data sits in a livemode directory and sandbox data in a testmode directory. Tables are grouped by dataset, for example charges, payment_intents, refunds, disputes and balance_transactions under payments, customers under customers, and invoices and subscriptions under billing. Stripe writes a SUCCESS file per run date, such as coreapi_SUCCESS, and updates data_load_times.json with the time and location of the latest load for each table.
| In the export | What it contains |
|---|---|
| Payments CSV | The filtered payments from the Transactions page with the columns you selected. |
| Customers CSV | Customer records without payment method details, for the date range and columns chosen. |
| Balance change from activity, itemized CSV | One row per balance transaction with gross, fee, net, reporting category and optional customer and card columns. |
| Payouts, itemized CSV | One row per payout with payout_id, effective date, expected arrival date, status, gross, fee and net. |
| Sigma query CSV | All rows returned by a SQL query. |
| Data Pipeline Parquet tables | Full tables such as charges, customers, invoices and balance_transactions, refreshed on a schedule. |
| coreapi_SUCCESS and data_load_times.json | Markers that a load finished and when each table was last loaded. |
Before you rely on it
Limits and gotchas.
- An itemized PDF of the Balance summary holds only the first 5,000 itemized rows. Export CSV to get every row. PDF export is not available for Stripe accounts based in India.
- A report CSV contains data only from the section where you started the export, so the summary, activity and payouts sections are three separate downloads.
- Dashboard financial reports include only complete days. A day's data is normally available by 12:00 pm the following day in the report's time zone.
- The Balance summary report does not associate payouts with the payments inside them. Stripe directs you to the Payout reconciliation report for that.
- The Sigma results table shows at most 1,000 rows on screen. The downloaded CSV includes all of them.
- Sigma templates filter by UTC and do not include metadata, while Dashboard reports default to the account's local time zone and can include it. The same date range can therefore return different rows.
- Data Pipeline is not instant. Stripe states a 12-hour freshness target with a 6-hour refresh for API-backed tables, and 28 to over 100 hours for derived analytical tables.
Handle with care
Personal data inside a Stripe export.
- These exports hold customer and payment-related personal data, and should be handled as such.
- Customer names and email addresses.
- Card billing address, customer address and shipping address, down to street line and postal code.
- Card brand, card country, funding type and payment method type for each payment.
- Customer description and transaction description fields, which Stripe notes are often used to store a name.
- Custom metadata your own systems attached to payments, refunds and transfers, which can contain anything.
- Connected account names and IDs for platforms, and payout destination IDs and bank statement descriptors.
An export is a copy outside the access controls of Stripe. Store it encrypted, limit who can open it and delete working copies when you are done. The personal data scrubber removes common identifiers in your browser before a file is shared.
What the export can be worth
Outrich Data is a direct buyer of de-identified company data for AI training, from companies with 50 or more employees. We never connect to your Stripe account: your team runs the export above and removes what is out of scope. Not every export qualifies, and a rights review comes before any offer.
Questions
Exporting from Stripe: common questions.
How do I export all Stripe payments to CSV?
Can I export Stripe customers with their card details?
Why do amounts in Sigma not match my Stripe report?
Do I need Sigma or Data Pipeline to get my data out?
Sources
- Stripe Support: Exporting Payment data2026-11-17
- Stripe Support: Export customer data without the payment details2026-11-17
- Stripe Docs: Balance summary report2026-11-17
- Stripe Docs: How report configuration works2026-11-17
- Stripe Docs: How the Reports API works2026-11-17
- Stripe Docs: How Sigma works2026-11-17
- Stripe Docs: Write queries2026-11-17
- Stripe Docs: Stripe data2026-11-17
- Stripe Docs: Data Pipeline2026-11-17
- Stripe Docs: Export data to cloud storage2026-11-17
- Stripe Docs: Cloud storage file organization2026-11-17
Steps were checked against Stripe documentation on 2026-11-17. Vendors change menus, plans and limits, so confirm against the linked pages. Stripe is a trademark of its owner. Outrich Data is not affiliated with Stripe.
Find out if your data qualifies.
Eleven questions, about five minutes, no call required. You get an answer on screen and a written follow-up.