status, currency, or a creation date range — and control page size with the limit parameter. Results are returned in reverse chronological order by default, with the most recently created payments first.
Query Parameters
Number of payment records to return per page. Accepts values between
1 and 100. Defaults to 20.Opaque pagination cursor returned in a previous response’s
pagination.cursor field. Pass this value to retrieve the next page of results.Filter payments by their current lifecycle status. Accepted values:
pending, processing, settled, delivered, failed, cancelled.Filter payments by source stablecoin. Accepted values:
USDC, USDT, EURC, PYUSD.Filter payments by corridor identifier (e.g.,
US-EU, US-MX).Return only payments created after this ISO 8601 datetime (e.g.,
2024-01-01T00:00:00Z). The timestamp is inclusive.Return only payments created before this ISO 8601 datetime. The timestamp is exclusive.
Sort order for results based on
created_at. Accepted values: asc, desc. Defaults to desc.Response
An array of payment objects matching your query. Each object has the same structure as a single payment returned by GET /payments/{id}. Returns an empty array if no payments match the filters.
Metadata for navigating through result pages.
Examples
Paginating Through Results
To retrieve subsequent pages, pass thecursor value from the previous response as a query parameter. Continue until pagination.has_more is false.