Skip to main content
GET
Read one scheduled Pix payment

Authorizations

Authorization
string
header
required

JWT bearer token issued by the identity provider.

Path Parameters

schedule_id
string
required

Schedule identifier.

Example:

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

Response

OK

accountId
string
required

Payer account.

Example:

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

amount
string
required

Amount to settle, in BRL.

Example:

"150.00"

attempts
object[] | null
required

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

cancellationCutoff
string<date-time>
required

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

Always BRL.

Example:

"BRL"

destination
object
required

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

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

id
string
required

Schedule identifier.

Example:

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

initiationType
enum<string>
required

How the destination was resolved.

Available options:
MANUAL,
DICT,
QR_CODE
Example:

"DICT"

purpose
enum<string>
required

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

Available options:
IPAY
Example:

"IPAY"

scheduledDate
string<date>
required

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

Example:

"2026-09-10"

source
object
required

The payer as photographed at creation.

status
enum<string>
required

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.

Available options:
PENDING,
EXECUTING,
DISPATCHED_OUTCOME_UNKNOWN,
AWAITING_RETRY,
SETTLED,
CANCELLED,
FAILED
Example:

"PENDING"

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

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

Available options:
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.

Example:

"Aluguel de setembro"

transferId
string

The transfer that settled this schedule, once it has.