Merchant Management

Split Payouts: Why Residual Revenue Belongs Inside the Transaction

Growing your portfolio should make revenue easier to manage, not harder. For most independent sales organizations (ISOs), the opposite happens. Every merchant you board carries its own pricing, every agent and referral partner carries its own split, and every value-added solution (VAS) you resell adds another party owed a cut.

Grow the portfolio and you don’t just grow revenue. You grow the work of dividing it up. McKinsey found that reconciliation and settlement are still manual processes at most financial institutions1, which tells you this isn’t a discipline problem. It’s a tooling problem

Once payments start flowing, the second job begins: waiting on the processor’s residual report, calculating what each agent earned, invoicing for your share and reconciling what should have been collected against what actually was.

That second job is a huge source of unwanted complexity for an ISO, and it doesn’t scale. Each new agent adds a set of terms and each new partner adds another stakeholder to account for. Volume grows, and the work of dividing up the revenue grows with it. The result is avoidable growing pains, a degraded merchant experience and under-optimized payment operations.

Modern automated split payouts solve this problem. With the right partner, you remove the complexity from payouts and build a strong foundation for future scaling with little to no technical lift. Here is how automated split payouts work, and how they solve the all-too-common problem of payout complexity.

The Traditional Disconnect Between Revenue Strategy and Money Movement

Slow, complex residual payouts have frustrated ISOs for decades. The problem persists because even traditional payments involve at least three stakeholders: the merchant, the ISO and the acquirer. Add agents and sub-agents to the mix, or a software platform you work with through a revenue-sharing agreement, and you have a fourth and fifth layer on an already complex structure. VAS partners complicate things further.

As an ISO, no single system in your stack does this whole job, so you end up with two separate journeys on every transaction. In one revenue lane is the processor you’re connected to. It moves the money and handles settlement, funding and returns. But it is completely isolated from the details of your individual merchant agreements. It has no idea that certain merchants are on legacy rates, that a referral partner earns a cut of your residual or that you’re offering promotional discounts to select merchants.

In the other revenue lane are your direct payments partners: technology enablers, your agents and referral partners and any third-party value-added service providers you offer to your merchants. These partners are where the account-level billing details live, and each one is due a specific split of the revenue left over after the processor and acquirer take their cut.

This separation between the stakeholders that each own part of the revenue is the source of all payout complexity. Decisions get made in one system and funds move in another, so somebody at your company has to bridge the gap manually. That is where errors show up and payout delays creep in. It is also the part of your payments operation that clogs up fastest as you scale, because every new merchant and every new agent adds more manual work.

Why Your Current Payments Toolkit Falls Short

The tools most payment platforms offer were built for a world in which portfolios were smaller and revenue share was simple. The next-generation rails, advanced VAS and complex multi-party revenue-share agreements that are common today did not exist. That leaves you with three key limitations:

  • Many systems apply one revenue model across an entire portfolio, with no practical way to price a large strategic account differently from a standard merchant
  • Commission payment tools are rules-based and built for flat agent splits, not tiered arrangements that shift as an agent’s portfolio grows
  • Spreadsheets and general finance tools still carry residual calculations at many ISOs, capping the portfolio-level visibility you can unlock without more advanced reporting

These legacy systems did the job for traditional payments and even earlier-generation embedded payments. But the tradeoffs on monetization, control and scale are now clear in a world where portfolios have grown faster than the systems built to pay them out. McKinsey reports that global payments revenue growth slowed to 4% in 2024, down from 12% the year before1, squeezed by peaking interest rates, a shift toward lower-yield payment methods and continued fee pressure. When the top line compresses, every dollar that leaks out in manual reconciliation costs you more than it did five years ago.

Revenue Capture Inside the Payment Flow

There is a simpler way to handle this complexity: automated split payouts. Split payouts move revenue redirection into the transaction itself. Instead of working out who earned what after settlement, the payment carries its own instructions, and each stakeholder’s split is portioned off instantly and automatically as soon as the transaction completes.

An automated split payout works like this:

  1. The buyer pays the gross amount
  2. Your configured fees apply immediately as a programmed part of the transaction
  3. Once authorized, each stakeholder’s share moves on as a net payout, already separated

Nothing has to be invoiced or collected afterward, and that is the critical part. Plenty of tools divide up funds after the fact. Split payouts handle that division directly inside the payment instead. That removes an entire workflow and simplifies your payment operations in a way that makes scaling far easier.

What to Look for in a Split Payment Solution

When evaluating split payment solutions, look for four critical factors:

In-Transaction Revenue Capture: Revenue must be captured automatically inside the transaction. If splits are calculated automatically but collection happens in another system, you are still running a reconciliation process you do not need.

Flexible Fee Configuration: Look for percentage, flat fee and hybrid models, customizable for each individual merchant and payment partner. Without that flexibility, you are stuck applying universal rules across your portfolio, which means under-optimized revenue and manual work every time you make a unique offer to an agent or merchant.

Multi-Party Distribution Support: Two-way splits are not good enough, even when they are automatic. Your payment operations likely involve you, your agents, at least one referral partner and several other stakeholders. You need automated split payouts that capture all of them, or you are back to manual reconciliation for anyone left out.

Transaction-Level Reporting: Every allocation must be visible and auditable on a payment-by-payment basis, not rolled up into a monthly figure you have to take on trust. The less you see through built-in reporting, the more manual verification you do to confirm everything is working as intended. That makes transaction-level reporting critical to actually streamlining your payouts.

Revenue Share as Infrastructure

The takeaway is simple: stop treating revenue share as a bolted-on process you perform, and start treating it as an integral part of your payment infrastructure. Once splits happen inside the transaction, highly customized per-merchant terms cost you nothing to run, and complex revenue share becomes a competitive advantage you can design around.

As infrastructure, splits run without supervision, and they behave the same on the first transaction, the thousandth and the millionth. Interchange and settlement are already infrastructure. Splits should be too, and automated split payouts now make that possible.

This isn’t a niche view. Among the six strategies McKinsey names for competing in the next era of payments is moving intelligence to the edge, meaning decisions belong at the point of transaction, embedded in APIs and workflows, rather than centralized in batch systems or driven by people. Revenue share is a decision. It belongs in the transaction with all the others.

NMI Split Payout captures and distributes fees, revenue shares and commissions within each transaction, delivering the correct net payout every time. Configure your fee schedules once, and every allocation is applied automatically and reported transaction by transaction. By embedding revenue capture into the payment flow, it removes the need for separate billing, invoicing or collection and gives you a consistent way to manage and scale revenue. Because we handle the entire process, you build it into your payment offering without technical lift. Paired with Merchant Central, you manage agent relationships, fee schedules and reporting in one place, so the terms you agree to and the money that moves stay in sync.

To find out more about how NMI Split Payout and Merchant Central will simplify your operations and support a portfolio built to scale, reach out to a member of our team today.

1The 2025 McKinsey Global Payments Report: Competing systems, contested outcomes

Last Updated 10/08/2026
Raquel Sud
Raquel Sud
Product Marketing Manager

Raquel is the Product Marketing Manager for NMI's Merchant Central. She turns product capabilities into clear stories and go-to-market plans that help partners differentiate, deepen merchant relationships, and grow revenue. Drawing on her strategic thinking and cross-functional collaboration, she shares forward-looking insights on payments and merchant management.

Ready to get started?

Talk to Our Team

Discover your full growth potential and strengthen merchant relationships with Merchant Central Payments CRM.

Invalid number

By submitting your information, you agree to NMI's Privacy Policy & Terms and Conditions