Skip to content

List processed scheduled payments​

GET
/v2/payments/collect/history

Requires COLLECTIONS_READ, granted by PAYMENTS_READ or COLLECTIONS_WRITE (bundles)

Returns payments that scheduled payout runs have picked up (processing, completed or failed), newest first, across every payout schedule in your business.

Parameters​

Query Parameters

currency

Only include schedules that pay out in this currency. Use the upper-case code, e.g. USDC.

Type
string
Example"USDC"
limit

Maximum number of payments to return.

Type
integer
Example50
Default
50
offset

Number of payments to skip, for paging.

Type
integer
Example0
Default
0

Responses​

OK

application/json
JSON
{
"items": [
{
"id": "2e4a6c8b-0d1f-4a3c-9e5b-7d9f1b3a5c7e",
"withdrawalCurrency": "USDC",
"withdrawalAmount": "82.45",
"receivedAt": 1792660600000,
"status": "COMPLETED",
"depositCurrency": "ZAR",
"depositAmount": "1500.00",
"payerName": "Thandi Nkosi",
"reference": "VLR4F7K2Q9",
"timeline": null
}
],
"total": 1,
"limit": 50,
"offset": 0
}

Samples​

Errors

HTTPErrorWhen
400BAD_REQUESTA query parameter or field is invalid.
403-16098PAYMENTS_USER_ACCESS_NOT_CONFIGUREDPayments haven't been set up for your business yet.
500INTERNAL_ERRORUnexpected error in the payments service.
502-16097EXCHANGE_API_ERRORThe payments service failed to process the request.
502EXCHANGE_API_ERRORThe payments service couldn't complete the request. Try again later.
503-16099PAYMENTS_BACKEND_PROXY_DISABLEDPayments endpoints are temporarily unavailable.

Plus the errors common to all signed endpoints.