Confirm a cautionary block settlement
Applies the outcome of the devolution that Settle a cautionary block started: the lock becomes SETTLED when the devolution was paid, goes back to PENDING when it was rejected, and stays as it is while the devolution is in flight. The call carries no result, because Pix Lerian reads it from the devolution. Repeat the call until the lock leaves SETTLING.
A pix_manual surplus is returned once, when the lock settles. If that return fails, the lock stays SETTLED and the answer is 200 without surplus_midaz_tx_id; this does not prove that the surplus stayed blocked. Check the ledger, then use Return a settlement surplus to the account holder. A lock whose surplus was already returned is refused with 409 (PIX-0656) and stays SETTLING.
X-Actor-Id, X-Override-Reason and X-Override-Ticket are optional. Sending any of them records the confirmation in the audit trail. For a lock opened for a MED infraction (origin_system med-infraction), use Confirm settle refund instead: DICT holds MED state that this route cannot see.
Autorizaciones
JWT bearer token issued by the identity provider.
Encabezados
REQUIRED. Client-supplied replay key, at most 64 bytes. A request without it is refused with PIX-0030 @ 400 before the handler runs. An identical resend within 1 hour returns the original response, status included, with X-Idempotency-Replayed: true. Reusing the key with a divergent method, URL or body is PIX-0031 @ 412.
1 - 64Who is acting. Declared by the caller; not verified against the access token
"backoffice.ops@example.com"
Why the caller is acting
"manual devolution paid by Pix"
Ticket reference
"MED-4821"
Correlation id
"med-2026-000123"
Request id
"01a17e29-5302-7c0a-b5e1-94d2f6a83c17"
Parámetros de ruta
Balance lock UUID
"01a17cf3-128e-7c41-9b2e-5d7a3f8c1e60"
Respuesta
OK
"01a17cf3-128e-7c41-9b2e-5d7a3f8c1e60"
"SETTLED"
"PIX_MANUAL"
"E87654321202610271405m3Hs7Yc5Pv1"
"2026-10-27T14:06:03Z"
"2026-10-27T14:06:03Z"
On SETTLED, the Midaz transaction that returned the pixManual surplus to the customer: made by this confirm once the lock is SETTLED, or already recorded (a replay, or a group member's). Absent when there is no surplus, or when the best-effort return failed -- recover it with POST /balance-locks/{lock_id}/return-surplus.
"01a17dae-b16e-7f28-9a03-6b1c4d8e2f75"

