How to create an Apple Wallet loyalty card

Define the job before designing the card. A loyalty pass may identify a member, display a tier or points balance, carry a redeemable code, or combine those roles. Choose the store card style for an ongoing retail relationship and a generic pass when the credential is a membership or access card without store-card behavior.

If you are copying a card issued by another business, check its terms and use the official Wallet option when available. If you operate the program, define the member identifier, reward rules, data owner, and update policy before issuing passes.

Put the fact needed at checkout in the primary field: member name, current balance, points, or tier. Use secondary and auxiliary fields for the member number, expiry, next reward, or program status. Keep terms, support details, and privacy information on the back.

Ask the point-of-sale operator which barcode formats and payload rules it accepts. Reuse the exact recognized member identifier or a secure token generated by the loyalty backend. Add alt text so staff can perform a manual lookup when scanning fails.

In PassMaker, start with a store card or generic template, enter the identity and field values, configure the barcode, then add an icon, logo, and supported artwork. Use enough contrast for labels and values, and preview long names and large balances before export.

A Wallet pass must be packaged and signed before iPhone will install it. Export the Wallet-ready PKPass, add it to Wallet, and verify the displayed issuer, fields, artwork, and code. Keep the signing identity under the control of the organization responsible for the program.

Test the finished pass at the real checkout or access point. Confirm that scans resolve the correct account, manual lookup works, long values remain legible, and staff know what to do when a member is offline or the program backend is unavailable.

A static pass will keep the values embedded when it was created. Live balances, points, status changes, and remote revocation require a Wallet web service and push-update infrastructure. Contactless loyalty passes require a separate Apple approval, NFC certificate, and certified point-of-sale integration; a barcode pass does not become contactless by adding an NFC-looking icon.