Overview

Connectors are integration accelerators that help connect The Wallet Crew with existing customer systems — CRM, POS, marketing automation, ticketing, e-commerce, and hardware. They are not plug-and-play solutions. Each customer has specific data models, business rules, and operational processes that shape how the integration is designed and deployed.

A connector can include built-in sync logic, configuration tooling, file exchange support, documentation, and integration guidelines. The customer's system remains the source of truth — TWC does not own or duplicate business data. It reads from source systems, transforms data into wallet-compatible content, and feeds wallet analytics back into the customer's ecosystem.

If your software is not listed

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
Your integration mostly needs runtime behavior (data fill hooks, install/uninstall hooks, script email delivery)	Start with Custom connector and continue in Developer custom connectors guide

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.

CRM, loyalty, and ticketing connectors

CRM & fidelity

Connect CRM and loyalty systems to Apple Wallet and Google Wallet passes.

Custom connector

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

E-commerce

Connect storefront journeys to wallet pass distribution and in-store usage.

Email provider

Configure how The Wallet Crew sends transactional wallet emails.

Hardware

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

Marketing automation

Connect lifecycle campaigns and wallet pass updates in existing tools.

POS

Connect point-of-sale systems to wallet passes for identification and redemption.

Ticketing

Distribute and update event tickets in Apple Wallet and Google Wallet.