Skip to main content

Rate limits

The public contract may return 429 when request patterns threaten stability or operational cost.

  • Apply exponential backoff with jitter.
  • Respect upstream timeouts on your side too.
  • Use queues and batching for high-volume sync jobs.
  • Do not retry forever on 422 or 401.

Minimum observability​

Track 429 rates by route, environment and credential. They usually expose loops, aggressive polling or poor replay control.

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