# List then drill into settlement reports across five report types.

List then drill into settlement reports across five report types.

1. Batches branch — list the batches your merchants submitted to the processor on `date` (a required query parameter). Each row reports transaction counts, sale/held/return totals, and the owning merchant. `merchantId` is an optional filter.
 [getbatches](/api/getbatches)
2. Batches branch — retrieve a single batch by its integer `batchId`. Chains from listBatches by reading the first row's `batchId`; supply a known `batchId` directly if you have one.
 [getbatch](/api/getbatch)
3. Transactions branch — list merchant transactions. You must provide EITHER `date` OR `batchId`; modeled here with `date`. Optional `merchantId` and `transactionType` (Capture/Return) filters also apply. Each row includes type, amount, batch, authorization, and settlement details.
 [getTransactions](/api/get-transactions)
4. Transactions branch — retrieve a single transaction by its integer `transactionId`. Chains from listTransactions; supply a known `transactionId` directly if you have one.
 [gettransaction](/api/gettransaction)
5. Authorizations branch — list authorizations. You must provide EITHER `date` OR `batchId`; modeled here with `date`. Optional `merchantId` filter. Each row shows the issuing bank's authorization response, the authorized amount, and card/transaction/batch details.
 [getAuthorizations](/api/get-authorizations)
6. Authorizations branch — retrieve a single authorization by its integer `authorizationId`. Chains from listAuthorizations; supply a known `authorizationId` directly if you have one.
 [getAuthorization](/api/get-authorization)
7. Disputes branch — list disputes submitted on `date` (a required query parameter). Each row carries the dispute type, its `currentStatus` (status + statusDate), and the linked transaction. Optional `merchantId` filter.
 [getdisputes](/api/getdisputes)
8. Disputes branch — list the full status history of one dispute by its integer `disputeId` (each entry has a statusId, status, and statusDate). Chains from listDisputes; supply a known `disputeId` directly if you have one.
 [getdisputesStatuses](/api/getdisputes-statuses)
9. ACH-deposits branch — list ACH deposits paid to your merchants on `date` (a required query parameter). Each row breaks down sales, returns, fees, and the net amount paid. Optional `merchantId` filter.
 [getAchDeposits](/api/get-ach-deposits)
10. ACH-deposits branch — retrieve a single ACH deposit by its integer `achDepositId`. Chains from listAchDeposits; supply a known `achDepositId` directly if you have one.
 [getAchDeposit](/api/get-ach-deposit)
11. ACH-deposits branch, OPTIONAL — list the fee breakdown for an ACH deposit. You must provide EITHER `date` OR `achDepositId`; modeled here chaining `achDepositId` from retrieveAchDeposit so the fees line up with the retrieved deposit. Optional `merchantId` filter.
 [getAchDepositFees](/api/get-ach-deposit-fees)

## Workflow diagram

```mermaid
flowchart TD
  step0["1. list batches · API"]
  step1["2. get batch · API"]
  step0 --> step1
  step2["3. list transactions · API"]
  step1 --> step2
  step3["4. get transaction · API"]
  step2 --> step3
  step4["5. list authorizations · API"]
  step3 --> step4
  step5["6. get authorization · API"]
  step4 --> step5
  step6["7. list disputes · API"]
  step5 --> step6
  step7["8. list dispute statuses · API"]
  step6 --> step7
  step8["9. list ACH deposits · API"]
  step7 --> step8
  step9["10. get ACH deposit · API"]
  step8 --> step9
  step10["11. list ACH deposit fees · API"]
  step9 --> step10
```