Skip to main content
POST
Cancel a scheduled Pix payment

Autorizações

Authorization
string
header
obrigatório

JWT bearer token issued by the identity provider.

Cabeçalhos

X-Idempotency
string
obrigatório

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.

Required string length: 1 - 64

Parâmetros de caminho

schedule_id
string
obrigatório

Schedule identifier.

Exemplo:

"019606a1-3b4c-7d8e-9f01-234567890abc"

Resposta

OK

accountId
string
obrigatório

Payer account.

Exemplo:

"019606a1-3b4c-7d8e-9f01-234567890abc"

amount
string
obrigatório

Amount to settle, in BRL.

Exemplo:

"150.00"

attempts
object[] | null
obrigatório

Every attempt of the scheduled day, oldest first. Empty before that date, and never null.

cancellationCutoff
string<date-time>
obrigatório

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.

createdAt
string<date-time>
obrigatório
currency
string
obrigatório

Always BRL.

Exemplo:

"BRL"

destination
object
obrigatório

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.

firstWindowOpensAt
string<date-time>
obrigatório

When the first settlement window of the scheduled date opens (IN 513 art. 12 caput). Photographed at creation.

id
string
obrigatório

Schedule identifier.

Exemplo:

"019606a1-3b4c-7d8e-9f01-234567890abc"

initiationType
enum<string>
obrigatório

How the destination was resolved.

Opções disponíveis:
MANUAL,
DICT,
QR_CODE
Exemplo:

"DICT"

purpose
enum<string>
obrigatório

Always IPAY: REG-Art.11-P prohibits scheduling any other purpose.

Opções disponíveis:
IPAY
Exemplo:

"IPAY"

scheduledDate
string<date>
obrigatório

Civil settlement date in AAAA-MM-DD, in America/Sao_Paulo.

Exemplo:

"2026-09-10"

source
object
obrigatório

The payer as photographed at creation.

status
enum<string>
obrigatório

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.

Opções disponíveis:
PENDING,
EXECUTING,
DISPATCHED_OUTCOME_UNKNOWN,
AWAITING_RETRY,
SETTLED,
CANCELLED,
FAILED
Exemplo:

"PENDING"

updatedAt
string<date-time>
obrigatório
cancelledReason
enum<string>

Present exactly when status is CANCELLED. A cancellation the payer asked for and one the domain performed are deliberately distinguishable.

Opções disponíveis:
USER_REQUEST,
OWNERSHIP_MISMATCH,
KEY_NOT_FOUND,
RECURRENCE_CANCELLED
description
string

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.

Exemplo:

"Aluguel de setembro"

transferId
string

The transfer that settled this schedule, once it has.