POST
/
mandates
/
{mandate_id}
/
execution
/
{execution_id}
/
status_check
cURL
curl --request POST \
  --url http://localhost:8080/mandates/{mandate_id}/execution/{execution_id}/status_check \
  --header 'X-Mandate-Execution-Id: <x-mandate-execution-id>'
{
  "amount": {
    "value": 123
  },
  "created_at": "<string>",
  "id": "<string>",
  "job_execution_id": "<string>",
  "last_modified_at": "<string>",
  "mandate_id": "<string>",
  "order_id": "<string>"
}

Headers

​
X-Mandate-Execution-Id
string
required

Per-firing Kronos execution id (templated via {{execution.execution_id}}). Used for log correlation only on this route.

Path Parameters

​
mandate_id
string
required

Aarokya internal mandate UUID (mandates.id)

​
execution_id
string
required

mandate_executions.id (UUID PK)

Response

Status reconciled (terminal-state fast-path or settled this attempt)

​
amount
object
required
​
created_at
string
required
​
id
string
required
​
job_execution_id
string
required
​
last_modified_at
string
required
​
mandate_id
string
required
​
order_id
string
required
​
status
enum<string>
required

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