Skip to main content
POST
Register a scheduled Pix payment

Autorizaciones

Authorization
string
header
requerido

JWT bearer token issued by the identity provider.

Encabezados

X-Idempotency
string
requerido

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

Cuerpo

application/json
accountId
string
requerido

Payer account UUID.

Ejemplo:

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

amount
string
requerido

Amount to settle, in BRL with two decimals. The available balance is NOT touched at creation (RF-07).

Ejemplo:

"150.00"

initiationType
enum<string>
requerido

How the destination is resolved. DICT reads the directory and requires payeeKey; MANUAL requires destination. QR_CODE is published but not yet accepted on this route.

Opciones disponibles:
MANUAL,
DICT,
QR_CODE
Ejemplo:

"DICT"

scheduledDate
string<date>
requerido

Civil settlement date in AAAA-MM-DD, evaluated in America/Sao_Paulo. Never an instant: a date that is still today in UTC can already be yesterday here. Non-business days are accepted -- Pix settles every day.

Ejemplo:

"2026-09-10"

currency
enum<string>

Always BRL. Present for forward compatibility only.

Opciones disponibles:
BRL
Ejemplo:

"BRL"

description
string

Free-text memo, at most 140 characters -- the RmtInf ceiling. Stored and returned VERBATIM: markup is not interpreted, escaped or stripped, and escaping belongs to whoever renders it (RF-16).

Ejemplo:

"Aluguel de setembro"

destination
object

The payee's account and owner. Required when initiationType is MANUAL.

payeeKey
object

The Pix key to resolve. Required when initiationType is DICT.

purpose
enum<string>

Only IPAY can be scheduled. Pix Saque (OTHR) and Pix Troco (GSCB) are point-in-time operations and REG-Art.11-P prohibits scheduling them, so they are refused at creation rather than on the scheduled date.

Opciones disponibles:
IPAY
Ejemplo:

"IPAY"

Respuesta

Created

accountId
string
requerido

Payer account.

Ejemplo:

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

amount
string
requerido

Amount to settle, in BRL.

Ejemplo:

"150.00"

attempts
object[] | null
requerido

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

cancellationCutoff
string<date-time>
requerido

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>
requerido
currency
string
requerido

Always BRL.

Ejemplo:

"BRL"

destination
object
requerido

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>
requerido

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

id
string
requerido

Schedule identifier.

Ejemplo:

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

initiationType
enum<string>
requerido

How the destination was resolved.

Opciones disponibles:
MANUAL,
DICT,
QR_CODE
Ejemplo:

"DICT"

purpose
enum<string>
requerido

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

Opciones disponibles:
IPAY
Ejemplo:

"IPAY"

scheduledDate
string<date>
requerido

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

Ejemplo:

"2026-09-10"

source
object
requerido

The payer as photographed at creation.

status
enum<string>
requerido

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.

Opciones disponibles:
PENDING,
EXECUTING,
DISPATCHED_OUTCOME_UNKNOWN,
AWAITING_RETRY,
SETTLED,
CANCELLED,
FAILED
Ejemplo:

"PENDING"

updatedAt
string<date-time>
requerido
cancelledReason
enum<string>

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

Opciones disponibles:
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.

Ejemplo:

"Aluguel de setembro"

transferId
string

The transfer that settled this schedule, once it has.