Skip to main content

KYC Passport

The KYC Passport lets an organization securely share verified KYC data with partner organizations, so users don't repeat verification across an ecosystem, while keeping the sharing under the user's consent and control.

This page covers the conceptual architecture: how access grants are generated, the rules that govern them, and the sequence flows behind partner data access. For the operational side, inviting partners, accepting invitations, managing consent, screenshots, and FAQs, see the KYC Passport guide.

Overview​

A main organization invites partner organizations to access KYC results from specific flows. The user consents once, during verification, to sharing with the named partners. This creates a trusted ecosystem where verified identity data is shared efficiently without re-verification.

Key benefits​

  • Seamless partner integration: share KYC results with multiple partners without repeat verification.
  • User-centric consent: users explicitly consent to the exact list of partners.
  • Efficiency: removes redundant verification across partner organizations.
  • Secure access control: cryptographic access grants ensure only authorized partners can decrypt data.

Consent is the precondition for every partner access grant:

  • No consent = no access. If the user does not consent, no partner grants are created, only the main organization receives a grant.
  • Invite timing matters. Partners invited after a user completes verification do not retroactively receive access to that user's data.
  • Consent is flow-specific. It binds to a specific flow and the list of partners invited at verification time.

Access grant generation​

Access grant rules​

  1. Main organization: always receives a grant when the user completes verification with consent.
  2. Accepted partner invites: receive a grant immediately.
  3. Pending partner invites: a grant is created and becomes active when the partner accepts.
  4. Rejected partner invites: no grant is created.
  5. No consent: no partner grants are created (only the main organization).

Partner invitation lifecycle​

Accepting an invite (existing organization)​

Accepting an invite (new organization)​

Partner data access​

Main organization data access​

Partner organization data access​

:::info Access grant differences

  • Main organization: grants establish a connection between the organization and the verified document.
  • Partner organizations: grants associate the invite with the verified document, linking it to the invitee organization on acceptance.

This ensures partners can only access data from the specific flow they were invited to, and only for users who completed verification after the invite was created (with proper consent). :::

Security considerations​

  • Access grants are proxy re-encryption keys that transform ciphertext from the user's key to the partner's key (see Data Sharing and Encryption). Zyphe acts as the proxy: it performs the transformation but never sees plaintext or holds either private key.
  • Data stays encrypted in decentralized storage under the user's key. Partners receive re-encrypted ciphertext that only their private key can decrypt; a full breach of Zyphe yields only encrypted data and re-encryption keys.
  • Grants are auditable and revocable. Revoking deletes the re-encryption key, ending future transformations for that pair. Where data-retention obligations apply, access remains until those obligations are met.
  • Invites are authenticated with a unique inviteId and a one-time password (OTP) sent by email, over encrypted HTTPS.
  • Consent is verified before any grant is created or activated, and is linked to the grant via flow consents.