A transaction details report is a structured record of payments a business has processed over a given period. Each line represents a single transaction and captures its larger lifecycle: the amount charged, the payment method used, the fees deducted, the settlement date, and the final status. Unlike a bank statement, which just shows what landed in your account, a transaction details report shows you how it got there.
Below, we cover what these reports contain, how businesses can acquire them, and how finance, customer support, and operations teams use them day to day.
Key takeaways
A transaction details report captures the broader lifecycle of each payment, from authorisation through settlement, including fees, refunds, and dispute activity.
Finance teams use these reports for reconciliation, while support and operations teams can use them to investigate individual payment issues.
Businesses can access transaction details through dashboard exports, scheduled reports, direct application programming interface (API) calls, or integrations with accounting software.
What is a transaction details report?
A transaction details report is a comprehensive record of every payment your business has processed over a given period. Each line represents a single transaction and captures its lifecycle, so you can see everything from the payment method used to the date the transaction actually settled. They’re often used for reconciliation and monitoring transaction statuses (i.e., successful, declined, pending) to evaluate daily sales performance.
What does a transaction details report include?
A transaction details report is only as useful as the fields it contains. While the format varies, here are some things you can typically expect to see:
Transaction ID: A unique identifier for each payment, used to look up and cross-reference the record across systems.
Date and time: Recorded at both authorisation and settlement, which often fall on different days.
Amount and currency: The gross amount charged to the customer, plus the currency if you're operating across multiple markets.
Payment method: The method the customer uses (e.g., credit card, digital wallet, bank transfer).
Card details: The card brand (e.g., Visa, Mastercard), last four digits, and funding type (credit or debit), where available.
Status: Where the payment sits in its lifecycle (i.e., authorised, captured, settled, refunded, or disputed).
Fee breakdown: The processing fee deducted per transaction, sometimes split into interchange and markup components.
Net amount: What actually lands in your account after fees are deducted.
Authorisation code: The code the payment network issues, confirming the transaction was approved.
Customer information: Name, email, billing address, or all three, depending on what was collected at checkout.
Dispute and refund flags: Whether a chargeback was filed or a refund was issued against the transaction.
Metadata: Custom fields you've attached (order IDs, customer segments, location codes) that tie payment records to your internal systems.
Why do businesses rely on transaction details reports?
Finance, support, and operations teams all use transaction details reports in different ways.
Finance teams use them to reconcile bank deposits against expected settlement amounts, verify that fees were calculated correctly, and produce accurate revenue records for monthly close.
Customer support teams use them to investigate individual payments without escalating to finance. When a customer contacts you about a charge they don't recognise or a refund they haven't received, the transaction record usually has the answer.
Operations and fraud teams work with transaction data in aggregate. They might filter for an increase in declines on a specific card type or an uptick in disputes from a particular sales channel. That data can surface a processing issue or a fraud pattern before it compounds, and it only becomes visible when you're looking at the transaction level.
How does a transaction details report support reconciliation?
Reconciliation is the process of confirming that your internal records match what actually moved between accounts. Transaction details reports are a primary source for that work.
The reconciliation workflow often runs like this:
Pull your transaction details report for the period, filtered by settlement date.
Sum the net amounts (gross minus fees) for all transactions in that period.
Compare that total against the actual deposit in your bank statement.
Investigate any gap. Common causes include transactions that settled in a different period, refunds that offset the deposit, or disputes that placed a hold on funds.
Flag and resolve discrepancies before closing the books.
Refunds can complicate this process. A refund issued in the current period against a transaction from a previous period appears as a negative line item in your current report. If your reconciliation process doesn't account for that, you'll show a shortfall against the original transaction and an unexplained credit in the current period. Reports that link refunds to the original transaction ID via a reference field make this simple to directly trace.
How does a transaction details report surface disputes, refunds, and failed payments?
Disputes, refunds, and declines are distinct failure modes, and they appear differently in transaction details reports.
Disputes
Disputes appear as a status change on a previously settled transaction. The original charge shows as disputed, and there will typically be a separate line item for the dispute fee and any associated hold on funds. Filtering for disputed status gives you a snapshot of open chargeback exposure, including the total dollar amount, the number of affected transactions, and how long each has been open.
Refunds
Refunds might appear as negative transactions linked to the original charge via transaction ID. A refund rate climbing on a specific product, channel, or time period is often visible in the data before it shows up anywhere else. If 4% of transactions in a given week are being refunded against a 1.5% rate for a prior week, that's worth investigating at the transaction level: which products, which customers, and which payment methods.
Declines
Declines are transactions that didn't complete. They don't represent lost revenue directly, but they do represent lost conversion. Decline data should include the reason code, which tells you whether the transaction was rejected for insufficient funds, suspected fraud, or an expired card. Segmenting declines by reason code helps you distinguish customer-level issues (such as a customer entering the wrong payment details) from systemic ones (such as a card type with a consistently high decline rate on your account).
How do businesses generate and export transaction details reports?
Many payments providers make transaction reports available through a dashboard user interface (UI), an API, or both. The right method depends on your volume and what you're doing with the data.
Dashboard exports: This is an accessible option because you can set a date range, apply filters for payment status, method, or currency, and export to CSV or PDF. This works well for ad hoc investigation and manual reconciliation, but it's a manual process, which makes it impractical at high volume.
Scheduled reports: Many providers let you configure automated exports on a daily, weekly, or monthly cadence, delivered to a designated email address or dropped into a cloud storage bucket. Finance teams that close the books monthly often set up a scheduled settlement report that runs automatically on the first of each month.
API access: This is a flexible option because you can pull transaction data programmatically, filter by any available parameter, and send it directly into your accounting software, data warehouse, or internal reporting tools. This is the standard approach for businesses running a large volume of transactions every day, where manual exports aren't realistic.
Accounting integrations: Many major platforms have native connectors or third-party integrations that automatically pull transaction data from your payments provider. Fees, net amounts, and refunds get categorised into the right accounts without manual data entry.
Stripe makes it easy for businesses to generate, analyse, and export detailed transaction reports through the Stripe Dashboard. The Reports API enables automated retrieval of transaction data and custom report generation for programmatic access. You get intuitive, real-time reporting with granular visibility into payments across different payment methods, currencies, and geographies.
Businesses with advanced analytics needs can use Stripe Sigma to run custom Structured Query Language (SQL) queries directly against Stripe data. You can unlock deeper insights and tailored reporting across payments, customers, payouts, and global operations.
How Stripe Payments can help
Stripe Payments provides a unified, global payments solution that helps any business – from scaling startups to global enterprises – accept payments online, in person and around the world.
Stripe Payments can help you:
Optimise your checkout experience: Create a frictionless customer experience and save thousands of engineering hours with prebuilt payment UIs, access to 125+ payment methods and Link, a wallet built by Stripe.
Expand to new markets faster: Reach customers worldwide and reduce the complexity and cost of multicurrency management with cross-border payment options, available in 195 countries across 135+ currencies.
Unify payments in person and online: Build a unified commerce experience across online and in-person channels to personalise interactions, reward loyalty and grow revenue.
Improve payments performance: Increase revenue with a range of customisable, easy-to-configure payment tools, including no-code fraud protection and advanced capabilities to improve authorisation rates.
Move faster with a flexible, reliable platform for growth: Build on a platform designed to scale with you, with 99.999% historical uptime and industry-leading reliability.
Learn more about how Stripe Payments can power your online and in-person payments or get started today.
The content in this article is for general information and education purposes only and should not be construed as legal or tax advice. Stripe does not warrant or guarantee the accuracy, completeness, adequacy, or currency of the information in the article. You should seek the advice of a competent lawyer or accountant licensed to practise in your jurisdiction for advice on your particular situation.