Skip to main content

Deliver a JSON event to the merchant HTTPS endpoint

Webhook 

POST with Content-Type application/json and the {id, type, data} envelope. MuPag-Signature and the X-Gateway-Signature alias carry t=<epoch>,v1=<hmac>. The request also sends X-Gateway-Event-Id and X-Gateway-Timestamp. Success is 200-299. There is no User-Agent, and redirects are not followed. An SSRF-blocked target produces internal status 0, which is not an HTTP response, and the delivery is abandoned.

Request​

Responses​

Retryable status.

Did this page unblock the next step?

Feedback stays inside the docs flow and should never include customer or card data.

mupag / support

How can we help?

Quick answers, AI and our team.

Frequently asked questions

How do I start integrating?

Follow the quickstart, configure the QA environment and create your first test charge.

Read documentation
My PIX payment is pending. What now?

Confirmation is asynchronous. Check the charge status and webhook events before fulfilling the order.

Read documentation
How do I receive payment notifications?

Register a webhook endpoint, verify its signature and handle duplicate events safely.

Read documentation
How do subscriptions work?

Read the subscriptions guide to configure recurring billing and follow the charge lifecycle.

Read documentation
Where can I find authentication help?

See how to use environment credentials in the documentation. Never share your key in chat.

Read documentation