What does an integrated payment offer require that a referral does not?
A referral needs no payment infrastructure: the platform sends merchants to a provider and earns a share of the revenue. An integrated offer needs merchant onboarding inside the software and a branded checkout. A full PayFac adds underwriting, risk monitoring and settlement control. Each stage asks more of the infrastructure, which is why platforms plan the full path early.
In detail
A referral needs no payment infrastructure: the platform sends merchants to a provider and earns a share of the revenue. An integrated offer needs merchant onboarding inside the software and a branded checkout. A full PayFac adds underwriting, risk monitoring and settlement control. Each stage asks more of the infrastructure, which is why platforms plan the full path early.
Three stages of embedded payments
In a referral, the software platform introduces merchants to a payment provider and earns a share. The merchant signs with the provider, uses the provider's tools, and the platform holds no infrastructure. In an integrated offer, the merchant never leaves the software: onboarding, checkout and reporting happen inside it, under the platform's brand. A full PayFac adds underwriting, risk monitoring, settlement and the regulatory role.
What integration needs
- Merchant onboarding with KYB forms and document collection inside the software.
- A branded checkout and payment links, with the methods each market expects.
- Transaction data and payouts visible in the software, not in a provider's portal.
- Routing and provider connections managed by the platform or its infrastructure partner.
Why plan the whole path
Each stage asks more of the infrastructure. A platform that builds a referral integration, then rebuilds for integrated payments, then again for a PayFac model, pays three times. Choosing infrastructure that supports all three from the start lets the platform move stage by stage as its volume and appetite for risk grow.