01
What attach rate actually means
One number that tells you how much of your payments opportunity you’re capturing
02
Why a small change in attach rate is a massive revenue event
Same platform. Same merchant base. Completely different payments business.
02b
What this means at the merchant level: doubling ARPU without raising prices
When a merchant attaches to payments, the revenue impact per customer is transformational
03
What drives attach rate up — and what kills it
Attach rate isn’t set at launch. It’s built over time through deliberate decisions.
↑ Drives attach up
Payments native to the workflow
When payments live inside the software — not as a separate tab or external link — merchants attach because it’s the path of least resistance. Friction is the enemy of attach.
Native UX
Onboarding that converts
The moment a new merchant signs up is your highest-leverage attach window. Platforms that prompt payments activation during onboarding — not weeks later — see dramatically higher attach.
Onboarding
One software. Everything runs inside it.
The most powerful attach story isn’t pricing — it’s elimination. When a merchant realizes they can run their entire business without leaving your platform, the swivel chair disappears. No separate terminal. No separate portal. No reconciling two systems at the end of the day. That’s not a feature. That’s a reason to never leave.
Merchant value prop
Showing merchants what they actually pay today
Most merchants have no idea what they’re paying their current processor. When you show them clearly — often 5%+ all-in once you add interchange, assessments, and processor markup — the conversation changes immediately.
Cost transparency
↓ Kills attach rate
No active attach strategy
Most platforms launch payments, tell their sales team, and wait. Attach rate doesn’t grow passively. It requires ongoing campaigns, in-app prompts, and someone accountable for the number.
Go-to-market
Merchants already have a processor
Existing relationships are the #1 attach barrier. Switching costs are real — especially for merchants with saved card-on-file data, existing disputes, or accounting integrations built around their current processor.
Switching friction
Your customers are swivel-chairing payments
If merchants are toggling between your software and a separate payments tool to run their business, they’re not attached — they’re tolerating. Every swivel chair is a churn risk and a revenue miss hiding in plain sight.
Product positioning
Mispriced payments
If your embedded payments pricing is out of step with what the market will bear, merchants won’t switch — even when the experience is better. Pricing needs to be competitive enough to remove the last objection, not just the first.
Pricing
Forward · Payments 101
Part of our ongoing series on embedded payments for SaaS
Figures are illustrative. Actual economics vary by platform, merchant mix, and processing volume.

