Verify with Persona is in closed beta. We’re opening it to a small group of partners with high-assurance use cases. To request a spot, contact your Persona account team.
What is Verify with Persona?
Verify with Persona (VwP) turns a returning user’s past verifications into new evidence at onboarding, with their consent.
Many people have already verified with Persona, often for other businesses. When one of those people verifies with you and agrees to Verify with Persona, Persona checks today’s session against their verification history across the Persona network. It then returns two signals to you alongside your normal verification results:
- Identity confidence: how strongly the person’s verification history supports that they are who they say they are.
- Session consistency: whether today’s session fits that history, including their face, device, network and location.
Your flow doesn’t change. Users still complete every step you’ve configured, including government ID and selfie. Verify with Persona adds evidence on top of those steps and doesn’t replace any of them.
Why use Verify with Persona?
- Higher assurance. Get identity confidence and session consistency on every Inquiry where the user opts in, so you know who’s returning and whether today’s session fits their history.
- Stronger fraud deterrence. A live selfie combined with cross-network history catches what a single session can miss: borrowed identities, unfamiliar devices and networks, and unexpected travel. A stolen ID or a convincing deepfake might pass one verification. Matching someone’s face and patterns across their whole Persona history is much harder.
- Private and in your control. Encrypted lookups return signals, never personal data. You decide what happens next in your own Workflows.
How does it work?
Here’s an example. A user has verified with Persona three times before:
| When | Verification | Device | Network | Location |
|---|---|---|---|---|
| March 2024 | Passport, NFC chip read | iPhone 15 Pro | Comcast | Austin, TX |
| November 2024 | Driver license, mobile SDK | iPhone 15 Pro | Comcast | Austin, TX |
| August 2025 | Selfie verification | iPhone 15 Pro | AT&T | Dallas, TX |
| Today | Your onboarding flow | Android phone | New network |
The face matches and the identity has a strong history, including an NFC chip read, so identity confidence is high. But today’s device and network have never been seen for this person, so session consistency flags them. You can then decide whether that’s expected, for example a new phone, or worth a closer look.
How does this change Inquiry flows?
Verify with Persona adds an option to the first screen of your flow. The user sees a short explanation that Persona will check whether they’ve verified before, using an encrypted version of their data so their identity is never revealed. They choose whether to leave the option on before they begin.
- If the user opts in and has Persona history: Persona runs the lookup alongside your flow and attaches the identity confidence and session consistency signals to the Inquiry.
- If the user opts out, or has no earlier Persona history: they complete your flow as normal, and no Verify with Persona signals are returned.
Either way, the user completes the same steps.
What happens when a signal looks unusual?
You decide. Persona doesn’t change your flow or add steps on its own. It returns the signals, and you choose what to do with them in your Workflows. For example, you can:
- add a step, such as an additional verification
- send the Inquiry for manual review
- approve with more confidence when both signals are strong
Recommended starting point: keep your existing government ID step and add Verify with Persona signals on top. Once you’ve seen how the signals perform for your users, talk to your account team about whether to adjust your flow.
What do I see in my Dashboard?
Verify with Persona signals appear on the Inquiry alongside your other verification results. They’re also available through the API, webhooks and Workflows, so they’re part of your audit trail for security and compliance reviews.
Closed-beta partners receive full signal definitions and field-level details during onboarding.
What data does my organization receive?
Signals only. Persona uses encrypted lookups to compare today’s session with the user’s verification history. You receive the identity confidence and session consistency results. You don’t receive personal data or details from the user’s verifications with other businesses. Persona never sells user data.
How is user consent handled?
Verify with Persona only runs for users who opt in during the flow. The option explains what Persona will check before the user begins, and users who opt out complete your flow as normal.
End users can ask Persona to delete their verification history, or to stop using it for Verify with Persona, through the Persona privacy portal. Requests about information users shared in your flow come to you, as with any Persona verification. See Can I delete my data?
Is Verify with Persona the same as Persona Wallet (Reusable Personas)?
No. Verify with Persona replaces Persona Wallet and works differently.
| Persona Wallet (Reusable Personas) | Verify with Persona | |
|---|---|---|
| Purpose | Let users skip steps by reusing saved information | Add evidence to a verification |
| Does the user skip steps? | Yes | No. Your flow runs as configured |
| How it works | A passkey-protected wallet the user creates | An encrypted, consented lookup against the user’s earlier Persona verifications |
| What you receive | The user’s reused information | Your normal results, plus identity confidence and session consistency signals |
| What the user sets up | A wallet and a passkey | Nothing. They opt in during the flow |
How do I get Verify with Persona?
Verify with Persona is in closed beta. We’re opening it to a small group of partners, starting with high-assurance use cases such as workforce identity and account security. To request a spot, contact your Persona account team.
Where is Verify with Persona available?
Availability depends on the user’s region and the type of ID. Your account team can confirm availability for your use case.