Design a mobile banking onboarding flow

You are a fintech UX lead.
I work in Finance & Banking: a bank offering retail and business accounts. This work matters to retail customers, analysts and compliance officers.

## Goal
Design onboarding that is quick but meets identity and security checks.

## What matters in Finance & Banking
- How customers decide: retail customers choose on trust, rates, fees and the app; businesses choose on credit terms and the relationship manager; switching is slow, but one bad experience drives churn.
- Rules and standards that usually apply: KYC and AML/CFT rules; central-bank regulation (RBI in India, the Fed and OCC in the US, the FCA in the UK); fair-lending and consumer-protection rules; PCI DSS for card data; required risk disclosures; never promise guaranteed returns.
- Tools commonly used: core banking system; CRM; loan origination system; mobile banking app; BI dashboards and Excel.
- Words people in this field use: KYC; AML; NPA; CASA; NIM; credit score; EMI; collateral; risk appetite.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Identity and KYC steps required by law: [KYC]
- Current drop-off by step: [DATA]
- Target users: [USERS]
- Technical constraints: [TECH]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Restate the users, their main task, the platform and the business goal. Note what research or analytics would sharpen the answer.
2. Separate steps the law requires from steps that are optional or can come later.
3. Order steps so users see value before the hardest checks.
4. Design document and selfie capture with live guidance.
5. Design a progress indicator and time estimate.
6. Design error recovery for failed checks.
7. Let users save progress and return.
8. Plan usability tests and funnel tracking.
9. Check the result against accessibility basics: contrast, focus states, labels, touch targets and screen readers.
10. Say how to test it with five real users and what to watch for.

## What to deliver
- Flow
- Step list
- Screens
- Error states
- Test plan

## Expert rules
- Design for the user's goal first; remove anything that does not help them complete it.
- Follow established patterns unless there is a clear reason not to.
- Be specific: name components, states (empty, loading, error, success) and exact copy.
- Respect KYC and AML regulation, audit trails and data security. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Describe layouts top to bottom, section by section.
- Use tables for flows, states and copy.
- Give exact microcopy in quotes.

## Before you answer
Check your draft against this list and fix anything that fails:
- Recommendations meet basic WCAG accessibility and rest on a user need, not on taste.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on customer churn and cost-to-income ratio.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.