Skip to main content

PIX

PIX in MuPag starts as an authenticated charge and finishes through asynchronous confirmation.

What to store​

  • charge_id
  • pix_emv_code
  • expires_at
  • request_id

Good practices​

  • Show the expiration time to the buyer.
  • Treat paid, expired and canceled as distinct terminal states.
  • In reconciliation, use charge_id and the webhook event as the source of truth.

To validate the technical path, create an authenticated, idempotent QA charge from your backend before wiring checkout.

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