Merchant Onboarding

KYC and Conversion Designed Together

May 27, 2026·8 min read·By Rizwan Zafar

KYC is usually owned by compliance. Conversion is usually owned by growth. The two teams meet at the release review and discover they have shipped two different products. The merchant experiences both as one bad flow.

The shared surface

KYC and conversion are not adjacent surfaces. They are the same surface viewed from different sides. Every KYC decision is a conversion decision. Every conversion decision is a risk decision. The teams that ship the best onboarding put both owners on the same product squad and measure the joint outcome.

Eight principles that hold across markets

1. Start with intent, not identity. Capture business intent (what they will sell, expected volume, geography) before asking for documents. This both lets you tier the merchant and gives the applicant a sense of progress.

2. Progressive disclosure. Ask only what you need to make the next decision. Do not collect 40 fields upfront because someone might want them later. Each additional field that is not strictly required costs measurable conversion.

3. One job per screen. Document upload, selfie capture, OTP, each is a different cognitive task. Combining them on one screen causes drops.

4. Show progress honestly. A 5-step progress indicator that turns out to have 9 steps destroys trust. If steps are conditional, say so.

5. Real-time validation, generous parsing. OCR the document the first time. Accept slightly off-format inputs. Never make the user fix a problem your parser could have fixed.

6. Explain rejections in plain language. "We could not verify your business" is useless. "The business name on your registration certificate does not match the name on your application" is actionable.

7. Resumable flows. Sessions die, networks drop, users leave. A flow that cannot be resumed from the last completed step loses conversion on every disruption.

8. Decision windows, not silence. Promise a decision in X hours. Meet it. If you cannot, send a status update before the merchant has to ask.

Where compliance and conversion actually conflict

The genuine conflicts are narrower than the religious-war versions:

Document re-upload on partial failure, compliance wants the original, conversion wants OCR retry. Resolve with explicit re-upload only when OCR confidence is low.
UBO depth, compliance wants every layer, conversion wants two. Resolve by tier and jurisdiction.
Selfie liveness, compliance wants strict, conversion wants permissive. Resolve with stepped-up checks for higher-risk tiers.
Bank verification mechanism, compliance prefers micro-deposit, conversion prefers Open Banking. Resolve by availability per market.

Each of these has a defensible answer. The bad outcome is leaving the question unresolved and letting the merchant pay the cost.

Instrumentation that holds both teams accountable

The metric set must serve both. A working dashboard:

Step-level conversion with drop-off attribution
Time-on-step and re-entry rate
KYC decision distribution (auto-approve, manual review, decline)
Manual review SLA
Post-onboarding default rate by cohort
Joint OKR: risk-adjusted activated merchants per week

When both teams are on the same dashboard with the same OKR, the religious war ends within a quarter.

What good looks like

A working flow in a mainstream vertical:

Application to first document upload in under 90 seconds
Mean activation under 30 minutes for T1/T2
p90 activation under 24 hours
Auto-approval rate above 70%
Manual review queue under 24-hour SLA
90-day default rate flat or down quarter over quarter

These numbers are achievable. Most platforms run at 30–50% of them because the two teams never sat at the same table.

Operator lens

The cheapest way to fix onboarding is to merge the org chart for two quarters. The teams discover that most of what they argued about did not matter, and the things that did matter were never on either backlog. After that, separate them again if you want, they will keep talking.