Read one scheduled Pix payment
Returns the schedule together with every attempt of its scheduled day, oldest first. The list is empty and never null before that date. A schedule belonging to another organization answers 404 rather than 403: the read is scoped by organization, so the row is never seen, and answering ‘forbidden’ would confirm the identifier exists.
Autorizações
JWT bearer token issued by the identity provider.
Parâmetros de caminho
Schedule identifier.
"019606a1-3b4c-7d8e-9f01-234567890abc"
Resposta
OK
Payer account.
"019606a1-3b4c-7d8e-9f01-234567890abc"
Amount to settle, in BRL.
"150.00"
Every attempt of the scheduled day, oldest first. Empty before that date, and never null.
The first instant a cancellation is REFUSED. Cancellation is accepted right up to it and refused AT it, and it is strictly before the first window so the two can never overlap.
Always BRL.
"BRL"
The payee as photographed at creation. On a DICT schedule it is compared on the scheduled date against a fresh directory answer (REG-Art.9§6), which is why it is stored rather than re-resolved; a MANUAL or QR_CODE schedule is sent to it as photographed, with no second lookup.
When the first settlement window of the scheduled date opens (IN 513 art. 12 caput). Photographed at creation.
Schedule identifier.
"019606a1-3b4c-7d8e-9f01-234567890abc"
How the destination was resolved.
MANUAL, DICT, QR_CODE "DICT"
Always IPAY: REG-Art.11-P prohibits scheduling any other purpose.
IPAY "IPAY"
Civil settlement date in AAAA-MM-DD, in America/Sao_Paulo.
"2026-09-10"
The payer as photographed at creation.
Lifecycle status. DISPATCHED_OUTCOME_UNKNOWN is NOT terminal: the order is awaiting reconciliation and will resolve to SETTLED or FAILED. It does NOT assert that the order reached the rail -- it also covers an order that provably did not, whose reserved funds are still being released.
PENDING, EXECUTING, DISPATCHED_OUTCOME_UNKNOWN, AWAITING_RETRY, SETTLED, CANCELLED, FAILED "PENDING"
Present exactly when status is CANCELLED. A cancellation the payer asked for and one the domain performed are deliberately distinguishable. CHARGE_AMOUNT_CHANGED and CHARGE_NOT_PAYABLE: on the scheduled date the QR charge asked another amount, or the receiver refused reading it (the charge was removed, concluded or expired); nothing was debited. A failed check of the receiver's site or signature cancels nothing: like a receiver that does not answer, it pays the recorded amount.
USER_REQUEST, OWNERSHIP_MISMATCH, KEY_NOT_FOUND, CHARGE_AMOUNT_CHANGED, CHARGE_NOT_PAYABLE, RECURRENCE_CANCELLED The payer's memo, returned exactly as it was stored. Markup is not interpreted here and was not escaped on the way in; escaping belongs to whoever renders it.
"Aluguel de setembro"
The transfer that settled this schedule, once it has.

