Does an ISV need a payment license to offer embedded payments?

Not necessarily. An ISV can embed payments while a licensed PSP, PayFac or acquirer carries the regulated responsibilities, such as safeguarding funds and merchant underwriting. The ISV owns the product, the brand and the pricing. Some ISVs later become PayFacs themselves to capture more margin, which adds sponsor acquirer, risk and compliance obligations.

Who carries what

Embedded payments mean the merchant pays and gets paid inside the software. Regulation attaches to handling funds and underwriting merchants, not to the user interface. An ISV can offer onboarding, checkout and reporting under its brand while a licensed PSP, PayFac or acquirer safeguards the funds, underwrites the merchants and answers to the regulator and the schemes.

What the ISV keeps

• The product and the brand: the merchant sees the ISV, not the provider.
• Pricing to the merchant, within the agreement with the provider.
• The merchant relationship and the data generated by payments.

When a license becomes relevant

Some ISVs later become PayFacs to capture more margin and control settlement. That adds a sponsor acquirer agreement, scheme registration, risk and compliance teams, and in Europe usually a payment or e-money institution license. The decision depends on volume, margin and appetite for regulatory work. White-label infrastructure lets an ISV start without a license and move to the PayFac model later on the same platform, instead of rebuilding.