How to Connect Square Loyalty with Apple Wallet and Google Wallet

Square and Litecard solve different parts of the customer journey.

Square manages payments, transactions, customers and loyalty. Litecard turns that customer and loyalty data into advanced Apple Wallet and Google Wallet experiences.

Square’s native loyalty pass provides a convenient NFC experience for eligible iPhone customers. Litecard extends the experience with:

• Apple Wallet and Google Wallet passes
• NFC, barcode and QR-code identification
• Advanced wallet designs
• Litecard-hosted signup forms
• Klaviyo and Mailchimp distribution
• CRM and CDP integrations
• Loyalty-triggered wallet notifications
• Location-based wallet messages
• Membership, offer and treatment-package journeys
• Compatibility with Square and other point-of-sale systems

Together, Square becomes the transactional engine and Litecard becomes the mobile-wallet engagement layer.

What does Square do?

Square provides the operational infrastructure for accepting payments and managing commerce.

Depending on the Square products being used, this can include:

• Square Point of Sale
• Payment processing
• Customer Directory
• Square Loyalty
• Products and catalogues
• Orders and transactions
• Discounts and rewards
• Appointments
• Subscriptions
• Customer groups
• Business reporting

Square Loyalty lets businesses enrol customers, award points and create rewards based on qualifying purchases.

Customers can normally enrol by entering their mobile number at checkout, through an invoice or during an online purchase. Square then connects their loyalty activity to the relevant customer account.

The Square Loyalty API allows approved applications to retrieve loyalty accounts, points balances, rewards and balance-changing events.

Does Square have a native Apple Wallet loyalty pass?

Yes. Square offers a native loyalty pass for eligible iPhone customers.

After enrolling, a customer may be prompted to add the business’s loyalty pass to Apple Wallet. The customer can then tap their iPhone against a compatible Square customer display or contactless reader to:

• Identify themselves
• Check in
• Earn points
• View their balance
• Redeem available rewards

Square’s Australian documentation describes this Apple Wallet loyalty enrolment and NFC check-in process.

Square’s customer documentation currently states that its native loyalty-pass feature is available on iOS devices. It should not be confused with accepting Apple Pay or Google Pay as payment methods.

Why add Litecard if Square already has a wallet pass?

Square’s native pass is a strong option for businesses wanting a straightforward Apple Wallet and NFC loyalty experience within Square.

Litecard is valuable when the business needs a broader mobile-wallet strategy.

Litecard does not need to replace Square Loyalty. It can present Square’s customer, loyalty and transaction data through a more configurable Apple Wallet and Google Wallet experience.

How Square and Litecard work together

A typical integration follows this process:

1. A customer joins through Square or a Litecard signup form.
2. A Square customer profile is created or identified.
3. Litecard creates a personalised wallet pass.
4. The pass stores the mapped Square Customer ID or another secure identifier.
5. The customer saves the pass to Apple Wallet or Google Wallet.
6. Square records purchases, loyalty points and rewards.
7. Square webhooks notify Litecard when relevant data changes.
8. Litecard updates the wallet pass.
9. Litecard can trigger relevant wallet messages.
10. The pass identifies the customer during their next visit.

The relationship is simple:

Square records the commercial event. Litecard turns that event into a wallet experience.

What can a Square-connected Litecard pass display?

A Litecard wallet pass can display information retrieved from Square or another connected system.

Common fields include:

• Customer name
• Customer or member number
• Points balance
• Loyalty tier
• Available rewards
• Reward expiry
• Membership status
• Treatment or class balance
• Visit count
• Available offer
• Favourite location
• Barcode or QR code
• Booking link
• Account link
• Store information

For example:

LITECARD LEGENDS

Jane Citizen

GOLD MEMBER

POINTS

820

REWARDS

1 available

MEMBER NUMBER

01234567

A clinic or spa might instead display:

LUMA SKIN & WELLNESS

Jane Citizen

5-TREATMENT PACKAGE

TREATMENTS REMAINING

3 of 5

VALID UNTIL

31 December 2026

Three ways to identify customers at Square POS

1. Square’s native NFC loyalty pass #

The customer taps their iPhone against compatible Square hardware.

Square handles the NFC identification, loyalty check-in, point accrual and reward-redemption journey.

This is the cleanest option when:

• Square Loyalty is the complete loyalty system
• The customer base is primarily on iPhone
• The standard Square pass is sufficient
• Advanced wallet marketing is not required

2. Litecard barcode or QR-code pass #

Litecard places a barcode or QR code on an Apple Wallet or Google Wallet pass.

The code can represent:

• Square Customer ID
• Loyalty account ID
• Member number
• Email or mobile number
• Secure Litecard identifier
• Another mapped customer identifier

When the code is scanned, the configured integration identifies the customer and connects them with the Square transaction.

This approach is useful when:

• Android customers require Google Wallet
• Existing barcode scanners are already available
• The business has multiple POS systems
• A visual membership card is required
• NFC is unavailable at some locations
• The business wants a fallback identification method

The barcode format, scanner and Square customer-matching workflow must be tested before launch.

3. Litecard NFC with barcode or QR fallback #

Litecard can also support NFC passes where the wallet platform, reader and implementation allow it.

A barcode or QR code can remain available as a fallback for locations without compatible NFC hardware.

This provides a flexible rollout:

• NFC at compatible locations
• Barcode or QR at other locations
• Apple Wallet for iPhone
• Google Wallet for Android
• One customer identity across the journey

NFC compatibility should be confirmed against the selected Square hardware and implementation before it is included in scope.

Step 1: Decide what Square will control

Start by defining Square’s responsibilities.

Square will normally remain responsible for:

• Customer records
• Transactions
• Orders
• Products
• Loyalty accounts
• Point accrual
• Reward creation
• Reward redemption
• Discounts
• Appointments, where applicable

Litecard will normally be responsible for:

• Pass creation
• Apple Wallet and Google Wallet delivery
• Wallet design
• Pass installation tracking
• Dynamic pass updates
• Wallet notifications
• Location configuration
• Wallet links and QR codes
• CRM and CDP connectivity
• Customer wallet journeys

This prevents conflicting calculations or duplicate loyalty records.

Step 2: Connect the Square account

A production integration normally uses Square OAuth so the merchant can authorise Litecard without sharing passwords.

The required permissions depend on the implementation, but may include access to:

• Customers
• Customer custom attributes
• Loyalty
• Orders
• Payments
• Locations
• Bookings
• Webhooks

Only request permissions required for the approved use case.

Square’s OAuth permissions reference lists the available scopes.

Step 3: Select the customer identifier

Every Litecard customer must map to the correct Square customer.

A typical record might contain:

{

  “squareMerchantId”: “MERCHANT_ID”,

  “squareCustomerId”: “CUSTOMER_ID”,

  “squareLoyaltyAccountId”: “LOYALTY_ACCOUNT_ID”,

  “litecardId”: “LITECARD_ID”,

  “email”: “jane@example.com”

}

The Square Customer ID should normally be the primary mapping key.

Email addresses and phone numbers can change or appear on duplicate records. They should not be the only method used to maintain the connection.

Step 4: Create the wallet-pass design

Create the Apple Wallet and Google Wallet templates inside Litecard.

Configure:

• Logo
• Brand colours
• Pass type
• Hero or strip imagery
• Customer fields
• Loyalty fields
• Barcode or QR code
• NFC configuration, where applicable
• Back-of-pass links
• Locations
• Terms and conditions
• Expiry behaviour
• Notification rules

Litecard can support multiple templates for:

• Standard members
• VIP members
• Different loyalty tiers
• Paid memberships
• Treatment packages
• Class packs
• Coupons
• Birthday rewards
• Referral offers
• Seasonal campaigns

The Litecard pass-design guide explains the layout differences between Apple Wallet and Google Wallet.

Step 5: Create the customer’s unique wallet links

Litecard generates individual wallet links for each customer:

apple_link

google_link

qrCode

litecardID

These can be stored as custom attributes against the Square customer profile or sent directly to the CRM.

Example custom attributes:

litecard_apple_link

litecard_google_link

litecard_qr_url

litecard_id

litecard_download_status

Square’s Customer Custom Attributes API allows applications to add integration-specific fields to customer profiles.

Use signed, unguessable wallet URLs. A raw Square Customer ID should not act as the credential that gives someone access to a personalised pass.

Step 6: Distribute the pass

Litecard provides more distribution flexibility than relying on a point-of-sale prompt alone.

For desktop email recipients, include:

• Add to Apple Wallet button
• Save to Google Wallet button
• Unique QR code to continue on mobile

Step 7: Connect Litecard with Klaviyo, Mailchimp or another CRM

Square is excellent at recording purchases. A CRM or CDP is normally better suited to customer segmentation and lifecycle communications.

Litecard can connect wallet engagement with:

• Klaviyo
• Mailchimp
• Dotdigital
• Bloomreach
• Braze
• Insider
• Microsoft Dynamics 365
• Other CRMs and CDPs with suitable APIs or webhooks

A typical flow is:

1. Square creates or updates the customer.
2. The customer is synced to the CRM.
3. The CRM calls Litecard.
4. Litecard creates the pass.
5. Litecard returns the unique wallet URLs.
6. The URLs are stored as profile attributes.
7. The CRM sends the wallet email or SMS.
8. Litecard reports whether the pass was installed.
9. Future campaigns can exclude or target passholders.

For example, Klaviyo might store:

{{ person.apple_link }}

{{ person.google_link }}

{{ person.qrCode }}

{{ person.litecardID }}

{{ person.DOWNLOAD_ACTIVE }}

Read the Litecard Klaviyo wallet guide or Mailchimp wallet-pass guide.

Step 8: Use Square events to update the pass

Square webhooks provide real-time notifications when supported objects change.

Relevant events may include:

Square documents changes to loyalty balances through events such as loyalty.account.updated and loyalty.event.created: Square loyalty webhook events.

Webhook processing should be idempotent. Receiving an event twice must not duplicate points, rewards, customers or passes.

Step 9: Configure wallet notifications

Pass creation is only the first step.

The revenue opportunity comes from using Square activity to send useful wallet messages at the right moment.

Loyalty-event notifications #

Examples:

• “You’ve unlocked a new reward.”
• “Only 50 points until your next reward.”
• “Your $10 reward is ready to use.”
• “Your reward expires this weekend.”
• “You’ve reached Gold status.”
• “One more visit unlocks your next treatment.”

Purchase-triggered notifications #

Examples:

• Thank-you and next-purchase offer
• Product replenishment reminder
• Cross-sell recommendation
• Bounce-back voucher
• Membership upgrade
• Next-appointment prompt

Lifecycle notifications #

Examples:

• Member anniversary
• Birthday reward
• Lapsed-customer offer
• Membership renewal
• Package expiry
• Treatment balance running low
• VIP early access

Location-based wallet messages #

A pass can be configured to become relevant when a customer approaches an eligible business location, subject to device settings and wallet-platform behaviour.

Examples:

• “Your reward is available nearby.”
• “Show your member card when you check in.”
• “Visit today and earn double points.”
• “You have one treatment remaining.”

Location messages should be useful and selective. Excessive notifications reduce trust and increase pass removals.

Step 10: Build advanced wallet journeys

Litecard can create different wallet experiences based on customer status.

New customer journey #

1. Customer signs up.
2. Square profile is created.
3. Litecard pass is issued.
4. Welcome email or SMS is sent.
5. The customer installs the pass.
6. First-purchase incentive is displayed.
7. Square records the first transaction.

Reward-unlocked journey #

1. Square updates the loyalty balance.
2. Square webhook notifies Litecard.
3. Litecard updates the pass.
4. The customer receives a wallet notification.
5. The reward appears on the pass.
6. The customer returns to redeem it.
7. Square records the redemption.

Lapsed-customer journey #

1. CRM identifies inactivity.
2. Litecard updates the pass with an offer.
3. The customer receives a wallet notification.
4. The pass links to the nearest location or online checkout.
5. Square records the returning transaction.

Treatment-package journey #

1. Customer purchases five treatments through Square.
2. Litecard creates the treatment pass.
3. The pass initially shows five remaining.
4. Each redeemed treatment updates the balance.
5. The pass sends a reminder when one treatment remains.
6. The customer is prompted to repurchase the package.

Can Litecard work with other point-of-sale systems?

Yes. Litecard is designed as an independent wallet layer rather than a Square-only product.

Depending on the required workflow, Litecard can connect with systems including:

• Square
• Shopify POS
• Lightspeed
• Cegid
• Retail Directions
• Retail Express
• Custom POS systems
• Other systems with APIs, webhooks or compatible identifiers

This is important for businesses with:

• Different POS platforms across countries
• Franchise locations
• Legacy stores
• Temporary locations
• Online and offline systems
• Planned POS migrations

The wallet experience can remain consistent even when the underlying commerce stack changes.

When should you use Square’s native pass?

Square’s native NFC pass may be sufficient when:

• The business uses Square Loyalty exclusively
• Customers predominantly use iPhone
• Standard Square branding and fields are acceptable
• NFC check-in is the main objective
• CRM-driven wallet journeys are not required
• Google Wallet is not required

When should you add Litecard?

Litecard is a stronger fit when:

• Both Apple Wallet and Google Wallet are required
• Barcode or QR identification is needed
• The business wants advanced wallet branding
• Customers need to see tiers, packages or memberships
• Wallet links must be delivered through Klaviyo or Mailchimp
• Signup forms are required
• Wallet notifications need to respond to loyalty events
• Location-based engagement is required
• The business uses multiple POS systems
• The wallet needs to support loyalty, offers and membership journeys
• Pass installation and engagement need to be measured

Recommended architecture

For most businesses, the cleanest setup is:

• Square: Transactions, customers, points and reward redemption
• Litecard: Wallet passes, designs, QR/barcode/NFC and notifications
• CRM/CDP: Segmentation, email, SMS and lifecycle orchestration
• Website/forms: Customer acquisition and enrolment
• POS: Identification, earning and redemption

Each platform performs the job it is strongest at while sharing a consistent customer identifier.

Frequently asked questions

Does Square support Apple Wallet loyalty cards? #

Yes. Square offers an Apple Wallet loyalty pass for eligible iPhone customers and Square Loyalty configurations. Customers can use NFC to check in and interact with their loyalty account on compatible Square hardware.

Does Square support Google Wallet loyalty cards? #

Square’s published loyalty-pass documentation currently describes the native feature as iOS-only. Litecard can provide personalised Google Wallet passes connected to Square customer and loyalty data.

Can Square scan a Litecard Apple Wallet or Google Wallet pass? #

Yes, through a configured integration. Litecard can encode a Square Customer ID or secure mapped identifier into a barcode or QR code. The integration then identifies the Square customer and performs the approved checkout or loyalty action.

Does Litecard replace Square Loyalty? #

No. Square Loyalty can remain responsible for points, rewards and redemption. Litecard presents that information through advanced Apple Wallet and Google Wallet passes.

Can Litecard show Square Loyalty points? #

Yes. Square’s Loyalty API and webhooks can provide account balances and balance-changing events. Litecard can use this data to update the customer’s pass.

Can Litecard send notifications when a Square reward is earned? #

Yes. A Square loyalty event can trigger a pass update and a relevant Litecard wallet notification.

Can Litecard connect Square with Klaviyo or Mailchimp? #

Yes. Litecard can generate unique wallet links and store them as customer properties in Klaviyo, Mailchimp or another connected CRM.

Do customers need to download an app? #

No. Customers save the pass directly into Apple Wallet or Google Wallet.

Is NFC better than QR codes and barcodes? #

Not universally. NFC offers a fast tap experience, while QR codes and barcodes provide broader device and hardware compatibility. Many businesses use NFC with QR or barcode fallback.

Can Litecard work if the business changes POS providers? #

Yes. Litecard is an independent wallet layer and can be connected to multiple point-of-sale, CRM, loyalty and commerce systems.

Conclusion

Square and Litecard are strongest when each platform performs a clearly defined role.

Square provides the transactional foundation: payments, customers, purchases, loyalty points and reward redemption.

Litecard turns that data into a configurable Apple Wallet and Google Wallet channel with:

• NFC, barcode and QR-code identification
• Advanced pass designs
• CRM and CDP distribution
• Signup forms
• Dynamic content
• Loyalty-triggered notifications
• Location-based engagement
• Multi-POS flexibility

The result is more than a digital loyalty card. It is a connected customer journey that begins at signup, continues through the wallet and returns to Square at checkout.