Introduction
Digital passes, stored in Apple Wallet or Google Wallet, offer a convenient and efficient way for users to access services, redeem offers, and authenticate their identity. However, to effectively accept and use passes, it’s important to understand the different methods available and clarify some common misconceptions about how passes work. This guide will first explore the various ways to accept passes and then address the misconceptions to help you better understand their functionality.
Methods for Accepting Passes
How someone uses a pass, and how you accept it, depends on the type of experience you want to provide and the technology you choose to implement. Below are the primary methods for accepting passes:
Barcodes
Passes can contain barcodes in formats such as QR, Aztec, PDF417, and Code128.
How it works: When a user presents their pass, the barcode is scanned using a compatible scanner or app (e.g., PassKit’s PassReader app). The information stored in the pass is then retrieved and processed.
Optimization: Wallet apps optimize the presentation of barcodes by locking the screen orientation and boosting brightness to ensure a successful scan.
Best practices: Test your passes with the hardware you plan to use for scanning. Optical scanners are generally better suited for scanning smartphone screens than laser scanners.
Weblinks
Passes can include weblinks that allow users to take specific actions, such as redeeming coupons or accessing exclusive offers.
How it works: Users tap on a link within the pass to initiate an action, such as making a purchase or redeeming a coupon.
Customer Initiated Redemption (CIR): PassKit provides a built-in solution for coupon redemption that doesn’t require complex integration with your Point of Sale (POS) system.
Best practices: Ensure the linked web pages are mobile-friendly and provide a seamless user experience.
Visual
Passes can display text or images below the barcode or in place of a barcode.
How it works: In situations where scanning isn’t feasible, the pass can display relevant information (e.g., a membership number or account details) visually. For membership cards, a user’s profile image can also be used for basic authentication.
Best practices: Keep the displayed information concise and easy to read, especially in low-light or high-traffic environments.
Near Field Communication (NFC)
Passes can be used with NFC readers for contactless interactions.
How it works: Users hold their device near an NFC reader to use the pass. This method is ideal for quick, seamless transactions, such as entering a venue or making a payment.
Requirements: Implementing NFC passes requires an NFC certificate from Apple and adherence to strict technical requirements.
Best practices: Ensure your NFC readers are compatible with Apple VAS and Google SmartTap.
Common Misconceptions About Passes
Now that we’ve covered the methods for accepting passes, let’s address some common misconceptions to help you better understand how passes function and what they can and cannot do.
Passes Don’t "Know" If Someone Has Made a Payment
Reality: Passes themselves do not track payments or financial transactions. Payment processing is handled by the payment gateway or app that interacts with the pass. Passes are simply a medium for storing and presenting information.
Passes Don’t Know If Someone Clicked on a Location Message or Push Notification
Reality: Passes cannot track user interactions with location-based messages or push notifications. These interactions are managed by the app or platform that sends the notification. Passes only become "active" when they are used in a specific context, such as being scanned or tapped.
Passes Don’t Know If Someone Has Walked Into a Building
Reality: Passes cannot autonomously detect a user’s physical location or movement. Location-based triggers, such as a pass appearing on the lock screen when a user arrives at an airport, are managed by the operating system (e.g., Apple Wallet or Google Wallet) and not by the pass itself.
PassKit Only Tracks Specific Actions
Reality: PassKit tracks the lifecycle of a pass, such as when it is created, installed, updated, or removed. However, it does not track how the pass is used unless the interaction occurs through specific PassKit tools like the PassReader app or self-redemption links.
Passes Are Not Always "Active"
Reality: Passes are passive until they are used in a specific context. For example, a pass only becomes "active" when it is scanned, tapped, or interacted with in some way. Until then, it simply sits in the user’s wallet app, waiting to be used.
Passes Don’t Automatically Update Based on User Behavior
Reality: Passes can be updated, but these updates are initiated by the issuer (e.g., a business or developer) and not by the pass itself. For example, if a user earns points on a loyalty card, the business must push an update to the pass to reflect the new balance.
Passes Don’t Track User Identity Without Explicit Action
Reality: Passes do not track or store personal information unless explicitly provided by the user or the issuer. For example, a membership card might display a user’s name or profile picture, but this information is added by the issuer and not automatically tracked by the pass.
Conclusion
Understanding the methods for accepting passes and clarifying common misconceptions is essential for businesses and developers looking to implement digital passes effectively. Passes are powerful tools for enhancing user experiences, but they rely on external systems (like scanning hardware, apps, or web services) to facilitate interactions and track usage. By leveraging the right methods and avoiding common misunderstandings, you can create seamless and engaging experiences for your users.