# Risk-based Onboarding Requirements for Connect

Stripe dynamically determines the risk profiles of your European users using carefully chosen signals that help us determine whether a user poses a low, standard, or high risk to Stripe. We undertake this exercise to meet regulatory obligations.
In certain regions, if an account is deemed to be lower risk, they may be eligible for lighter onboarding requirements. For example, lower risk accounts in Europe may not require verification until after they’ve passed a certain threshold in processing, or been active for an extended period of time. Once verification is required for these accounts, they may also be subject to fewer requirements, including not needing to provide an `additional_document` as proof of address.
Because this assessment is dynamic, accounts can, at any point, change risk designations. When new requirements are added as a result of an updated risk designation, accounts will receive a grace period to verify before being disabled.
# What do I need to do?
You should ensure that your application doesn’t assume that empty `currently_due` requirements mean that an account is guaranteed to not have any future [requirements](https://stripe.com/docs/connect/required-verification-information). That means ensuring you are listening to [Stripe webhooks](https://stripe.com/docs/connect/webhooks) and updating your workflows accordingly, based on information you receive from the Stripe API.
You may want to review any automated actions triggered by the `account.updated` webhook, and, if necessary, prepare your support teams in case your users have questions about the change to their requirements.