> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/connectors/wallet-pass-connectors.md). # Wallet pass connectors Explore The Wallet Crew connectors for CRM, loyalty, ticketing, e-commerce, POS, and marketing platforms that create, update, and distribute Apple Wallet and Google Wallet passes. Wallet pass connectors link existing business systems to Apple Wallet and Google Wallet passes managed by The Wallet Crew. They support CRM, loyalty, ticketing, e-commerce, point-of-sale, marketing automation, email, and hardware integrations. Connectors are integration accelerators, not plug-and-play solutions. Each integration reflects its data model, business rules, and operating processes. A connector can include sync logic, configuration tooling, file exchange support, and implementation guidance. The brand or partner system remains the source of truth for business data. The Wallet Crew does not replace or duplicate it. The platform transforms source data into wallet-compatible content and can send wallet analytics back to connected systems. ### What a wallet pass connector provides * Create and update Apple Wallet and Google Wallet pass content from source data. * Deliver wallet lifecycle events and analytics to connected business systems. * Support standard connectors or custom integrations for private APIs and workflows. ## Integrate software without a listed connector You can still integrate with The Wallet Crew even when no native connector exists. Use this sequence: 1. Start from the integration model and identify where your source data lives. 2. Decide whether a built-in connector is enough or a custom connector is needed. 3. Implement runtime scripting only for the parts that are truly specific to your stack. ### Main integration model The integration model stays the same for all projects: 1. Your system remains the source of truth for business data. 2. TWC stores identifiers and wallet-facing operational data. 3. TWC reads and transforms source data into Apple Wallet and Google Wallet payloads. 4. Wallet lifecycle events and analytics can be pushed back to your systems. This model avoids data duplication while keeping wallet experiences up to date. ### Choose your integration path | Situation | Recommended path | | ---------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- | | Your software already has a documented connector | Use the connector page in this section | | Your software has no connector, but your APIs and events are available | Use [Custom connector](/connectors/custom-connector.md) | | Your integration mostly needs runtime behavior (data fill hooks, install/uninstall hooks, script email delivery) | Start with [Custom connector](/connectors/custom-connector.md). | ### Responsibilities | Responsibility area | Customer / partner system | The Wallet Crew | | ------------------------------ | ------------------------------------------------ | ------------------------------------------------ | | Business data ownership | Owns CRM/POS/ticketing/e-commerce records | Does not replace source systems | | Identifier strategy | Defines stable identifiers shared across systems | Uses identifiers to resolve and update pass data | | Wallet payload generation | Provides source fields and business rules | Maps data to Apple/Google wallet formats | | Pass delivery and updates | Triggers source events and change inputs | Orchestrates wallet updates and pass lifecycle | | Optional integration scripting | Implements project-specific API/event logic | Provides runtime hooks and execution context | The cards below cover each connector family. ## Wallet pass connector categories
Cover image

CRM & fidelity

Connect CRM and loyalty systems to Apple Wallet and Google Wallet passes.01-crm-fidelity.pngCRM & loyalty

Custom connector

Build a custom integration when a ready-to-use connector is not available.02-custom-connector.pngCustom connector

E-commerce

Connect storefront journeys to wallet pass distribution and in-store usage.03-ecommerce.pngE-commerce

Email provider

Configure how The Wallet Crew sends transactional wallet emails.04-email-provider.pngEmail provider

Hardware

Check hardware compatibility for barcode, QR, and NFC wallet validation.05-hardware.pngHardware

Marketing automation

Connect lifecycle campaigns and wallet pass updates in existing tools.06-marketing-automation.pngMarketing automation

POS

Connect point-of-sale systems to wallet passes for identification and redemption.07-pos.pngPoint of Sale (POS)

Ticketing

Distribute and update event tickets in Apple Wallet and Google Wallet.08-ticketing.pngTicketing
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.thewalletcrew.io/connectors/wallet-pass-connectors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.