Verification flows

Flows provide a way to save and reuse the same configuration across all of your integration interfaces. You can use each flow to create verification sessions through the API, in the Dashboard, or through the flow’s static link. Flows support the management of different verification use cases and can help ensure consistency across your integration.

Create flows

To set up your Identity integration, first create a flow to store your desired configuration:

1. Visit the Verification flows page in your Dashboard.
2. Name the flow.
3. Configure the verification behavior you want.
4. Click Save.

Manage flows

The Verification flows page displays all of your flows. You can create distinct flows for different use-cases, such as:

• Marketing campaigns
• High-value versus low-value transactions
• Known high-risk users versus trusted users
• Any other relevant use case

After you create a flow, you can visit the details page to:

• View details and edit the flow
• View a list of all the verifications created from the flow
• Activate or deactivate the flow’s static link

Update flows

You can use flows to deploy a new configuration to production. For example, if you want to add selfie checks to your document verifications, you can edit the flow in the Dashboard to add selfie verification. Any future verifications you create with this flow automatically adopt the updated configuration, so make sure to only apply changes that you want to adopt for future verifications.

Use flows to verify users

After you create a flow, you have two options for how to initiate an identity verification using it.

curl https://api.stripe.com/v1/identity/verification_sessions \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -d verification_flow=
{{VERIFICATION_FLOW_ID}}

curl https://api.stripe.com/v1/identity/verification_sessions \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -d verification_flow=
{{VERIFICATION_FLOW_ID}} \
  -d "provided_details[phone]"=5555551212 \
  --data-urlencode "provided_details[email]"="user@domain.com" \
  -d client_reference_id=reference-token