Request event types
Webhook create and update requests use JSON numbers:1—PIX_IN2—PIX_OUT3—REFUND_IN4—REFUND_OUT5—VA_ACCOUNT_KYB6—MASTER_ACCOUNT_KYB
webhook.event_type is mapped to PIX_PAYMENT_IN, PIX_PAYMENT_OUT, PIX_REFUND_IN, PIX_REFUND_OUT, VA_ACCOUNT_KYB, or MASTER_ACCOUNT_KYB.
Owner and target rules
- Account credential: supported for Pix transaction and refund events on its bound account.
VA_ACCOUNT_KYBandMASTER_ACCOUNT_KYBare not supported delivery scopes for an account-owned subscription. - User credential: transaction and refund events require
account_number.VA_ACCOUNT_KYBrequiresaccount_numberto be omitted.MASTER_ACCOUNT_KYBis not accepted. - Platform credential:
MASTER_ACCOUNT_KYBonly, with noaccount_number.
VA_ACCOUNT_KYB with an account credential. VA_ACCOUNT_KYB delivery resolves USER-owned subscriptions only; an account-owned registration does not receive this event.
Current lifecycle behavior
callback_urlis trimmed and must be non-empty. This layer does not validate URL syntax or require HTTPS.webhook_idis the practical identifier returned by the mapper. For Get, Update, or Delete, send it assubscription_idwhen exact targeting is needed.- List currently ignores its contract-level
subscription_idfilter. - Create has no client idempotency field.
- Delete disables a configuration; it does not physically erase the record.
- Account-scoped List explicitly requests active subscriptions. Do not infer identical filtering for every owner type.
Endpoints
- Create —
POST /v3/webhooks/create - Get —
POST /v3/webhooks/get - Update —
POST /v3/webhooks/update - Delete —
POST /v3/webhooks/delete - List —
POST /v3/webhooks/list