Read rediscount operation status
Reads the lifecycle of a commanded rediscount by its operation id. PENDING until BACEN answers, then one of five states — and the distinction between two of them is the point of this read. ACCEPTED means BACEN registered the request and Selic is HOLDING it because the institution is short of securities: it is neither settled nor failed, no money moved, and the end-of-day sweep may still cancel it or roll it into one business day. SETTLED means a Reservas Bancárias entry exists, evidenced by the numCtrlSTR BACEN stamped, and it is deliberately NOT terminal — a settled rediscount is still an open borrowing until it is repaid, converted or swept. A payment response also reports the remaining balance BACEN sent, verbatim: Lerian SPB never derives it by subtracting a payment from a contract.
Authorizations
JWT bearer token issued by the identity provider.
Path Parameters
Rediscount operation UUID returned by the create endpoint.
Response
OK
Commanded amount, verbatim.
"1500000.00"
Request-scoped correlation identifier echoing X-Request-ID.
"req-7a3f9c2e"
Rediscount operation UUID.
"9f1c2d3e-4b5a-6c7d-8e9f-0a1b2c3d4e5f"
Operator-facing command kind.
"contract"
BACEN business date (DtMovto) the frame was sent for.
"2026-06-15"
Selic operation number this frame carried.
"000123"
Lifecycle state. PENDING = submitted, nothing heard. ACCEPTED = BACEN took the request and Selic is HOLDING it for want of securities — registered, NOT settled, no settlement fact emitted. SETTLED = a Reservas Bancárias entry exists (numCtrlSTR proves it). REJECTED = BACEN refused it. CANCELLED = withdrawn, or swept at STR close. CONVERTED = liquidated by a conversion, or rolled into one business day by the end-of-day sweep. SETTLED is deliberately NOT terminal: a settled rediscount is still an open borrowing until it is repaid.
PENDING, ACCEPTED, SETTLED, REJECTED, CANCELLED, CONVERTED "ACCEPTED"
RDC message code that was put on the wire.
"RDC0002"
BACEN's own situation timestamp (DtHrSit), verbatim as the wire spells it. Deliberately not parsed: BACEN's clock and this deployment's are two different facts.
"2026-06-15T09:30:00"
SFN operation number of the transmitted frame. Empty when the submit failed.
^[0-9A-Z]{8}[0-9]{15}$"12345678202606150000014"
Handle BACEN minted for this operation. Every later message quotes it as originalHandle.
"RDC20260615000000001"
Settlement reference BACEN sent. Its ABSENCE on an accepted operation is the pending state, not a missing field: a SETTLED operation always carries it, because it is the only evidence a Reservas Bancárias entry exists.
"STR20260615000001"
BACEN handle of the operation this command acted on. Empty on a contract.
"RDC20260615000000001"
Operator-facing reason the operation went REJECTED.
Remaining balance (SldAtl) BACEN REPORTED on a payment response, verbatim as text. Never derived by subtracting a payment from a contract. The operation stays open until it reaches zero.
"500000.00"
RFC3339 UTC timestamp this deployment projected the terminal answer — a freshness stamp, never a BACEN fact.
"2026-06-15T12:30:01Z"
BACEN situation code (SitLancRDC), verbatim.
"16"
Set when a conversion liquidated this operation: the id of the replacement that superseded it.

