Skip to main content
Use the verification’s current status.state, status.code, and status.errors to decide whether to resume the existing verification or create a new one.

​
Choose a recovery action

​
Session not completed

If the user closes the connection flow, or the session link expires, retrieve the verification and check its current status. When the verification remains active in pending or user_session_started, create a new session for the same verification with POST /partners/v2/sessions. Do not create another verification solely to replace an expired session link. For connection_attempted or syncing_error, review the current account connection error in status.errors, correct the issue, and create another session for the same active verification.

​
User details missing or invalid

If POST /partners/v2/verifications returns a 400 response for missing or invalid user details:
  1. Update the user with PATCH /partners/v2/users/{id}.
  2. Retry POST /partners/v2/verifications.

​
More documents required

When a Doc VOI verification enters more_data_required, review status.errors for the missing information. Upload the additional files for the same user with POST /partners/v2/user-uploads. Continue listening for the verifications.updated webhook as processing resumes.