Skip to main content
After you create a user, call Get verification requirements. Use the fields in its data object to see what remains:
  • state is the user’s verification state: ok, disabled, or closed. ok means the user is neither disabled nor closed. The user can still have onboarding steps in required_actions.
  • required_actions lists the outstanding steps. They can include accepting terms, providing personal details, completing identity verification, or waiting for a check to finish.
  • user_action_required tells you whether the user or your integration has an action to take now.

​
Confirm initial onboarding is complete

Initial onboarding is complete only when both conditions are met: state is ok and required_actions is empty.
For example:
An ok state can still have required actions. If required_actions contains provide_details or verification, follow the reported requirement. A wait action means processing or review is still outstanding. In this example, user_action_required is false because the user has no action to take:
Initial onboarding and eligibility for a specific quote or conversion are separate checks. See Identity verification vs. eligibility.

​
Keep requirements current

Subscribe to verification.requirements_updated to learn when requirements change. When you receive the event, call Get verification requirements again. The event itself does not confirm approval. Requirements can change after onboarding, so fetch the latest response before making an eligibility decision.