Google Access Hub (LEGIC service)
LEGIC's Google Wallet integration service — analogous role to their Apple Credential Provider service, but for Google Wallet Corporate badges. Paired with LEGIC Orbit for key management. Operates as a direct integration with Google's Access Platform (no external mediator like the NXP MIFARE2GO path Wavelynx uses).
In the LEGIC topology, LEGIC operates Google Access Hub & Orbit Service and the Client Backend (AE's system) drives the provisioning flow by: (1) requesting credential preparation and receiving a provisioning token, (2) delivering that token to the user's registered mobile app, and (3) managing lifecycle changes by calling LEGIC's Google Access Hub API.
The Google flow requires a LEGIC Mobile SDK running inside the mobile app. The SDK speaks Google's Access Platform protocol on-device — initiating the add-to-Wallet sequence, requesting the credential bundle, and handling installation into Google Wallet. No equivalent SDK is needed for the Apple flow (iOS handles the wallet protocol natively).
Card format for Google Wallet credentials is chosen at project onboarding: neon (LEGIC's proprietary NFC format) or DESFire (NXP MIFARE DESFire). This choice determines reader compatibility at the customer site.
What other systems call it
Per-vendor / per-standard terminology for this same concept.
| System | Term / Notes |
|---|---|
| Access Hub (LEGIC) |
- src/LEGIC/email-john-harvey-2026-05-13.md — Q3, Q6 — Google "Access Hub" service language
- src/LEGIC/pptx-alert-req-diagrams-2026-05-14.md — Slide 2 — Google flow; Mobile SDK; neon/DESFire card format; token-based provisioning