Sigma data freshness
Learn how Sigma handles data freshness.
Sigma allows you to analyze the same underlying data that’s accessible through the Stripe API, but uses a SQL-based interface for custom queries and analysis. For Data Pipeline data freshness, see Data Pipeline data freshness.
Additionally, Sigma provides access to certain data that isn’t available through the Stripe API, such as reports.
Data freshness
Sigma makes most of your Stripe transaction data available to query within three hours. All API activity is available to query approximately three hours after it occurs. For example, data from 12:00am UTC is available by 3:00am UTC on the same day.
Query data load times
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 the relevant part of the product, the data_load_time is interpreted as 2026-09-21 00:00:00 +0000. At times, Sigma might reflect activity that is more recent than data_load_time. For example, a charge authorized just before midnight, but captured soon after, might 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:
| Date | Timeline for results |
|---|---|
| 2026-09-21 | data_load_time is interpreted as 2026-09-21 The scheduled query includes transaction data through EOD 2026-09-20 Query results are available on 2026-09-21 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:
| Date | Timeline for results |
|---|---|
| 2026-09-24 | data_load_time is interpreted as 2026-09-21 00:00:00 +0000 The scheduled query includes transaction data through EOD 2026-09-20 Query results are available on 2026-09-24 by 2am UTC |
Dataset freshness
| Dataset | Table Name | Freshness (hours) |
|---|---|---|
| billing | coupons | 3 |
| billing | coupons_currency_options | 3 |
| billing | coupons_metadata | 3 |
| billing | credit_note_discount_amounts | 3 |
| billing | credit_note_line_item_discount_amounts | 3 |
| billing | credit_note_line_item_tax_amounts | 3 |
| billing | credit_note_line_items | 3 |
| billing | credit_note_tax_amounts | 3 |
| billing | credit_notes | 3 |
| billing | credit_notes_metadata | 3 |
| billing | discounts | 3 |
| billing | invoice_custom_fields | 3 |
| billing | invoice_customer_tax_ids | 3 |
| billing | invoice_items | 3 |
| billing | invoice_items_metadata | 3 |
| billing | invoice_line_item_discount_amounts | 3 |
| billing | invoice_line_item_tax_amounts | 3 |
| billing | invoice_line_items | 3 |
| billing | invoice_payments | 3 |
| billing | invoice_shipping_cost_taxes | 3 |
| billing | invoices | 3 |
| billing | invoices_metadata | 3 |
| billing | plans | 3 |
| billing | plans_metadata | 3 |
| billing | price_tiers | 3 |
| billing | prices | 3 |
| billing | prices_currency_options | 3 |
| billing | prices_metadata | 3 |
| billing | products | 3 |
| billing | products_metadata | 3 |
| billing | promotion_codes | 3 |
| billing | quotes | 3 |
| billing | subscription_items | 3 |
| billing | subscription_items_metadata | 3 |
| billing | subscription_schedule_phase_add_invoice_items | 3 |
| billing | subscription_schedule_phase_configuration_items | 3 |
| billing | subscription_schedule_phases | 3 |
| billing | subscription_schedule_phases_metadata | 3 |
| billing | subscription_schedules | 3 |
| billing | subscription_schedules_metadata | 3 |
| billing | subscriptions | 3 |
| billing | subscriptions_metadata | 3 |
| billing | tax_rates | 3 |
| billing | tax_rates_metadata | 3 |
| billing | usage_records | 3 |
| checkout | checkout_custom_fields | 3 |
| checkout | checkout_line_items | 3 |
| checkout | checkout_sessions | 3 |
| checkout | payment_links | 3 |
| connect | accounts | 3 |
| connect | accounts_metadata | 3 |
| connect-fees | application_fee_refunds | 3 |
| connect-fees | application_fee_refunds_metadata | 3 |
| connect-fees | application_fees | 3 |
| crypto | crypto_onramp_sessions | 3 |
| customers | customer_balance_transactions | 3 |
| customers | customer_balance_transactions_metadata | 3 |
| customers | customer_cash_balance_transactions | 3 |
| customers | customer_tax_ids | 3 |
| customers | customers | 3 |
| customers | customers_metadata | 3 |
| issuing | issuing_authorizations | 3 |
| issuing | issuing_authorizations_metadata | 3 |
| issuing | issuing_cardholders | 3 |
| issuing | issuing_cardholders_metadata | 3 |
| issuing | issuing_cards | 3 |
| issuing | issuing_cards_metadata | 3 |
| issuing | issuing_disputes | 3 |
| issuing | issuing_network_tokens | 3 |
| issuing | issuing_transactions | 3 |
| issuing | issuing_transactions_metadata | 3 |
| payments | balance_transaction_fee_details | 3 |
| payments | balance_transactions | 3 |
| payments | charges | 3 |
| payments | charges_metadata | 3 |
| payments | disputes | 3 |
| payments | disputes_enhanced_eligibility | 3 |
| payments | disputes_metadata | 3 |
| payments | payment_intents | 3 |
| payments | payment_intents_metadata | 3 |
| payments | payment_method_details | 3 |
| payments | payment_methods | 3 |
| payments | payment_methods_metadata | 3 |
| payments | payment_reviews | 3 |
| payments | refunds | 3 |
| payments | refunds_metadata | 3 |
| payments | rule_decisions | 3 |
| payments | setup_attempts | 3 |
| payments | setup_intents | 3 |
| payments | setup_intents_metadata | 3 |
| payments | sources | 3 |
| payments | sources_metadata | 3 |
Data schema
You can view the complete schema, which closely follows our API conventions, in a split-view format that shows details on table relationships. It 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. Many tables correspond to specific API objects, with each column representing a reported attribute. For example, the charges table represents information about Charge objects, which appears in the Payments section of the Dashboard.
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, and Foreign key). 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. When writing queries, refer to our API reference for additional context and values.