From Integration to Adoption
Attach rate is the metric that decides whether your embedded payments product is a real business or a slide in a deck. Engineering it requires five operational levers — and the May 2026 Rainforest data shows most platforms have never seriously pulled any of them.
20 min read
Why attach rate is the metric that matters
Most embedded payments conversations start with the wrong number. Executives fixate on take rate — the basis points earned per transaction — when the more important variable sits upstream: how many of your customers are using your payments product at all.
Two related metrics in the Rainforest 2026 vocabulary anchor this. ATTACH rate is the percentage of NEW customers who sign up for payments — a measure of how well your onboarding and sales motion convert. ADOPTION rate is the percentage of ALL eligible customers signed up — including the “backbook” of customers who joined before payments existed or before your onboarding was tight. ACTIVE ADOPTION rate is the percentage of signed-up customers who are actually transacting. The full Rainforest 2026 medians:
| Benchmark | 50th percentile (median) | 75th percentile | 90th percentile |
|---|---|---|---|
| Attach rate (% of new customers signed up) | 63% | 78% | 93% |
| Adoption rate (% of all eligible signed up) | 48% | 63% | 78% |
| Active adoption rate (% of signed-up who actively use) | 63% | 78% | 93% |
| Take rate | 0.83% | 0.98% | 1.13%+ |
| Percent of platform revenue from payments | 30% | 35% | 40%+ |
The revenue implication of each percentage point is not trivial. On a 2,000-merchant platform at $500K average annual GPV and 50 bps net take rate:
| Attach Rate | Active Merchants | Annual GPV | Annual Payments Revenue |
|---|---|---|---|
| 40% | 800 | $400M | $2.0M |
| ~50–60% (industry median) | 1,000–1,180 | $500M–$590M | $2.5M–$2.95M |
| 75% | 1,500 | $750M | $3.75M |
| 93% (Optimized median) | 1,860 | $930M | $4.65M |
The delta between roughly 50–60% attach and 93% (Rainforest Optimized median) is over $2M in additional annual revenue — on the same merchant base, at the same take rate, simply by improving adoption. Multiply across a platform with tens of thousands of merchants, and the stakes get serious quickly.
Beyond direct revenue, attach rate is a leading indicator for churn. Platforms consistently find that merchants using embedded payments churn at 30–50% lower rates than non-payments customers. Payments create workflow dependency — a contractor who accepts payments through your platform, stores customer cards on file, and reconciles invoices in-app is deeply embedded in your ecosystem. Switching software means rebuilding all of that. Attach rate is, in effect, retention rate dressed up as a revenue metric.
Charge Forward Insight
Rainforest’s headline finding is that 78% of vertical SaaS platforms target an adoption rate of 71% or higher — and only 25% have reached that level today. Most platforms sit 15–30 percentage points below their stated target. The gap holds across verticals, ARR bands, and years in payments. Time alone does not close it — platforms with five or more years of payments experience can sit at the same performance level as platforms in their second or third year. What separates the platforms that close the gap from those that don’t is operational maturity. That is what this chapter is about.
The performance gap, in three views
By maturity stage (the strongest predictor)
Rainforest segments platforms into three maturity stages — Emerging, Scaling, Optimized — self-reported and cross-validated against benchmark performance. Maturity stage was the strongest predictor of four out of five benchmarks (the fifth, take rate, is most strongly predicted by leadership structure):
| Benchmark (median) | Emerging (8%) | Scaling (76%) | Optimized (16%) |
|---|---|---|---|
| Attach rate | 33% | 63% | 93% |
| Adoption rate | 33% | 48% | 78% |
| Active adoption rate | 48% | 63% | 78% |
| Take rate | 0.53% | 0.98% | 0.98% |
| Percent revenue from payments | 10% | 30% | 35% |
The Scaling-to-Optimized jump (63% → 93% attach, 48% → 78% adoption) is non-linear. Two platforms in the same vertical, at the same ARR, can be a stage apart — and the operational profile that gets a platform from Scaling to Optimized is what the rest of this chapter is about.
By vertical
| Vertical | Typical Range | Leader Rate | Key Driver |
|---|---|---|---|
| Restaurant Tech | 75–90% | 95%+ (Toast) | POS integration mandatory; payments embedded in every order flow |
| Property Management | 50–70% | 80%+ (AppFolio) | Rent collection workflows; ACH dominance reduces friction |
| Field Services / HVAC | 40–60% | 75%+ (ServiceTitan) | Mobile field payments; job-completion-to-payment workflow |
| Auto Repair | 35–55% | 70%+ | In-shop invoice integration; fleet billing CNP |
| Healthcare / Dental | 30–50% | 65%+ | Patient billing portals; co-pay at point of care |
| Fitness / Wellness | 50–70% | 80%+ (Mindbody) | Recurring membership billing; stored card on file |
| Legal | 25–40% | 55%+ | Trust accounting complexity; specialized billing platforms |
| Construction | 15–30% | 45%+ | Large B2B ACH preference; commercial invoice cycles (57-day avg) |
Several patterns stand out. Restaurant tech operates at structurally higher attach rates because payments are inseparable from the point-of-sale workflow — a restaurant cannot take orders through Toast without also processing payments through Toast. That is the gold standard of integration depth.
Construction sits at the opposite end: large B2B invoices, ACH dominance, procurement-team involvement, and 57-day average payment delays create friction that suppresses attach rates even on mature platforms. For construction-focused SaaS, the near-term attach opportunity is in ACH adoption and supplier-payment automation, not card processing.
Important nuance from the Rainforest data: vertical was the FOURTH strongest predictor of payments performance, behind maturity, payments age, and payments leadership structure. Vertical context matters, but it is not destiny.
By payments leadership (the strongest predictor of take rate)
| Payments leadership structure | Median take rate | Implication |
|---|---|---|
| C-suite-level payments leader (CRO, CPO, GM-Payments) | 98 bps | Top quartile of vertical SaaS platforms |
| Non-C-suite dedicated payments leader | 83 bps | 15-bps deficit vs. C-suite leadership |
| No dedicated payments leader | 53 bps | 45-bps spread = ~$900K/yr on $200M GMV |
Practitioner heuristic from Rainforest: adoption is everyone’s job — product, engineering, marketing, sales, customer success — and take rate is the payments leader’s job. Keep the broader team focused on adoption as the north star. Let the payments leader optimize take rate. Without a dedicated leader, both stall.
The five levers of payment adoption
Attach rate does not improve by itself. Every platform that has moved from Emerging to Optimized has done so by systematically pulling the same set of operational levers. Each lever is independently fixable; each one moves the rate; none of them is mysterious.
Lever 1 — Product integration
The single most powerful determinant of attach rate is how deeply payments are embedded in the core workflow. The Rainforest 2026 data is unambiguous on this: 90% of platforms cite seamless integration with the core software as a top adoption driver — far ahead of any other factor.
Good integration: when a contractor closes a job in ServiceTitan, the app surfaces a payment collection step in the same workflow. The contractor cannot skip it without explicitly choosing to invoice later. Payment is the default, not the exception.
Poor integration: a button in the sidebar labeled “Accept Payments” that redirects users to a separate merchant portal with its own login. That is not an embedded product — it is a referral with extra steps.
The architectural principle: every moment in your software where money changes hands should have a payments touchpoint native to that moment. Job completion, invoice approval, subscription renewal, tenant move-in — each is an integration opportunity. If your top 10 user flows do not all have a native payments hook, you have not finished integration.
Lever 2 — Onboarding experience
Onboarding friction is where attachment goes to die. The ServiceTitan case study is canonical: when customers had to complete an external merchant account application — financial statements, underwriting wait — the process dragged on two to three months and fewer than 20% of contractors made it through.
When ServiceTitan moved to a PayFac-as-a-Service model with in-app KYC, the experience went from months to minutes. Pre-populated data (business name, EIN, address) from the existing software account eliminated redundant entry. Instant underwriting decisions removed the waiting period. Adoption exploded.
The operational targets for a best-in-class onboarding flow:
• Time to activate: under 5 minutes for the majority of merchant types.
• Pre-population rate: 80%+ of required fields completed from existing account data.
• KYC pass rate: 90%+ of starts result in approved sub-merchants.
• Time to first transaction: under 48 hours from activation.
Each metric should be tracked and owned by a specific team. The platforms that treat onboarding as a product problem — not a compliance necessity — consistently outperform peers.
Lever 3 — Sales and incentive alignment
Your sales team is the most direct adoption lever you control. If payments are positioned as a “nice to have” add-on rather than a core platform feature, that is exactly how they will be sold — optionally, and rarely.
The mechanics that actually move attach rate:
• SPIF structures. $50–$200 per merchant activated on payments is a common range. The exact figure matters less than consistency and visibility — reps need to see a payment activation on every deal board.
• Comp plan integration. Leading platforms tie ACV credit partially to payment activation, not just software seats. This aligns quarterly rep incentives with long-term platform economics.
• Core-sale positioning. Train reps to present payments as part of the platform, not as an upsell. The pitch: “Our payments are built into the software — you won’t need a separate merchant account or to reconcile two systems.”
• Customer success ownership. Post-sale CS teams should track payments adoption by account in their health scoring. An account not using payments is a retention risk, not just a missed revenue line.
Lever 4 — UI/UX defaults
Defaults drive behavior. The platforms with the highest attach rates have one thing in common: payments is the path of least resistance, not an opt-in.
• Default on. New accounts should have payments enabled in their setup flow by default, requiring active opt-out rather than opt-in.
• Prominent placement. Payment initiation should appear in the primary workflow, not buried in settings menus.
• Streamlined checkout. For end-customers, the payment experience should require fewer than three taps. Every additional step reduces conversion by a measurable margin.
• Stored payment methods. Prompt customers to save cards on file after first use. Recurring payments and future invoices should pre-populate saved methods, not re-enter card details.
• Friction on alternatives. When a merchant chooses to accept a check or external payment, require them to actively log it. Make the manual alternative slightly inconvenient — without being punitive.
Empirical signal from Rainforest: platforms supporting digital wallets (Apple Pay, Google Pay) show a 63% median adoption rate vs. 48% for platforms that don’t — a 15-point delta. Wallet support is partly a maturity proxy, but it’s also a UX signal merchants and end-customers respond to.
Lever 5 — Pricing strategy
Price is both a lever and a signal. Aggressive undercutting communicates that payments is a commodity feature; value-based pricing communicates that it is a premium capability worth paying for.
The data from Rainforest reframes the conventional wisdom here. The assumption in most pricing conversations is that there is a necessary tradeoff between take rate and adoption — charge more, fewer merchants will participate. The actual data shows the opposite: platforms with higher take rates also tend to have higher adoption rates. Both metrics track with the same underlying variable (maturity), and the empirical correlation is positive, not negative. Optimized platforms have BOTH the highest take rates AND the highest adoption rates.
ServiceTitan’s original sin was a “match or beat” pricing strategy. It signaled to contractors that the embedded product was interchangeable with whatever they already had — and they saw no reason to switch. When ServiceTitan moved to value-based pricing (charging for integration convenience and reconciliation savings, not just the processing rate), attach rate and ARPU both improved.
Advanced pricing strategies worth modeling:
• Software subsidy model. Discount or zero out the software tier for customers who commit to embedded payments. Payment revenue subsidizes software cost. Toast’s low-cost hardware bundle is the canonical case.
• Tiered processing rates. Lower processing rates for customers on higher-tier software plans reward loyalty and create stickiness across both products simultaneously.
• Volume incentives. Rate reductions above threshold volume levels encourage merchants to consolidate payment volume through your platform.
Practitioner caveat from Rainforest: many payments leaders find merchants are less price-sensitive when payments is presented as integral to the holistic solution rather than an optional feature. Merchants often underestimate their processing costs with their current provider — for the largest merchants, an “apples to apples” review of their existing processing statements is a more effective sales motion than a competitive rate quote.
Charge Forward Insight
The five levers are not equal in effort or impact at every stage. Below ~$25M GMV, integration depth and onboarding speed dominate — get the activation flow right and the rest follows. Between $25M–$100M GMV, sales incentives and UX defaults become the marginal lever — your product can already activate merchants in five minutes, but your reps still treat payments as an upsell. Above $100M GMV, pricing strategy and value-based repricing become the leverage point — the same product is now worth more than you’re charging. The Charge Forward Maturity Framework maps which lever to prioritize at each stage.
What does not drive adoption — the Rainforest data on barriers
The 2026 Rainforest study asked platforms to name their single biggest barrier to growing adoption. The distribution of responses is the most useful empirical guide we have to where attention should be focused — and, equally important, where it should not.
| Adoption barrier (single biggest) | % of platforms citing | What it means |
|---|---|---|
| Integration complexity | 31% | Top barrier. Product friction between payments and the customer workflow. |
| Trust / comfort with existing solutions | 26% | Merchant switching cost — even when value is clear, inertia is real. |
| Price sensitivity | 13% | Far less of a barrier than commonly assumed. Reframes the pricing strategy debate. |
| Other (awareness, regulatory, features, etc.) | ~30% | Long tail; no single dominant factor. |
The implication is direct: most platforms over-invest in pricing strategy as the lever to drive adoption, when the actual binding constraint is product friction. If your roadmap conversation about payments is dominated by “should we discount the processing rate?”, you are probably solving the wrong problem.
Charge Forward Insight
The “integration > price” finding has direct implications for sell-rate strategy. Most platforms under-price embedded payments because they treat it as commodity infrastructure. The data says the merchants on the other side of those checkout flows don’t see it that way — they’re paying for the integration, not the rate. If you are sitting on a sell rate that hasn’t been repriced since you launched, the Rainforest data is your evidence for taking price. 60% of platforms in the Rainforest sample reported take-rate INCREASES over the last two years (only 1% reported decreases) — the “race to the bottom” narrative is empirically wrong. Pair this with the Charge Forward Payments Revenue Calculator to model the impact of a 5–15 bps repricing on your existing book.
Real-time payments data — the underweighted enabler
Rainforest 2026 surfaced a finding that ties directly to Chapter 8: 77% of vertical SaaS platforms view real-time payments data as “critical to our value proposition” or “very important.” Only 25% report reliable access to accurate real-time data. Another 65% say their payments data is “mostly real-time.”
The gap matters because real-time payments data is what powers the high-value workflows that drive adoption: automated reconciliation (24% at Emerging → 75% at Scaling/Optimized), workflow automation (47% Emerging → 75% Optimized), cash flow forecasting, intelligent routing, and the advanced features that make the integration feel native rather than bolted on.
Practical implication: if your current vendor agreement does not grant transaction-level, real-time data access, you are capped on adoption — not because of pricing or sales motion, but because you cannot build the advanced features that move the needle from Scaling to Optimized. Renegotiate the data terms before you renegotiate the rate terms.
Case study — ServiceTitan’s adoption journey
ServiceTitan is the most extensively documented case study in embedded payments adoption. The publicly disclosed journey from referral-model integration to fully embedded PayFac provides a replicable blueprint.
Phase 1 — The referral model (pre-2017)
When ServiceTitan first offered payments, it referred customers to a third-party processor via integration. The architecture was technically functional but organizationally fragmented: customers created merchant accounts directly with the processor, onboarding was handled by the partner (not ServiceTitan), and the platform had limited visibility into the process.
The results reflected the friction. Onboarding dragged on two to three months. Because ServiceTitan’s pricing was “match or beat,” margins were thin on the merchants who did complete onboarding. Attach rate: approximately 10–20%.
Phase 2 — The embedded PayFac transition (2017)
After evaluating 30+ payment partners, ServiceTitan launched ServiceTitan Payments — a fully branded, in-app solution powered by a PayFac-as-a-Service vendor. The architecture shifted fundamentally: ServiceTitan now owned the onboarding experience, controlled the UI, and captured a meaningful share of processing revenue.
The core changes:
• Controlled onboarding. KYC handled within the ServiceTitan app, with pre-populated business data. Activation time went from months to minutes.
• In-app payments. Contractors could store customer cards on file, process payments from the job-completion screen, and reconcile revenue without leaving ServiceTitan.
• Value-based pricing. ServiceTitan moved away from rate-matching to pricing that reflected integrated-workflow value.
• Sales training. The sales organization was retrained to present payments as a core platform feature, not a referral.
Phase 3 — Results
Within three years of the embedded launch, the vast majority of ServiceTitan’s contractors were using the payments offering — versus fewer than 20% before. Payments became a meaningful revenue contributor and a retention driver. The company’s Chief Growth Officer described payments as “just as critical” to the platform as its core job management features.
By fiscal year 2026 (ending January 2026), ServiceTitan reported $961M in total revenue on approximately $82.1B in gross transaction volume, with Usage Revenue (primarily Titan Pay) representing the highest-growth contributor. Effective payments take rate is approximately 29 bps on GTV. At current penetration estimates (still well below full attach), the incremental revenue runway from attach-rate expansion alone is multiples of current Usage Revenue. (Sources: ServiceTitan FY2026 10-K, March 2026; Flagship Advisory Research.)
Charge Forward Insight
ServiceTitan’s transition validates a principle confirmed across every high-attach platform AND in the Rainforest 2026 study: adoption is an ops problem, not a product problem. The payment technology was available in Phase 1. What changed in Phase 2 was who owned the customer journey, how onboarding was structured, and how the sales organization was compensated. Before rearchitecting your payment product, audit those three operational elements — most of the time, that is where the gap lives.
How do you know if you’re optimized?
Attach rate is the headline, but the diagnostic framework requires a more granular measurement stack. Run this quarterly:
| Metric | What to Measure | Benchmark Target |
|---|---|---|
| Attach + Adoption vs. Rainforest stage | Your attach rate (new customer signup) and adoption rate (eligible-base coverage) vs. Emerging/Scaling/Optimized medians | Optimized: 93% attach, 78% adoption |
| Onboarding funnel | Rate of starts → completions → activations → first transaction | 90%+ activation from starts; 48hr to first txn |
| Time-to-first-transaction | Hours/days from merchant activation to first live payment | Under 48 hours for 80%+ of merchants |
| Active adoption rate | Of those signed up, what % actively transact? | Optimized: 78% median |
| Real-time data quality | Is your payments data reliably real-time and accurate? | 25% of industry has it; target this band |
| Payments customer churn | Annual churn for payments users vs. non-payments users | Payments churn 30–50% lower |
| Revenue per merchant | ARPU for payments-active vs. payments-inactive merchants | Payments merchants 40–80% higher ARPU |
If your onboarding funnel completion is below 80%, the problem is onboarding — not product or pricing. If your time-to-first-transaction is over a week, the activation experience needs redesign. If payments users are churning at the same rate as non-payments users, the integration is not deep enough to create workflow dependency. If your active adoption rate is below 63% (Scaling median), you have signed up customers who never actually used the product — usually a UX or sales-handoff problem.
Compliance and risk as adoption scales
Growth in attach rate is growth in regulated activity. Every percentage point of additional adoption brings additional compliance surface area. Platforms that treat risk and compliance as afterthoughts at early attach stages typically encounter expensive and disruptive problems at scale.
PCI DSS at scale
As payment volume grows, PCI scope expands. Platforms processing below $1M annually typically qualify for SAQ-A or SAQ-A-EP (the lightest self-assessment questionnaire tiers). Platforms above $6M in Visa/Mastercard annual volume face Level 1 merchant requirements, including on-site QSA audits costing $200,000+ annually. Build your PCI roadmap around projected volume milestones, not your current state.
KYC/AML as merchant volume grows
Every sub-merchant onboarded through your platform is a KYC event. Under a PayFac model, you are responsible for the identity verification and ongoing monitoring of your merchant population. At 100 merchants this is manageable. At 10,000 you need automated identity verification, sanctions screening, and ongoing transaction monitoring — either built internally or through your processor partner. Notable Rainforest finding: compliance jumps from a 29% concern at Emerging stage to 60% at Scaling and 62% at Optimized — compliance complexity grows non-linearly with adoption. Evaluate your vendor’s KYC tooling before you are at scale, not after.
Chargeback management
Chargeback rates vary by an order of magnitude across verticals. The Worldpay/Payrix all-client average is 0.04% — far below the VAMP early-warning threshold of 0.65%. Fitness and wellness platforms (0.50%–0.86%) and education platforms (0.80%–1.02%) are structurally at risk of approaching program thresholds as volume grows. Visa’s VAMP Standard tier triggers at 0.9% and 100 disputes per month; Excessive at 1.8%. Penalties: monthly fines of $50–$100 per chargeback and, ultimately, card-acceptance termination.
Rainforest 2026 finding: 50% of Optimized platforms cite fraud and chargeback management as a top priority — consistent with higher volumes. Implement chargeback monitoring dashboards before you need them. Set internal alert thresholds at 50% of network program triggers. Work with your processor to implement real-time dispute alerts (Ethoca, Verifi) that allow pre-chargeback resolution with issuers. See Chapter 6 for the full chargeback rate table by vertical.
Charge Forward Insight
The platforms that will define vertical SaaS economics over the next decade are not the ones with the most sophisticated payment technology — they are the ones with the highest attach rates. The Rainforest data confirms what we have argued in advisory work for years: the technology has commoditized across PFaaS providers. The differentiator is operational discipline: the onboarding flow that takes four minutes instead of four months, the SPIF structure that makes every rep think about payment activation on every deal, the UX default that turns payments on before the merchant has to think about it, and the dedicated payments leader (ideally in the C-suite) whose job it is to optimize the whole system. If your attach rate is below your stage’s top-quartile, the gap is almost certainly not product quality — it is one of the five levers in this chapter. Each is fixable with focused operational effort, not a platform rebuild.
What’s next
Chapter 8 — “Payments as Your Data Advantage” — examines the asset that high-attach-rate platforms are building without always realizing it: a proprietary financial data engine. Every transaction your merchants process through your platform generates signals about their business — revenue trends, customer behavior, seasonal patterns, fraud risk. Chapter 8 explores how the most sophisticated embedded finance platforms are converting that payment data into AI-driven insights, new product lines (lending, insurance, banking), and durable competitive moats. The Rainforest finding that 77% of platforms view real-time data as critical but only 25% have reliable access is the structural opening Chapter 8 addresses head-on.
For attach rate benchmarks by vertical and maturity stage, see Chapter 11 (Sections 2 and 10). To quantify the revenue impact of attach-rate improvement on your specific platform, run the Charge Forward Payments Revenue Calculator. To identify which adoption lever to prioritize at your stage, download the Embedded Payments Maturity Framework.
SOURCES & REFERENCES
Rainforest, “2026 Vertical SaaS Embedded Payments Benchmarking Study” (Q1 2026 fielded; May 2026 release — first independent industry survey of vertical SaaS payments performance).
UBS Global Research, Tim Chiodo: “The Question 6.0” (May 4, 2026); “Vertical SaaS & Embedded Finance: Takeaways from Vertex hosted by Rainforest” (April 15, 2026).
Worldpay/Payrix Vertical SaaS Benchmarking Study (January 2025); ServiceTitan FY2026 10-K (March 2026); Toast FY2024 10-K; AppFolio FY2024 10-K; Mindbody public disclosures; Flagship Advisory Research.
Ethoca 2025 State of Chargebacks; Clearly Payments 2024 Chargeback Benchmarks; Visa Acquirer Monitoring Program (VAMP) and Mastercard Excessive Chargeback Program documentation.
Charge Forward Embedded Payments Benchmark Report (April 2026); see Chapter 11 for the full benchmark dataset.
Public Charge Forward tools referenced in this chapter: Embedded Payments Fit Assessment, Maturity Framework, Payments Revenue Calculator. All available at chargeforward.io/tools.
By Jane Podbelskaya · Updated