Single autopay-execution row by id. Same auth as the list
(`require_self_or_trusted_backend`); the core handler asserts the execution
belongs to `mandate_id` and the mandate to `user_id` (fails closed).
Mandate Execution
Get Mandate Execution
GET
Single autopay-execution row by id. Same auth as the list
(`require_self_or_trusted_backend`); the core handler asserts the execution
belongs to `mandate_id` and the mandate to `user_id` (fails closed).
Path Parameters
User ID
Aarokya internal mandate UUID (mandates.id)
mandate_executions.id (UUID PK)
Response
The mandate execution
Internal lifecycle status of a mandate-execution (autopay) firing, independent of the linked order's external_status (Juspay vocabulary). Inserted as Initiated when the Kronos firing is claimed, advances to Pending once the charge is dispatched, and lands on Success/Failed from the /orders reconciliation. Distinct from OrderStatus so the firing's vocabulary can diverge from the payment's. See From<&ExternalOrderStatus> for the provider-status mapping.
Available options:
INITIATED, PENDING, SUCCESS, FAILED