Apple Pay

Apple’s mobile payment and digital wallet service. In MDM environments, Apple Pay can be restricted or allowed through configuration profiles to prevent unauthorized purchases or enforce payment policies.

What to Know

Apple Pay restrictions prevent users from adding personal payment methods to corporate devices, which is critical for preventing unauthorized purchases and maintaining clear boundaries between corporate and personal use. Organizations issuing devices to field workers, retail employees, or delivery drivers often restrict Apple Pay to prevent devices from being used for personal transactions, which could create liability issues or complicate expense reporting.

Common Scenarios

Enterprise IT: Corporate IT restricts Apple Pay on shared devices like retail point-of-sale iPads, showroom demo devices, or field service iPhones to prevent personal purchases. For employee-assigned devices, policies vary based on the organization’s BYOD stance—some allow Apple Pay for employee convenience, while others block it to maintain strict corporate-only usage.

MSP: MSPs typically restrict Apple Pay on client devices by default unless the client explicitly requests otherwise. This prevents accidental personal charges and eliminates confusion about which devices are approved for personal payment methods. MSPs should clarify Apple Pay policies during client onboarding to avoid misunderstandings.

Education: Schools universally restrict Apple Pay on student devices to prevent unauthorized purchases and eliminate the risk of students using school-issued devices for personal transactions. Teacher devices may have Apple Pay enabled for personal use if the school allows personal use of teacher-assigned devices.

In Addigy

Addigy’s Restrictions payload includes an “Allow Apple Pay” toggle that disables Apple Pay when unchecked. This restriction prevents users from adding cards to Wallet, making payments with existing cards, or using Apple Pay on the web. The restriction applies on supervised iPhones and iPads and takes effect immediately upon profile deployment. Addigy’s interface clearly labels this as a supervised-only restriction to prevent admins from deploying unsupported policies.