Release the settlement claim on a stuck scheduled debit
Releases the settlement claim on ONE scheduled debit whose settlement attempt went out and never got an outcome, so the debit becomes eligible for a further attempt.
THE SPI DECIDES, NOT THE CALLER. The request has no field to state what happened. Pix Lerian releases the debit only when nothing was sent, or when the SPI has no record of the attempt or rejected it and the ledger entry was reverted. Any other answer refuses the release with PIX-0827, including when the SPI cannot be asked.
The attempt must be at least 2 minutes old. The response names which of the three cases applied.
NOTHING IS CANCELLED. The charge, the schedule and the authorization stay as they are, and the receiving PSP is told nothing. To stop a charge, use POST /v1/payer/scheduled-payments//cancel instead.
The caller needs the scheduled-payment-recovery permission with the post action. The permission that allows the cancel operation does not grant it.
Autorizações
JWT bearer token issued by the identity provider.
Cabeçalhos
Non-zero UUID of the payer account selected by the calling PSP. The PSP must authorize its end user for that account before calling this API. A resource outside the selected account returns 404; a read with no records returns an empty page. See the API overview for the complete trust boundary.
^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-[0-9A-Fa-f]{4}-[0-9A-Fa-f]{4}-[0-9A-Fa-f]{12}$REQUIRED. Client-supplied replay key, at most 64 bytes. A request without it is refused with PIX-0030 @ 400 before the handler runs. Replaying the same key with a divergent method, URL or body is PIX-0031 @ 412. X-Account-Id is part of the compared request too, so replaying one account's key under another account is divergent rather than a replay.
1 - 64Parâmetros de caminho
Internal identifier of the scheduled debit whose settlement claim is to be released. A debit that exists under a DIFFERENT account than X-Account-Id names is answered 404, not 403: the lookup carries the account as a predicate, so this end never learns that a debit exists elsewhere.
"0198f3a2-1c4e-7c8b-9d1e-2f3a4b5c6d40"
Corpo
Optional. Carries the operator attribution. Pix Lerian does not use it to decide the release.
Identifier of the human operator requesting the release. It does not influence the decision and the response does not return it.
120"ops-maria"
Why the operator is intervening. It does not influence the decision, which rests on what the SPI answers, and the response does not return it.
200"settlement stuck since the morning window"
Ticket the intervention is recorded under in your own system. It does not influence the decision and the response does not return it.
60"OPS-4711"
Resposta
Claim released. The debit is eligible again; nothing was cancelled and the receiving PSP was told nothing.
Which proof permitted the unblock. NOTHING_SENT: no settlement attempt was ever filed under the claim, so nothing was sent. NOT_ON_RAIL: an attempt was filed, and the SPI has no transfer for its identifier. RAIL_REJECTED: the SPI rejected the order and the ledger entry was reverted.
NOTHING_SENT, NOT_ON_RAIL, RAIL_REJECTED "NOT_ON_RAIL"
Execution operation that was holding the debit.
"settlement-dispatch-2026-09-10-org-a"
Internal identifier of the scheduled debit whose claim was released.
"0198f3a2-1c4e-7c8b-9d1e-2f3a4b5c6d40"
Lifecycle status the debit holds after the unblock. It returns to SCHEDULED, which is what makes it eligible for a further settlement attempt.
"SCHEDULED"
Instant Pix Lerian released the claim, in UTC. It is Pix Lerian's own clock reading, not a value from the request.
"2026-09-10T14:00:00Z"

