> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # 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. ## OpenAPI ````yaml /en/openapi/v3-current/spb.yaml get /v1/str/operations/rediscounts/{operationId} openapi: 3.1.0 info: contact: email: contact@lerian.studio name: Lerian Studio url: https://lerian.studio description: >- OpenAPI 3.1 surface for Lerian SPB, the direct integration between the institution and the Brazilian Payment System (SPB) over the National Financial System Network (RSFN). It covers the Reserve Transfer System (STR): message registry and capability catalog, operation lifecycle (bank transfers, IBS repasses, liquidity transfers, returns and cancellations), reserve-account and schedule queries, alçada governance, SME and LDL operations, inbound quarantine triage, reconciliation, and event delivery. license: name: Lerian Studio General License title: Lerian SPB API version: 1.0.0 servers: - url: https://spb.sandbox.lerian.net security: [] tags: - description: Immutable audit-record trails for STR operations and lifecycle events. name: Audit - description: >- STR capability catalog describing supported message types and their constraints. name: Capabilities - description: >- ICP-Brasil certificate inventory with hot-reloadable rotation and activation. name: Certificates - description: >- STR compulsory-movement (RCO) family: the movements BACEN orders on a participant's reserve account, their answers and the periods they belong to. name: Compulsory - description: >- Maker-checker approval queue for emissions parked above their alçada band: list pending, sign (approve), and deny. name: EmissionApprovals - description: Webhook event-delivery records with retry control for failed dispatches. name: EventDeliveries - description: Operation event catalog enumerating the emitted domain event types. name: Events - description: >- Inbound GEN-family notice log (GEN0001 connectivity echo, GEN0004 transmission error, GEN0005 administrative notice). name: GenNotices - description: >- SPB alçada governance config: value-band table + per-message-type signature requirements, hot-reloaded at runtime. name: Governance - description: >- Read raw STR message status: list messages and read a single message by NUOp. name: Messages - description: Aggregated operational summaries and metrics across STR operations. name: OperationalIntelligence - description: >- STR operation lifecycle for bank transfers and IBS repasses, including returns and cancellations. name: Operations - description: >- Service readiness state covering startup self-probes and dependency health. name: Readiness - description: Reconciliation cases and the actions that resolve operation discrepancies. name: Reconciliation - description: >- Redesconto do Banco Central: collateralised intraday and one-business-day BCB lending against Selic-registered federal securities. One create door derives the nine RDC commands from four operator-facing kinds (contract, payment, conversion, cancellation), plus the two consultas over eligible-security prices and open positions. An accepted rediscount is not necessarily a settled one — Selic may hold the request for want of securities, and that middle state is reported as its own. name: Rediscounts - description: >- STR Relatórios suite: synchronous, date-ranged aggregate reports (movimento financeiro, transações rejeitadas, volumetria) over Lerian SPB's own transmission record. name: Reports - description: >- STR0013 reserve-account balance and STR0014 statement (extrato, message-mode) queries and their async results. name: ReserveQueries - description: >- GEN0019 participant responsável roster: full-replacement updates announced to BACEN. name: Responsibles - description: STR operating-window schedule governing when operations may be sent. name: Schedule - description: >- STR0001 single-party schedule queries (consulta de horários do STR) and their async STR0001R1 grid results. name: ScheduleQueries - description: >- STR lançamentos (SLB) family: the charges BACEN raises against this participant, the payments that settle them, payments to BACEN it never demanded, and the entry consultas over them. name: SLB - description: >- Reads over an IEME's conta correspondente a moeda eletrônica (CCME): SME0003 statement (extrato) queries and their async SME0003R1 results, plus the log of SME0001R2/SME0002R2/SME0004R2 movement advices the STR delivered about movements this rail did not command. name: SMEQueries - description: Runtime SPB configuration settings for the STR integration. name: Settings - description: Webhook endpoint registration and management for event delivery. name: Webhooks - description: >- Flow (mandatory order): certificate → readiness → connectivity-test → submit. Activate a certificate, confirm the rail reports ready, pass a connectivity test, then submit an operation. Each step is its own resource; a submit must not be attempted before readiness passes. name: onboarding - description: >- Flow (mandatory order): parent operation SETTLED → return/cancel. A return or cancellation is a sub-resource of a settled parent operation; the {operationId}/{endToEndID} path segment enforces the parent structurally. name: lifecycle paths: /v1/str/operations/rediscounts/{operationId}: get: tags: - Rediscounts summary: Read rediscount operation status description: >- 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. operationId: getRediscount parameters: - description: Rediscount operation UUID returned by the create endpoint. in: path name: operationId required: true schema: description: Rediscount operation UUID returned by the create endpoint. format: uuid type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/RediscountStatusResponse' description: OK '401': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Unauthorized '403': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Forbidden '404': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Not Found '422': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Unprocessable Entity '429': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Too Many Requests '500': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Internal Server Error '503': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Service Unavailable default: content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Error security: - BearerAuth: [] components: schemas: RediscountStatusResponse: additionalProperties: false properties: amount: description: Commanded amount, verbatim. examples: - '1500000.00' type: string bacenStatusAt: description: >- 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. examples: - '2026-06-15T09:30:00' type: string correlationId: description: Request-scoped correlation identifier echoing X-Request-ID. examples: - req-7a3f9c2e type: string id: description: Rediscount operation UUID. examples: - 9f1c2d3e-4b5a-6c7d-8e9f-0a1b2c3d4e5f format: uuid type: string kind: description: Operator-facing command kind. examples: - contract type: string movementDate: description: BACEN business date (DtMovto) the frame was sent for. examples: - '2026-06-15' type: string nuOp: description: >- SFN operation number of the transmitted frame. Empty when the submit failed. examples: - '12345678202606150000014' pattern: ^[0-9A-Z]{8}[0-9]{15}$ type: string numCtrlRDC: description: >- Handle BACEN minted for this operation. Every later message quotes it as originalHandle. examples: - RDC20260615000000001 type: string numCtrlSTR: description: >- 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. examples: - STR20260615000001 type: string originalHandle: description: >- BACEN handle of the operation this command acted on. Empty on a contract. examples: - RDC20260615000000001 type: string rejectionReason: description: Operator-facing reason the operation went REJECTED. type: string remainingBalance: description: >- 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. examples: - '500000.00' type: string selicOperation: description: Selic operation number this frame carried. examples: - '000123' type: string settledAt: description: >- RFC3339 UTC timestamp this deployment projected the terminal answer — a freshness stamp, never a BACEN fact. examples: - '2026-06-15T12:30:01Z' format: date-time type: string sitLancRDC: description: BACEN situation code (SitLancRDC), verbatim. examples: - '16' type: string status: description: >- 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. enum: - PENDING - ACCEPTED - SETTLED - REJECTED - CANCELLED - CONVERTED examples: - ACCEPTED type: string supersededById: description: >- Set when a conversion liquidated this operation: the id of the replacement that superseded it. format: uuid type: string wireCode: description: RDC message code that was put on the wire. examples: - RDC0002 type: string required: - id - kind - wireCode - status - amount - selicOperation - movementDate - correlationId type: object Detail: additionalProperties: false properties: code: description: >- Stable, machine-readable domain error code scoped to the emitting service (format: -NNNN). type: string correlationId: description: Request-scoped correlation identifier echoing X-Request-ID. examples: - req-7a3f9c2e type: string detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string errors: description: Optional list of individual error details items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string upstream: $ref: '#/components/schemas/Upstream' description: >- RFC 9457 extension member: the error a proxied third-party provider reported. Absent unless the emitting service explicitly surfaced one. required: - correlationId type: object ErrorDetail: additionalProperties: false properties: location: description: >- Where the error occurred, e.g. 'body.items[3].tags' or 'path.thing-id' type: string message: description: Error message text type: string value: description: The value at the given location type: object Upstream: additionalProperties: false properties: code: description: The upstream provider's own error code, verbatim. examples: - E4001 type: string message: description: >- The upstream provider's own error message, verbatim (bounded, never its raw response body). examples: - account not found at provider type: string type: object securitySchemes: BearerAuth: bearerFormat: JWT description: JWT bearer token issued by the identity provider. scheme: bearer type: http ````