Skip to main content

Changelog

2026-10-08​

  • Changed (breaking): signup POST /v1/accounts in the customer API (customer.yaml) no longer returns 201 with account_id for new accounts. Every valid request now gets 202 {"status":"accepted"}, whether the email is new or already registered, and the response carries no identifier and does not reveal whether the account exists. Clients that relied on account_id should read it from GET /v1/accounts/me after email verification and login. The change was approved in PR #722.

2026-07-15​

  • Public reference consolidated around public-v1.yaml
  • Quickstart aligned with authenticated, idempotent charge creation
  • Clear separation between public endpoints and dashboard-managed finance workflows

How to read it​

  • Added for new routes, fields or guides
  • Changed for compatible behavior updates
  • Deprecated when a migration window starts

Read this page before regenerating clients, Postman assets or operational automations.

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