Cancel a scheduled Pix payment
Cancels a schedule at the payer’s request, accepted right up to the cancellation cut-off recorded on it and refused AT that instant. The deadline compared against is the one photographed when the schedule was created, not whatever the configuration derives today: the deadline the payer was told is the deadline they get. Because the cut-off is strictly before the first settlement window, cancelling and executing can never both be in time. Nothing is released — nothing was held.
Autorizaciones
JWT bearer token issued by the identity provider.
Encabezados
REQUIRED. Client-supplied replay key, at most 64 bytes. A request without it is refused with PIX-0030 @ 400 before the handler runs. Replaying the same key with a divergent method, URL or body is PIX-0031 @ 412.
1 - 64Parámetros de ruta
Schedule identifier.
"019606a1-3b4c-7d8e-9f01-234567890abc"
Respuesta
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 the scheduled date this is compared against a fresh directory answer (REG-Art.9§6), which is why it is stored rather than re-resolved.
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.
USER_REQUEST, OWNERSHIP_MISMATCH, KEY_NOT_FOUND, 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 (RF-16); escaping belongs to whoever renders it.
"Aluguel de setembro"
The transfer that settled this schedule, once it has.

