Recursive B2B Distribution: Incentives and Limits

CSG acquired iCheckGateway.com, later branded iCG Pay, in 2024 after the payment processor had spent roughly sixteen years building merchant and software relationships around established ACH and card networks. CSG paid $17.6 million at closing and agreed to additional performance-related consideration that could reach $15 million, according to Beige Media's examination of the transaction.

The acquisition included payment technology, though the purchase record assigned substantial value to customer contracts and operating continuity. CSG acquired merchants, independent software vendor relationships, personnel, and recurring transaction flows that could continue after ownership changed.

iCG built that value by embedding payment collection into software products already serving businesses in recurring-payment sectors. Merchant and software relationships converted access to established payment rails into recurring transaction flows.

A software partner could add payments to its existing workflow, share in transaction economics, and offer merchants a more complete product while iCG continued to perform the underlying processing.

The Recursive Distribution Model

iCG Pay centralized payment execution while software partners distributed that capability through merchant relationships they already controlled.
Recursive B2B distribution creates new usage when each intermediary turns an upstream capability into a distinct downstream offering.
Commercial depth remains bounded by the margin between the terminal customer's willingness to pay and the upstream cost of execution.
Support delays and lost customer attribution can weaken a channel even when the underlying technology continues to work.
Persistent intermediaries contribute integration, operation, trust, or liability management beyond the initial introduction.
Tenant controls, usage records, support boundaries, and contractual responsibility keep recursive channels economically and operationally legible.

The iCG Distribution Model

An independent software vendor often reaches the merchant before a payment processor does. Property-management software already organizes leases and balances, while utility or insurance systems already maintain accounts that generate recurring obligations.

Adding payment collection inside those systems lets the merchant resolve an established task without coordinating a separate interface and vendor relationship. iCG supplied the reusable payment layer behind that experience.

Its documented products included hosted payment pages, recurring billing, invoicing, virtual terminals, verification, and developer tools. The partner supplied the surrounding business system and the relationship through which the merchant encountered those functions.

The commercial incentives followed the integration. iCG’s 2021 ISV materials described sharing merchant transaction fees with software partners. CSG Forte’s current partner program similarly allows software vendors to receive a revenue share from ongoing processing volume or negotiate pricing.

One integration could reach several merchants, and every merchant could generate many transactions without requiring iCG to reproduce the full partner sales process for each account.

Execution remained concentrated. A public iCheckGateway merchant agreement identified the company as a third-party processor whose ACH transactions settled through an originating financial institution.

Merchants supplied transaction information and retained evidence of customer authorization, while the processor originated entries, reported returns, and maintained the operating connection to the payment system.

This division let the partner own a meaningful customer surface without rebuilding payment operations. The merchant could remain inside familiar software, the software vendor could deepen its product and earn recurring revenue, and iCG could receive additional processing volume. Each participant gained from continued use by the party below it.

Why Embedded Relationships Accumulate Value

The sectors identified in the acquisition made that continued use especially valuable. Financial services, insurance, utilities, and government collect recurring or necessary payments whose failure creates administrative work.

A rejected payment can trigger outreach, account review, another collection attempt, and reconciliation, giving the payment provider a role in operating continuity as well as transaction acceptance. An embedded gateway becomes harder to replace as those routines accumulate around it.

Migration may require new software work, merchant underwriting, bank and processor arrangements, and changes to stored payment instructions. The integration consequently ties the processor to both the software roadmap above it and the merchant's collection process below it.

Hosted interfaces strengthened that position by concentrating sensitive payment functions. The partner could preserve its customer-facing workflow while iCG handled payment credentials and transaction controls inside the processor environment.

This reduced the amount of payment infrastructure the software vendor had to build, secure, document, and support on its own. Compliance changes could then become shared product improvements.

When an account-validation requirement affected certain online ACH debits, iCG added verification functions that partners could use across their merchant base. A rule that would otherwise create repeated implementation work became another centralized capability distributed through existing integrations.

The acquisition record reflects the resulting commercial position. CSG reported approximately $9.5 million in 2023 revenue after transaction fees and described a history of double-digit organic growth. Its later purchase accounting recorded $10.7 million in acquired customer contracts, giving the installed relationships a distinct value apart from settlement balances moving through the processor.

The documented iCG structure contains one major software-partner layer followed by merchant fan-out. It provides evidence for a broader model without establishing an indefinitely nested iCG processing chain.

The general lesson comes from the way one headless capability, meaning a service that can operate beneath another company's interface, became part of another company's saleable product.

When Distribution Can Recurse

Recursive B2B distribution occurs when a capability passes through successive business relationships and remains commercially useful at the end. An infrastructure provider may serve a software company that serves a managed operator that serves an operating business.

Each intermediary incorporates the upstream service into its own product, workflow, or customer relationship. This structure differs economically from repeated delegation of one obligation.

A subcontracting chain can begin with one customer payment for one deliverable, after which each intermediary retains compensation and passes substantially the same work downward. The amount available for terminal execution declines with every transfer.

The iCG channel generated new usage as distribution expanded. A software partner introduced merchants, merchants introduced recurring payment activity, and iCG processed each eligible transaction. The payment capability remained stable while the number of commercial surfaces through which it could be reached increased.

Cloud software channels use the same economic structure through explicit wholesale and retail boundaries. Under AWS Marketplace's channel partner offers, an independent software vendor sets a wholesale cost and authorizes a partner to resell the product.

The partner marks up that cost for a particular buyer, and AWS distributes the resulting funds according to the agreed pricing. The revenue arrangement can take several forms without changing the underlying model.

A provider may charge wholesale subscription rates, meter usage, or share transaction revenue with the partner. Commercial viability depends on whether the resulting economics reward continued distribution and service at every necessary boundary.

Customer ownership must remain credible for the same reason. A partner will hesitate to place an upstream capability inside its product when the integration gives the supplier a route to bypass it.

Deal registration, account boundaries, and contractual customer protections preserve the partner's incentive to introduce demand while allowing the provider to retain enough visibility to support the service.

Low marginal execution cost increases the opportunity for recursion. Once a software integration is complete, another merchant or managed account may require little additional infrastructure from the upstream provider.

The partner's installed customer base can then create volume faster than the provider could reproduce those relationships through direct sales. A new layer remains viable when its contribution supports another source of revenue or reduces the cost of reaching and serving the next customer.

Integration can make the capability usable inside an established workflow. Managed operation can relieve the customer of specialized labor. Vertical trust can place the product before buyers who would not accept an unfamiliar upstream supplier on its own.

Every channel still operates within a finite margin envelope. The terminal customer's willingness to pay creates a ceiling, and the upstream cost of supplying the capability creates a floor.

Each intermediary consumes some of the remaining headroom through margin, service cost, or both, so commercially thin products reach their maximum useful depth sooner than high-margin capabilities with low marginal execution costs.

How Recursive Channels Decay

Channel depth can weaken the customer experience before margin disappears. A terminal customer reports a fault to the company holding the immediate relationship.

That company may escalate to a distributor, which may escalate to the infrastructure provider, while each handoff adds diagnosis, context transfer, and waiting time. This escalation latency grows when an intermediary cannot observe the underlying service or reproduce the failure.

The upstream provider may receive an incomplete account identifier, a modified description of the event, or a request stripped of the configuration that produced it. The capability can execute reliably in general while a particular customer's problem remains unresolved across organizational boundaries.

Attribution also decays with distance. The upstream provider may know aggregate usage while losing sight of the terminal organization, its operating context, and the intermediary responsible for its configuration.

Weak attribution impairs support, pricing, compliance, product planning, and concentration analysis because the provider cannot connect consumption to the conditions under which it occurred.

Programmatic advertising shows how a technically integrated chain can lose economic legibility. A 2020 ISBA and PwC study found that publishers received about half of the advertiser spending examined, while 15 percent could not be attributed to disclosed fees.

The causes of that unknown share remained unresolved, and the results documented the difficulty of reconciling money and activity across demand-side technology, exchanges, and supply-side systems.

Programmatic advertising begins with a media budget allocated to impressions. Intermediaries can improve targeting, verification, or market access, while their compensation draws from the same advertiser budget for the impression.

The chain becomes economically fragile when its cumulative fees and opacity consume the value available to the publisher and advertiser faster than the intermediaries improve the transaction.

Disintermediation creates another pressure. A layer that supplies only an introduction may remain useful while the upstream company lacks market access or the downstream account remains too small to serve directly.

As transaction volume grows, both sides gain a reason to contract around an intermediary whose continuing contribution no longer exceeds its margin. Persistent channel partners therefore accumulate functions that survive the introduction.

They may configure the product, operate it for the customer, or absorb responsibility the upstream supplier is poorly positioned to carry. iCG's software partners controlled established workflows, and the payment integration strengthened products merchants already depended upon; replacing the partner relationship would have required more than moving a lead into a direct sales queue.

Keeping the Chain Legible

Durable recursive distribution requires infrastructure that represents the chain directly. Twilio uses subaccounts to separate each downstream customer's activity and resources while billing aggregate usage to the parent account, according to its account documentation.

The parent can operate a shared integration while preserving customer-level boundaries for administration and diagnosis. Cloudflare addresses a similar problem through tenant accounts for channel and alliance partners.

Its tenant structure gives a partner administrative access across customer accounts while keeping customer data and settings separate. The partner can build a customer-facing interface or grant direct access without collapsing every deployment into one undifferentiated account.

Payments adds contractual controls to this technical separation. Nacha's nested third-party sender rules require a chain of origination agreements across participants. The rules prescribe no maximum number of levels, while each sender remains responsible for its own risk assessment and originating institutions must identify nested relationships. These controls preserve identity, activity, and responsibility across the channel.

The record connects the terminal customer to its intermediary, the relevant usage, and the party expected to respond. Pricing and branding can vary by layer while the operating history remains connected.

The same controls protect partner economics. Customer-level attribution allows revenue sharing, wholesale pricing, usage limits, and support costs to follow actual activity.

Clear account boundaries also reduce the incentive for an upstream provider to treat every partner-introduced customer as an unassigned direct account, which would weaken the reason to distribute the capability in the first place.

Aggregation introduces a separate strategic choice. A product that routes among substitutable upstream providers can improve price and resilience for the customer while reducing any one supplier's control over the relationship. A product embedded around one provider can produce deeper integration and shared switching costs. Both structures extend distribution, though they allocate pricing power and loyalty differently.

iCG built value through the embedded form. Its partners gained a payment capability and recurring economics inside products they already sold, while iCG gained merchant reach and transaction volume without taking over every downstream relationship.

Centralized processing, contractual responsibility, and visible transaction outcomes kept the underlying service intact as distribution expanded.

Recursive B2B distribution reaches its useful limit when another layer consumes more margin, time, or accountability than it contributes in access and operation. Before that point, one company's infrastructure can become another company's product and then travel again through another commercial relationship.

The resulting chain can turn a technical capability into a transferable network of integrations and customers, as long as every participant can still identify what it contributes, what it earns, and what it must do when execution fails.