---
title: "Retrieve a Stripe payout"
method: GET
path: "/companies/{company}/payouts/{payout}"
tags: ["Stripe"]
---

# Retrieve a Stripe payout

`GET /companies/{company}/payouts/{payout}`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/companies/{company}/payouts/{payout}`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Retrieve a Stripe payout by its `id` (UUID v7). Returns the amounts, currency, arrival date, reconciliation state (`bank_transaction_ref` once reconciled) and the informative `composition` of component charges. Returns 404 if the payout does not exist or belongs to another company.

## Path parameters

- `company` string, uuid, required
- `payout` string, uuid, required

## Headers

- `Factuarea-Version` string, date

## Response `200`

- object
  - `data` StripePayout, required: A Stripe payout ingested from `payout.paid`, together with its bank-reconciliation state. The public `id` is the payout UUID v7. `connected_account_id` (`acct_xxx`) and `stripe_payout_id` (`po_xxx`) are external Stripe ids, not foreign keys. `bank_transaction_ref` is the UUID v7 of the reconciled bank statement transaction (`null` while `status` is `ingested`). `composition` is the informative breakdown reported by Stripe (component charges + fees), referencing opaque Stripe ids — payouts are read-only on the public API; reconciliation happens in the dashboard.
    - `id` string, uuid, required: UUID v7 of the payout. Public identity (KEY `id`).
    - `object` 'stripe_payout', required: Stripe-like discriminator. Always `stripe_payout` for this resource.
    - `connected_account_id` string, required: External Stripe connected account id (`acct_xxx`) the payout was paid out from. NOT an internal UUID nor a foreign key.
    - `stripe_payout_id` string, required: Opaque Stripe payout identifier (`po_xxx`), unique in Stripe.
    - `amount_net` string, required: Net amount transferred to the bank account (gross minus fees), in the payout currency.
    - `fee_total` string, required: Total Stripe fees deducted from the payout.
    - `amount_gross` string, required: Gross amount before fees.
    - `currency` string, required: ISO-4217 currency code of the payout.
    - `arrival_date` string, date, required: Expected arrival date of the payout in the bank account (YYYY-MM-DD).
    - `status` 'ingested' | 'reconciled', required: Reconciliation state. `ingested` once persisted; `reconciled` (terminal) once matched against a bank statement transaction.
    - `reconciled_at` string, date-time, nullable, required: When the payout was reconciled against the bank statement (ISO 8601), or `null` while `ingested`.
    - `bank_transaction_ref` string, uuid, nullable, required: UUID v7 of the reconciled bank statement transaction, or `null` while `ingested`.
    - `composition` object, required: Informative breakdown of the payout reported by Stripe (component charges and fees). Component references are opaque Stripe ids (`payment_intent` = `pi_xxx`, `charge_id` = `ch_xxx`), NOT internal payment UUIDs. May be empty when the breakdown could not be read.
      - `components` object[]
        - `payment_intent` string, nullable
        - `charge_id` string
        - `amount` string: Amount of the component charge, as a 2-decimal string in the payout currency.
        - `fee` string: Fee of the component charge, as a 2-decimal string in the payout currency.
      - `fee_total` string: Sum of the component fees, plus the standalone fees and the fees of the refunds, as a 2-decimal string in the payout currency.
      - `gross_total` string: Sum of the component amounts, as a 2-decimal string in the payout currency.
      - `refunds_total` string: Sum of the refunds settled in the payout (negative), as a 2-decimal string in the payout currency. `"0.00"` when there are none.
      - `standalone_fee_total` string: Sum of the Stripe fees charged on their own, not attached to a charge (such as monthly or currency conversion fees), as a 2-decimal string in the payout currency. Already included in `fee_total`. `"0.00"` when there are none.
      - `other_total` string: Sum of the remaining movements settled in the payout (adjustments, disputes and similar; signed), as a 2-decimal string in the payout currency. `"0.00"` when there are none.

## Other responses

- `400`: `parameter_unknown` with `subcode` `retired_active_profile_header`: the retired `X-Active-Profile` header was sent; the company goes in the path. `parameter_invalid_format` on `Factuarea-Version`: the header is not a `YYYY-MM-DD` date. `unsupported_api_version`: the `Factuarea-Version` date is not a supported version.
- `401`: Missing or invalid API key.
- `403`: The request is authenticated but not allowed: the API key lacks the required scope (`insufficient_scope`), the plan does not include the public API or this feature (`addon_not_active`, `feature_not_available_in_plan`), or the module is not available with a test key (`module_not_available_in_sandbox`).
- `404`: The requested resource does not exist or belongs to another company.
- `429`: Rate limit exceeded. Retry after the duration in `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/factuarea/apis/factuarea-public-api.md) · [All operations](https://skmtc.dev/factuarea/apis/factuarea-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/factuarea/apis/factuarea-public-api/revisions/718e77934422?raw)