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_KEY

Merchant 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.

ACH funding (merchant reports)

ReportEndpointWhat it shows
ACH ActivityGET /checkout/v3/report/ach/activitySummarySummary of ACH funding activity for the range.
ACH ReturnsGET /checkout/v3/report/ach/returnsACH transactions that were returned.
🚧

ACH Returns is Production-only

The 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)

ReportEndpointWhat it shows
User SalesGET /checkout/v3/report/usersalesSales by user.
User Sales SummaryGET /checkout/v3/report/usersalessummarySummarized sales by user.
Expired CardsGET /checkout/v3/report/cardexpirationSaved cards that are expired or expiring.
API TrafficGET /checkout/v3/accesslogAPI 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):

  1. Match settled batches. Pull the Batch report (TSYS / First Data) for the date range and reconcile it against your batch totals.
  2. Drill into transactions. Use the Batch Transactions report (TSYS / First Data) for per-transaction settlement detail.
  3. 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:

  1. Review funding activity. Pull the ACH Activity report for the date range to see settlement, origination, and return activity summarized by processing date.
  2. 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

PracticeDescription
Reconcile dailyMatch 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 pathCall 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 tightNarrow date windows return faster and are easier to reconcile; page large ranges rather than one huge request. See Pagination.
Watch disputes and ACH returnsPull the Disputes and ACH Returns reports regularly so reversed funds don't surprise your books.
Automate expiring cardsUse the Expired Cards report (or Account Updater) to refresh saved cards before they fail.

See also



Did this page help you?