What Are Embedded Payments
Definition
Embedded payments is the integration of payment acceptance capabilities directly within a software application's native user experience, allowing end users to pay without leaving the platform or being redirected to a third-party checkout.
How It Works
The ISV integrates payment APIs from a PayFac-as-a-Service provider, gateway, or its own PayFac infrastructure into its application workflows. Payment UI is rendered inline via hosted fields, SDKs, or direct API calls. The ISV's platform handles merchant onboarding (KYC/KYB), transaction routing, settlement orchestration, and reconciliation — all within the software context.
Why ISVs Care
Embedded payments transform a software product from a cost center into a revenue engine. ISVs earn a margin on every transaction their merchants process (typically 20-80 basis points), creating recurring revenue that scales with merchant GMV. It dramatically increases switching costs and improves end-user conversion rates by eliminating checkout redirects.
Embedded payments is the single most significant revenue opportunity for ISVs in the last decade. It’s how SaaS companies turn their software into a payments platform — and it’s reshaping how B2B software is monetized.
What Embedded Payments Looks Like in Practice
Embedded payments means your software’s users can accept and make payments without ever leaving your application. No redirects. No third-party checkouts. No “powered by [payment company]” branding.
Real-world examples:
- Salon booking software with built-in checkout — the client books and pays in one flow
- Property management platform where tenants pay rent through the landlord’s software
- Restaurant POS that handles table orders, payment splitting, and tip processing natively
- Field service software where technicians collect payment on-site through the mobile app
In each case, the payment experience is indistinguishable from the rest of the software. That’s what “embedded” means.
How Embedded Payments Work (Architecture)
An embedded payments implementation has five technical components:
1. Merchant Onboarding
Your software includes a payments setup flow where your customers (the merchants) provide their business details. Behind the scenes, KYC/KYB verification runs through your payment provider’s APIs. Approval can happen in minutes.
2. Payment Capture
Your checkout or payment screen uses the payment provider’s SDK or hosted fields to collect card data. The sensitive data never touches your servers — it goes directly to the provider, which returns a token.
3. Transaction Processing
Your backend sends the token, amount, and metadata to the payment provider’s API. The provider routes the transaction through their processing infrastructure (or your PayFac master MID) to the card networks.
4. Settlement and Fund Splitting
After authorization and batch settlement, funds flow to a trust or settlement account. The payment provider (or your PayFac) splits funds: the merchant receives their share minus processing fees and your platform’s markup.
5. Reporting and Reconciliation
Transaction data flows back into your application through webhooks and APIs. Your software can display payment dashboards, generate statements, and handle payment reconciliation — all within the platform.
The Business Case for ISVs
Revenue Impact
The math behind embedded payments is what makes it transformational:
| Metric | SaaS-Only Model | SaaS + Embedded Payments |
|---|---|---|
| Monthly SaaS revenue | $200/merchant | $200/merchant |
| Payment volume per merchant | — | $50K/month |
| Payment margin (30 bps) | — | $150/month |
| Total per merchant | $200/month | $350/month |
| Revenue increase | — | +75% |
At scale, payment revenue often exceeds SaaS subscription revenue. Toast generates more from payments than from software. Shopify’s merchant solutions (including payments) are 3x its subscription revenue.
Retention Impact
Once a merchant’s payments are embedded in your software, switching means migrating their entire payment infrastructure — transaction history, recurring billing profiles, customer payment methods. Churn drops dramatically.
Industry data suggests ISVs with embedded payments see 30-50% lower churn than those without.
Valuation Impact
Public markets value payment revenue at higher multiples than SaaS revenue because it scales with merchant GMV without proportional cost increases. ISVs with embedded payments command higher revenue multiples at exit.
Three Paths to Embedded Payments
| Path | Setup Time | Revenue Share | Best For |
|---|---|---|---|
| Payment gateway referral | Days | 5-15 bps | Testing demand, minimal investment |
| PayFac-as-a-Service | 2-8 weeks | 20-50 bps | Most ISVs starting embedded payments |
| Full PayFac registration | 6-12 months | 60-100+ bps | ISVs with $100M+ TPV |
Most ISVs should start with PayFac-as-a-Service (Stripe Connect, Finix, Adyen for Platforms) and evaluate full registration once they reach significant transaction volumes.
What Makes Embedded Payments Work (vs. Just Adding a Payment Button)
The difference between embedded payments and slapping a “Pay Now” button on your app:
Embedded payments:
- Merchant onboarding is part of your software setup flow
- Payment data feeds your application’s reporting and analytics
- Settlement and reconciliation are visible within your dashboard
- The payment experience carries your brand
- You earn revenue on every transaction
Payment button:
- Customer clicks a link to a third-party payment page
- Payment data lives in a separate system
- No integration with your application’s data model
- The third-party brand is visible
- You earn nothing
The technical gap between these two approaches is significant, but the business impact gap is massive.
Common Implementation Mistakes
- Treating payments as an afterthought — Payments should be designed into your product architecture from the start, not bolted on later
- Underinvesting in merchant onboarding UX — If your merchants can’t get set up in minutes, adoption stalls
- Ignoring reconciliation — Merchants will call your support team when deposits don’t match expectations. Build reconciliation tools early.
- Choosing the wrong payment partner — Evaluate partners on ISV-specific capabilities (sub-merchant onboarding, split settlement, white-label) not consumer-facing features