Know why a PIX deposit was refunded — and re-engage the payer
Jul 24- The
payment.refundedwebhook now includesrefundReasonDetail, a machine-readable reason for the refund:med_chargeback,cpf_mismatch,cnpj_mismatch,spam_like,user_blocked, orpayer_refused. - Every refund now also carries
payerEuid, a stable pseudonymous ID of the bank account that paid. Use it to correlate refunds from the same payer — for example, to issue a fresh QR code so the customer can pay again from the same account, or to block repeat offenders — without ever handling their personal identity. - On document-mismatch refunds (
cpf_mismatch/cnpj_mismatch), the payload additionally includes the payer's name and tax ID so you can reconcile against the document typed at checkout. CPFs are always masked (***.999.999-**); company/PSP CNPJs are sent in full, as they are public registry data. - See the
payment.refundedevent in the API docs for full payload examples.
