Overview
MuPag publishes only the approved merchant-facing contract here. Everything in the portal should match docs/openapi/public-v1.yaml and the workflows that already exist in the dashboard.
Official hosts
| Surface | URL |
|---|---|
| Portal | https://docs.mupag.com.br |
| QA API | https://api.sandbox.mupag.com.br |
| Reserved production API | https://api.mupag.com.br — unavailable; do not use |
| QA dashboard | https://qa.dashboard.mupag.com.br/app |
Recommended path
- Create a restricted QA key and keep it only on your server.
- Make the first call with
Authorization: Bearer sk_test_.... - Enable idempotency on every mutable operation.
- Verify webhook signatures before treating any payment as final.
- Do not switch to
api.mupag.com.br: theprdenvironment does not exist yet and will be planned separately.
Current public scope
- Charges for PIX and card flows
- Customers and catalog
- Checkout sessions
- Subscriptions
- Webhooks
- OpenAPI, raw HTTP examples and AI-readable files
Affiliates, splits, balances and payouts stay documented as dashboard-managed workflows until a public API contract is approved.
Did this page unblock the next step?
Feedback stays inside the docs flow and should never include customer or card data.