Create express onboarding flow

We need an express onboarding flow for developer partners so they can accept payments in three days. Build a short flow and send it to Priya in dev and Omar in product: show only essential questions, permit skip for nonmandatory fields, require just business name, contact, and bank link, and include a single checkbox for terms. Test with Priya and activate by Thursday.

Before I ship the express onboarding for developer partners, make it easy for a busy engineer to finish in one go: surface how long it will take, show a progress indicator, let them save and return, hide optional tax fields behind an expandable section, and call out the single most common reason for review delay.

We pushed an express onboarding beta and several engineers dropped out when they hit tax classification questions. I don’t know if they have the info or are simply uncomfortable answering on behalf of their company. What’s the likeliest reason for abandonment, what do I tell testers now so they resume, and what small change minimizes this friction without losing compliance?

Across multiple releases, express onboarding fails because we still ask too many optional fields and don’t make the path for minimal compliance obvious. This bleeds developer goodwill and slows integrations. Which habit should I stop doing in form design, and what single rule should I adopt for every future onboarding field?