---
title: "List Transfers"
method: POST
path: "/listTransfers"
tags: ["Transfers"]
---

# List Transfers

`POST /listTransfers`

## Request

- Base URL: `{corename}.payment-hub.{env}.gpsrv.com/payment-hub/1.0`
- URL: `{corename}.payment-hub.{env}.gpsrv.com/payment-hub/1.0/listTransfers`
- Auth: none declared. Required headers: `Authorization`

Use the List Transfer endpoint to get incoming and outgoing transfers attached to the provided account_no.All transfers created by <a href="ref:payhub_post_createTransfer" target="_blank">Create Transfer</a> will be returned as outgoing transfers.

## Headers

- `Authorization` string, required

## Request body

- object
  - `accountNo` string, required: All transfers associated with this <<glossary:PRN>>. Pattern: PRN Example: `074103447228`
  - `filters` object: Filters the list of transfers by direction, payment method, and status.
    - `direction` 'IN' | 'OUT', nullable: Direction of the transfer relative to the specified account. - IN: The specified account is the destination account of the transfer - OUT: The specified account is the source account of the transfer Note: Direction indicates transfer flow, but actual fund movement depends on the debit/credit indicator. For example, an incoming debit or outgoing credit may both result in funds leaving the specified account.
    - `paymentMethod` 'ACH' | 'FEDNOW' | 'FEDWIRE' | 'CARD', nullable: Filters the list by the payment network used for the transfer relative to the specified account. Example: `ACH`
    - `status` 'CREATED' | 'IN PROGRESS' | 'COMPLETED' | 'FAILED' | 'PENDING REVIEW' | 'SENT' | 'ACCEPTED WITHOUT POST' | 'BLOCKED' | 'REJECTED' | 'REQUESTED' | 'REQUEST APPROVED' | 'REQUEST REJECTED', nullable: Status of the transaction. **For FedNow and FedWire transactions:** - CREATED: Initial state for transactions after creation via API call. - SENT: Outbound-only state indicating payment message (pacs.008 or pacs.004) successfully published to the payment network, awaiting pacs.002 status report. - IN PROGRESS: Transaction is being processed. - COMPLETED: Terminal success state. Payment network confirmed successful settlement via pacs.002 with ACSC or ACCC status. - FAILED: Terminal failure state. Transaction rejected by payment network or receiving FI initially. **For FedNow transactions only:** - ACCEPTED WITHOUT POST: Special intermediate state for outbound payments. Received pacs.002 with ACWP status - funds have settled but receiving Financial Institution requires additional investigation time before posting. - BLOCKED: Terminal state for outbound payments previously in ACCEPTED WITHOUT POST. Receiving FI sent pacs.002 with BLCK status - funds are blocked and will not be posted. - REJECTED: Terminal state for outbound payments previously in ACCEPTED WITHOUT POST. Received pacs.002 with RJCT status after investigation - funds must be returned via new pacs.004. - REQUESTED: Return has been requested (FedNow returns only). - REQUEST APPROVED: Return request has been approved (FedNow returns only). - REQUEST REJECTED: Return request has been rejected (FedNow returns only).
  - `dateFrom` string: Start date for the transaction query. Defaults to the past 30 days from the current date. Pattern: YYYY-MM-DD or ISO 8601 date-time Example: `"2025-07-13"`
  - `dateTo` string: End date for the transaction query. Defaults to the current date and time. Pattern: YYYY-MM-DD or ISO 8601 datetime Example: `"2025-08-13"`
  - `limit` integer: Maximum number of transfers to return in the response. Pattern: Integer, max 15 Example: 15
  - `page` string, nullable: Pass the `nextPage` token from a previous response to fetch the subsequent page. Pattern: Alphanumeric token Example: `"NO34BNT04TV234N6V274692376G32NNFNNF7988247923865017061N"`

## Response `200`

Successful Response

- object
  - `nextPage` string, nullable, required: Token used to retrieve the next page of results. This field is null if there are no more results.
  - `data` object[], required: A list of transfer history data objects.
    - `transferId` string, required: The unique identifier for the transfer.
    - `currencyAmount` object, required: Response-side currency amount. Raises InternalServiceException (500) on invalid persisted data — bad values in response construction reflect server-side data integrity issues, not client error.
      - `amount` number, required
      - `currency` string: Currency code following ISO 4217 standard. Validation: Exactly 3 uppercase letters. Pattern: ^[A-Z]{3}$ Example: 'USD' (US Dollar), 'EUR' (Euro), 'GBP' (British Pound)
    - `purpose` string, nullable: Purpose provided for the transfer.
    - `createdDate` string, required: The date when the transfer was created or received, either a date or date-time.

## Other responses

- `400`: Bad Request
- `401`: No valid API credentials provided.
- `403`: The provided API credential does not allow this operation.
- `422`: Validation Error
- `429`: Too many requests.
- `500`: Internal Server Error
- `502`: Bad Gateway.
- `503`: Service Unavailable.

---

[API](https://skmtc.dev/galileo-ft/apis/payment-hub-api-2-0.md) - [All operations](https://skmtc.dev/galileo-ft/apis/payment-hub-api-2-0/llms.txt) - [OpenAPI document](https://skmtc.dev/galileo-ft/apis/payment-hub-api-2-0/revisions/20e06b09d5e4?raw)