What Is the Failed Transactions Report?
The Failed Transactions Report lists payment transactions with a Failure status during the transaction date range you select. It brings unsuccessful payment attempts into one place, alongside the related order and customer details.
Use it to locate affected orders, understand the value of failed attempts, and find customers who may need payment assistance. Each entry concerns a failed transaction; it is not automatically a lost sale, and a later payment attempt may have succeeded.
The premade report provides a starting point for reviewing failures without manually assembling the same order and transaction columns each time.
Report Overview
- Period
- selected transaction date range.
- Data included
- order name, order date and amount, customer identity and email, transaction status and transaction amount.
- Best for
- investigating failed payment attempts and prioritizing order-specific follow-up.
- Export
- Excel, CSV, TXT or PDF.
- Frequency
- optionally schedule delivery daily, weekly or monthly.
What Can You Learn from Failed Payment Data?
1. Which orders need a closer look
Order Name connects a failed attempt to its order, while Order Amount and Transaction Amount give useful financial context.
Example: An order has a failed transaction amount of $120.
What you can do: Open the affected order and check its latest payment state before contacting the customer.
2. How large the failed attempts are
Transaction Amount helps you sort unsuccessful attempts by value. It should not be summed as confirmed lost revenue because one order may have multiple attempts.
Example: Two unsuccessful attempts appear for the same $80 order.
What you can do: Review attempts at the order level before calculating a recovery opportunity.
3. Who may need payment assistance
Customer First Name, Last Name and Email can help locate the person associated with an unsuccessful attempt when those details are present.
Example: A failed attempt is listed with a customer email address.
What you can do: Confirm whether payment is still outstanding, then send an appropriate support message.
4. When problems cluster around orders
Comparing failures across selected periods can reveal patterns worth investigating. The Order Date is contextual; the selected transaction date range determines which attempts are included.
Example: A selected transaction period returns more failures than the previous one.
What you can do: Check your payment processing logs or gateway dashboard for causes not present in the report.
What Should You Check First in This Report?
Use these checks to turn the list into a manageable review queue:
- Transaction Amount: start with higher-value failed attempts while avoiding assumptions about lost revenue.
- Order Name: group related attempts so one order is not treated as multiple lost orders.
- Customer Email: identify cases where a follow-up is possible after checking current order status.
- Order Date versus transaction period: do not interpret the order date as the failed-transaction timestamp.
When Should You Use This Report?
| When to Use It | How It Helps |
|---|---|
| Reviewing unsuccessful payments after a promotion | Find orders with failed attempts in the selected transaction window. |
| Prioritizing high-value payment follow-ups | Sort Transaction Amount to see larger failed attempts first. |
| Investigating a customer payment issue | Locate an order using its name or customer contact details. |
| Preparing a payment-exception review | Share a focused list of failed transactions with an authorized colleague. |
| Checking repeated unsuccessful attempts | Compare order names to spot multiple failures that might relate to one order. |
How to Create This Report in Data Export
Start with the premade Failed Transactions report and adapt it only where needed.
- Open Data Export and find the premade Failed Transactions report.
- Open it and review the default order, customer, status and transaction amount columns.
- Choose the transaction date range; adjust available sorting or filters if needed.
- Save the report, then export it in your preferred available format.
- Optionally schedule email delivery daily, weekly or monthly for ongoing review.
Make the Most of This Report
Four simple practices make failed-transaction reviews more reliable:
01 / DATE RANGE
Choose a clear review window. Compare like-for-like transaction periods when checking trends.
02 / ORDER CONTEXT
Check the order before outreach. A failed attempt may be followed by a successful retry.
03 / COUNTING
Avoid double-counting. Multiple failed attempts can belong to one order.
04 / SAFE SHARING
Limit access to customer names and email addresses when exporting or scheduling reports.
Frequently Asked Questions
What counts as a failed transaction?
This report lists payment transactions marked with Failure status in the chosen transaction date range.
Does each row mean a lost order?
No. A failed attempt does not prove the order remained unpaid. Review the current order payment state separately.
Can I see why the payment failed?
Not from the eight default fields. Consult the relevant payment provider or transaction details for a failure explanation.
Can I contact customers using this report?
The Customer Email field helps identify a contact where available. Check whether action is still needed and follow applicable communication and privacy practices.
Can I schedule the report?
Yes. You can schedule email delivery on daily, weekly or monthly intervals.