# List transactions

Returns the statement of a payment account: credits and debits, newest first by `processed_at`.
A line is written when money moves on the account. A card payment adds a credit when it succeeds. A
payout adds a debit when it succeeds. While a payout is in progress, its amount shows in the `on_hold`
balance and not on the statement.
`before` and `after` filter on `processed_at`. A bare date (`YYYY-MM-DD`) means a whole day in UTC.

Endpoint: GET /payment-accounts/{payment_account_id}/transactions
Version: 1.0.0
Security: JWT

## Security:

  - `JWT` (unknown)
    http bearer JWT

## Path parameters:

  - `payment_account_id` (string, required)
    The ID of a payment account you own. Starts with `pacct_`.

## Query parameters:

  - `type` (string)
    Returns only credits or only debits. The value is not case-sensitive.

  - `currency` (string)
    Returns only lines in this currency.

  - `before` (string)
    Return only resources created at or before this time. Send an [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) timestamp with an offset, such as `2025-02-18T12:03:44Z` or `2025-02-18T17:33:44+05:30`. A timestamp without an offset is read as UTC. A bare date (`YYYY-MM-DD`) means the end of that day in UTC (`23:59:59.999999Z`). An invalid value returns `400 Bad Request`. Use this to avoid page drift. See [Pagination parameters](/platform/pagination#parameters) for more details.

  - `after` (string)
    Return only resources created at or after this time. Send an [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) timestamp with an offset, such as `2025-01-18T12:03:44Z` or `2025-01-18T17:33:44+05:30`. A timestamp without an offset is read as UTC. A bare date (`YYYY-MM-DD`) means the start of that day in UTC (`00:00:00Z`). An invalid value returns `400 Bad Request`. Use this to avoid page drift. See [Pagination parameters](/platform/pagination#parameters) for more details.

  - `page` (integer)
    Page number for pagination. Starts from 1. Get the next page number from the `next` field in the response.

  - `per_page` (integer)
    Number of resources per page. Should be between 1 and 100.

## Response 200:

  - `200` (unknown)
    Statement lines

## Response 200 fields (application/json):

  - `data` (array)

  - `data.id` (string)
    Example: pactxn_6ab59b40Lx2Rb

  - `data.type` (string)
    Enum: "credit", "debit"

  - `data.amount` (integer)
    The amount that moved on the account, in minor units of `currency`.
    Example: 100000

  - `data.currency` (string)
    Example: USD

  - `data.funds_available` (boolean | null)
    Set only on a credit from a card payment. `false` while the money is in the `pending` balance, and `true` when it is in `available`. `null` on every other line.
    Example: true

  - `data.source` (object)
    The movement behind the line.

  - `data.source.type` (string)
    `payment` is a card payment that added funds. `payout` is money sent to a beneficiary. `refund` is a card payment returned to the card.
    Enum: "payment", "payout", "refund"

  - `data.source.id` (string)
    Example: payt_6ab59b22oXGRy

  - `data.source.status` (string)
    The status of the payment, payout or refund behind the line. Present only on Get a transaction.
    Example: success

  - `data.processed_at` (string)
    When the money moved on the account. The statement is sorted by this time, and `before` and `after` filter on it.
    Example: 2026-10-15T09:18:05Z

  - `page_meta` (object)

  - `page_meta.current` (integer)
    The current page number.
    Example: 2

  - `page_meta.previous` (integer | null)
    The previous page number.
    Example: 1

  - `page_meta.next` (integer | null)
    The next page number.
    Example: 3

  - `page_meta.per_page` (integer)
    The number of items per page.
    Example: 20

  - `page_meta.pages` (integer)
    The total number of pages.
    Example: 10

  - `page_meta.count` (integer)
    The total number of items.
    Example: 200

## Response 400:

  - `400` (unknown)
    Invalid filter or pagination parameter

## Response 400 fields (application/json):

  - `error` (string, required)
    The HTTP reason phrase.
    Example: Bad Request

  - `message` (string, required)
    What went wrong. Show it in logs, not to the customer.
    Example: Payment account cannot send money

  - `code` (string)
    A stable code for the error. Present only on some errors, for example `INSUFFICIENT_BALANCE` on a payout and `order_amount_above_cap` on an order. Branch on `code` when it is present, and on the HTTP status when it is not.
    Example: INSUFFICIENT_BALANCE

## Response 404:

  - `404` (unknown)
    The payment account does not exist or you do not own it

## Response 404 fields (application/json):

  - `error` (string, required)
    The HTTP reason phrase.
    Example: Bad Request

  - `message` (string, required)
    What went wrong. Show it in logs, not to the customer.
    Example: Payment account cannot send money

  - `code` (string)
    A stable code for the error. Present only on some errors, for example `INSUFFICIENT_BALANCE` on a payout and `order_amount_above_cap` on an order. Branch on `code` when it is present, and on the HTTP status when it is not.
    Example: INSUFFICIENT_BALANCE

