Businesses using Mindbody can connect Litecard to automatically create personalised membership cards for Apple Wallet and Google Wallet.
Each customer receives a unique wallet pass containing their membership information, rewards, available visits, offers and a scannable customer ID. Passes can be delivered through welcome emails, SMS, booking confirmations, membership-purchase messages or an in-clinic QR code.
Does Mindbody support Apple Wallet and Google Wallet membership cards?
Mindbody supports Apple Pay and Google Pay for payments. It also provides a digital membership barcode inside some Mindbody-branded mobile apps.
However, these are different from a native Apple Wallet or Google Wallet membership pass.
Based on Mindbody’s publicly available product documentation, Mindbody does not currently provide a built-in feature that automatically exports each customer’s membership card to Apple Wallet or Google Wallet.

Litecard provides this missing wallet layer while Mindbody remains the primary system for bookings, customers, memberships and transactions.
| Capability | Mindbody | Mindbody with Litecard |
| Store customer profiles | Yes | Yes |
| Manage bookings and memberships | Yes | Yes |
| Membership barcode inside an app | Available on some plans | Yes |
| Apple Wallet membership card | Not natively documented | Yes |
| Google Wallet membership card | Not natively documented | Yes |
| No app required | No | Yes |
| Dynamic rewards and membership information | Inside Mindbody | Inside the wallet |
| Wallet notifications | No | Yes |
| Location-based wallet messages | No | Yes |
How the Mindbody and Litecard integration works
Mindbody remains the customer, booking and membership system. Litecard uses Mindbody’s APIs and webhooks to create and update the wallet pass.
- A customer registers, books or purchases a membership in Mindbody.
- Mindbody sends the relevant event to Litecard.
- Litecard identifies or creates the customer.
- Litecard generates unique Apple Wallet, Google Wallet and QR-code links.
- The links can be written back to the Mindbody customer profile.
- The customer receives their pass by email, SMS or on-screen confirmation.
- Future Mindbody activity automatically updates the pass.
Mindbody provides a Public API and a Webhooks API for approved integrations.
What can appear on the wallet pass?
The pass design can be adapted to the business and membership program.
Common fields include:
- Customer name
- Mindbody customer or membership ID
- Membership type
- Membership status
- Expiry or renewal date
- Available visits or class credits
- Loyalty points
- Current rewards
- Available offers
- Preferred location
- Scannable barcode or QR code
- Booking and account links
The pass can also contain buttons linking back to:
- Book an appointment
- View available classes
- Purchase another package
- Manage a membership
- Refer a friend
- Contact the business
- View current offers
Step 1: Connect the Mindbody business to Litecard
The business must authorise Litecard to access its Mindbody site.
The implementation requires:
- A Mindbody Site ID
- An approved Mindbody developer application
- A Mindbody API key
- Appropriate API authentication
- A Litecard account and wallet-pass template
- A secure webhook endpoint
API credentials must remain on the server. They should never be placed inside a customer-facing website, mobile application or wallet pass.
Start through the Mindbody Developer Portal.
Step 2: Create the wallet-pass template
Create the Apple Wallet and Google Wallet design in Litecard.
Configure:
- Business name and logo
- Brand colours
- Membership labels
- Barcode or QR-code format
- Front-of-pass information
- Back-of-pass links and terms
- Location settings
- Pass-expiry behaviour
- Notification rules
The Apple and Google versions should use the same customer record, even though the underlying wallet formats are different.
Step 3: Choose the Mindbody customer identifier
Every Litecard member must be mapped to the correct Mindbody customer.
A typical mapping includes:
{
“mindbodySiteId”: “12345”,
“mindbodyClientId”: “1000281”,
“mindbodyUniqueClientId”: “8439201”,
“litecardMemberId”: “lc_82bfa38”,
“walletToken”: “secure-random-token”
}
The combination of the Mindbody Site ID and customer identifier should be unique.
Do not use an email address as the only identifier. Emails can change, be shared or exist against duplicate profiles.
Step 4: Subscribe to Mindbody webhooks
The most useful Mindbody webhook events include:
| Mindbody event | Litecard action |
| client.created | Create the Litecard customer |
| client.updated | Update customer details |
| clientMembershipAssignment.created | Activate or change the wallet membership |
| clientMembershipAssignment.cancelled | Expire or deactivate the pass |
| clientContract.created | Add contract and renewal information |
| clientContract.updated | Update status or expiry |
| clientContract.cancelled | Remove or expire membership access |
| clientSale.created | Update rewards, spend or purchased packages |
| appointmentBooking.created | Add the upcoming booking |
| appointmentBooking.updated | Update booking information |
| appointmentBooking.cancelled | Remove the cancelled booking |
| clientProfileMerger.created | Consolidate duplicate customers |
Mindbody recommends processing webhook events idempotently. This means the same event can be received twice without creating duplicate customers or passes.
Litecard should also return a successful response quickly and process the event asynchronously. Mindbody retries webhook delivery when it does not receive a successful response within its documented timeframe.
Step 5: Generate three unique customer links
Litecard creates three unique URLs for every customer:
Apple Wallet:
https://wallet.litecard.com/apple/{signed-token}
Google Wallet:
https://wallet.litecard.com/google/{signed-token}
QR-code image:
https://wallet.litecard.com/qr/{signed-token}.png
The QR code should normally encode a universal wallet landing page:
https://wallet.litecard.com/member/{signed-token}
That page detects the device and displays the appropriate option:
- iPhone: Add to Apple Wallet
- Android: Save to Google Wallet
- Desktop: display both buttons and a scannable QR code
All links must use signed, unguessable tokens. A raw Mindbody Client ID should not act as the credential that grants access to a wallet pass.
Step 6: Save the links against the Mindbody customer
Create text-based custom fields inside Mindbody:
- Open Settings.
- Navigate to Clients.
- Select Client Profile Custom Fields.
- Create:
- Litecard Apple Wallet URL
- Litecard Google Wallet URL
- Litecard QR Code URL
- Litecard Member ID
Mindbody explains custom-field setup in its client custom fields guide.
Litecard can use Mindbody’s UpdateClient endpoint to write these values back to the customer profile.
Conceptually, the update contains:
{
“Client”: {
“Id”: “1000281”,
“CustomClientFields”: [
{
“Name”: “Litecard Apple Wallet URL”,
“Value”: “https://wallet.litecard.com/apple/secure-token”
},
{
“Name”: “Litecard Google Wallet URL”,
“Value”: “https://wallet.litecard.com/google/secure-token”
},
{
“Name”: “Litecard QR Code URL”,
“Value”: “https://wallet.litecard.com/qr/secure-token.png”
}
]
}
}
The final request must use the field IDs and request schema returned for that Mindbody site.
Step 7: Deliver the pass to the customer
The best delivery moment depends on the program.
| Placement | Best use |
| New-client welcome email | Give every new customer a wallet card |
| Membership-purchase email | Issue passes only to active members |
| Welcome SMS | Mobile-first pass installation |
| Booking confirmation | Encourage adoption before arrival |
| Transaction receipt | Reach customers immediately after purchase |
| Customer account page | Permanent self-service access |
| Reception QR code | Convert existing or walk-in customers |
| Renewal email | Update or reactivate expiring members |
| Staff-assisted enrolment | Add the pass during checkout |
Recommended welcome email #
Subject: Your membership is ready for your phone
Hi First name,
Your membership card is ready. Add it to your phone for easier check-in and quick access to your membership, rewards and offers.
Add to Apple Wallet
Save to Google Wallet
Opening this email on a computer? Scan the QR code below using your phone.
The finished product may look something like this:

Recommended welcome SMS #
Welcome to [Business]. Your digital membership card is ready: [unique wallet link]
SMS should use the universal Litecard link rather than sending separate Apple and Google URLs.
Can the links be inserted into Mindbody’s welcome email?
Mindbody supports replacement phrases such as <CLIENTID> in several automated emails, including its New Client/Welcome Email. Mindbody lists the available fields in its client-management replacement phrase documentation.
However, arbitrary custom client fields are not shown as supported replacement phrases in the published documentation.
There are three implementation options.
Option 1: Litecard or a connected platform sends the message #
This is the recommended option.
Litecard generates the signed wallet URLs and passes them to the connected email or SMS platform. Each button and QR image can therefore use the customer’s unique URL directly.
Option 2: Sync the links into the marketing platform #
The URLs can be saved as customer attributes in platforms such as Klaviyo, Attentive, Dotdigital, Bloomreach or Insider.
Example attributes:
litecard_wallet_url
litecard_apple_wallet_url
litecard_google_wallet_url
litecard_qr_code_url
These values can then be inserted into buttons and images using that platform’s normal personalisation syntax.
Option 3: Use Mindbody’s Client ID in a secure claim link #
A native Mindbody email can link to:
The customer must then verify their email address or mobile number before Litecard reveals the wallet pass.
The pass should never be issued solely because someone supplied a valid Mindbody Client ID. Public customer IDs may be predictable.

Using the wallet pass for Mindbody check-in
The wallet pass can contain a barcode or QR code linked to the Mindbody customer.
There are two approaches.
Existing Mindbody customer barcode #
Encode the same customer identifier accepted by the business’s existing Mindbody check-in process.
This provides the lightest implementation, but the exact barcode format must be tested against the business’s scanner and Mindbody configuration.
Litecard secure identifier #
Encode a secure Litecard member token. When staff scan it, Litecard resolves the token to the correct Mindbody customer and performs the required lookup or attendance action.
This provides more control, security and analytics, but requires a connected Litecard scanning workflow.
Never assume the barcode will work at reception without testing:
- Barcode format
- Scanner compatibility
- Screen brightness
- Mindbody lookup behaviour
- Duplicate customer profiles
- Location-specific memberships
- Expired memberships
- Offline or slow connections
Updating the wallet pass automatically
A wallet pass should not become a static image of the membership card.
It can update whenever Mindbody data changes.
Examples include:
- A new membership is purchased
- Membership status changes
- Contract expiry is extended
- A class credit is used
- A new reward becomes available
- A customer reaches a new tier
- An appointment is booked or cancelled
- A package is nearly exhausted
- A membership is suspended
- A customer’s preferred location changes
This gives customers useful information without asking them to open Mindbody or download another branded application.
What should appear on the front of the pass?
Keep the front simple.
A strong structure is:
NAME
Jane Citizen
MEMBERSHIP
Glow Member
REWARDS
1 available
VISITS
4 remaining
Place secondary information on the back of the pass:
- Book now
- View rewards
- Membership terms
- Contact details
- Location information
- Privacy policy
- Help and support
Recommended implementation strategy
Phase 1: MySkin Clinics pilot #
- Connect one Mindbody site
- Create passes for a controlled customer group
- Add Apple, Google and QR links to each profile
- Deliver through one welcome journey
- Test reception scanning
- Measure downloads, removals and repeat visits
Phase 2: Full rollout #
- Backfill existing eligible customers
- Add all locations
- Automate membership and contract updates
- Add rewards and offer discovery
- Introduce lifecycle wallet messaging
- Connect reporting to the CRM or customer-data platform
Phase 3: Litecard for Mindbody application #
- One-click Mindbody business authorisation
- Automated webhook subscription
- Self-service pass design
- Custom-field provisioning
- Existing-customer backfill
- Configurable membership mappings
- Email and SMS integrations
- Download and engagement reporting
- Mindbody Partner Store submission
Why connect Mindbody with Apple Wallet and Google Wallet?
Faster customer identification #
The membership card is available from the customer’s phone without searching for an email, opening an app or remembering a password.
Better membership visibility #
Customers can see their membership, visits, rewards and current offers in a place they already use.
Higher app-independent reach #
A customer does not need to install or regularly use a separate branded application.
Easier reward discovery #
Available rewards and offers can be displayed directly on the wallet pass instead of remaining hidden inside an account.
Real-time updates #
Membership status, balances, rewards and renewal information can change without issuing a new card.
A new owned communication channel #
Apple Wallet and Google Wallet provide a direct customer touchpoint that complements email, SMS, Mindbody and branded applications.
Frequently asked questions
Does Mindbody have an Apple Wallet membership card? #
Mindbody supports Apple Pay for payments and provides an in-app digital membership barcode in some branded-app configurations. Its public documentation does not currently show a native feature that exports personalised customer membership cards to Apple Wallet. Litecard adds this capability through Mindbody APIs and webhooks.
Can Mindbody membership cards be added to Google Wallet? #
Not directly through a documented native Mindbody membership-pass feature. Litecard can create a personalised Google Wallet pass using customer and membership data from Mindbody.
Can a Mindbody barcode work from Apple Wallet? #
Potentially. The wallet pass must encode the identifier and barcode format expected by the business’s Mindbody check-in configuration. Scanner compatibility and customer lookup should be tested before rollout.
Can every Mindbody customer receive a different wallet link? #
Yes. Litecard generates signed Apple Wallet, Google Wallet and QR-code URLs for each customer. These can be stored against the Mindbody profile and distributed through personalised communications.
Can the wallet pass show visits or class credits? #
Yes, provided the relevant information is available through Mindbody and mapped into Litecard. The pass can update when credits are purchased, redeemed or expire.
Can existing Mindbody customers receive passes? #
Yes. Existing customers can be imported through an API backfill or controlled batch process. Litecard should match customers using stable Mindbody identifiers to prevent duplicates.
Does Litecard replace Mindbody? #
No. Mindbody remains the booking, membership and customer-management platform. Litecard extends it into Apple Wallet and Google Wallet.
Do customers need to download another app? #
No. The membership pass is saved directly into Apple Wallet or Google Wallet.
Conclusion
Connecting Mindbody with Litecard gives fitness, wellness, beauty and clinic businesses a practical way to place membership cards, rewards and customer identification into Apple Wallet and Google Wallet.
Mindbody continues managing customers, memberships, bookings and transactions. Litecard creates the wallet experience, maintains the unique customer links and updates each pass when relevant customer information changes.
The strongest starting point is a controlled pilot: create passes for new members, distribute them through the welcome journey and validate check-in before expanding to the full customer base.