Pay BACEN an amount SLB never demanded
Submits an SLB0007 paying BACEN an amount no SLB0001 charged, including the return of a credit BACEN made with an SLB0005 — name that credit’s control number to make the payment a return (RSLB0008). Unlike the charge authorisation this command is bounded by nothing but its own fields, which is why it carries its own scope. When the deployment configures an alçada band covering the amount, the message parks in PENDING_APPROVAL until the required signatures are collected. Idempotent — the X-Idempotency key lives with the payment: the same key and parsed request (member order and whitespace do not count; any other difference, such as number spelling, null for an absent field, or an unknown member, is another request) answer the stored payment with X-Idempotency-Replayed: true, also after X-TTL has dropped the cached response, and the same key with another request answers 422.
Autorizações
JWT bearer token issued by the identity provider.
Cabeçalhos
Idempotency key. Required on every mutation.
Seconds the cached response is kept; it may only shorten IDEMPOTENCY_DEFAULT_TTL_SEC. The key itself lives with the payment.
Corpo
Payment amount in decimal reais (VlrLanc).
^[1-9][0-9]{0,15}\.[0-9]{2}$|^0\.(0[1-9]|[1-9][0-9])$"2500.75"
Free text (Hist). Mandatory on this message — SLB0002 declares no Hist at all, and that asymmetry is BACEN's.
1 - 200"DEVOLUCAO DE CREDITO"
BACEN finalidade code (FinlddSLB) of the payment. Mandatory on this message.
1 - 4"01"
Optional agreement CNPJ (CNPJConv).
14"00038166000105"
Control number of the SLB0005 credit being returned (RSLB0008). Omit it for a spontaneous payment.
20"SLB20260915000000009"
Optional processing preference (NivelPref).
4"0001"
Resposta
Accepted
Request-scoped correlation identifier echoing X-Request-ID.
"req-7a3f9c2e"
Correlation id (the outbound NUOp). The answer leg is correlated to it.
"46026562202609150000001"
The SLB wire code that was submitted.
"SLB0002"
BACEN business date (DtMovto) stamped on the frame, derived server-side.
"2026-09-15"
This participant's own control number for the message — the handle BACEN quotes back on the answer.
"20260915000000000001"
SUBMITTED when the message was queued for the rail, PENDING_APPROVAL when the configured alçada band parked it awaiting signatures.
"SUBMITTED"
RFC3339 UTC timestamp the message was submitted.
"2026-09-15T12:00:00Z"

