How to distinguish Stripe Connect verification in review from information that is due

· 3 min read

A Stripe Connect account can have some information in review and still need more information before a capability is available. The requirements object distinguishes information that is currently due, information that may become due and information under asynchronous verification. Treat those statuses as different states for each requirement. An operator looking only at the account’s overall status may ask an account holder to resubmit data that Stripe is already reviewing and miss a separate item that really needs attention.

Read the requirement and deadline together

Stripe describes currently due requirements as the items to resolve by the current deadline to keep the account active as specified. The deadline is the earliest relevant deadline across the account’s requested capabilities and risk requirements. Eventually due shows potential future requirements that can become currently due when a threshold is reached. Past due is a subset of currently due items that were not resolved in time and have disabled capabilities. Keep the exact requirement and whatever deadline is actually reported in the account record. A generic reminder date on a project plan does not replace the provider’s state.

Use the error details to determine which specific information was rejected and the reason. If a document or field does not pass validation, the item can return to a due list with error details. Review those details before requesting a correction. Depending on the error, the next step could be confirming a name, replacing a file or completing a different requirement. Keep the status display tied to discrete items instead of treating every pending record as another document upload.

Separate information under review from a new request

The pending verification list identifies information Stripe is reviewing or might request depending on review. The guide also explains that an unsuccessful verification can shift a requirement into other lists, and in some cases a failed requirement under further review can remain pending. Look at the current state of the individual requirement and any errors rather than deciding based on a single earlier status. If an account has an item pending and a different item currently due, the user needs two clear messages: one for what is being reviewed and one for action.

For example, a platform receives a new account update after a representative uploads an identity document. The identity check is pending while another business field stays currently due. The platform shows that the identity file was received and requests only the unresolved business information. If a later update includes an identity-document error, the platform can then prompt for the correction described by Stripe. Repeating the original request on each update would hide which action actually changed.

Recheck the capability after the requirement changes

Use the charges enabled and payouts enabled fields and the relevant capability to see whether the account can start taking the action you intend. A completed item may be only one condition. Stripe’s guidance recommends monitoring account updates for requirement changes and using the account state to select the next step. Document the recent transitions with their timestamps so another operator can distinguish a new deadline from the earlier one. It is easier to explain the next action when the requirement, review state and capability outcome are tracked separately.

Official sources

  1. Handle verification with the API
  2. The Account object
  3. Identity verification for connected accounts