Skip to main content
GET
Fetch payout

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

Content-Type
string

Content-Type must be set to application/json

Path Parameters

businessId
string
required

The UUID of the business to fetch the payout for

payoutId
string
required

The UUID of the payout to fetch

Query Parameters

include_deleted
boolean

If this flag is false or not included, requests will 404 if the payout with the given ID was deleted.

Response

id
string<uuid>

Unique ID for the Payout. Idempotency key.

external_id
string | null

Unique ID of the payout in your system for linking purposes.

Example:

"payout-1234"

business_id
string<uuid>

ID of the Business that generated the payout.

paid_out_amount
integer<int64>

The amount of the payout, in cents

fee
integer<int64>

The platform fee associated with the payout

processor
enum<string> | null

Processor used to make the payment, if any. If not null, every payment or refund associated with the payout must have the same processor

Available options:
STRIPE,
PAYPAL,
SHOPIFY,
ADYEN,
RAINFOREST
Example:

"STRIPE"

imported_at
string<date-time>

Timestamp of when the payout was imported

completed_at
string<date-time>

Timestamp of when the payout was completed

match
object

The transaction match associated with the payout

Example:
payments
object[]

A list of invoice payments associated with the payout

refunds
object[]

A list of refunds associated with the payout

transaction_tags
object[]

A list of tags associated with the payout

memo
string | null

Memo for any text you would like to associate with the payout (for example, to display to end users).

metadata
object | null

Arbitrary custom metadata in JSON format with a size limit of 1KB

Example:
reference_number
string | null

Any (typically user-visible) identifier you would like to associate with the payout. Can be used to filter when listing payouts.