Configure a Stripe Identity VerificationSession's dynamic requirements (matching selfie, provided_details) to reconcile document data against information the user already gave you

In-depth guide

Steps

1. Create a VerificationSession with options.document.require_matching_selfie enabled when you need liveness-bound identity assurance, not just document capture
2. Pass provided_details (e.g., the email or other data you already collected) so Stripe can surface it to the user during the flow for confirmation
3. After completion, retrieve the VerificationSession and read the verified outputs alongside the input_test/provided details to check for mismatches (e.g., name on ID vs. name on account)
4. Define a policy for handling partial mismatches (e.g., minor name formatting differences) versus hard mismatches (different person entirely)
5. Route hard mismatches to manual review or account rejection instead of silently accepting the verified session as an automatic pass