Event families
Pix transactions
PIX_PAYMENT_IN, PIX_PAYMENT_OUT, PIX_REFUND_IN, and PIX_REFUND_OUT. Delivery scope: ACCOUNT or USER.
KYB
VA_ACCOUNT_KYB is delivered to USER-owned subscriptions for virtual accounts. MASTER_ACCOUNT_KYB is delivered to PLATFORM-owned subscriptions for master accounts.
MED processing
MED_CASE_CREATED, MED_CASE_STATUS_CHANGED, INFRACTION_RECEIVED, and INFRACTION_STATUS_CHANGED. Delivery scope: USER or ACCOUNT.
See the dedicated Transaction Webhooks, KYB Webhooks, MED Processing Webhooks, Delivery and Retries, and Signature Verification pages for payload and receiver details.
Webhook Management API event values
The/v3/webhooks management API currently accepts these numeric event values:
1— configurePIX_IN; callback eventPIX_PAYMENT_IN.2— configurePIX_OUT; callback eventPIX_PAYMENT_OUT.3— configureREFUND_IN; callback eventPIX_REFUND_IN.4— configureREFUND_OUT; callback eventPIX_REFUND_OUT.5— configure and receiveVA_ACCOUNT_KYB.6— configure and receiveMASTER_ACCOUNT_KYB.
MED_PROCESSING subscription family. This family is not represented by the numeric values currently accepted by /v3/webhooks.
For management endpoints and owner-specific rules, see Webhook Management.
Receiver checklist
- Expose a stable callback URL.
- Read and retain the exact raw request body.
- Verify
X-Content-HashandX-Signaturebefore parsing JSON. - Reject stale timestamps and replayed nonces.
- Store the event with the documented idempotency key.
- Return HTTP 200 after the event is durably accepted.
- Process asynchronously and tolerate duplicate or out-of-order delivery.