> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reclack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List Transactions

> Every payment, with the chain's own record attached.

## Overview

List payments. Every transaction carries its hash and the address it settled
to, so a figure in your books can always be traced to a block.


## OpenAPI

````yaml GET /v1/transactions
openapi: 3.1.0
info:
  title: Reclack API
  version: 1.0.0
  description: >-
    Recurring and one-time stablecoin payments, taken straight from your
    customers' wallets.


    Reclack is non-custodial. Payments move from a customer's wallet to a
    settlement address you control, and Reclack never holds funds and never asks
    anyone for a seed phrase or a private key.


    ## Authentication


    Send your API key in the `Api-Key` header:


    ```

    Api-Key: rk_live_your_key_here

    ```


    `X-API-Key` is accepted too. The key prefix decides the environment:
    `rk_sandbox_` for test chains, `rk_live_` for production.


    ## Responses


    Objects and lists come back under `data`. Errors come back under `error`
    with a `type`, an optional `code` and a message written for a person.
servers:
  - url: https://api.reclack.com
    description: Sandbox and live, chosen by your key
security:
  - apiKeyAuth: []
tags:
  - name: Products
  - name: Prices
  - name: Customers
  - name: Subscriptions
  - name: Usage
  - name: Invoices
  - name: Checkouts
  - name: Payment links
  - name: Transactions
  - name: Webhooks
  - name: API keys
  - name: Settlement
paths:
  /v1/transactions:
    get:
      tags:
        - Transactions
      summary: List transactions
      description: Every payment, with the chain's own record attached.
      operationId: transactions-list
      parameters:
        - name: customer_id
          in: query
          required: false
          schema:
            type: string
          description: Only this customer's payments.
        - name: status
          in: query
          required: false
          schema:
            type: string
          description: pending, confirmed or failed.
        - name: limit
          in: query
          required: false
          schema:
            type: integer
          description: How many to return.
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/Transaction'
        '400':
          description: The request is missing something or contradicts itself
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: No key, a revoked key, or a key that does not exist
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: The key is valid but is not allowed to do this
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Transaction:
      type: object
      properties:
        id:
          type: string
          example: txn_2e2df306
        status:
          type: string
          enum:
            - pending
            - confirmed
            - failed
          example: confirmed
        amount:
          type: string
          example: '29.00'
        currency:
          type: string
          example: USDC
        network:
          type: string
          example: base
        chain_id:
          type: integer
          example: 8453
        hash:
          type: string
          description: The transaction hash onchain.
          example: '0x2e2d9a41c7f1b86d05e4a3c2b7f9d1083e6a5c4b2d8f7091a3c5e7b9d1f3a5306'
        customer_id:
          type: string
          example: cus_7Fh2PqX9
        invoice_id:
          type: string
          example: in_0219
        settled_to:
          type: string
          description: The settlement address the funds landed in.
          example: '0x71B9a0C4f3b1d8e2A5c7E9f0B4d6A8c2E1f34921'
        confirmed_at:
          type: string
          format: date-time
          example: '2026-10-18T22:07:41Z'
        created_at:
          type: string
          format: date-time
          example: '2026-10-18T22:07:41Z'
    Error:
      type: object
      properties:
        error:
          type: object
          properties:
            type:
              type: string
              description: >-
                One of invalid_request_error, authentication_error,
                permission_error or api_error.
              example: invalid_request_error
            code:
              type: string
              description: A stable, machine readable reason.
              example: price_not_found
            message:
              type: string
              description: A sentence written for a person.
              example: No price was found for that id
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: Api-Key
      description: >-
        Your Reclack API key. The prefix decides the environment: rk_sandbox_
        for test chains, rk_live_ for production.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.