Verification Sessions can now collect verification information for a related Person
What’s new
Connect platforms can now use Stripe Identity to collect required verification information, such as the document or proof_of_liveness for a Person, while onboarding a connected account.
Impact
When creating a VerificationSession, use the related_person parameter to associate the session with a person from one of your connected accounts who’s required to provide a document or proof_of_liveness.
After Stripe completes verification, collected data is attached to the associated person, fulfilling all unmet requirements.
Changes
| Parameters | Change | Resources or endpoints |
|---|---|---|
| related_person | Added | Identity. VerificationSession Identity. VerificationSession#create |
| matching | Added | Identity. VerificationSession. options |
Upgrade
- View your current API version in Workbench.
- If you use an SDK, upgrade to the corresponding SDK version for this API version.
- If you don’t use an SDK, update your API requests to include Stripe-Version: 2025-06-30. basil
- Upgrade the API version used for webhook endpoints .
- Test your integration against the new version.
- If you use Connect, test your Connect integration .
Learn more about Stripe API upgrades.