Create IBS repasse operation
Prerequisite: the rail must be ready before a submit — an active certificate (see rotateCertificate, activateCertificate), a READY readiness report (see getReadiness), and a passing connectivity test (see createConnectivityTest). Accepts a STR0053 IBS-repasse operation (reserve repasse of IBS settlement values to the comitê gestor) through the operation-centric API. The handler translates the JSON request into the STR0053 XML request path, persists the operation aggregate and SUBMITTED outbound relay work, and returns the canonical OperationAccepted envelope. Dispatch was accepted, not BACEN settlement confirmation. Idempotent — replaying the same X-Idempotency key with the same body returns the cached response.
Autorizaciones
JWT bearer token issued by the identity provider.
Encabezados
Idempotency key. Required on every mutation.
Idempotency key TTL in seconds.
Cuerpo
Repasse amount as a decimal string in BRL, minor-unit precision (two decimal places). Canonical form only: exactly two decimal places and no leading integer zeros — the single spelling the durable column stores; anything else is refused at the door with 422.
^(0|[1-9][0-9]*)\.[0-9]{2}$"1500.25"
Financial repasse date in BACEN STR0053 ISO date form (e.g. 2026-06-09).
"2026-06-09"
Financial-repasse identifier the comitê gestor keys the repasse on (required, 1-50 characters). This service mints no value for it: an absent or blank identifier is refused with 422.
1 - 50"REP-2026-0001"
Crediting participant account (comitê gestor) receiving the IBS repasse.
Debiting participant account originating the IBS repasse.
Optional caller-supplied correlation reference echoed back for client-side reconciliation.
"ibs-ref-1"
Optional repasse-originator CNPJ (official CNPJ type: exactly 14 characters, [0-9A-Z]{12}[0-9]{2}). Omitted from the wire when absent.
^[0-9A-Z]{12}[0-9]{2}$"12345678000199"
Optional free-text description carried with the operation.
"Repasse IBS comite gestor"
Repeating segregation-informe group ([0..n]); each entry requires both an identifier and a timestamp. Absent means the repasse references no informe. No item ceiling is imposed: the official XSD declares maxOccurs='unbounded' and no BACEN rule caps it.
Opaque client-side metadata forwarded verbatim to the legacy submit DTO. NOT persisted on the operation intent or sanitized payload.
Optional transaction count (digits only).
"10"
Respuesta
Created
UTC RFC 3339 timestamp at which the command was accepted.
"2026-05-06T18:30:00Z"
STR capability identifier resolved for the accepted operation (e.g. STR0004).
"STR0004"
Request correlation identifier for tracing the accept across logs and traces.
"req-7c8b3a2e-9f1d-4a55-9b8e-1e1234567890"
True when this response replays a prior idempotent accept rather than creating a new operation.
false
Operation family the accepted command belongs to (e.g. bankTransfer).
bankTransfer "bankTransfer"
Server-assigned operation aggregate UUID used for subsequent status, return, and cancellation calls.
"7c8b3a2e-9f1d-4a55-9b8e-1e1234567890"
Current control-plane lifecycle status of the operation; ACCEPTED on initial accept.
ACCEPTED, SUBMITTED, SENT, CONFIRMED, REJECTED, FAILED, PENDING_CONFIGURATION, PENDING_RECONCILIATION, RETURN_REQUESTED, RETURNED, CANCEL_REQUESTED, CANCELLED, RECEIVED, DELIVERED "ACCEPTED"
Optional SAFE protocol correlation fields; present once the operation is mapped to STR wire identifiers.

