How long does it take to launch embedded payments?
It depends on the operating model. A PSP referral arrangement launches in 4–8 weeks — the constraint is legal review, not engineering. A light PFaaS (revenue-share) integration takes 5–10 weeks from signed vendor contract to first live transaction. A full PFaaS / managed PayFac integration takes 3–9 months from signed contract to first live transaction, with 1–2 engineers for 3–6 months. Managed PayFac with orchestration takes 9–18 months from decision to full transition. Full registered PayFac status takes 2+ years, driven by state money transmission licensing (18–36 months). Migrating between vendors runs 3–9 months end-to-end.
Reviewed by Jane Podbelskaya · last reviewed 2026-07-28 · how we produce answers
The timeline, by operating model
Launch time is a function of the model you choose, because the model determines how much infrastructure, compliance, and engineering sits on your side of the line:
| Operating model | Time to launch | What the clock measures | Team required |
|---|---|---|---|
| PSP referral | 4–8 weeks | Referral agreement to live; constraint is legal review, not engineering | Part-time partner manager |
| Light PFaaS / revenue share | 6–10 weeks | Signed vendor contract to first live transaction | One engineer for 1–2 months, plus a PM |
| Full PFaaS / managed PayFac | 3–9 months | Signed vendor contract to first live transaction; 3–6 months of API integration | 1–2 engineers for 3–6 months, payments PM, one CS resource |
| Managed PayFac + orchestration | 9–18 months | Decision to full transition, including 3–6 months of vendor negotiations | 3–8 dedicated payments FTEs |
| Full registered PayFac | 2+ years | Decision to full operational status | 8–20+ FTEs — a payments org |
For the full registered PayFac path, the components stack: card network registration takes 3–6 months, PCI DSS Level 1 takes 6–12 months, and money transmission licenses take 18–36 months for full 50-state coverage. That licensing timeline — not engineering — is why the total runs past two years, and it is one reason only 10% of vertical SaaS platforms surveyed in the Rainforest 2026 study (released May 2026) are full registered PayFacs, versus 82% operating on managed PayFac / PFaaS models.
[Review: Jane] The chapters state time-to-launch from signed vendor contract (Stages 2–3) but do not state a typical vendor-selection-and-negotiation duration for a first-time launch. The migration chapter’s weeks 4–8 vendor-selection phase covers migrations specifically. If we want an all-in “decision to live” figure for first launches at Stages 2–3, that needs a source or an advisory estimate.
What fills the calendar
For a full PFaaS launch, the 3–9 month window covers API integration (payment capture, settlement, reporting, dispute management, onboarding flows), sandbox testing, formal processor certification, and staff training. Two planning rules from the guide are worth budgeting from day one. First, add a 25% buffer to engineering estimates — payment integrations routinely take longer than expected. Second, if you are replacing an existing processor, plan for parallel processing: running old and new processors simultaneously for 30–90 days per merchant cohort, with legacy stored cards continuing on the old processor for a typical 6–12 month dual-processing window because processor-specific card tokens do not move.
Migrations run on their own clock
Switching vendors or models after launch is a 3–9 month project end-to-end, phased as: assessment (weeks 1–4), vendor selection (weeks 4–8), technical integration (weeks 8–20), merchant migration (weeks 16–36), then ongoing optimization. Merchant migration is where most projects underestimate — new merchants go on the new processor first, existing merchants move in cohorts, and access to the old processor’s dispute system should be kept for 120 days post-migration. The payback math typically works: a well-constructed migration business case shows a 6–18 month payback period, and a full PFaaS integration pays back in 18–24 months for platforms that crossed the $50M GMV threshold on referral economics.
When the fastest launch is not the right launch
Referral’s 4–8 week timeline is real, but so are its constraints: 0–20 bps of net take rate, and — uniquely among the models — a merchant onboarding flow owned by the processor, not by you. In trust-sensitive verticals such as healthcare, legal, and professional services, a branded in-product payments experience is a product-quality requirement, not a nice-to-have, which effectively rules out referral regardless of how fast it ships. And speed at launch can become cost later: staying on referral past $50M GMV — where full PFaaS delivers a 4–5x revenue uplift on identical volume — costs $900K–$1.5M in foregone revenue over three years. A restaurant-tech or field-services platform expecting to scale GMV quickly should weigh a slower PFaaS launch against a fast referral launch plus a 3–9 month migration later.
Where to go deeper
The five-stage model framework, GMV thresholds, and graduation triggers are in the payment models chapter; the phase-by-phase transition playbook, including the token-vault problem, is in the migration chapter. To find which stage fits your platform today, run the payments model navigator, and short-list providers in the payments vendor database. For the model-choice question that usually precedes the timeline question, see PayFac vs PayFac-as-a-service: which should software companies choose?
FAQ
How long does migrating from one payments vendor to another take?
Migrations typically run 3–9 months end-to-end across five phases: assessment (weeks 1–4), vendor selection (weeks 4–8), technical integration (weeks 8–20), merchant migration (weeks 16–36), then ongoing optimization. Merchant migration is where most projects underestimate — plan it with the same rigor as the technical build.
Why does full PayFac registration take 2+ years?
The long pole is money transmission licensing: 18–36 months for full 50-state coverage. Card network registration takes 3–6 months and PCI DSS Level 1 compliance takes 6–12 months. Only 10% of vertical SaaS platforms surveyed in the Rainforest 2026 study are full registered PayFacs — for most, it is an optional endpoint, not a required one.
Can we launch fast on referral and upgrade later?
Yes — referral launches in 4–8 weeks and is the standard starting point below $10M GMV. The risk is staying too long: above $50M GMV, full PFaaS delivers a 4–5x revenue uplift on the same volume, and staying on referral past that threshold costs $900K–$1.5M in foregone revenue over three years.
How much engineering does a full PFaaS launch require?
Typically one to two engineers for three to six months of API integration work, plus a product manager owning the payments roadmap and a customer success resource trained on payment onboarding. The vendor bears the compliance and risk obligations. Add a 25% buffer to engineering estimates — payment integrations routinely take longer than expected.
Sources
- Rainforest, 2026 Vertical SaaS Embedded Payments Benchmarking Study (Q1 2026 fielding, May 2026 release) (2026)
- UBS Global Research, Tim Chiodo, The Question 6.0 (May 2026)
- Charge Forward, Choosing Your Embedded Payments Model (Embedded Payments Guide) (June 2026)
- Charge Forward, The Migration & Transition Playbook (Embedded Payments Guide) (June 2026)