/v1.0/merchants/{merchant_code}/payoutsLists payout and payout-deduction records for the specified merchant account within the requested date range.
The response can include:
- regular payouts (
type = PAYOUT) - deduction records for refunds, chargebacks, direct debit returns, or balance adjustments
Results are sorted by payout date in the requested order.
OAuth scopes: Requires one of: user.profile, user.profile_readonly, payouts.read.
Path parameters
Short unique identifier for the merchant.
Example:
"MH4H92C7"
Query parameters
- format:
dateStart date of the payout period filter, inclusive, in ISO8601
dateformat (YYYY-MM-DD).Example:
"2024-02-01" - format:
dateEnd date of the payout period filter, inclusive, in ISO8601
dateformat (YYYY-MM-DD). Must be greater than or equal tostart_date.Example:
"2024-02-29" - formatstringOptions:
"json""csv"default:"json"Response format for the payout list.
Example:
"json" - limitintegerminimum:
1maximum:9999Maximum number of payout records to return.
Example:
10 - orderstringOptions:
"asc""desc"default:"asc"Sort direction for the returned payouts.
Example:
"desc"
Responses
200application/json
Returns the list of payout and deduction records for the requested period.
- format:
int64Unique identifier of the payout-related record.
Example:
123456789 - Options:
"PAYOUT""CHARGE_BACK_DEDUCTION""REFUND_DEDUCTION""DD_RETURN_DEDUCTION""BALANCE_DEDUCTION"High-level payout record category.
Example:
"PAYOUT" - format:
floatAmount of the payout or deduction in major units.
Example:
132.45 - format:
datePayout date associated with the record, in
YYYY-MM-DDformat.Example:
"2024-02-29" Three-letter ISO 4217 currency code of the payout.
Example:
"EUR"- format:
floatFee amount associated with the payout record, in major units.
Example:
3.12 - Options:
"SUCCESSFUL""FAILED"Merchant-facing outcome of the payout record.
Example:
"SUCCESSFUL" Processor or payout reference associated with the record.
Example:
"payout-2024-02-29"Transaction code of the original sale associated with the payout or deduction.
Example:
"TEENSK4W2K"
text/plain
id,type,amount,date,currency,fee,status,reference,transaction_code
123456789,PAYOUT,132.45,2024-02-29,EUR,3.12,SUCCESSFUL,payout-2024-02-29,TEENSK4W2K400application/json
The request is invalid for the submitted query parameters.
- messagestring
Short description of the error.
Example:
"Resource not found" - error_codestring
Platform code for the error.
Example:
"NOT_FOUND" - paramstring
Parameter name (with relative location) to which the error applies. Parameters from embedded resources are displayed using dot notation. For example,
card.namerefers to thenameparameter embedded in thecardobject.Example:
"card.name"
401application/json
The request is not authorized.
- format:
uriA URI reference that identifies the problem type.
Example:
"https://developer.sumup.com/problem/not-found" - titlestring
A short, human-readable summary of the problem type.
Example:
"Requested resource couldn't be found." - statusinteger
The HTTP status code generated by the origin server for this occurrence of the problem.
Example:
404 - detailstring
A human-readable explanation specific to this occurrence of the problem.
Example:
"The requested resource doesn't exist or does not belong to you." - instancestringformat:
uriA URI reference that identifies the specific occurrence of the problem.
Example:
"https://api.sumup.com/v0.1/checkouts/4e425463-3e1b-431d-83fa-1e51c2925e99"