Skip to main content
The payment history endpoint returns a paginated list of all payment sessions on the FlareHQ ledger, ordered from most recent to oldest. It is intended for building dashboards, generating settlement reports, and reconciling USDC volumes. Unlike the verify endpoint which targets a single payment by reference, this endpoint returns aggregate metrics alongside the transaction list, making it easy to calculate total processed volume and outstanding balances in a single request.

Endpoint

Request

Headers

Query Parameters

number
default:"20"
Maximum number of payment records to return in a single response. Accepted range: 1100. Use in combination with offset to paginate through large result sets.
number
default:"0"
Number of records to skip before returning results. Use this with limit for cursor-style pagination. For example, to fetch the second page of 20 results, set offset=20&limit=20.
string
Filter results to payments in a specific state. Accepted values:Omit this parameter to return payments in all states.
string
ISO 8601 date-time string. Only payments created at or after this timestamp are returned. Example: 2025-01-01T00:00:00Z.
string
ISO 8601 date-time string. Only payments created before or at this timestamp are returned. Example: 2025-01-31T23:59:59Z. Use together with from to define a reporting window.

Response

boolean
true when the request completed without error.
object
Aggregate statistics computed across the returned ledger snapshot.
array
Ordered list of payment records (newest first). Each element represents a single payment session.
number
Total number of matching records across all pages (accounting for any status, from, or to filters). Use this value with limit and offset to calculate total page count.
boolean
true if there are additional records beyond the current page — i.e. offset + limit < total. Use this flag to drive “Load more” or infinite-scroll pagination in your UI.

Examples

Response — Success

Error Response

Notes

The history endpoint fetches up to the latest 50 records in a single pass when no limit is specified. Pass an explicit limit and offset to implement paginated views. Use hasMore and total to drive pagination UI controls.
Combine from and to filters with status=SUCCESS to generate accurate settlement reports for a given accounting period. The metrics.totalVolumeProcessed field in the response is pre-computed for you, so you do not need to sum the amount field of each transaction manually.
PENDING sessions that have passed their 120-minute expiry window may still appear as PENDING in the raw results. If you need accurate EXPIRED counts, compare each PENDING record’s timestamp against the current time plus 120 minutes and treat those as expired on your end.