Execute Mandate

post

https://services.jiopay.co.in/api/subscription/execute

Triggers the actual debit/execution against an active mandate. Server-side supports a bulk executions array.

txnID and secureHash may return null when the execution is queued/pending rather than settled — poll Mandate Status with request_type: EXECUTE for the final outcome.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Triggers the actual debit/execution against an active mandate. Server-side supports a bulk executions array — this is the shape shown directly in the source's own example.

client_id

string

required

Merchant/client identifier.

executions

array of objects

required

executions*

secureHash

string

HMAC-SHA256 signature, computed client-side before sending and validated server-side (auto-generated by the caller, not a value you choose). Algorithm: remove any existing secureHash, sort the remaining top-level keys alphabetically, join String(value).trim() per key with |, then HMAC-SHA256 the resulting string with your client_secret, hex-encoded. A second variant used by some endpoints strips comments from the raw body first and JSON-stringifies object values instead of String()-converting them — confirm which variant applies with the JPSL integration team before implementing.

Response

200OK