Retrieve the individual lines for a wallet statement.
Each line represents a single transaction that affected the wallet balance during the statement period, including the line type, amount, and running balance after the line.
⚠️ Statement Must Be Ready
This endpoint can only be called when the statement state is READY. If the statement is still being processed (PENDING) or has failed (FAILED), an HTTP 409 Conflict error will be returned.
You can check the statement state using the Get Statement endpoint before calling this endpoint.
📋 Line Types
Each statement line includes a type field indicating the nature of the transaction:
| Type | Description |
|---|---|
COLLECTION_COLLECTED | Funds collected into the wallet |
COLLECTION_CONVERTED | Collected funds converted to wallet currency |
CONVERSION_INITIATED | Currency conversion initiated |
CONVERSION_CONVERTED | Currency conversion completed |
PAYOUT_INITIATED | Payout initiated from wallet (debit) |
PAYOUT_FAILED | Payout failed, funds returned to wallet (credit) |
PAYOUT_REVERSED | Payout reversed, funds returned to wallet (credit) |
PAYOUT_SENT_TO_FAILED | Previously sent payout moved to failed state |
PAYOUT_FAILED_TO_SENT | Previously failed payout moved to sent state |
🔗 Resource References
Where applicable, each line includes a resource object with references to the associated transaction (e.g., payout ID, collection ID). This allows you to cross-reference statement lines with other API resources.
📄 Pagination
Results are paginated. Use the paging_limit parameter to control how many lines are returned per request (default and maximum vary by configuration). Use the paging_after cursor from the response metadata to fetch subsequent pages.