Effectuate a MED refund debit (THIRD RAIL — moves money)
Effectuates the refund DEBIT at SPI for an accepted refund (JDPI POST /od, contract §2.24): posts a balanced PENDING Midaz double-entry (contestado debit, clearing credit) and generates the pacs.004. The debit commits on the settlement reconcile poll. The precondition (accepted AND not-yet-effectuated) is checked before any ledger touch: a non-accepted request returns a coded 422, and an already-effectuated one echoes its recorded ids with no second post. A failed request is not safe to retry blindly: its reserve may have landed, and the ledger deduplicates a retry only within 300 seconds, so past that window an operator reconciles the request before it is sent again. An unknown id returns a coded 404.
Authorizations
JWT bearer token issued by the identity provider.
Path Parameters
The accepted refund-request GUID to effectuate.
"d4e5f6a7-b8c9-0123-def4-56789012345a"
Response
OK
Debit-effectuation FSM code (0=NotStarted, 1=DebitPending, 2=Settled, 3=Failed).
1
Human-readable eff_status label.
"DebitPending"
The Pending Midaz debit posting id (the reconcile commit/cancel reference).
"01HXYZ..."
The JDPI /od request id (the debit-poll handle).
"f1e2d3c4-b5a6-7890-1234-567890abcdef"
Deprecated: read refundRequestId, which carries the same value. The effectuated refund-request GUID.
"d4e5f6a7-b8c9-0123-def4-56789012345a"
The effectuated refund-request GUID.
"d4e5f6a7-b8c9-0123-def4-56789012345a"

