Reports & Reconciliation
Reconcile card settlement, deposits, and disputes by processor — and pull ACH funding, sales, and activity reports
Reports let you reconcile what you processed, what settled, and what was deposited — and review ACH funding, sales, and account activity. They come in two families:
- Acquiring Report API — card settlement batches, batch transactions, transactions, ACH funding, and disputes, routed per processor (TSYS, First Data) under
/checkout/report/v1. Use these to reconcile card settlement and deposits and to investigate disputes. - Merchant reports — ACH funding activity and returns, sales by user, expiring saved cards, and API traffic, under
/checkout/v3/report.
Each report is a read-only GET that returns a paged list. For the full catalog, jump to Available reports.
Common use cases
- Reconcile settled card batches and deposits for a processor
- Investigate a dispute (chargeback) against your transactions
- Reconcile ACH funding activity and returns against your bank account
- Review sales by user, and track expiring saved cards and API activity
How reporting works
Acquiring Report API (card settlement, batches, transactions, disputes). Call the path for your processor — /checkout/report/v1/tsys/… or /checkout/report/v1/fd/… — with your PCE x-api-key. Results are restricted to the merchants your API key is authorized for (there is no merchantId parameter). Filter with accountNumbers and a date range: either absolute (startDate/endDate as YYYY-MM-DD) or a relative window (dr_type=rel with dr_count/dr_unit). Page with from and size, sort with sort.
GET /checkout/report/v1/tsys/batch?startDate=2026-01-01&endDate=2026-01-31&size=50
x-api-key: YOUR_API_KEYMerchant reports (ACH funding, sales, activity). Call /checkout/v3/report/… with a merchantId and (for most reports) a MM/DD/YYYY date range. Most return a records array with a recordCount; the ACH reports wrap records in a Result object. For example, User Sales Summary:
GET /checkout/v3/report/usersalessummary?merchantId=1000157980&startDate=01/01/2026&endDate=01/31/2026
x-api-key: YOUR_API_KEY{
"records": [
{
"userName": "Jane Clerk",
"transactionCount": 70,
"totalAmount": "354.76"
},
{
"userName": "RecurringBilling",
"transactionCount": 10,
"totalAmount": "199.90"
}
],
"recordCount": 2
}Page through results with the report's paging parameters. See Pagination.
Available reports
Card settlement, batches & disputes (Acquiring Report API)
Processor-specific — call the path for the processor behind your merchant. Each report is available for both TSYS and First Data.
| Report | TSYS | First Data |
|---|---|---|
| Batch (settled batches) | GET /checkout/report/v1/tsys/batch | GET /checkout/report/v1/fd/batch |
| Batch Transactions (per-transaction settlement detail) | GET /checkout/report/v1/tsys/batch/transactions | GET /checkout/report/v1/fd/batch/transactions |
| Transactions | GET /checkout/report/v1/tsys/transactions | GET /checkout/report/v1/fd/transactions |
| ACH funding | GET /checkout/report/v1/tsys/ach | GET /checkout/report/v1/fd/ach |
| Disputes (chargebacks) | GET /checkout/report/v1/tsys/disputes | GET /checkout/report/v1/fd/disputes |
ACH funding (merchant reports)
| Report | Endpoint | What it shows |
|---|---|---|
| ACH Activity | GET /checkout/v3/report/ach/activitySummary | Summary of ACH funding activity for the range. |
| ACH Returns | GET /checkout/v3/report/ach/returns | ACH transactions that were returned. |
ACH Returns is Production-onlyThe ACH Returns report runs against live ACH activity and is not available in Sandbox. Calling it in Sandbox returns an HTTP 404 (
No HTTP resource was found that matches the request URI) — this is expected and does not mean your integration is broken. Test this report in Production.
Sales & activity (merchant reports)
| Report | Endpoint | What it shows |
|---|---|---|
| User Sales | GET /checkout/v3/report/usersales | Sales by user. |
| User Sales Summary | GET /checkout/v3/report/usersalessummary | Summarized sales by user. |
| Expired Cards | GET /checkout/v3/report/cardexpiration | Saved cards that are expired or expiring. |
| API Traffic | GET /checkout/v3/accesslog | API request activity for your account. |
Reconcile payments to your bank
Card payments — reconcile with the Acquiring Report API, using the path for your processor (TSYS or First Data):
- Match settled batches. Pull the Batch report (TSYS / First Data) for the date range and reconcile it against your batch totals.
- Drill into transactions. Use the Batch Transactions report (TSYS / First Data) for per-transaction settlement detail.
- Confirm funding and disputes. Use the ACH report (TSYS / First Data) for funding and the Disputes report (TSYS / First Data) for chargebacks.
ACH funding — reconcile with the merchant ACH reports:
- Review funding activity. Pull the ACH Activity report for the date range to see settlement, origination, and return activity summarized by processing date.
- Account for returns. Pull the ACH Returns report (Production only) for anything that bounced back.
For the settlement-to-funding flow, auto-close configuration, and how settled batches become bank deposits, see Settlement & Funding.
Invoice activity can also be exported for reconciliation with Invoice Export (GET /checkout/v3/invoice/export). See Invoicing and Recurring Billing.
Best practices
| Practice | Description |
|---|---|
| Reconcile daily | Match your bank statement each processing day — card settlement via the Acquiring Report API Batch reports, ACH funding via the merchant ACH reports. |
| Use the right processor path | Call the TSYS or First Data path that matches the processor behind your merchant; the two return the same report shape per processor. |
| Keep date ranges tight | Narrow date windows return faster and are easier to reconcile; page large ranges rather than one huge request. See Pagination. |
| Watch disputes and ACH returns | Pull the Disputes and ACH Returns reports regularly so reversed funds don't surprise your books. |
| Automate expiring cards | Use the Expired Cards report (or Account Updater) to refresh saved cards before they fail. |
See also
- Settlement & Funding: how a payment moves from capture to settlement to deposit
- Batch Management: open, close, and read batches
- Payment Lifecycle: how a payment moves from capture to settlement
- Invoicing: export invoices for reconciliation
- Recurring Billing: export contracts for reconciliation
- Pagination: page through large report results
Updated 9 days ago