Alert EnterpriseWiki

LEGIC — Google Wallet issuance

google walletandroid10 steps6 actorsCandidate
10
Candidateoverall flow status
10/ 10 candidate
0%
steps cited
0 of 10 · plus flow-level
Triggers
  • One-time — Partner onboards project with LEGIC (steps 1–2); chooses card format (neon or DESFire)
  • Per-credential — Client Backend prepares credential and receives provisioning token from LEGIC (step 3)
  • Per-credential — Client Backend sends token to user's registered mobile app (step 4)
  • Per-credential — Mobile SDK (on device) initiates add-to-Wallet via Google Access Platform (steps 5–8)
TLSTLSTLSUser / Manageme…userClient BackendpartnerLEGICGoogle Access H…serviceGoogle Access P…platformMobile App (wit…deviceReader Devicedevice?Setup project / configuration and templates (neon or DESFire)?Configure infrastructure incl. keyset?Prepare credential & receive token?Send token to registered mobile app of authenticated user?Gather additional input & initiate add-to-Wallet?Prep credential for wallet?Request credential?Retrieve credentialCrosses trust boundary?Interact with reader?Manage credential lifecycle
Hover steps or envelopes to inspect.
Trust boundary
Source
  • src/LEGIC/pptx-alert-req-diagrams-2026-05-14.md — Slide 2 — Wallet Solutions Flow for LEGIC's Google Wallet Service
Verifying access
Desktop only

The AE Mobile Wiki needs a bigger screen.

The diagrams, comparisons, and animated flows aren't built for phones. Open this link on your laptop or desktop browser and you'll see the full reference.

wiki.alertenterprise.app

Same Google sign-in as the AE App Hub — you'll be in once you open it on a larger screen.