Answer a MED dispute
Records the account holder’s response to the report: AGREE acknowledges the fraud, DISAGREE contests it.
The answer and the attached evidence enter CorpX’s review: reviewStatus moves from awaiting_defense to pending_review and a pix.med.review.updated webhook with reason: submitted is sent. Answering records the account holder’s side of the case; the decision comes later, through the webhook.
Attach evidence before answering: after the answer the dispute only accepts attachments again if the review asks for clarification (info_requested); otherwise evidence/* answers 409 med_not_writable.
The answer is sent once; a second call fails with 409 conflict.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
The medId (infraction report id).
Headers
Optional client-generated idempotency token (recommended for safe retries).
Request
AGREE acknowledges the fraud; DISAGREE contests the report.
Your defense, free text. Required on DISAGREE: a contestation with no justification supports nothing in the analysis. Files go through the evidence routes, before this call.
Response
Stage of CorpX’s review. awaiting_defense → pending_review (→ info_requested → pending_review) → in_execution → refunded | awaiting_funds, or refused. awaiting_result is the dispute CorpX opened on the holder’s behalf (direction: opened): outside the review, waiting for the settlement bank.