
Revenue Models: How to Make Money with White Label Payments
Summary: Offering payments has shifted from a cost center to a revenue stream. Explore the monetization models that a white label operation enables, from MDR to split and value-added services, and how to price without falling into a race to the bottom on fees.
Introduction
Many companies see payments as an expense: the fee charged by the acquirer on each sale. The key shift is understanding that by offering payments as a proprietary product (under your brand, on a white label infrastructure), that same operation becomes a source of recurring revenue.
The question this post answers is straightforward: what are the concrete ways to make money from this? There are several models, they can be combined, and the right choice depends on your audience, your volume, and the value proposition you want to deliver.
This text is for owners and managers evaluating the decision. We'll walk through each monetization model, show an illustrative calculation example, and close with the most strategic point: how to think about pricing without comparing solely on fees the race where everyone loses.
Context and data
The size of the market explains the appetite. In 2024, the card sector in Brazil surpassed R$ 4.1 trillion, a growth of 10.9% over 2023, with approximately 45.7 billion transactions and around 125 million payments per day, according to ABECS data. Add to that PIX, which has become the most used payment method in the country in terms of transaction volume and moves figures in the tens of trillions of reais per year, according to the Central Bank.
The message for your business: there is a gigantic flow of payments passing through the hands of intermediaries every day. Each transaction that goes through your platform can carry a fraction of revenue. You don't need to capture a lot from each one; you need to capture intelligently and at scale. This is why marketplaces, ERPs, management software, franchises, and vertical platforms are embedding payments into their products. The revenue comes from the flow that was already passing through them anyway.
Monetization models
There is no single way to make money with payments. There are layers, and the best operations combine several.
- MDR / transaction fee (cards): the classic model. You charge a percentage on each card transaction, the MDR. Since the acquiring cost behind it is your input, your margin is the difference between what you charge the end customer and what you pay on the backend. It is predictable and scales with volume.
- Markup on acquirer cost: a transparent variation of the previous one. You pass through the real acquiring cost and add a defined markup, either fixed in percentage points or a portion on top of the cost. It works well with larger clients who appreciate knowing what is cost and what is your compensation.
- Fixed fee per transaction, especially for PIX: In PIX, the processing cost per transaction is low and not proportional to the amount. This opens up space to charge a fixed amount per transaction instead of a percentage. With high volumes and low tickets, this model is much more profitable than trying to apply a percentage.
- Setup and monthly fee, SaaS logic: charging an implementation fee and/or a recurring monthly fee for platform access, regardless of transacted volume. This ensures a predictable revenue base that doesn't depend solely on flow and anchors the customer to the product.
- Payment split as revenue: Split allows automatically dividing a transaction among multiple parties. For those operating a platform or marketplace, it organizes payouts to sellers while also allowing you to automatically retain your commission on each divided transaction.
- Value-added services: This is where the margin lives that no one can copy with a low fee. Anti-fraud (charging for risk analysis), receivables anticipation (one of the most profitable lines in the sector), and analytics and reporting (dashboards and reconciliation as a premium product).
The more layers of value you add, the less your revenue depends exclusively on transaction fees, and the harder it becomes for a customer to switch to a competitor that only offers a lower fee.
Practical application
The numbers below are purely illustrative, only to show the logic of revenue composition, and do not represent fees, costs, or promises of results. Actual values depend on the acquirer, volume, sector, and negotiation.
Imagine a platform that processes R$ 5,000,000 per month for its customer base, distributed as follows:
- Cards, 60% of volume (R$ 3,000,000): you charge 3.5% and your acquiring cost is 2.8%. A margin of 0.7% results in about R$ 21,000/month.
- PIX, 40% of volume (R$ 2,000,000): assuming an average ticket of R$ 100, that's approximately 20,000 transactions. Charging an illustrative fixed fee of R$ 0.40 per PIX, that amounts to R$ 8,000/month.
- SaaS monthly fee: 50 active clients at R$ 200/month add up to R$ 10,000/month.
- Additional services (anticipation, anti-fraud): conservative estimate of R$ 6,000/month.
Total monthly revenue: approximately R$ 45,000. Note that less than half comes from card MDR. The layers of PIX, recurring fees, and services are what build a healthy, hard-to-replicate revenue stream. That's the point of the exercise, not the number itself.
Common pricing mistakes: relying on a single model and becoming hostage to the fee war; pricing PIX as a percentage when volume calls for a fixed fee; forgetting the total cost (acquiring, anti-fraud, chargeback, infrastructure) and discovering that the "good" margin was actually negative; not charging setup or monthly fees and leaving predictable money on the table.
How to think about pricing without competing only on fees
The most expensive mistake in the sector is selling payments as a commodity and fighting over decimal points of a percentage. In that race, there is always someone willing to charge less, and margins tend toward zero for everyone.
The way out is to anchor the price on the value delivered, not the transaction cost. A customer happily pays for an integration that solves their pain: automatic reconciliation, split that eliminates spreadsheets, anticipation that improves cash flow, anti-fraud that reduces losses, support that responds. When payment is embedded in a product the customer already uses and trusts, the fee stops being the decision criterion.
In practice: segment your base between those sensitive to fees and those who value service, combine recurring, transaction, and service models, and communicate value, not numbers. That's how you build a defensible margin, and it's exactly the kind of operation that a white label base makes viable without rebuilding the infrastructure from scratch.
Next steps
Do the exercise with your own numbers: estimate volume, the mix between card and PIX, and which services you can add in the first year. This calculation, even approximate, shows whether the model works and which revenue combination makes the most sense for your audience.
To see how all this materializes in practice, the next post brings a concrete growth example: Anatomy of a Case: How a Platform Scaled by Offering Payments.
Conclusion
Payments can be the revenue line your company hasn't tapped yet, and the white label model is the shortcut to get there without carrying the regulatory and infrastructure complexity alone. Want to design the ideal combination of models for your business? Talk to the Plutech team and simulate your revenue potential.
