List Payments
Intent
Reads the available payments as a pageable collection without changing them.
When to call it
Call this when an interface, sync, or support workflow needs to inspect payments. Use the filters and paging controls shown below to limit the result.
Access boundary
Authorize the request with a token that carries payments:read.
Successful result
A successful request returns 200. The response schema below defines the body your integration receives.
Operational notes
List payments.
Scopes: payments:read
Authorizations
Query Parameters
Filter by organization ID. The organization ID.
"1dbfc517-0bbf-4301-9ba8-555ca42b9737"
Filter by checkout ID.
Filter by order ID.
Filter by customer ID. The customer ID.
Filter by payment status.
pending, succeeded, failed Filter by payment method.
Filter by customer email.
Page number, defaults to 1.
Size of a page, defaults to 10. Maximum is 100.
Sorting criterion. Several criteria can be used simultaneously and will be applied in order. Add a minus sign - before the criteria name to sort by descending order.
created_at, -created_at, status, -status, amount, -amount, method, -method