Enhanced Pagination and Query Parameters for ACH Transactions Endpoint

We have updated the Collects all ACH transactions endpoint (GET /v2/ach/transactions) to support comprehensive pagination and standard filtering query parameters. These updates allow you to efficiently page through large sets of transaction history and drill down into data using specific search criteria, date ranges, amounts, and statuses.

New parameters available

Pagination

• page (integer): Page number for paginated results (must be greater than or equal to 1).
• limit (integer): The number of transactions returned per request. Max limit is 125. Defaults to 125 if omitted.

Date Filters

• startDate (date, YYYY-MM-DD): Filter transactions created on or after this date.
• endDate (date, YYYY-MM-DD): Filter transactions created on or before this date.

Note: If both are provided, endDate must not be earlier than startDate.

Amount Filters

• amountMin (float): Filter transactions by a minimum amount.
• amountMax (float): Filter transactions by a maximum amount.

Note: If both are provided, amountMax must not be less than amountMin.

Status & User Filters

• statusAuth (array of strings): Filter transactions by authorization status.
• statusClearing (array of strings): Filter transactions by clearing status.
• users (array of integers): Filter transactions handled by specific user IDs.

Text Search

• search (string): Performs a text search across multiple transaction fields, including:
  • Transaction ID
  • Last 4 digits of the bank account (bankAccountL4l4)
  • Order ID
  • Batch ID
  • Contact Name
  • Business Name

Impact and Actions Required

Backwards Compatibility: This change is fully backwards compatible. Existing integrations calling GET /v2/ach/transactions without parameters will continue to work as expected, defaulting to page 1 with a maximum of 125 objects returned.

Recommendation: Update your data fetching logic to utilize the page and limit parameters to manage response payload sizes and optimize application performance.