> ## Documentation Index
> Fetch the complete documentation index at: https://docs.planewallet.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Account statements and transactions

> Reconcile card account movements independently from card purchases.

## Account statement

`GET /api/v1/account-statements?from=2026-09-01&to=2026-09-30` requires `balance:read`. Dates are inclusive UTC calendar dates. The maximum range is 366 days and 10,000 ledger rows. Reduce the range if it exceeds the limit.

The response includes opening and closing balances, incoming and outgoing amounts and ordered entries with running balances. Deposits and the 1.5% account fee appear separately. Reservations have zero net movement; captured operations reduce the account balance. A consistent database snapshot is used for all totals.

The console provides a CSV export with the same period and ledger totals. A card-account statement does not include the on-chain wallet balance or treat card purchases as another debit from the card account.

## Card payment transactions

`GET /api/v1/transactions` requires `operations:read`. Use optional `cardId` and `before` filters. The response returns up to 100 records and a `nextCursor`; pass that value as `before` for the next page. `GET /api/v1/transactions/{id}` returns one scoped transaction.

Records come from the issuing provider and include type, status, amount, currency, merchant, country and occurrence time. The provider-reported amount is retained; interpret its direction with the transaction type, including refunds and reversals. Sync is asynchronous and is not a real-time authorization stream.

Card issuance and top-ups remain available through `/operations`. The console combines those operations, account deposits and card payments for navigation while keeping their accounting sources separate.