The residual engine, and why partners stay.
Most providers can pay a channel on processing because processing is all they sell. Ours splits any revenue event down a multi-level hierarchy, which is what lets a partner be paid on software, tax filings and funding too.
From revenue event to payout
Events collected
Every billable event across every product lands in one stream.
Split by hierarchy
Platform, OEM or bank, partner, branch, rep. Each event takes exactly one split path.
Statement generated
Per party, per period, published to their own portal rather than emailed as a spreadsheet.
Payout and mark
Paid, marked and reconciled, with disputes attached to the line rather than the total.
Paid on more than basis points
Every line splits
Subscriptions, filings, funding fees and device revenue are all events the engine can divide.
Your own downline
Offices carry branches, branches carry reps, each seeing its own numbers and nothing above.
Expansion counts
When a merchant adds a product a year later, it lands on the original split path.
A real dispute path
Disagree with a line rather than argue about a total.
Same engine for us
We are not running separate books for the channel.
Portal, not attachments
Each party signs in and sees their own history.
Talk to an engineer, not a form.
Integration questions get answered by the people who built it.