PIX payment gateway: what it is, how it works, how to choose
Learn what a PIX payment gateway is, how QR Code charges, webhooks and reconciliation work in Brazil, and what to compare before choosing a provider.
Learn how split payments divide each sale between sellers and the platform, which rules to set up and how to handle fees, refunds and chargebacks correctly.

A split payment is the automatic division of a single sale between two or more recipients, carried out by the payment system at the moment of the transaction. In a marketplace, the customer pays once, and the seller and the platform each receive their share directly in their own accounts. The platform no longer has to collect everyone's money and pay it out later.
Any business where one sale generates revenue for more than one party is a candidate. The most common cases:
The underlying problem is always the same: the customer wants to pay once, and each party wants to see its own money without depending on the other.
Many platforms start by receiving the full amount and transferring partners' shares at the end of the week. It works at first, but the problems grow with volume. The examples below come from Brazil, but most apply elsewhere too.
The first issue is tax. If the full amount lands in the platform's account, it may be treated as the platform's revenue, which inflates the tax base on money that belongs to someone else. With split payments, each party receives and books only its own share. The outcome depends on the tax regime and business model, so bring in your accountant at the design stage.
The second is regulatory. In Brazil, holding and passing on third-party funds can bring an operation close to activities governed by Law 12.865/2013, the framework for payment institutions supervised by the Banco Central do Brasil. A legal review is worth it before scaling that model.
The third is operational: manual transfers, a transfer fee for every partner, wrong amounts and reconciliation nobody wants to do. Trust matters too, since sellers would rather watch their own balance than wait for a payout.
The flow is similar across most providers that offer splitting through an API:
A hypothetical example makes it concrete. Picture a sale of 200 on a marketplace with a 15% commission and a processing fee of 8, shared in the same proportion as the sale.
| Item | Seller | Platform |
|---|---|---|
| Share of the sale | 170.00 | 30.00 |
| Share of the processing fee | 6.80 | 1.20 |
| Net amount received | 163.20 | 28.80 |
If the rule were for the platform to absorb the whole fee, the seller would receive 170 and the platform 22. Same sale, very different result for each side.
The splitting technology is the easy part. The real work is in the business rules, which must be identical in your partner contracts and in your code.
A few problems show up in almost every project, and they are cheap to avoid if you plan for them.
Changing the commission midstream is one. The rule must be stored with each transaction, so that a new percentage does not alter the math on sales that already happened.
Negative balances are another. If a seller withdraws everything and a chargeback arrives weeks later, someone has to cover the gap. A reserve on the balance or a deduction from future receivables solves it, as long as the contract allows it.
Pending registrations also block sales. A seller whose account has not been approved cannot receive funds, so verify recipients before listing their products.
Long chains complicate everything. A creator, a co-creator, an affiliate and an affiliate manager on one sale multiply the refund and rounding cases. Limit the number of parties per transaction whenever the model allows.
On invoicing, each recipient typically issues an invoice for its own share, and the platform invoices its commission or service. Confirm the format with your accountant.
Before writing code, map the flow of each type of sale and choose a provider that accepts per-transaction split rules through an API, with clear handling of refunds and chargebacks per recipient. Test the hard scenarios in a sandbox: partial refunds, a chargeback after withdrawal, installment sales and a blocked recipient. Then give partners a dashboard with their own balance and statement, and reconcile amounts every day.
Bridgemoon runs its own payment processing system with splitting between recipients and builds the integration with the client's marketplace or platform, from commission rules to the partner dashboard.
Whoever the platform defines in its rules. It can be the platform alone, the recipient alone or both in proportion to the sale. What matters is that the rule is the same in the partner contract and in the split configuration.
The disputed amount is debited from whoever the rules name as responsible, which may be the seller, the platform or both. If that party has already withdrawn the money, its balance can go negative and be offset against future sales. Set reserves and priorities before you start selling.
No. A commercial split divides a sale among business partners, while the split payment mechanism in Brazil's tax reform separates consumption taxes at the moment of payment. That mechanism has its own rules and timeline, so follow it with your accountant.