The boarding flow is where most embedded payments programs lose merchants before they start. The integration is live, the economics are sound, and the product team has moved on to the next feature. But 60% of merchants never complete the onboarding. They start, hit a friction point, and quietly abandon it.
Boarding conversion is the most underinvested part of a payments program. Most of the operational energy goes into the technical integration. Very little goes into the experience that determines whether merchants actually use it. It's also the single biggest lever for the activation rate KPI that predicts whether your payments revenue will scale.
What Merchants Are Being Asked to Do
To board a merchant for embedded payments, you need to collect KYB (Know Your Business) and KYC (Know Your Customer) information sufficient for underwriting. At minimum:
- Legal business name and DBA
- Business EIN or SSN (for sole proprietors)
- Business address and phone
- Business type and MCC category
- Owner identity: name, date of birth, address, SSN last 4 (or full SSN for high-risk categories)
- Bank account for settlement: routing and account number
In some configurations, you also need a voided check or bank statement for account verification, and photo ID for identity confirmation. For certain business types or risk categories, additional documentation is required.
This is a significant ask. You're requesting sensitive financial and identity information from a small business owner who may not have all of it immediately available, may not understand why it's needed, and hasn't yet seen enough value from your payments program to feel the request is worth the friction.
The Progressive Disclosure Principle
The single most effective design principle for boarding flows is progressive disclosure: collect only what you need to take the next step, not everything you'll eventually need up front.
Most boarding flows fail because they present a single long form that asks for everything before the merchant can process a single transaction. The merchant sees 12 fields on screen, estimates the effort required, and abandons.
A progressive flow breaks this into stages:
- Stage 1: Enable. Collect business name, EIN, and bank account. This is enough to create a merchant record and run soft underwriting. The merchant can see their account is active and understand what they'll be able to do. Time to complete: 3-5 minutes.
- Stage 2: Verify. Collect owner identity information. Triggered when the merchant processes their first transaction or when their volume crosses a threshold. Framed as "complete verification to remove your processing limit." Time to complete: 2-3 minutes.
- Stage 3: Expand. Additional documentation for higher-risk categories or higher volume tiers. Only collected when the merchant actually needs it. Most merchants never reach this stage.
Progressive disclosure typically improves boarding completion rates by 30-50% over single-form approaches. The merchant experiences early success before encountering the most sensitive requests.
Where Merchants Drop Off
Analyze your boarding funnel by step. The drop-off points are predictable:
EIN entry. Many small business owners don't have their EIN memorized and don't know where to find it quickly. A link to the IRS EIN lookup tool, alongside a note that it's on their CP-575 letter or prior tax filing, reduces abandonment at this step significantly.
SSN or date of birth. The moment you ask for personally identifiable information, trust becomes a conversion factor. Explain why you need it ("required by federal law for identity verification"), where it's used ("not stored after verification"), and who's doing the verification ("our banking partner, not us"). Merchants who understand the request are far more likely to complete it.
Bank account entry. Merchants are wary of entering routing and account numbers, especially before they trust the platform with their settlement. Micro-deposit verification (two small deposits that the merchant confirms) is slower but less fraught. Instant bank verification via Plaid is faster and has high acceptance rates for digital-native merchants.
Document upload. If you require a voided check or photo ID, file upload is a friction point on mobile and a conversion killer for merchants who aren't at a computer. Make this step skippable when possible, with a follow-up email that catches it later.
The Role of Context and Timing
When you surface the boarding flow matters as much as how you design it.
The worst time to ask a merchant to board for payments is immediately after software onboarding, when they're still learning the core product. They haven't seen enough value to feel motivated to add another task.
The best time is at a natural workflow moment where the absence of payments creates friction: when they try to send an invoice and there's no payment link option, when they're setting up a new service that involves billing, or when they receive a report showing how much revenue they could be collecting through the platform.
Contextual prompts (surfaced at the right moment in the right workflow) convert at 2-3x the rate of standalone email campaigns promoting the payments feature.
Staffed Boarding as a Conversion Strategy
For high-value merchants or verticals where the average merchant volume justifies the investment, staffed boarding drives the highest activation rates. A customer success rep who walks the merchant through the boarding flow over a 20-minute call (answering questions, handling document requests in real time) converts at 70-85% versus 25-35% for self-serve flows.
The economics work when the expected lifetime payments revenue from the merchant exceeds the cost of the call. At $150K/year in merchant volume and a 60 bps net take rate, that's $900/year in payments revenue per merchant. A 20-minute boarding call is worth the investment for any merchant above roughly $50K in annual volume.
The onboarding flow is a product, not a compliance checklist. Design it for the merchant who has five minutes and a suspicious mind. Not for the one who already trusts you.
Related: Why Merchants Don't Use Embedded Payments covers the structural activation challenges beyond onboarding. For operational design support (boarding flow review, activation strategy, or merchant support design), see the advisory engagement.