How do ISVs earn revenue from embedded payments?

Most ISVs set a price per transaction for their merchants and keep the difference between that price and their processing costs. Others bundle payments into a software subscription or charge a monthly platform fee. On white-label infrastructure, the ISV decides the pricing model per merchant segment, while its own infrastructure cost stays predictable.

Three pricing models

Most ISVs set a transaction price for their merchants, for example a percentage plus a fixed fee, and keep the difference between that price and their processing cost. Others include payments in a software subscription tier, where the payment margin funds a higher plan. A third group charges a monthly platform fee for payments on top of transaction pricing.

Which one, for whom

• Transaction pricing suits merchants with variable volume and ISVs that want revenue to scale with usage.
• Bundled pricing suits ISVs selling to small merchants who prefer one bill.
• Platform fees suit larger merchants negotiating interchange-plus rates.

What white-label infrastructure changes

The ISV's own cost per transaction stays predictable, whatever the acquirer behind it, because routing and provider contracts sit on the infrastructure. The ISV can then price per merchant segment, by country, by volume tier or by product line, and see the margin per merchant in reporting. Payments often become the ISV's largest revenue line within a few years, which is why pricing control matters more than the initial rate.