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

# payouts

> HSA/FSA payouts deposited for this store. Dates filter on the payout (value) date.

**Required scopes:** [`payments_read`](/docs/api-reference/v3/reference/scopes#scope-payments_read)

## Arguments

<ResponseField name="after" type="String">
  Forward pagination cursor — returns items after it. Cursors are positions in the filtered list, so a row can shift onto another page if new activity lands in the requested range.
</ResponseField>

<ResponseField name="before" type="String">
  Backward pagination cursor — returns items before it. Cursors are positions in the filtered list, so a row can shift onto another page if new activity lands in the requested range.
</ResponseField>

<ResponseField name="dateFrom" type={<a href="/docs/api-reference/v3/reference/common/date">Date</a>}>
  Inclusive first payout (value) date. Rejected when it is after `dateTo`.
</ResponseField>

<ResponseField name="dateTo" type={<a href="/docs/api-reference/v3/reference/common/date">Date</a>}>
  Inclusive last payout (value) date.
</ResponseField>

<ResponseField name="first" type="Int">
  Forward pagination: returns the first N items (max 100, default 25). Use with `after`; mutually exclusive with `last`/`before`.
</ResponseField>

<ResponseField name="last" type="Int">
  Backward pagination: returns the last N items (max 100, default 25). Use with `before`; mutually exclusive with `first`/`after`.
</ResponseField>

## Returns

<ResponseField name="payouts" type={<a href="/docs/api-reference/v3/pagination">PayoutConnection!</a>} required>
  A paginated list of Payout items.

  <Expandable title="fields" lazyRender>
    <ResponseField name="edges" type={<a href="/docs/api-reference/v3/pagination">[PayoutEdge!]!</a>} required>
      The list of edges (each a node plus its pagination `cursor`).

      <Expandable title="fields" lazyRender>
        <ResponseField name="cursor" type="String!" required>
          Opaque cursor for this item; pass to `after`/`before` to page from here.
        </ResponseField>

        <ResponseField name="node" type={<a href="/docs/api-reference/v3/reference/payments/payout">Payout!</a>} required>
          The item at this edge.

          <Expandable title="fields" lazyRender>
            <ResponseField name="amount" type={<a href="/docs/api-reference/v3/reference/common/money">Money!</a>} required>
              Amount of the payout. Positive for both deposits and reversals.
            </ResponseField>

            <ResponseField name="confirmedAt" type={<a href="/docs/api-reference/v3/reference/common/date-time">DateTime</a>}>
              When the payout report confirmed this payout, as a UTC instant. Null until the report lands.
            </ResponseField>

            <ResponseField name="createdAt" type={<a href="/docs/api-reference/v3/reference/common/date-time">DateTime</a>}>
              When the payout was created, as a UTC instant.
            </ResponseField>

            <ResponseField name="date" type={<a href="/docs/api-reference/v3/reference/common/date">Date</a>}>
              Banking value date of the payout (YYYY-MM-DD): the date the deposit is valued, not the order date.
            </ResponseField>

            <ResponseField name="estimatedArrivalDate" type={<a href="/docs/api-reference/v3/reference/common/date">Date</a>}>
              Estimated calendar date the funds arrive at the bank.
            </ResponseField>

            <ResponseField name="id" type="ID!" required>
              Opaque id of the payout. Pass it to `payoutBreakdown` for the per-order lines.
            </ResponseField>

            <ResponseField name="status" type={<a href="/docs/api-reference/v3/reference/payments/payout-status">PayoutStatus!</a>} required>
              Settlement status of the payout.
            </ResponseField>

            <ResponseField name="type" type={<a href="/docs/api-reference/v3/reference/payments/payout-type">PayoutType!</a>} required>
              Whether this row is a deposit or a reversal.
            </ResponseField>
          </Expandable>
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="nodes" type={<a href="/docs/api-reference/v3/reference/payments/payout">[Payout!]!</a>} required>
      The nodes in this page, without the edge/cursor wrapper — a convenience over `edges`.

      <Expandable title="fields" lazyRender>
        <ResponseField name="amount" type={<a href="/docs/api-reference/v3/reference/common/money">Money!</a>} required>
          Amount of the payout. Positive for both deposits and reversals.

          <Expandable title="fields" lazyRender>
            <ResponseField name="amount" type={<a href="/docs/api-reference/v3/reference/common/decimal">Decimal!</a>} required>
              The exact amount as a decimal string (e.g. "19.99").
            </ResponseField>

            <ResponseField name="currency" type="String!" required>
              ISO 4217 currency code (e.g. USD).
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="confirmedAt" type={<a href="/docs/api-reference/v3/reference/common/date-time">DateTime</a>}>
          When the payout report confirmed this payout, as a UTC instant. Null until the report lands.
        </ResponseField>

        <ResponseField name="createdAt" type={<a href="/docs/api-reference/v3/reference/common/date-time">DateTime</a>}>
          When the payout was created, as a UTC instant.
        </ResponseField>

        <ResponseField name="date" type={<a href="/docs/api-reference/v3/reference/common/date">Date</a>}>
          Banking value date of the payout (YYYY-MM-DD): the date the deposit is valued, not the order date.
        </ResponseField>

        <ResponseField name="estimatedArrivalDate" type={<a href="/docs/api-reference/v3/reference/common/date">Date</a>}>
          Estimated calendar date the funds arrive at the bank.
        </ResponseField>

        <ResponseField name="id" type="ID!" required>
          Opaque id of the payout. Pass it to `payoutBreakdown` for the per-order lines.
        </ResponseField>

        <ResponseField name="status" type={<a href="/docs/api-reference/v3/reference/payments/payout-status">PayoutStatus!</a>} required>
          Settlement status of the payout.
        </ResponseField>

        <ResponseField name="type" type={<a href="/docs/api-reference/v3/reference/payments/payout-type">PayoutType!</a>} required>
          Whether this row is a deposit or a reversal.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="pageInfo" type={<a href="/docs/api-reference/v3/pagination">PageInfo!</a>} required>
      Pagination metadata for the current page.

      <Expandable title="fields" lazyRender>
        <ResponseField name="endCursor" type="String">
          Cursor of the last edge in this page; pass to `after` to page forward.
        </ResponseField>

        <ResponseField name="hasNextPage" type="Boolean!" required>
          Whether more items exist after this page (drives forward pagination with `first`/`after`).
        </ResponseField>

        <ResponseField name="hasPreviousPage" type="Boolean!" required>
          Whether more items exist before this page (drives backward pagination with `last`/`before`).
        </ResponseField>

        <ResponseField name="startCursor" type="String">
          Cursor of the first edge in this page; pass to `before` to page backward.
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Expandable>
</ResponseField>

## Example

```graphql theme={null}
query {
  payouts(after: "...", before: "...", dateFrom: "...", dateTo: "...", first: 10, last: 10) {
    nodes {
      confirmedAt
      createdAt
      date
      estimatedArrivalDate
      id
      status
      type
    }
    pageInfo { hasNextPage endCursor }
  }
}
```


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