LEGIC

AE manages credential issuance and lifecycle directly with the wallet platforms.

Active integration2 flows

Apple Wallet

direct

Google Wallet

direct

Samsung Wallet

—

Lifecycle authority

LEGIC Connect

Status events from

LEGIC Connect

Status

Active integration

Sequence flows

appleios

Apple Wallet issuance

10 steps · 6 actors · 3 crypto envelopes

googleandroid

Google Wallet issuance

10 steps · 6 actors · 3 crypto envelopes

API surface

LEGIC Connect Wallet API (current)active

Deploys Corporate badges to Apple and Google Wallet. Accepts payload formatted per the latest OSS-SO (Wallet extension) specification. Supports credential updating on Apple + Google Wallet passes post-provisioning (Q5). Customer-supplied master keys via API or manual key ceremony; HSM-wrapped key import is NOT supported (Q2). Key rotation supported when LEGIC Orbit is in use (Q4).

LEGIC Orbit (key management service)active

LEGIC's HSM-backed key management service. Generates "never-visible" random keys within LEGIC HSMs. Recommended path over customer-supplied master keys. Mobile-credential keys are INDEPENDENT of physical card encryption keys — architecturally distinct from the Wavelynx / HID diversification models. The installed base of LEGIC secure-module-based reader/lock hardware integrates with Orbit so wallet-specific encryption keys flow into access hardware without ever appearing in plaintext outside an HSM.

Architectural differentiator vs. Wavelynx / HID: LEGIC's wallet encryption keys are INDEPENDENT of physical card encryption keys (per Q2). Wavelynx and HID both derive per-credential keys from a master that's shared with physical-card encryption; LEGIC isolates the wallet key from any physical card encryption key. This means compromise scope is narrower per-credential, but it also means LEGIC's mobile credentials live in a separate key universe from the customer's existing physical badging — relevant for side-by-side deployments. Average end-to-end provisioning time per LEGIC: 20-30s (Q6), with >90% of that latency inside Apple/Google services. LEGIC processes themselves are "under Apple and Google benchmarks." Same range we'd quote for the other CPs — useful for Sales answering "how fast does it provision" without splitting hairs by vendor. OSS-SO support: LEGIC Connect deploys Corporate badges where the payload is formatted per the latest OSS-SO (Wallet extension) specification (Q1). The standard's Wallet extension is what LEGIC explicitly confirmed; OSS-SO Parts II/III + OSS-SID weren't separately confirmed — see Open Questions.

Sequence flows

API surface

The AE Mobile Wiki needs a bigger screen.