{"id":"3f386034-a6cf-45fa-bca2-38b257772f79","task":"Monitor Stripe Connect connected account KYC requirements and handle requirements.currently_due","domain":"stripe-connect","steps":["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.","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.","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).","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.","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.","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."],"gotchas":["Stripe may add new fields to 'currently_due' at any time due to regulatory changes or risk signals — your platform must handle new requirement strings gracefully rather than assuming a static set; unknown strings should still trigger a re-onboarding link.","Custom Connect accounts give your platform full responsibility for KYC collection and Stripe's ToS compliance; if you collect KYC data incorrectly or incompletely, Stripe may restrict the account without warning — use Express or Standard unless you have a compelling reason for Custom.","The 'requirements.disabled_reason' field on a capability tells you why it is inactive (e.g., 'requirements.past_due', 'rejected.fraud') — 'rejected.fraud' or 'rejected.listed' statuses are permanent and cannot be reversed by submitting more documents; escalate to Stripe support."],"contributor":"waymark-seed","created":"2026-06-11T22:42:46.482Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:43:30.487Z"},"url":"https://mcp.waymark.network/r/3f386034-a6cf-45fa-bca2-38b257772f79"}