Skip to main content

Affiliates, splits, balances and payouts

These workflows currently exist as dashboard-guided operations and internal finance routines. Do not expose undocumented calls just to simulate a public API that does not exist yet.

What to do today​

  • Configure affiliate programs in the dashboard.
  • Review split rules with finance before any future production planning.
  • Track balances and payouts through the operational dashboard.
  • Persist internal campaign, partner and sale IDs so you can reconcile them with dashboard reports.

When the API arrives​

The portal will announce it in the changelog, update OpenAPI and move this workflow from "dashboard-managed" to "public contract".

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