Sign in
An image of the Stripe logo
Create account
Sign in
Home
Payments
Business operations
Financial services
Developer tools
No-code
All products
Home
Payments
Business operations
Home
Payments
Business operations
Financial services
Developer tools
Support
Overview
Fraud detection
Stripe data
    Overview
    Get started
    Access data in your Stripe Dashboard with Sigma
    Access data in your data warehouse with Data Pipeline
    Data freshness
    Query data
    Write queries
    Query transactional data
    Query Billing data
    Query Connect data
    Query Issuing data
    Schedule queries
Financial reports
Payment authentication reports
Revenue recognition
Startup incorporation
Climate
Identity
Tax
Financial Connections
Account
Dashboard
HomeBusiness operationsStripe data

Data freshness

Learn about the data freshness of Stripe data and the schema.

Sigma and Data Pipeline provide access to the Stripe data available with the Stripe API. You can also access data such as Stripe financial reports, which isn’t available in the Stripe API.

Data freshness

Sigma and Data Pipeline make most of your transaction data available to query within one day.

Sigma makes most of your Stripe transaction data available to query within one day. All API activity for a given day (from 12:00am to 11:59pm UTC) is available to query by 12:00pm UTC the following day. For example, data for the end of day Sunday UTC time is available by Monday at 12:00pm UTC. Similarly, data for the last day of the month is available one day into the following month.

Query data load times with Sigma

The interface in the Dashboard displays the date and time of the last payments data. You can use data_load_time as a value in your queries to represent when data is most recently processed on your account. For example, if payment tables were last updated on 3/31/2023, the data_load_time is interpreted as 2023-03-28 00:00:00 +0000. At times, Sigma may reflect activity that is more recent than data_load_time. For example, a charge authorized just before midnight, but captured soon after, may show as captured.

Making data available requires additional time. You can use data_load_time as a value in your queries that represents when data is most recently processed on your account. Use this value to dynamically set a date range in your scheduled queries.

For example, consider the following scheduled query that returns a list of balance transactions created one month before data_load_time.

select id, amount, fee, currency from balance_transactions -- this table is the canonical record of changes to your Stripe balance where created < data_load_time and created >= data_load_time - interval '1' month order by created desc limit 10

The following timeline illustrates how this works based on data availability.

DateTimeline for results
2023-03-28
  • data_load_time is interpreted as 2023-03-28
  • The scheduled query includes transaction data through EOD 2023-03-27
  • Query results are available on 2023-03-28 by 2pm UTC

Now, consider the following scheduled query that returns a list of charge_ids and interchange billing amounts associated with each fee balance debit created one month before data_load_time.

select ic.charge_id, ic.billing_currency, ic.billing_amount, ic.balance_transaction_id, ic.balance_transaction_created_at, from icplus_fees as ic join balance_transactions as bt on ic.balance_transaction_id = bt.id where bt.created >= data_load_time - interval '1' month and bt.created < data_load_time

If this query is scheduled to recur daily, the following timeline illustrates when you can expect the results.

DateTimeline for results
2023-03-31
  • data_load_time is interpreted as 2023-03-28 00:00:00 +0000
  • The scheduled query includes transaction data through EOD 2023-03-27
  • Query results are available on 2023-03-31 by 2am UTC

Data freshness for datasets

View the table below for information on data freshness for specific datasets.

DatasetExample tablesSigma freshnessData Pipeline freshness
Core API tables (including Connect versions)balance_transactions, charges, connected_account_balance_transactions24 hours9 hours
Daily refreshed tablesexchange_rates_from_usd, radar_rules24 hours28 hours

About the schema

Our full-page schema documentation shows the schema in a split-view format and provides more details on table linkages.

The schema follows our API conventions as closely as possible. Many of the tables correspond to specific API objects, with each column representing a specific attribute that’s reported. For instance, the charges table represents information about Charge objects, which is displayed in the Payments section of the Dashboard.

When you write queries, refer to the our API reference for additional content and values.

Sigma schema tab

The Schema tab in Sigma displays all the available data that you can use in your queries, organized by category. Each category contains a set of tables that represents the available data.

You can select a table to expand it and reveal its available columns, along with a description of the type of data it contains (for example: Boolean , Varchar, Foreign key, and so on). Hover the cursor over any column to reveal a description. Use the search field at the top of the schema to find specific tables and columns.

Was this page helpful?
Questions? Contact us.
Watch our developer tutorials.
Check out our product changelog.
Powered by Markdoc
You can unsubscribe at any time. Read our privacy policy.
On this page
Data freshness
Data freshness for datasets
About the schema
Stripe Shell
Test mode
Welcome to the Stripe Shell! Stripe Shell is a browser-based shell with the Stripe CLI pre-installed. Login to your Stripe account and press Control + Backtick on your keyboard to start managing your Stripe resources in test mode. - View supported Stripe commands: - Find webhook events: - Listen for webhook events: - Call Stripe APIs: stripe [api resource] [operation] (e.g. )
The Stripe Shell is best experienced on desktop.
$