Webhooks

Checkout abandoned

The hosted checkout saved the payer's name, e-mail and CPF or CNPJ, and the payment was still unpaid 30 minutes later. The checkout saves them as soon as all three are filled in and valid, or when it opens with details the browser remembered. When the payment was created with a customer that has a name of 2 to 120 characters, a valid e-mail and a CPF or CNPJ with valid check digits, the wait starts instead the first time the checkout is opened while the payment is waiting for a method, with or without skip_customer=1. The delay is set by YuvexPay for the whole platform and can change.

Opt-in: delivered only to endpoints that selected this event, never to the others. Sent at most once per payment, never for headless payments or for sandbox payments, and never by a manual resend. The payment can still be paid after this event: read its current status with GET /v1/payments/{paymentId} before contacting the payer. buyer carries the payer's contact, and the same response carries it in payer.

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. All five fields are always present.

postWebhookCHECKOUT_ABANDONED

Payload

idstring uuid required

Payment id.

txIdstring required

Payment transaction id.

status'PENDING_METHOD_SELECTION' | 'NEW' | 'PROCESSING' | 'EXPIRED' | 'CANCELLED' required

The payment's status when the event was sent. The event can arrive after PAYMENT_EXPIRED or PAYMENT_CANCELLED for the same payment.

amountnumber required

The payment amount in BRL, the same value GET /v1/payments/{paymentId} returns.

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.