Skip to main content
POST
Authorise payment of an SLB charge

Authorizations

Authorization
string
header
required

JWT bearer token issued by the identity provider.

Headers

X-Idempotency
string
required

Idempotency key. Required on every mutation.

X-TTL
string

Idempotency key TTL in seconds.

Body

application/json
amount
string
required

The charge's FULL value in decimal reais. SLB admits no partial payment (Catálogo v5.13 Vol I), so anything other than the notified amount is refused.

Pattern: ^[1-9][0-9]{0,15}\.[0-9]{2}$|^0\.(0[1-9]|[1-9][0-9])$
Example:

"1500.00"

controlNumberSLB
string
required

Control number (NumCtrlSLB) of the charge being paid, as the SLB0001 notice carried it. Rule RSLB0002 makes it mandatory on the wire: a payment that does not name the charge it pays is not a payment of that charge.

Required string length: 1 - 20
Example:

"SLB20260915000000001"

preferenceLevel
string

Optional processing preference (NivelPref).

Maximum string length: 4
Example:

"0001"

Response

Accepted

correlationId
string
required

Request-scoped correlation identifier echoing X-Request-ID.

Example:

"req-7a3f9c2e"

id
string
required

Correlation id (the outbound NUOp). The answer leg is correlated to it.

Example:

"46026562202609150000001"

messageType
string
required

The SLB wire code that was submitted.

Example:

"SLB0002"

movementDate
string
required

BACEN business date (DtMovto) stamped on the frame, derived server-side.

Example:

"2026-09-15"

numCtrlPart
string
required

This participant's own control number for the message — the handle BACEN quotes back on the answer.

Example:

"20260915000000000001"

status
string
required

SUBMITTED when the message was queued for the rail, PENDING_APPROVAL when the configured alçada band parked it awaiting signatures.

Example:

"SUBMITTED"

submittedAt
string
required

RFC3339 UTC timestamp the message was submitted.

Example:

"2026-09-15T12:00:00Z"