Endpoint
POST /v3/med/detail
Authentication and target
Use an account credential for its bound account, or a user credential with bothX-ISPB and X-Account-Number. If an account credential sends those headers, both must be present and must match its bound account. Platform credentials are not accepted. All requests require the standard HMAC-SHA256 headers. The selected account determines payer-side MED owner scope; receiver-side operations are not exposed by these routes.
The curl example below uses an ACCOUNT credential bound to the operated account, so it omits X-ISPB and X-Account-Number. If X-Client-ID identifies a USER credential, add both target headers and include their exact trimmed values in the canonical header set before calculating X-Signature.
Request body
Success data
med_case using the full case-detail model: identifiers, numeric status, display/progress fields, decimal-string amounts, millisecond times/deadlines, original transaction, timeline, infractions, and refunds.
Behavior and validation
The downstream MED service supplies timeline, deadline, infraction, refund, andcan_cancel projections. Do not infer eligibility or deadlines from the Open API layer.
Errors
Every call can fail for missing or invalid signature headers, an expired timestamp, nonce replay, an invalid body hash or signature, insufficient permission, or a downstream service error. Endpoint-specific errors include:4000missing case ID.- Common owner-scope, MED RPC, and mapped provider errors.