Merchants can generate reports to monitor transactions, deposits, ACH funding, disputes/chargebacks, and statements. This page lists endpoints and parameters only (no request/response bodies) to streamline reporting & reconciliation workflows. Legacy endpoints are included for reference but should not be used for new implementations.

Notes

Most reports return data only in production. Use live MIDs with activity.

Acquiring account reports (TSYS, Fiserv Omaha, Fiserv North) are the recommended sources for reconciliation.

Statements are retrieved via APIs for non‑legacy customers. MX Merchant authentication is technically possible but not the primary approach.

For issues, customers should contact Client Services or MXM Support; they will escalate internally if needed.

Authentication summary (from collection)

Context	Method	Credentials	Notes
MX Merchant Reporting (acquiring)	Bearer	`token`	Used across TSYS, Fiserv Omaha/North reporting endpoints.
Legacy MX Merchant	Basic	`username`/`password` (also `ConsumerKey`/`ConsumerSecret` in some flows)	Legacy endpoints under `/checkout/v3/report/...`.
MX Connect	Bearer	`token`	Used by some Fiserv Omaha reporting (e.g., ACH via `api.mxconnect.com`).

ACH Funding — Reconciliation (TSYS)

Funding activity and adjustments for TSYS acquiring; use to reconcile deposits/fees at the bank level.

GET https://api2.mxmerchant.com/report/v1/tsys/ach

Name	Type	Required	Example	Description
`from`	integer	No	`0`	Pagination offset.
`size`	integer	No	`100`	Page size.
`sort`	string	No	`batchDate:desc`	Sort field/order.

Authentication (TSYS Bearer)

Basic Auth to get token: GET https://api2.mxmerchant.com/security/v1/application/merchantId/{TSYS-MID}/token with username={{TSYS-KEY}} and password={{TSYS-SECRET}}.

Read jwtToken from the response and set it as Bearer token for reporting calls above.

Batch report

Batch-level view to reconcile settlement activity by batch date and totals.

GET https://api2.mxmerchant.com/report/v1/tsys/batch

Name	Type	Required	Example	Description
`startDate`	string (YYYY-MM-DD)	Yes	`2025-08-01`	Start of date range.
`endDate`	string (YYYY-MM-DD)	Yes	`2025-09-01`	End of date range.
`from`	integer	No	`0`	Pagination offset.
`size`	integer	No	`100`	Page size.
`sort`	string	No	`batchDate:desc`	Sort field and order.
`summary`	boolean	No	`false`	If true, returns summary aggregates only.

Batch transactions report

Drill-down of transactions within a specific batch for detailed reconciliation.

GET https://api2.mxmerchant.com/report/v1/tsys/batch/transactions

Name	Type	Required	Example	Description
`batchDate`	string (YYYY-MM-DD)	Yes	`2025-08-19`	Batch processing date.
`batchNumber`	string	Yes	`123456`	Batch identifier.
`from`	integer	No	`0`	Pagination offset.
`size`	integer	No	`100`	Page size.
`sort`	string	No	`batchDate:desc`	Sort field and order.

Important: Avoid using an includeFields parameter for batch transactions. It does not function as intended and returns all fields; therefore it is excluded from this documentation until fixed.

Transactions report

Detailed view of individual transactions (type, card brand, amounts, auth code, batch/terminal references) to investigate charges and support reconciliation.

GET https://api2.mxmerchant.com/report/v1/tsys/transactions

Name	Type	Required	Example	Description
`paymentType`	string	No	`any`	Filter by payment type (e.g., `card`, `ach`, `any`).
`cardType`	string	No	`visa`	Filter by card network.
`size`	integer	No	`100`	Page size.
`from`	integer	No	`0`	Pagination offset.
`sort`	string	No	`transactionDate:desc`	Sort by transaction date.
`isExport`	boolean	No	`true`	Toggles export formatting.

Additional TSYS reports (if present in your environment, e.g., Disputes): follow the same query conventions for pagination and sorting.

Batch report

Batch-level view for Fiserv Omaha acquiring; use to summarize settlement activity and gather batchDate/batchNumber for drill-downs.

GET https://api2.mxmerchant.com/report/v1/fd/batch

Name	Type	Required	Example	Description
`from`	integer	No	`0`	Pagination offset.
`size`	integer	No	`20`	Page size.
`sort`	string	No	`batchDate:desc`	Sort field/order.
`summary`	boolean	No	`false`	Summary aggregates only when `true`.

Transactions report

Transaction-level detail for Fiserv Omaha (card/ACH), useful for investigations and line-level reconciliation.

GET https://api2.mxmerchant.com/report/v1/fd/transactions

Name	Type	Required	Example	Description
`paymentType`	string	No	`any`	Filter by payment type (e.g., `card`, `ach`, `any`).
`size`	integer	No	`100`	Page size.
`from`	integer	No	`0`	Pagination offset.
`sort`	string	No	`transactionDate:desc`	Sort by transaction date.

Chargebacks / disputes

Dispute cases for Fiserv Omaha; includes reason codes, amounts, and processing dates.

GET https://api2.mxmerchant.com/report/v1/fd/disputes

Name	Type	Required	Example	Description
`from`	integer	No	`0`	Pagination offset.
`size`	integer	No	`100`	Page size.
`dateTypeFilter`	string	No	`Year`	Time window selector (e.g., `Day`, `Month`, `Year`).
`sort`	string	No	`processingDate:desc`	Sort by processing date.

ACH funding — reconciliation (MX Connect)

Reconciliation view showing adjustments, chargebacks, deposits, fees, and reserves aligned to bank movements.

GET https://api.mxconnect.com/report/v1/fd/ach

Name	Type	Required	Example	Description
`size`	integer	No	`100`	Page size.
`from`	integer	No	`0`	Pagination offset.
`sort`	string	No	`batchDate:desc`	Sort field and order.

Batch transactions

Transaction details within a selected Fiserv Omaha batch for line-level reconciliation.

GET https://api2.mxmerchant.com/report/v1/fd/batch/transactions

Name	Type	Required	Example	Description
`batchDate`	string (YYYY-MM-DD)	Yes	`2025-08-19`	Batch date.
`batchNumber`	string	Yes	`123456`	Batch identifier.
`from`	integer	No	`0`	Pagination offset.
`size`	integer	No	`100`	Page size.
`sort`	string	No	`batchDate:desc`	Sort order.

This section covers available endpoints for Fiserv North acquiring found in the shared collection. A standalone Transactions endpoint was not present in the JSON, so it is not included.

Batch report

Batch-level records for Fiserv North acquiring accounts; use with batch-transaction detail to complete reconciliation.

GET https://api2.mxmerchant.com/report/v1/fiserv/north/batch

Name	Type	Required	Example	Description
`startDate`	string (YYYY-MM-DD)	Yes	`2025-05-01`	Start of date range.
`endDate`	string (YYYY-MM-DD)	Yes	`2025-09-09`	End of date range.
`from`	integer	No	`0`	Pagination offset.
`size`	integer	No	`100`	Page size.
`sort`	string	No	`batchDate:desc`	Sort field and order.
`summary`	boolean	No	`false`	If true, returns summary aggregates only.

Chargebacks / disputes

Review chargeback cases with reason codes, amounts, and transaction dates for dispute management and reconciliation.

GET https://api2.mxmerchant.com/report/v1/fiserv/north/chargeback

Name	Type	Required	Example	Description
`from`	integer	No	`0`	Pagination offset.
`size`	integer	No	`100`	Page size.
`dateTypeFilter`	string	No	`Year`	Time window selector (e.g., `Day`, `Month`, `Year`).
`sort`	string	No	`transactionDate:desc`	Sort by transaction date.

ACH funding

ACH funding activity for Fiserv North—use alongside batches to match funding lines to source transactions.

GET https://api2.mxmerchant.com/report/v1/fiserv/north/achFunding

Name	Type	Required	Example	Description
`startDate`	string (YYYY-MM-DD)	Yes	`2025-05-01`	Start of date range.
`endDate`	string (YYYY-MM-DD)	Yes	`2025-09-01`	End of date range.
`size`	integer	No	`100`	Page size.
`from`	integer	No	`0`	Pagination offset.
`sort`	string	No	`companyDescriptiveDate:desc`	Sort order.

Statements

Primary approach: Non‑legacy customers must retrieve statements via MX Connect APIs. While MX Merchant authentication remains technically possible, it is not the primary method.

Legacy note: The MX Merchant statements endpoint remains only for legacy accounts.

Legacy — Statements

GET https://api.mxmerchant.com/checkout/v3/report/statement

Name	Type	Required	Example	Description
`merchantId`	string	Yes	`{MID}`	Merchant ID.
`statementDate`	string (MM/DD/YYYY)	Yes	`08/01/2025`	Statement month/day/year.

Legacy Reports (reference only)

Work with MX ISO Agent or VIMAS boarded accounts using MX Merchant. Use Basic Auth. Prefer acquiring reports for new builds.

Deposits (legacy)

Deposit-level funding view for legacy MX ISO Agent/VIMAS accounts; align deposits, fees, reserves, and adjustments for bank reconciliation.

GET https://api.mxmerchant.com/checkout/v3/report/deposit (path representative)

Name	Type	Required	Example	Description
`merchantId`	string	Yes	`{MID}`	Merchant ID.
`startDate`	string (MM/DD/YYYY)	Yes	`09/01/2025`	Start date.
`endDate`	string (MM/DD/YYYY)	Yes	`09/10/2025`	End date.
`limit`	integer	No	`100`	Page size.
`offset`	integer	No	`0`	Pagination offset.

Settlement — batch transaction detail (legacy)

Line-level settlement details for a specified legacy batch; trace batch totals back to individual transactions.

GET https://api.mxmerchant.com/checkout/v3/report/settlement/batch/transaction

Name	Type	Required	Example	Description
`batchId`	string	Yes	`{batchId}`	Settlement batch identifier.
`limit`	integer	No	`100`	Page size.
`offset`	integer	No	`0`	Pagination offset.

Chargebacks (legacy)

Legacy dispute case list for MX ISO Agent/VIMAS accounts; filter by date range to review reason codes, amounts, and statuses.

GET https://api.mxmerchant.com/checkout/v3/report/chargeback

Name	Type	Required	Example	Description
`merchantId`	string	Yes	`{MID}`	Merchant ID.
`startDate`	string (MM/DD/YYYY)	Yes	`09/01/2025`	Start date.
`endDate`	string (MM/DD/YYYY)	Yes	`09/10/2025`	End date.
`dateRange`	string	No	`Custom`	Date-range preset.
`limit`	integer	No	`100`	Page size.
`offset`	integer	No	`0`	Pagination offset.

Volume (legacy)

Aggregated legacy processing volume with optional grouping (for example, by batch) to analyze trends over a date range.

GET https://api.mxmerchant.com/checkout/v3/report/volume

Name	Type	Required	Example	Description
`merchants`	string	Yes	`{MID}`	One or more merchant IDs.
`startDate`	string (MM/DD/YYYY)	Yes	`09/06/2025`	Start date.
`endDate`	string (MM/DD/YYYY)	Yes	`09/11/2025`	End date.
`groupBy`	string	No	`batch`	Grouping key.
`limit`	integer	No	`10`	Page size.
`offset`	integer	No	`0`	Pagination offset.

Tips for reconciliation

Prefer acquiring reports for the most robust, accurate reconciliation.
Use consistent date formats per endpoint (YYYY-MM-DD vs MM/DD/YYYY).
Combine Batch + Batch Transactions + ACH Funding to trace funding → deposit lines → transaction sources.
If issues arise, contact Client Services or MXM Support; they will escalate internally as needed.