Persona Connect Overview

What is Persona Connect?

Persona Connect lets one Persona customer (the Source Organization) share an end user’s previously collected identity (KYC) or business (KYB) verification data with another Persona customer (the Destination Organization), so the end user doesn’t have to go through the same verification steps twice. Every share is gated by the end user’s explicit consent — Persona doesn’t move any data between organizations without the end user opting in.

Connect is an organization-to-organization way of reusing verified data: the two organizations set up a sharing relationship directly (no consortium or shared data pool involved), and data only moves between them when the end user agrees to a specific share.

Key concepts

• Source Organization — the organization that shares an end user’s data with a partner. It creates the Connection and the Share Token, and sends the token to the Destination Organization.
• Destination Organization — the organization that receives an end user’s data from a partner. It accepts the Connection and redeems the Share Token.
• Connection — the ongoing relationship between two organizations that must be active before either side can create or redeem a Share Token between them. An organization can also create a self-Connection to itself, which is a convenient way to test Connect without a partner.
• Share Token — a secure token the Source Organization creates to share one end user’s data; the Destination Organization redeems it to access that data.

How sharing works

1. The Source Organization creates a Connection with the Destination Organization (from the Dashboard or via API), and the Destination Organization accepts it.
2. The Source Organization creates a Share Token for a specific Inquiry, Account, or Transaction, and sends the token to the Destination Organization (for example, as part of a redirect or a backend handoff).
3. The Destination Organization redeems the Share Token against an Inquiry on its own side. Redeeming automatically fills in the steps of the destination Inquiry that the Share Token’s data covers.
4. If the destination Inquiry’s template requires information the Share Token didn’t include, the Inquiry pauses at the first step it’s missing. The end user can be sent a resume link to provide just that remaining information.

Destination Organizations can also use Workflows to automatically redeem incoming Share Tokens, rather than building custom logic to handle them.

What can be shared

Share Tokens can carry data from Inquiries, Accounts, and Transactions. When a Destination Organization redeems a Share Token, it can:

• Re-run Verifications — import the shared data and run it through its own verification checks, producing a fresh decision under its own configuration.
• Prefill an Inquiry — pre-fill a destination Inquiry with the shared data, sending the end user back into the flow only to provide whatever additional information the destination’s template requires.

Persona is also rolling out the ability for a Destination Organization to clone a Source Organization’s Verification results directly, without re-running its own checks, to select partners. If you see a purple Cloned sticker or a clone banner in your Dashboard, see Persona Connect: cloned verifications for what that means.

Consent and data ownership

Both the Source and Destination Organizations are responsible for getting end-user consent before sharing or accepting data — Persona doesn’t collect this consent on a customer’s behalf. In practice, this means:

• Updating your Terms of Service and/or Privacy Policy to disclose the data sharing.
• Giving end users an explicit opt-in (and opt-out) moment before their data is shared, typically shown inline in the Persona flow.

Data shared through Connect still belongs to the end user, not to Persona or to either organization. Each organization is a controller of its own copy of the data it sends or receives through Connect, and Persona remains a processor for both organizations — Connect doesn’t change the controller/processor relationship either organization already has with Persona, it just adds a consent-gated way to move data between them.

Getting started

• Sandbox: Connect can be enabled in your Sandbox environment on request — ask your Persona account team.
• Production: Using Connect in Production requires a one-time agreement with Persona. Once that’s in place, your organization can act as a Source, a Destination, or both, with any number of partners.

Frequently Asked Questions (FAQ)

Do both organizations need to be Persona customers?

Yes. Connect only works between two organizations that both use Persona — it doesn’t support sharing data to a partner that isn’t a Persona customer.

Can I test Connect without a partner?

Yes. You can create a self-Connection (a Connection from your organization to itself) in Sandbox or Production and exchange Share Tokens between your own Inquiries to see how creation, sending, and redemption work end to end.