Stripe Connect Requests Proof of Liveness for One Person

· 2 min read

Locate the person associated with the request

A connected account can include several Person objects. Stripe documents that proof of liveness may apply to one or more of these people. Start from the outstanding requirement and connect it to the person record before you contact the business. A company may otherwise ask the account representative to repeat a step even when Stripe is waiting for someone else.

Let the supported flow present the challenge

The form of liveness verification can vary. The Stripe guidance describes electronic credentials and Stripe Identity document or selfie collection as possible methods. It recommends hosted or embedded onboarding to handle the possible variants. In a hosted flow you can send the account through an Account Link and allow Stripe to prompt the relevant user for the currently due request.

Situation Check
Several associated people Which Person is named in the requirement
Personal challenge Which hosted or embedded collection option applies
Owner finished their screen What the updated account or person record shows
Another request remains Whether it concerns the same person or another record

Reconcile the result with the intended person

Suppose a company has two owners, and the new liveness item appears for the second person while the account representative has finished an earlier identity task. Keep the two case records separate. Route the new request through the supported experience and use the subsequent account update to read its current requirements. A browser return from the flow is useful for navigation. The account's updated records determine what remains to collect. A deliberately narrow support message that names the requested action helps the merchant route the prompt without asking the wrong owner to share sensitive documents.

Official sources

  1. Handle verification with the API
  2. Identity verification for connected accounts