Wallet

Stores digital cards and IDs. In MDM, Wallet can be restricted or managed to prevent unauthorized payment methods or deploy corporate access passes.

What to Know

Wallet restrictions prevent users from adding personal payment cards to corporate devices while still allowing organizations to deploy corporate access badges, transit passes, or event tickets. Blocking Wallet entirely prevents both payment functionality and useful business applications like building access cards, so organizations typically restrict payment card additions while allowing corporate-issued passes. MDM also enables remote deployment of Wallet passes, allowing IT to push employee badges, conference tickets, or boarding passes without requiring manual installation.

Common Scenarios

Enterprise IT: Corporate IT restricts Apple Pay card additions on company-owned devices to prevent personal payments while using Wallet to deploy corporate building access badges, employee ID cards, or event passes. IT pushes Wallet passes through MDM for company-wide events, facility access, or transit benefits. On shared devices like retail kiosks or field service iPads, IT typically disables Wallet entirely to prevent any personal use.

MSP: MSPs configure Wallet restrictions based on client policies around personal device use. Most clients restrict payment card additions by default while allowing corporate passes. MSPs should clarify whether clients want to deploy corporate passes through Wallet (building access, transit, etc.) before completely disabling the feature. Some retail or hospitality clients use Wallet to deploy employee badges or shift credentials.

Education: Schools restrict Wallet on student devices to prevent unauthorized purchases and eliminate the risk of students using school-issued devices for personal transactions. Schools may use Wallet to deploy student ID cards for library access, cafeteria payments, or campus building entry. Teacher devices may allow Wallet for personal use if the school permits personal use of teacher-assigned devices.

In Addigy

Addigy’s Restrictions payload includes separate controls for “Allow Wallet” (completely disables Wallet) and “Allow Apple Pay” (disables payment functionality while allowing passes). This granularity allows admins to block payments while still deploying corporate passes. Addigy supports deploying Wallet passes through configuration profiles, pushing corporate badges, tickets, or credentials to devices without user intervention. The Restrictions interface clearly distinguishes between full Wallet disablement and payment-only restrictions.