Revenue-Sharing Model
A revenue-sharing model is a commercial arrangement in which partners split the revenue a product generates — a percentage of interchange, processing margin, interest, commission or subscription — rather than one paying the other a fixed fee, so that both are paid in proportion to the product's success. It is the standard structure of embedded finance, banking as a service and referral arrangements; the terms that matter are what "revenue" means, who bears the costs, and what happens at termination.
- Also known as
- Revenue share, Rev share, Revenue-sharing agreement, Profit share
- Used at
- embedded payments (the software company and the payment provider split net processing revenue), BaaS (the fintech brand and the sponsor bank split interchange and fees), embedded lending (the distributor earns a share of margin or an origination fee), insurance distribution (commission share), affiliate and referral programmes, app-store and marketplace economics, and content and data licensing
- Binding
- contract; regulated products carry constraints — a bank's payments to a distributor must not be an inducement that breaches conduct rules, a lender's referral fees are regulated as credit broking, and insurance commission disclosure rules apply; tax and accounting treat the share as revenue to each party on a gross or net basis depending on who is principal
- Typical splits
- embedded payments 30–70% of net revenue to the software distributor depending on who owns the merchant relationship and bears risk; BaaS 50–80% of interchange to the fintech brand after scheme and processing costs; lending referrals 1–3% of principal or 10–30% of margin; insurance 10–30% of premium; the split usually improves with volume tiers
- Typical terms to negotiate
- the revenue definition (gross or net of scheme fees, processing, fraud losses, chargebacks, refunds); the cost items deducted before the split; minimums and tiers; reporting and audit rights; exclusivity; term and termination; what happens to the customers and the revenue stream after termination (tail payments, or nothing); and who owns the customer data
- Parties
- the distributor (software, marketplace, brand), the provider (bank, PSP, lender, insurer), the platform between them if any, the customers whose payments generate the revenue, and the acquirers who value the revenue stream
How a revenue-sharing model works in practice
A vertical-software company signs an embedded-payments agreement with a payment provider. Merchants on the software process through the provider; the provider charges merchants 2.9% plus 30 cents; scheme and interchange costs of about 2.1% are deducted, processing costs of 0.15%, fraud and chargeback losses; the net revenue of about 0.6% is split 50/50; the software company earns 0.3% of every transaction its merchants process. At €500 million of volume that is €1.5 million a year of revenue at near-100% margin — for the software company, its highest-margin product line; for the provider, distribution without a sales force. The agreement defines every deduction, gives the software company monthly reporting and annual audit rights, tiers the split to 60/40 above €1 billion, and states that on termination the merchants remain the provider's and the software company receives a tail of 50% of its share for 24 months.
The disputes come from the definitions. "Revenue" that turns out to be net of costs the distributor never saw; fraud losses allocated to the split though the provider's risk controls decided them; a platform in the middle taking a margin before the split; a termination clause that leaves the distributor with nothing when the provider is acquired and the programme ended. For a fintech provider, the model is growth on other companies' customer relationships; for a distributor, it is a revenue line that a buyer will value on its durability — which is the contract's term and tail, and the switching cost of the merchants. In an acquisition of either party, the revenue-share agreements are read for change-of-control clauses, exclusivity, and whether the revenue is the target's or its partner's.
Example
A software company earning €4 million a year from an embedded-payments revenue share is acquired by a private-equity firm. Diligence reads the agreement: the split is 50% of net revenue, "net" being defined by a schedule the provider updates unilaterally; the provider added a "platform fee" to the schedule two years ago that reduced the software company's share by 12%; the agreement has three years to run with no tail on expiry; and it contains a change-of-control clause allowing the provider to terminate. The buyer discounts the payments revenue in its model by 40%, negotiates a renegotiated agreement as a condition — fixed definitions, audit rights, a five-year term with a 36-month tail, and the change-of-control clause removed — and closes at a price €9 million lower than the seller's expectation, the difference being what the original contract had left to the provider's discretion.
Common mistakes
- "Revenue" undefined, or defined by a schedule one party controls. - Costs deducted before the split that the distributor cannot see or audit. - No tail on termination, so the revenue disappears with the relationship. - Change-of-control clauses that let the partner walk when either party is sold. - Valuing a revenue-share line without reading the agreement's term and definitions.