---
title: "Scaling Verify with Wallet for Identity Verification at Uber"
description: "Uber integrated Apple’s Verify with Wallet API into its cross-app Identity Verification Platform to support government-backed digital IDs across driver onboarding, age-gated ordering, and car rental use cases. The central challenge was allowing each use case to request only its Apple-approved identity data while operating through a scalable, platform-agnostic service rather than separate integrations. Server-side configurations map Uber identity models to PassKit objects, set one-time or persistent storage intent, and validate responses using HPKE decryption, CBOR payloads, session transcripts, MSOs, device signatures, and issuer certificate chains under ISO/IEC 18013-5. A registry of IACA certificates, sourced from jurisdictional portals and AAMVA’s VICAL, supports overlapping certificate rotations, while the platform is intended to accommodate new document types and cross-platform digital credential integrations."
---

# Scaling Verify with Wallet for Identity Verification at Uber

[Uber](https://yomu.fyi/company/uber) · Jul 9, 2026

**Type:** Problem & solution

## Summary

Uber integrated Apple’s Verify with Wallet API into its cross-app Identity Verification Platform to support government-backed digital IDs across driver onboarding, age-gated ordering, and car rental use cases. The central challenge was allowing each use case to request only its Apple-approved identity data while operating through a scalable, platform-agnostic service rather than separate integrations. Server-side configurations map Uber identity models to PassKit objects, set one-time or persistent storage intent, and validate responses using HPKE decryption, CBOR payloads, session transcripts, MSOs, device signatures, and issuer certificate chains under ISO/IEC 18013-5. A registry of IACA certificates, sourced from jurisdictional portals and AAMVA’s VICAL, supports overlapping certificate rotations, while the platform is intended to accommodate new document types and cross-platform digital credential integrations.

## Context

Uber needed to support different identity verification requirements across multiple apps and marketplace segments while ensuring each Verify with Wallet request stayed within its Apple-approved data scope. The integration also had to handle platform abstraction, ISO/IEC 18013-5 validation, cryptographic security, and rotating government certificate authorities at scale.

## Approach / What changed

Uber centralized orchestration in its Identity Verification Service. Server-side configurations define use-case-specific data elements and storage intent, a mapping layer converts internal identity models into PassKit objects, and the service decrypts and validates responses using HPKE, session transcripts, MSOs, device signatures, issuer certificate chains, and a registry of rotating IACA trust anchors.

## Takeaways

- Per-use-case scoping occurs in Uber’s backend, allowing an app-level Entitlements file to cover multiple flows while requests remain limited to pre-vetted identity data elements.
- Verification responses use HPKE-encrypted CBOR payloads and undergo session-transcript, MSO, device-binding, and issuer-certificate validation under ISO/IEC 18013-5.
- The IACA registry supports multiple active certificates per jurisdiction, allowing credentials signed with older keys to remain valid during certificate rotations.

**Tags:** [Apple](https://yomu.fyi/topic/apple), [Digital Identity](https://yomu.fyi/topic/digital-identity), [Identity Verification](https://yomu.fyi/topic/identity-verification), [Privacy](https://yomu.fyi/topic/privacy)

- Source: [Uber](https://www.uber.com/us/en/blog/scaling-verify-wallet)
- Source URL: https://www.uber.com/us/en/blog/scaling-verify-wallet
- Ingested by Yomu: 2026-09-10T20:02:20.475Z

[Read original post](https://www.uber.com/us/en/blog/scaling-verify-wallet)