A platform that processes customer transactions earns more from each account than one that only sells seats. Subscription revenue grows with headcount, while payments revenue grows with the customer’s sales volume. That is why embedded payments have become a major priority on vertical software roadmaps.
Revenue Per Customer and Take Rates
Bain & Company and Bain Capital estimated that US revenue for platforms and enabling partners would rise from $21 billion in 2021 to $51 billion in 2026, with transaction value reaching $7 trillion. Payments and lending represent the largest parts of that opportunity.
The per-customer economics are even clearer. Platforms typically keep 1% to 3% of processed volume. A field service company running $600,000 a year through its scheduling software could generate $6,000 to $18,000 in processing revenue, compared with perhaps $3,600 in annual subscription fees. Platforms adding financial products have reported revenue per customer rising 2 to 5 times, changing both unit economics and pricing strategy.
Adoption Across Vertical Software
More than half of North American software vendors offered embedded payments in 2025, and about 76% of vertical platforms in one 2026 benchmark called the capability very important or a critical revenue driver. Adoption is strongest where software already sits inside the transaction, such as restaurant point of sale, field service scheduling, legal practice management, veterinary software, and youth sports registration.
These platforms already know what was sold, to whom, and for how much. Sending customers to a separate payment system breaks that workflow and gives up both data and revenue. Strong vertical software businesses also tend to retain customers well, so once payments are adopted, the revenue can persist for years.
Paths Into the Product
The main models differ in how much responsibility the platform accepts. A referral model sends the customer to a payment provider in exchange for a revenue share. An integrated model keeps sign-up inside the software while the provider retains the merchant relationship. A facilitator model makes the platform the party of record, producing better economics but much heavier obligations.
Most companies begin with embedded payments delivered through a provider that handles onboarding, underwriting, and settlement behind an interface controlled by the software platform. Customers remain inside one product while regulated operations stay with a specialist partner. Platforms with enough volume may later take on more of the payment stack to improve margins.
Liability Under the Facilitator Model
A payment facilitator must underwrite and monitor each sub-merchant under an acquiring bank’s supervision. That includes identity checks, sanctions and money laundering screening, transaction monitoring, and dispute processes.
The liability is real. If a merchant accepts deposits and closes before delivering the service, the facilitator may be responsible for returning funds to cardholders. Platforms serving contractors, events, or other businesses that collect money well before fulfillment therefore take on financial risk unrelated to software performance.
Compliance Staffing and Security Scope
Compliance is easy to underestimate. Underwriting, monitoring, and dispute handling require permanent staff, often before payment revenue reaches scale. Security obligations also expand because the product now touches cardholder data and inherits additional assessment requirements. Cyber incidents can make that downside expensive, with breaches costing US organizations an average of $10.22 million.
The Attach Rate Problem
Attach rate, the share of active customers using the payment product, can matter more than pricing. A 3% take rate with only 10% adoption may produce less revenue than a 2% take rate with half the customer base using payments. Expansion within the existing base also improves the retention benchmarks investors track.
Selling payments to existing customers is also cheaper than acquiring new software customers. A platform with 2,000 paying accounts and a 15% attach rate still has about 1,700 existing customers whose payment volume is going elsewhere.
Onboarding is where attach rate is won. Extra forms, slow manual underwriting, and difficult migrations reduce adoption. Strong platforms make payment acceptance part of initial setup rather than a separate project. Pressure and discounts are poor ways to reduce churn, and sales teams also need to explain operational details such as deposit timing and settlement clearly.
The Shape of the Business Afterward
Once embedded payments are established, the company is no longer only a software vendor. Revenue increasingly follows customer transaction volume, compliance becomes a permanent function, and the subscription product becomes an acquisition channel for a larger financial-services revenue stream. Platforms that manage the transition well plan for those staffing, security, and liability costs before payment volume begins to scale.
