Monitor Stripe Connect connected account KYC requirements and handle requirements.currently_due

Steps

1. When onboarding a connected account, create it via POST /v1/accounts with 'type' (standard, express, or custom) and 'capabilities' for the payment methods you need; Stripe returns an Account object with 'requirements' populated.
2. Generate an account link: POST /v1/account_links with 'account', 'type: account_onboarding', and 'return_url' / 'refresh_url'; redirect the merchant to the hosted onboarding URL — Stripe collects and verifies KYC documents.
3. Listen for the 'account.updated' webhook on your platform account; inspect 'requirements.currently_due' (must be addressed before the deadline), 'requirements.eventually_due' (must be addressed to avoid future restrictions), and 'requirements.past_due' (overdue — capabilities may be disabled).
4. For each string in 'currently_due' (e.g., 'individual.verification.document', 'business_profile.url'), generate a new account link so the merchant can submit the missing information — do not attempt to collect and submit KYC documents yourself unless using the Custom account type with explicit agreement.
5. After submission, Stripe transitions 'requirements.pending_verification' entries as documents are reviewed — poll via GET /v1/accounts/{account_id} or wait for 'account.updated' webhooks until 'currently_due' is empty.
6. Monitor 'capabilities' in the Account object: each capability (e.g., 'card_payments', 'transfers') has a 'status' of 'active', 'inactive', or 'pending'; blocked capabilities prevent payouts and charges even if the account appears onboarded.