Conta

Balance statement: ledger entries or grouped operations

Use visao=operacoes for end-user activity: one signed total per operation and a single nested fee (tipo=servico, descricao=Taxa), including the PIX tariff and all fee components. Refunds remain separate. Group before pagination and deduplicate notifications by origem_id and tipo, never by accounting fee entries. Never present debits/fees as income or subtract fees again. Projects configured for consolidated presentation also receive this view by default; visao=movimentos explicitly selects the accounting view for backend reconciliation. Other projects retain individual accounting entries by default. Sandbox follows the same behavior. Internal fee ownership and component fields must not be forwarded to end-user notifications. See https://docs.luniumpay.com/en/manual.html#extrato-por-operacao.

get/saldo/extrato

Request

  • Base URL: https://api.luniumpay.com
  • URL: https://api.luniumpay.com/saldo/extrato
  • Auth: API key in header X-API-Key

Query parameters

customer_refstring
limitinteger
visao'lancamentos' | 'operacoes'

operacoes groups related fees inside the operation; omission preserves the raw ledger contract.

beforestring

Use proxima_pagina from the same view and customer_ref. Decimal bigint string; do not convert to Number. Grouped view anchors to the earliest ledger ID.

Response

OK

proxima_paginastring nullable
visao'operacoes'

Only present for grouped view.

has_moreboolean

Grouped view: whether another page exists. Cursor is null on the last page.

Changes

No recorded changes to this operation across all 3 revisions of this API.