YUyuvexpay
Webhooks

MED resolved

A PIX MED reached a terminal outcome.

The HTTP body is this object exactly — there is no envelope and no type field. The event name is delivered in the X-Webhook-Event header. Most optional fields arrive as an explicit null; a few keys are dropped from the JSON entirely when unset, and those are marked as such below. Read values with a null-safe accessor rather than testing key presence.

postWebhookMED_RESOLVED

Payload

medIdstring uuid required

MED id.

paymentIdstring uuid required

Payment id.

resolution'ACCEPTED_BY_USER' | 'REJECTED_BY_USER' | 'ACCEPTED_BY_PSP' | 'REJECTED_BY_PSP' | 'CANCELLED_BY_PSP' required

How the MED ended. Switch on this non-exhaustively — new outcomes can be added.

amountnumber

Disputed amount in BRL. Absent on some resolution paths, which omit the key entirely.

refundIdstring uuid

Refund id, when the resolution produced a refund.

shortfallnumber

Unfrozen shortfall, when applicable.

sourcestring nullable

merchant_refund when your own refund resolved the MED. null or absent otherwise.

Response

Return a 2xx status to acknowledge receipt.

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.