Tap to Pay on iPhone Support
USER MANUALS - Quick Install Guide
This guide provides the developer an overview of the steps needed to integrate the MagTek Virtual Reader iOS SDK for Tap to Pay on iPhone into their own mobile App. The documents focus on the MagTek Virtual Reader integration and related features and not the features of the Magensa Payment Protection Gateway (MPPG) or Unigate that are addressed in their respective documentation or online tools
Receive notifications on the latest software, SDKs, APIs and Demo programs..
Subscribe to Software RSSAPI
Generate and sign a JWT as needed for the Apple iOS Proximity Reader framework and sample code under TRANSACTION > EMV > and see both auth and sale. On the Auth drop down see Auth (AppleTaptoPay).
SDK
This SDK enables developers to add Tap to Pay on iPhone functionality to their apps. With Tap to Pay on iPhone and an enabled app, merchants can accept all types of in-person, contactless payments right on their iPhone—no extra readers or hardware needed.
- Merchants can accept a wide range of contactless payments, including:
- - EMV Contactless credit and debit cards.
- - Digital wallets like Apple Pay and other NFC wallets.
- - Apple Watch and other wearables.
- Merchants will need an iPhone Xs or a newer model. The device should also be updated with the latest version of iOS. To update to the latest version of iOS on your iPhone, go to Settings > General > Software Update. Then tap Download and Install.
- Visit https://support.apple.com/en-us/118575
- Security against skimming: Contactless cards use radio waves to transmit data. If the cardholder name were included, a fraudster with a hidden reader could potentially capture it to attempt identity theft or online purchases.
- Privacy compliance: Financial regulations like GDPR and GLBA encourage data minimization. Since a cardholder name is not required to authorize a tap-to-pay transaction, issuers omit it to reduce the risk of exposing personal information during a data breach.
- EMV standards: While cardholder name is stored on the chip for "dipped" (inserted) transactions, the contactless protocol is specifically programmed to block that data field. This is why a receipt might show "Valued Customer" or "No Name" when tapped.