How is a portfolio structured?
As a tree. A channel sits at the top, sub-portfolios branch beneath it, and merchants hang off whichever node owns the relationship. An ISO with three sales offices models exactly that: one channel, three sub-portfolios, each office’s merchants under its own branch.
Every setting inherits down the tree and can be overridden at any node: pricing, residual splits, branding, user access. That one model replaces the usual pile of per-office spreadsheets and side agreements with structure the platform enforces. When the deal you cut with an office lives in the tree instead of in someone's memory, it survives the person who negotiated it.
How are residuals calculated and paid?
Line by line. Every merchant’s transactions, fees, and costs post to the ledger, and the residual engine computes each level’s share from the actual line items, not from a summarized statement you have to take on faith. You can trace any residual dollar back to the transactions that produced it.
Because QorPay is the processor, there is no upstream processor’s margin hidden in the math. Splits are defined per node in the hierarchy, and payouts run on a fixed schedule. If you have ever taken a residual statement on faith because checking it was impossible, that is the difference being sold here: every dollar traceable, every month. Bring a statement you have doubts about and we will show you what line-item looks like.
What can partners white-label?
The merchant-facing surfaces: checkout pages, payment forms, receipts, and statements can all carry the partner’s brand instead of QorPay’s. Styler handles the checkout and receipt theming (colors, logos, and layout) without custom development.
Branding is set per node in the hierarchy, like everything else in Channels. A channel can set a default look and let sub-portfolios override it for their own merchants. Your merchants see your name at the moment money changes hands; the relationship equity that builds belongs to you, not to your processor.
How do operators manage merchants at scale?
By exception, not by scrolling. Dashboards surface the merchants that need attention (dispute ratios climbing, volume out of profile, boarding applications stuck in review), so a portfolio of hundreds is managed by working a short queue.
Bulk operations cover the routine work: pricing updates across a sub-portfolio, statement access, user provisioning. The same risk signals that drive Circuit Breaker at the platform level are visible to the operator at the portfolio level, so you see the merchant drifting toward trouble in the same window the platform does, while there is still time to make the call that saves the MID.
What's available through the API?
Channels is part of the same REST APIs as processing: merchant boarding, hierarchy management, and reporting are endpoints, not portal-only features. Anything an operator can do in the portal, an integration can do programmatically.
That matters for ISOs and platforms running their own CRM or back office: portfolio data flows into your systems instead of living only in ours. The Channels introduction covers setup and the core objects.