Repair Transfer Ledger Scope
Use this endpoint to correct the accounting scope of one transfer whose ledger is the all-zeroes UUID. That value addresses no Midaz ledger and matches no routing binding, so the transfer’s refund stays held, and no configuration that an operator could write frees it.
The operator supplies the ledger, because only a person may authorize an edit to the scope of a money row. CRM must report the same ledger for the transfer’s own account before anything is written; if the two disagree, nothing is written. No money moves here and no ledger call is made: the next reconciliation or poller cycle moves the money, once, on the routes that the repaired ledger resolves.
The operator reason is required. It is recorded in the transfer’s status history and audit trail with the subject from the bearer token. This endpoint requires the transfers:repair permission and a user token.
Autorizações
JWT Bearer token authentication. The tenantId is derived from the bearer token or authenticated request context and is not supplied through X-Organization-Id.
Cabeçalhos
Midaz organization scope for the request, used for downstream CRM, Fees, and Midaz calls. Required on org-scoped transfer routes in every deployment mode; a missing or non-UUID value returns 400. This is not the tenant identifier — tenantId is derived from the bearer JWT or authenticated context, never from this header. Background workers (TED IN poller, reconciliation) have no request header and, in single-tenant mode, fall back to the deployment's ORGANIZATION_ID env.
Required idempotency key for safe retries. Use a UUID v4 or unique business identifier. If the same key is sent again and the original request was already processed, the cached response is returned.
See Retries and idempotency for details.
255Parâmetros de caminho
The unique identifier of the transfer.
Corpo
The ledger that the operator asserts, the justification, and an optional evidence reference.

