Wallet Loyalty for Card-Show Vendors

Begin with a customer benefit

A digital pass is a delivery format, not a loyalty strategy. Before designing it, name the behavior and customer problem the program addresses. Useful show-vendor benefits can include:

points earned on eligible purchases;
early access to a scheduled inventory drop;
member-only products or pricing;
a persistent link to the seller's storefront;
a scannable member identifier at the booth;
saved collecting preferences or want-list access; and
clear progress toward a defined reward.

Avoid vague status with no operational value. A collector should be able to explain why they would add the pass and what changes after doing so.

Write the program terms before the promotion. Define who can join, eligible transactions, points or benefit calculation, exclusions, redemption, returns, expiration, transfer, account closure, and support. Review applicable consumer, promotion, privacy, and accounting obligations with qualified advisers.

Keep authoritative state outside the pass

The seller's commerce and loyalty system should own membership, transactions, balances, and redemption history. The wallet pass displays current state and a convenient identifier. This distinction matters when a phone is offline, a pass is out of date, a purchase is refunded, or a customer changes devices.

A durable loyalty ledger records why every balance changed:

earned from an eligible paid order;
adjusted after a refund or cancellation;
redeemed against an eligible benefit;
corrected by an authorized staff member with an audit reason; or
expired according to published rules.

Use idempotency for provider and order events so a payment retry cannot award points twice. Enforce seller isolation on every customer, order, balance, and adjustment. The CRM guide explains how loyalty state connects to the broader customer record.

Understand Google Wallet's model

Google Wallet's loyalty documentation distinguishes a loyalty class from a loyalty object. The class contains shared program properties, while the object represents an individual user's pass. That model is useful for separating seller-wide branding and program details from customer-specific identifiers, points, and status.

Google also documents issuing passes through web, email, and SMS using an "Add to Google Wallet" link. Follow Google's brand, signing, account, and review requirements. Do not hand-build a lookalike button or expose signing credentials in the browser.

Plan how object updates occur after purchases, refunds, redemptions, and program changes. A successful add does not prove future balance updates work.

Understand Apple Wallet passes

Apple's Wallet Passes documentation covers creating, distributing, and updating passes. Apple describes signing passes with an Apple-issued certificate and provides an update model for passes that need current information.

Treat signing certificates and keys as production secrets. Keep them outside source control and client code, rotate them through an established secret process, and monitor expiration. Use the official pass package format and distribution guidance.

Test adding, viewing, updating, and removing a pass on supported devices. Also test what the customer sees when the pass is stale or the update service is unavailable.

Design the show-floor enrollment flow

The booth flow should not force a collector through a long registration merely to understand the program.

Explain the concrete benefit on the sign or conversation.
Send the QR code to a seller-branded mobile page.
Show program terms and required account information.
Separate marketing consent from membership enrollment when they are distinct.
Confirm the account or membership.
Offer the correct Apple Wallet or Google Wallet action for the device.
Provide a normal account link as a fallback.

Use the owned storefront guide to keep the enrollment, account, and checkout under one recognizable seller journey. The pass should link back to a safe seller-owned page, not an opaque shortener.

Choose an identifier carefully

A barcode or QR code on the pass can retrieve membership at the booth, but it should not expose sensitive account data. Use a random, revocable identifier or signed token appropriate to the risk. Do not encode an email address, balance, or authorization decision directly in a reusable visible code.

At scan time, staff authorization and seller scope still matter. Looking up a member does not authorize staff to alter a balance or view unnecessary customer information. Log redemptions and adjustments with seller, staff, reason, and time.

Provide a recovery process for lost devices, duplicate passes, and compromised identifiers. The account, not possession of a static code alone, should control high-value actions.

Decide what appears on the pass

Prioritize information the collector can use quickly:

seller and program name;
membership identifier or display name when appropriate;
current points or status with last-updated context;
the next defined benefit or threshold;
a storefront or account link;
support contact; and
concise terms or a terms link.

Avoid turning the pass into a miniature marketing page. Keep changeable content tied to authoritative data, make links descriptive, and use accessible contrast and text. Do not display inventory availability or an expiring offer unless the update system can keep it accurate.

Integrate orders, returns, and offline operations

Award points only from defined order states, commonly after payment is confirmed. Decide whether points become redeemable immediately or after a return window. When an order is refunded, reverse the correct earned amount using a ledger entry rather than silently overwriting the balance.

Shows can have poor connectivity. Define what staff may do offline. A safe approach may allow a pass identifier to be recorded while deferring balance mutation until the server confirms current state. If offline redemption is supported, set limits, prevent replay, synchronize deterministically, and give staff a conflict workflow.

The vendor tech stack guide covers payment, connectivity, inventory, and customer systems that loyalty depends on.

Communicate without abusing wallet access

Wallet platforms may support pass updates and relevant notifications, but access to a pass is not permission for unlimited marketing. Keep messages tied to the program and platform policies. Maintain email or other channel consent separately.

The follow-up email sequence uses explicit marketing eligibility and unsubscribe checks for recurring email. A pass should coexist with those preferences rather than bypass them.

Make it easy to understand how data is used, get support, leave the program, and remove or deactivate the pass. Program closure or major term changes need a planned customer communication and balance treatment.

Test the complete loyalty lifecycle

Before launch, test:

new enrollment and duplicate enrollment;
add-to-wallet on supported Apple and Android devices;
pass display with long names and large balances;
an eligible purchase and point award;
retry of the same payment event;
a partial and full refund;
redemption and insufficient balance;
pass update and temporary provider failure;
lost device or identifier replacement;
account closure and program exit;
cross-seller access denial; and
support access with the least required information.

Measure retention, not pass adds

Pass adds are an activation metric. Measure identified show visits, member purchases, redemption, repeat purchase rate, contribution margin after rewards, program support issues, dormant balances, and retention compared with an appropriate baseline.

Watch for gaming, duplicate accounts, point reversals, failed updates, and benefits that cost more than the behavior they produce. Improve the benefit and operating rules before increasing enrollment promotion.

Frequently asked questions

Do I need both Apple Wallet and Google Wallet?

Supporting both provides broader device coverage, but launch only what can be issued, updated, secured, and supported correctly. Always provide a normal account fallback.

Can the pass itself store the loyalty balance?

It can display a balance, but the authoritative balance should remain in the seller's ledger. The pass may be stale, offline, duplicated, or removed.

Should points be awarded at the booth before payment settles?

Tie earning to a defined trustworthy order state. If the payment can still fail or reverse, pending points may be safer than immediately redeemable value.

Is adding a pass the same as marketing consent?

No. Membership, wallet distribution, service notifications, and recurring marketing can have different purposes and legal bases. State each choice clearly and maintain the relevant preference.