Unblock a Pix refund stuck in PROCESSING
Resolves ONE outbound refund that is stuck in PROCESSING. Pix Lerian asks the SPI for the outcome of the refund and applies it. The request has no field to state what happened.
The refund must have been in PROCESSING for at least 90 minutes. If the SPI reports the refund as completed, the refund becomes COMPLETED. If the SPI reports it as rejected or failed, the refund becomes FAILED and Pix Lerian reverses the debit. If the SPI has no final outcome yet, the call is refused with PIX-0556: retry later. If Pix Lerian cannot get the status from the SPI, the call answers 502 (PIX-0557) and Pix Lerian changes nothing.
A refund that is already in a final status is refused with PIX-0554. A refund in any other status is refused with PIX-0551.
The caller needs the refunds permission with the post action, the same permission that creates a refund.
The response is the refund as Get refund returns it.
Autorizações
JWT bearer token issued by the identity provider.
Cabeçalhos
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 different URL, X-Account-Id, X-Actor-Id, X-Override-Reason or X-Override-Ticket is PIX-0031 @ 412.
1 - 64Source account UUID. A refund that exists under a different account is answered 404.
"019606a1-3b4c-7d8e-9f01-234567890abc"
Optional. Identifies the person in your back office who asked for the check. Pix Lerian does not use it to decide the outcome.
255"ops-maria"
Optional. Reason for the check. Pix Lerian does not use it to decide the outcome.
512"outcome never arrived"
Optional. Ticket reference in your own back office. Pix Lerian does not use it to decide the outcome.
255"OPS-4711"
Parâmetros de caminho
Refund UUID
"0196080a-1234-7890-abcd-ef0123456789"
Resposta
OK
"100.00"
"2026-05-06T10:45:00Z"
"019606b1-3b4c-7d8e-9f01-234567890dee"
"E12345678202605061030abcdef12345"
"MD06"
"COMPLETED"
"OUTBOUND"
"2026-05-06T10:45:30Z"
"019606a0-1a2b-7c3d-8e4f-567890123abc"
"Estorno solicitado pelo pagador"
"D12345678202605061045fedcba54321"
Fee the ledger reported on the create that moved the refund's money. Absent when no fee answer was recorded for this refund (its ledger create never landed, an error was logged at the time, or the refund was created before fees were read back); {"applied": false} when the ledger reported that no fee was charged; the full object when it charged one. A refund carries no ledger.revert field and needs none here: a FAILED refund that carries feeCharge was reverted first -- every path that writes a refund FAILED after its ledger create landed reverts the debit before marking it (a revert that does not complete leaves the refund PROCESSING), and every other path fails before any create -- so the fee was returned with the amount; applied reports what the create did and the object records the create.

