Balance Management
Balance Types
A seller's balance isn't a single number: it depends on when it's queried. Split distinguishes three balance views, and understanding the difference between them avoids most reconciliation discrepancies.
| Balance type | What it contains | What it's for |
|---|---|---|
| Overdue balance | Amounts with a past-due receipt date that haven't been settled yet, usually because they're pending release (unreleased amounts) or held (blocked amounts) | Detect stuck funds and act on them |
| Current balance | Amounts already sent to the settlement process, with settlement confirmed | Know what was actually paid to the seller |
| Future balance | Amounts with a receipt date beyond D+2, pending settlement | Anticipate future payment commitments and assess refunds or adjustments |
The sum of the three views is the seller's complete position. Verifying funds for a refund and assessing an adjustment both rely on these views.
GET /v1/mgm/balances/balance/summary) when you need a summary of a seller's position, with the schedule's aggregated amounts. For a breakdown by item, commissions, and adjustments, use the Statement API.Note: The Balance API reflects the balance position as of the start of the query day. Sales, cancellations, chargebacks, and adjustments made the same day only appear in the balance query on D+1. To see the day's activity, use the Statement API.
Release
Note: Release is optional. If your model doesn't require holding payment until a later milestone, the amount follows the normal receipt calendar with no action needed on your part. Release is the tool for models that need to condition payment on a business-specific event.
/v2/payments/{paymentId}/release to release the payment.Points to note:
- Release works per item: to release a complete payment, you need to release every item in the payment.
- Before releasing, the transaction needs to be in a status that allows it.
- A released amount enters the seller's next settlement cycle.
- It's also possible to release via the Portal Minha Conta, with no development needed, which is useful for anyone operating through channels other than the API.
Important: If you release items whose payment date has already passed, the original date isn't recovered. These amounts enter the settlement following the release.
Adjustments
| Adjustment type | When it's used |
|---|---|
| In the seller's favor | Compensation, corrections in their favor, agreed bonuses |
| Against the seller | Recovery of amounts, penalties, cost pass-through |
POST /v1/mgm/adjustment/request-adjustments) or the Portal Minha Conta.Note: Adjustments are applied only to the seller's free balance, meaning amounts that are already released and have no pending negotiation.
Cancellations
A cancellation refunds the buyer the full or partial amount of a purchase. In a split model, the refunded amount needs to be deducted from whoever received it, so the cancellation request also requires split information: which part of the amount corresponds to each seller and to the platform.
- Full cancellation: reverses the original transaction's complete distribution.
- Partial cancellation: this is where split information becomes essential. You need to indicate how the refunded amount is applied (what's deducted from each seller and what's deducted from the platform's commission), because the same partial amount can be distributed in different ways.
- Partial item cancellation: it's also possible to cancel only part of an item's value, as long as that item isn't duplicated within the same order. This is the case, for example, with insurance bundled into a product: the insurance is canceled, and the product sale remains active.
POST /v2/payments/cancel: on the same day as the transaction (D0) only a full cancellation is allowed, and from D+N you can cancel the full or a partial amount. The per-seller detail goes in additional_data.split.subseller_list_payment.With this information, the cancellation impacts each participant's balance consistently with the original sale and is reflected in the statement for reconciliation. Cancellations can originate from any channel, including the point of sale, and can also be made through the Portal Minha Conta. Split behavior is the same in every case, and cancellations beyond D+1 are also possible, both through the API and through the Portal Minha Conta.
Chargebacks
By default, the platform is charged for the chargeback. It's the platform's responsibility to identify the seller associated with each chargeback and correct the balance through an adjustment.
When the Balance Doesn't Match
Whenever a seller's balance doesn't match what's expected, first check for a pending release, a recent adjustment, or an in-progress refund: these are the most common causes of discrepancy before reconciliation.
Next Steps
- Balance API: check each seller's available balance.
- Backoffice API — Adjustments: post and check manual adjustments to a seller's balance.
- Risk Management: understand what Getnet validates and what stays your platform's responsibility.
On this page