Embedded payments for vertical SaaS / PayFac
The short answer
Build payments around the industry workflow, not just a checkout button. Decide whether the software platform uses a provider-led embedded payments arrangement or operates as a registered payment facilitator with a sponsoring acquirer. Branding a payment experience does not by itself make the platform a PayFac.
Where does the vault sit?
Upstream of the parent platform account: a platform-managed token layer with explicit per-merchant permissions.
Upstream of each child merchant account: merchant-scoped storage and forwarding boundaries.
Neither design makes tokens interchangeable or changes merchant-of-record and settlement responsibilities.
What your team needs to do
- Map the vertical workflow: bookings, invoices, deposits, subscriptions or in-person collection, including refunds and disputes.
- Choose the supported platform model and document who onboards and underwrites merchants, monitors risk and handles disputes.
- Set merchant-scoped account access and payment references. Confirm supported platform fees, seller payouts, reserves and settlement reports.
- Reconcile payments to the underlying business object and monitor merchant activation, retention and payment margin.
Before you build
- PayFac registration, sponsorship and obligations depend on jurisdiction, card-network rules and the approved provider model. Software integration alone does not establish that status.
- Merchant of Record, payment facilitator, processor and software platform are distinct roles. Document their responsibilities; do not infer them from branding or the direction of a fee transfer.
- PCI scope, lawful credential use, tenant isolation and authorization still require review. A vault is not a compliance guarantee.
Measure the right outcome
Activated merchants, payment adoption, net payment margin, reconciled payouts, dispute rate and support effort.
Questions operators ask
Is a vertical SaaS platform automatically a PayFac?
No. Its status and duties depend on its agreements, sponsorship and registration where required. A provider-led embedded payment model can allocate responsibilities differently.
Does a platform fee make the platform the Merchant of Record?
No. Fee allocation does not alone identify the seller of record or transfer the corresponding obligations.
Integration considerations
A forward proxy can resolve token references for permitted outbound requests; inbound capture typically uses a separate collection or reverse-proxy flow. Validate exact behavior, endpoint contracts and permission. Some workflows need asynchronous batch transfer rather than HTTP forwarding. Industry eligibility depends on jurisdiction and provider underwriting.
Make the next decision concrete
Write down the business model, account owner, required operation, permitted data and proof of completion. Resolve those five points before comparing providers.