If your organisation manages its Android devices through Android Enterprise, MDM, or a managed Google Workspace account, adding a Weel card to Google Wallet can behave differently. This article covers what Weel controls, what depends on your device policy, and your fallback options. Knowing this before a managed-device rollout means fewer surprises for your team.
How It Works
- Weel hands provisioning to Nium, which talks to Google Wallet directly. Any MDM or Android Enterprise policy on Google Wallet applies equally to a Weel card.
- If your IT policy blocks cards in Google Wallet, check with your IT team, not Weel Support, since it's a device restriction we can't see.
- Only your Primary card can be added to a wallet. Secondary cards stay online-only, regardless of your device management setup.
- If wallet provisioning doesn't work, add your card manually: Card tab → cog icon → Add to wallet manually → Get card details.
- Issuing a physical card gives your team a wallet-independent option that works under any device management policy.
- Apple Pay requires a personal Apple ID too, so mixed Android and iOS teams get the same fallback pattern on both platforms.