What Up-Front and Incremental Stripe Connect Onboarding Collect

· 2 min read

A Stripe Connect platform can collect information for a connected account up front or collect only what is currently required. The difference affects when a merchant is asked for records and the conditions required to keep the account's intended functions available. Decide which capabilities the merchant will use and review the requirements tied to them before choosing the collection strategy.

Match the collection setting to the account

Up-front onboarding collects the account's eventually-due requirements. The merchant can provide more of the anticipated records early. Incremental onboarding collects currently-due requirements, so the initial flow can ask for less. Additional information might become necessary later. The relevant requirements vary by country, business type and capabilities as well as other account factors. Avoid treating one country's document checklist as universal.

Collection decision What it emphasizes What to plan for
Up-front collection Anticipated information for the selected capabilities A deeper initial request and fewer repeated prompts in typical cases
Incremental collection The requirements due now A way to contact the merchant if Stripe later requests information
Requesting a capability Turning on a function the connected merchant needs Check the requirements associated with that capability

Example with phased marketplace features

A platform plans to enable one capability at launch and consider a second after the merchant completes its first sales. Request the launch capability and decide whether the initial team can support a longer information collection flow. When a new capability is eventually needed, check the requirements for the existing account. Explain why another request can appear even if the merchant supplied everything for the first launch.

Review later changes using the account itself

Do not promise an account will never need another check. Stripe documents further verification at variable thresholds and changes in requirements over time. Keep a way to show merchants the outstanding action for their account. Review the current requirements when the business type or requested capability changes so the platform can collect the relevant records without asking for information merely because it appeared on another merchant's form.

Official sources

  1. Stripe-hosted onboarding
  2. Identity verification for connected accounts