Querying transactions

Use Stripe Sigma to create custom reports for charges, refunds, disputes, and more.

There are two groups of tables within Stripe Sigma’s schema that contain suitable data for reporting on your account’s balance activity. The Payment Tables section contains tables that represent funds that flow between your customers and your Stripe account, such as charges or refunds. Information about transfers of your Stripe account balance to your bank account (payouts) are listed within the Transfer Tables section.

The balance_transactions table is our recommended starting point for accounting purposes. Its biggest advantage over using separate tables (such as charges or refunds) is that it provides a ledger-style record of every type of transaction that comes into, or flows out of, your Stripe account’s balance. Use balance transactions to generate the most frequently used reports and greatly simplify how you report on financial activity. Some common types of balance transactions include:

  • charges
  • refunds
  • transfers
  • payouts
  • adjustments
  • application_fees

Each balance transaction row represents an individual Balance_transaction object that, once created, does not change. For instance, when a charge is created, a corresponding balance transaction of type charge is also created. If this charge is refunded at any time, a separate balance transaction of type refund is also created—the original balance transaction is not modified. Similarly, when a payout is sent to your bank account (represented as a transfer), a balance transaction is created.

The following example query uses this table to retrieve some information about the five most recent balance transactions.

select date_format(created, '%Y-%m-%d') as day, id, amount, currency, source_id, type from balance_transactions order by day desc limit 5
day id amount currency source_id type
2020-10-20 txn_eZptDm8H1bJh8vK -1,000 usd re_D9Whjlk09JVlg0S refund
2020-10-20 txn_W9cpG4cJcOn52dg 1,000 usd ch_Khz2GLC9cRzw9ly charge
2020-10-20 txn_Y8HQvWL7uNTbvZR 1,000 usd ch_9fazxn1akJs0Ib9 charge
2020-10-20 txn_ax7f1NUw50lxBQj 1,000 eur ch_zKSCI9foQ5zjiav charge
2020-10-20 txn_X9QJqhfW6CZqobm -1,000 usd re_cmK6QLAhFx6kY9a refund

The most common financial summaries can be calculated by joining the balance_transactions table with other tables containing the appropriate information. Some of our query templates (such as daily balance and monthly summary and balance) work by joining this table to others.

Balance transaction fee details

Fee information about each individual balance transaction is provided in the balance_transaction_fee_details table. Joining this table to balance_transactions in the manner below allows you to return fee information for each balance transaction.

The following query joins the balance_transactions and balance_transaction_fee_details tables together. Each balance transaction item returned includes the amount, fee, type of fee applied, and a description of the fee.

select date_format(date_trunc('day', balance_transactions.created), '%Y-%m-%d') as day,, balance_transactions.amount, balance_transactions.fee, balance_transaction_fee_details.type from balance_transactions inner join balance_transaction_fee_details on order by day desc limit 5
day id amount fee type
2020-10-20 txn_I7Xd6L4QeyCUOvO 1,000 59 stripe_fee
2020-10-20 txn_Sew1tv1NXAYrPfz 1,000 59 stripe_fee
2020-10-20 txn_4SkkbFnMmWCJUX7 1,000 59 stripe_fee
2020-10-20 txn_HgULJYS5A3jRzUN 1,000 59 stripe_fee
2020-10-20 txn_PApX9ehOyavymuq 1,000 59 stripe_fee


The charges table contains data about Charge objects. This table is best suited for queries that focus on charge-specific information rather than for accounting or reconciliatory purposes. It also supplements accounting reports with additional customer data. For example, The payment card mix template query uses the charges table to report on the different types of cards your customers have used.

You can join the charges table to a number of others to retrieve more information with your queries.

The following example uses the charges table to report on failed charges, returning the card brand as well as failure code and message.

select date_format(date_trunc('day', created), '%Y-%m-%d') as day, id, card_brand, failure_code, failure_message from charges where status = 'failed' order by day desc limit 5
day id card_brand failure_code failure_message
2020-10-20 ch_mSpF5KASn5JhRNn Visa card_declined Your card was declined.
2020-10-20 ch_gX4ewtFRGXpalYe MasterCard card_declined Your card does not support this type of purchase.
2020-10-20 ch_iwGfvXZTO1QjgB6 Visa card_declined Your card has insufficient funds.
2020-10-20 ch_GY8owduVUAe8RMg Visa card_declined Your card was declined.
2020-10-20 ch_o5aIOuEjb4yLuLA MasterCard card_declined Your card was declined.


Data about Customer objects is contained in the customers table (this is not part of the Payment Tables group). Use this table if you’re creating charges using customers (e.g., with saved payment information). It’s also useful if you’re making use of subscriptions.

The following example retrieves a list of failed charges, with the ID and email address for each customer.

select date_format(date_trunc('day', charges.created), '%Y-%m-%d') as day,,, from charges inner join customers on where charges.status = 'failed' order by day desc limit 5


Charges and refunds are separate objects within the API. When a charge is refunded, a Refund object is created. This data is available within the refunds table and provides in-depth information about refunds that have been performed. Similar to reporting on charges, a best practice is to start with information about balance transactions. If necessary, you can then gather additional details using the refunds table.

The refunds table can be joined to the balance_transactions and charges tables to further explore refund data.

The following example joins the balance_transactions and refunds tables together using the refunds.balance_transaction_id and columns. Each balance transaction item returned is a refund, displaying the associated charge ID and amount. Only balance transactions created after a certain date are returned.

select date_format(date_trunc('day', balance_transactions.created), '%Y-%m-%d') as day, balance_transactions.source_id, refunds.charge_id, balance_transactions.amount, from balance_transactions inner join refunds on where balance_transactions.type = 'refund' order by day desc limit 5
day source_id charge_id amount
2020-10-20 re_gJqoFB0p09Ijbx5 ch_aM4JpednWBVZZNN -1,000
2020-10-20 re_djBkvuPpYLJ42R2 ch_iJrY5WvkkmWB25D -1,000
2020-10-20 re_2WAlJIB7Q43nAWw ch_jxhSF7Nqjrq3Tv2 -1,000
2020-10-20 re_wH6Xk7O7Ox8DLX9 ch_j1yWrevcQFiu8g9 -1,000
2020-10-20 re_lxsbemGb2OgibZl ch_WnFscaHPugb5IOM -1,000

Partial capture refunds

If you’re using auth and capture and capturing only some of the authorized amount, this is represented by both charges and refunds. When a charge is authorized, a charge and associated balance transaction for the full amount are created. After a partial capture has been completed, the un-captured amount is released and represented by a refund with a reason field of partial_capture and an associated balance transaction.

For instance, if you authorize a $10 charge but only capture $7, a charge is first created for $10. A refund with the reason partial_capture is then created for the remaining $3.

Take this into account if your business is performing auth and capture charges and you’re creating reports to review customer refund rates. Without consideration, auth and capture can misrepresent the number of refunds on your account. Use the refund’s reason field to filter out partial capture refunds when retrieving payment information.

select, balance_transactions.amount from balance_transactions inner join refunds on where reason != 'partial_capture' limit 5


The disputes table contains data about all disputes on your account. Each row represents a Dispute object, created when a charge is disputed. Each dispute also includes any available data about any dispute evidence that may have been submitted.

The following example provides some preliminary information about the five most recent disputes that were lost. It joins the disputes and charges tables together using the disputes.charge_id and columns. Along with a dispute ID, each row contains an associated charge ID, the amount, and the outcome of the ZIP and CVC checks.

select date_format(date_trunc('day', disputes.created), '%Y-%m-%d') as day,, disputes.charge_id, disputes.amount, charges.card_address_zip_check as zip, charges.card_cvc_check as cvc from disputes inner join charges on where disputes.status = 'lost' and disputes.reason = 'fraudulent' order by day desc limit 5
day id charge_id amount zip cvc
2020-10-20 dp_bRgxm4LMjOWPyBs ch_71Lku57rrHHYgoJ 1,000 pass
2020-10-20 dp_29yVJxkmFGbvwkM ch_jE16g44cNzGyZLf 1,000 pass fail
2020-10-20 dp_Ox3Qh4gb7f64JDp ch_WlB2jCHmkpCLE5L 1,000 fail fail
2020-10-20 dp_Q9m5ajuZkv4bP8c ch_e6Pm1iULC0wf5dK 1,000 pass
2020-10-20 dp_kHMUvQGLbKksXXD ch_sDdA6HpqT5NiH4N 1,000 pass

Using Stripe Sigma to create reports about your disputes can help you identify fraudulent payments, which can be prevented using Stripe Radar.

Transfers and payouts

The transfers table contains data about payouts made from your Stripe balance to your bank account. You can use this table to reconcile each payout with the specific charges, refunds, and adjustments that it’s made up of, as long as you’re using automatic payouts.

For Connect platforms, this table also includes data about transfers of funds to connected Stripe accounts.

If you are performing payouts manually, the amount in each payout to your bank account is arbitrary. As such, it cannot be reconciled to specific balance transactions and only reflects the amount you requested to pay out to your bank account.

The following example joins the balance_transactions and transfers tables together. It returns a list of charges and refunds, the payout they relate to, and the date that the payout was scheduled to arrive into your bank account.

select date_format(date_trunc('day', balance_transactions.created), '%Y-%m-%d') as bt_created, balance_transactions.source_id, balance_transactions.type, as net_amount, balance_transactions.automatic_transfer_id as transfer_id, date_format(date_trunc('day',, '%Y-%m-%d') as transfer_date from balance_transactions inner join transfers on where balance_transactions.type = 'charge' and balance_transactions.type != 'refund' order by bt_created desc limit 5
day source_id type net_amount transfer_id transfer_date
2017-05-22 ch_6fpboNiTBTothxR charge 941 po_Az1rKq6Vt9z9kCZ 2017-05-24
2017-05-22 ch_TWAacHwNL2UYfis charge 941 po_3oRuKKGY9VSYcaa 2017-05-24
2017-05-21 ch_26zv7unkvcn0Ev9 charge 941 po_uDJssk8QHeWQREv 2017-05-23
2017-05-21 ch_w96tD5lDj8SHVRi charge 941 po_Ro5UQQTAPgYTbqM 2017-05-23
2017-05-21 ch_URd9sHp8Tq0oplV charge 941 po_SsuW8Dj2x5Hwa3j 2017-05-23

Transfer reversals

A payout (or transfer to a connected Stripe account) that has been created manually can be reversed if it has not yet been paid out, with any funds returned to your account’s available balance. These are represented as Transfer_reversal objects and reside in the transfer_reversals table.

Transfer reversals only apply to payouts and transfers that have been created manually—automatic payouts cannot be reversed.

Was this page helpful?
Questions? Contact us.
Developer tutorials on YouTube.