# Hybrid ID: connection approval and verification requests

## Applicant flow

1. The person signs in through Hybrid ID and approves the application's requested
   sign-in permissions. Hybrid ID records **Application connection approved**.
   This confirms the approval, not that the bank has opened an account or that
   its callback/onboarding succeeded. Returning sign-ins with unchanged approval
   do not create repeated connection notices.
2. An application with enabled verification requests and the user's explicit
   `verification:request` scope creates a case using its saved policy version.
   The existing authenticated `POST https://auth.hybrid-id.com/verification/requests`
   contract and idempotency key apply. A new case is `consent_required`.
3. The person sees **Additional approval required** in Hybrid ID. The request
   names the application and policy. Hybrid ID's **Access requests** inbox and
   **My verification** show the current request and its review link.
4. Hybrid Verify shows the evidence requested, purpose, retention and authorized
   result disclosure. The person must explicitly consent; biometric processing
   has its own consent. Opening a notification or successfully signing in grants
   none of these permissions. Approval for one app does not share documents with
   other apps. Changed requirements use a new immutable policy and request.
5. Saved consent is recorded separately from evidence collection, review and a
   verification decision. Cancellation is also shown. An application must check
   the supported authenticated case/result APIs; notifications and redirects
   are never authorization evidence or proof that KYC passed.

## Email availability

Hybrid ID account email delivery is enabled. Optional notices depend on the
user's confirmed current email address and delivery-time notification preferences;
in-account notices remain available. The encrypted notification outbox supports
connection approval, changed sign-in permissions, additional approval, saved
consent and cancellation. Enqueueing a notice does not establish receipt or a
completed verification. Actual verification-result delivery requires its separate
its own delivery capability; account email and result delivery are separate.

These emails identify the requesting app and link to
<https://hybrid-id.com/account/service-access>. The link requires ordinary
Hybrid ID authentication; it contains no bearer token, one-click approval,
document link, account identifier or verification result. Email has no document
attachments and never requests passwords or authenticator codes by reply.

Canonical Data Vault document intake is enabled after protection setup, current
authority and the user's approval. Camera capture and automated verification
decisions remain gated. Saved consent is not a passed check. Applications must
not treat `collection_enabled` as permission to retrieve or collect documents.

## Integration references

- [Application policies and requests](https://hybrid-id.com/developers/verification#application-policies)
- [Developer API schema](https://hybrid-id.com/integrations/developer-openapi.json)
- [Hybrid ID integration guide](https://hybrid-id.com/developers/integration)
- [Account notification delivery](https://hybrid-id.com/integrations/account-notifications.md)
- Current verification releases (contact the integration team)

Applications cannot supply a recipient address, send arbitrary email through
Hybrid ID, mark a notice as delivered, or use developer management credentials
to read a person's notification history.
