AE Mobile Wiki

Wallet platforms — feature parity

Apple Wallet, Google Wallet, and Samsung Wallet are not equivalent. The differences below are the most-asked questions during AE customer onboarding — capability, not opinion.

CapabilityApple WalletGoogle WalletSamsung Wallet
User-initiated provisioning
User opens "Add to Wallet" on their own device.
Standard add-to-Wallet UX.
Admin-only token redemption — user can't pull a credential.
User-initiated suspend / resume
From the device, no admin action.
iCloud Lost Mode + Find My.
User must contact admin — no in-Wallet path.
2FA enforcement at reader
Force biometric/passcode before credential is presented.
Reader sets TRA flag; device requires Face ID / Touch ID / passcode.
No TRA equivalent.
Tap-and-go on locked device
Authenticate without unlocking.
Express Mode — tap-and-go without unlocking.
Screen must be on; no equivalent to Express Mode.
Dead-battery fallback
Credential authenticates after device powers down.
Power Reserve Mode — up to ~5 hours after shutdown.
NFC reader protocol
Wire-level protocol the reader speaks.
Apple ECP (Enhanced Contactless Polling) + VAS.
Google Smart Tap.
Reader certification required
Reader hardware must be approved by the platform.
Apple Wallet Access Program — certified readers only.
Smart Tap-compatible readers (Collector ID issued).
AE integration paths today
via Wavelynx (direct) or HID Origo (mediated).
via Wavelynx (through NXP MIFARE2GO) or HID Origo (mediated).
Most AE customers run Google Corporate Badge on Samsung devices instead.

Why the asymmetry matters

Apple's user-initiated path means a cardholder can self-recover from a lost or stolen device without admin intervention. On Google, every lifecycle change still routes through the admin tooling. AE's Guardian Wallet flows account for both — but the customer-facing UX you can promise is bounded by the platform.

Samsung — coverage gap

Samsung Wallet (Company ID) is referenced in AE materials but no flow diagrams or technical depth exist in current sources. Most AE customers running Samsung devices use Google Corporate Badge as an installable app. The Samsung integration record renders as a stub until primary documentation is obtained.

Verifying access