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

# List inbound card payments

> Retrieve a paginated list of acquiring card payments, optionally filtered by entity.

Returns acquiring card payments ordered by most recent first. These are cards processed in Lemma's lockbox, or charged by one of the entity's employees in the Lemma dashboard. These are separate from [debit cards issued on Lemma](/docs/api-reference/card-payments). Results are [paginated](/docs/api-reference/pagination).

## Query parameters

<ParamField query="entity_id" type="string">
  Filter card payments to a specific entity, prefixed with `entity_`. You can
  find entity IDs using the [List entities](/docs/api-reference/list-entities)
  endpoint. Omit to list card payments across every entity you can access.
</ParamField>

<ParamField query="limit" type="integer" default="10">
  The number of card payments to return. Maximum is 100.
</ParamField>

<ParamField query="cursor" type="string">
  Cursor from the previous response. Omit to fetch from the beginning.
</ParamField>

## Response

<ResponseField name="data" type="object[]">
  The list of card payment objects for the requested page.

  <Expandable title="Inbound card payment object">
    <ResponseField name="id" type="string">
      Unique identifier for the inbound card payment.
    </ResponseField>

    <ResponseField name="created_at" type="string">
      [ISO 8601](/docs/api-reference/timestamps) timestamp of when the card payment was
      created.
    </ResponseField>

    <ResponseField name="entity_id" type="string">
      The Lemma entity that received the card payment.
    </ResponseField>

    <ResponseField name="amount" type="integer">
      The amount charged, in cents. Always positive.
    </ResponseField>

    <ResponseField name="status" type="string">
      Current status of the card payment.

      <Expandable title="possible values">
        * `processing` — the charge is in flight.

        * `succeeded` — the card was charged.

        * `failed` — the charge did not go through.

        * `canceled` — the charge was canceled before completing.
      </Expandable>
    </ResponseField>

    <ResponseField name="type" type="string">
      How the card was captured.

      <Expandable title="possible values">
        * `lockbox_card` — a virtual card paid into the entity's Lemma lockbox.

        * `customer_card` — a card charged directly by one of the entity's
          employees in the Lemma dashboard.
      </Expandable>
    </ResponseField>

    <ResponseField name="transaction_id" type="string | null">
      The settled transaction that lands in the entity's account, once the payment
      posts.
    </ResponseField>

    <ResponseField name="fee_transaction_id" type="string | null">
      The transaction for the processing fee, once it posts.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="has_next" type="boolean">
  Whether more card payments exist after this page.
</ResponseField>

<ResponseField name="cursor" type="string | null">
  Pass this value as `cursor` on the next request to fetch the following page.
  `null` when this is the last page.
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "data": [
      {
        "id": "inbound_card_payment_Wp5mRx3nKv8bTh2d",
        "created_at": "2026-05-01T12:00:00Z",
        "entity_id": "entity_Rv4nBt8xKw2pMh6s",
        "amount": 48900,
        "status": "succeeded",
        "type": "lockbox_card",
        "transaction_id": "transaction_Kd8mNx2pRv5cTh9b",
        "fee_transaction_id": null
      }
    ],
    "has_next": false,
    "cursor": null
  }
  ```
</ResponseExample>


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