Contesting a sent PIX
Opening the contestation at the settlement bank is still done by the desk. The API records the request, sends the email and returns a code to follow it.
POST /v1/accounts/{accountId}/pix/med-requests requires:
- a PIX sent by this account (
med_request_not_outgoing_pixotherwise); - a date within 80 days (
med_request_out_of_window); - a
descriptionof at least 40 characters; reasoninfraud_scam,unauthorized,wrong_recipient,duplicate,other;Idempotency-KeyandX-Acting-Document;- scope
med.defend.
The response carries trackingCode in the MED-YYYY-NNNNNN format. If
the email to the desk cannot be sent, nothing is stored (503
email_unavailable).
An open contestation for the same PIX answers 409 med_request_pending.
Follow-up
GET on the list and on the detail (the requestId can be the code).
Until it is closed, messages and attachments stay open, including after
the desk opens the MED (status=opened, medId filled). The MED we
opened, on the /pix/med route, stays read-only.
Cancelling only applies in submitted or info_requested, before there
is a medId.
The pix.med.request.updated webhook carries the code, the status and,
when present, the medId and the information request. It does not carry
the description.