> 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/guides-enrolment/enrolment/via-email.md).

# Via email

Deliver Apple Wallet and Google Wallet passes by email using signed or token-based links that keep personal data out of the URL.

Email is the simplest way to reach existing customers and get them into Apple Wallet or Google Wallet. It works well for loyalty and membership cards because customers already trust this channel, and the call-to-action can be placed in journeys a brand already runs (welcome, purchase confirmation, service emails).

The key is to keep links secure. A wallet link is a bearer action. Anyone who gets the URL can try to open it. Use signed URLs or tokens, and avoid personal data in query parameters.

<details>

<summary><strong>Real-world examples</strong></summary>

* A retail brand sends “Your loyalty card is ready” after newsletter sign-up.
* A ticketing operator sends a “Save your ticket” email right after purchase.
* A luxury brand sends “Add your client card” after an in-store visit, with consent capture.

</details>

## What is needed before starting

A [pass template](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/how-to-create-a-template.md) and an issuance flow are required, plus a way to identify the customer. In most setups, The Wallet Crew resolves a pass either from an internal `passId` or from an external identifier coming from the brand CRM.

A sender identity that customers trust, and that mailbox providers accept, is also required. Configure this once, including the sending domain setup, then reuse it across all journeys.

{% hint style="info" %}
When sending from a brand-owned domain, set up SPF/DKIM and a DMARC policy. This improves deliverability and reduces phishing risk.
{% endhint %}

## Choose the right email flow

There are two common flows. Pick one based on whether the customer already exists in the brand database.

### Flow A — Customer exists: direct download

Use this when the customer already has a loyalty account (or any stable identifier) and a one-tap install is the goal. The email contains a secure URL that opens The Wallet Crew pass page and lets the customer save the pass.

To prevent ID enumeration, do not expose predictable identifiers like a loyalty number without a signature or token. This follows the same principle as signed Add to Wallet links described in [Wallet card security](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/wallet-card-security.md).

**Example: signed direct-download link (HMAC)**

For customers who already exist in the CRM, and who can safely be referenced with an internal identifier, a link can resolve directly to their pass.

Example:

`https://app.thewalletcrew.io/{tenantId}/pass?id.y2.customerId={customerId}&id.y2.customerId.hmac={hmac256(customerId,tenantSecret)}`

`pass` is the slug of the download page that opens; replace it with the slug configured for the tenant (see [Download pages](https://docs.thewalletcrew.io/guides-enrolment/enrolment/download-pages.md)). Sign the identifier as described in [Download pages](https://docs.thewalletcrew.io/guides-enrolment/enrolment/download-pages.md#build-a-delivery-url) and keep the tenant secret server-side.

### Flow B — Customer does not exist: enrolment first

Use this when the email list is larger than the loyalty base, or when missing data or consent must be collected before issuing a pass. The link sends the customer to an enrolment form, then The Wallet Crew issues the pass at the end of the form journey.

Start here: [Enrolment form](https://docs.thewalletcrew.io/guides-enrolment/enrolment/enrolment-form.md).

**Example: customer not in the CRM (pre-fill form)**

If the customer is not in the CRM yet, the enrolment flow can capture missing data and then push it to the CRM. Some brands choose to pre-fill the form using query parameters from their email campaign tool.

Example (not recommended):

`https://app.thewalletcrew.io/{tenantId}/mobile?email=jane.doe@example.com&firstName=Jane&lastName=DOE`

{% hint style="danger" %}
This URL is **not signed**. Anyone can edit the query parameters. Avoid this setup in production.
{% endhint %}

**Recommended: token-based enrolment link (no PII in the URL)**

Use a token to secure the link. This avoids exposing personal data in the URL and reduces tampering risk.

Example:

`https://app.thewalletcrew.io/{tenantId}/mobile?neo.authToken={neostore-JWT}`

The prefix `neostore` is the platform's former name and is kept in technical identifiers. `mobile` is the slug of the download page or form layout that opens; replace it with the slug configured for the tenant.

**How to include The Wallet Crew links in an emailing tool**

One of The Wallet Crew’s marketing connectors listed below can be used, or the brand’s own platform.

{% stepper %}
{% step %}

#### Generate the token

Generate the token with The Wallet Crew API, or generate it manually in the admin console (**Settings → Access control → Token generator**).

In the Token generator, set the **Claim type** (for example `email`, or `https://neostore.cloud/customer/identifiers:id.y2.customerId` for a customer ID), enter the **Values** and select **Generate**. For a customer identifier, the claim type is `https://neostore.cloud/customer/identifiers:` followed by the identifier key, the same key as in the direct-download link above.

Use a stable input (typically a customer ID or an email), then keep the token opaque in the campaign tool.
{% endstep %}

{% step %}

#### Store the token in the audience

Store the token in the emailing database as a custom attribute, so it can be merged into the CTA URL.
{% endstep %}

{% step %}

#### Build the CTA URL

Use a button like “Add to Wallet” and point it to a tokenized URL:

`https://app.thewalletcrew.io/{tenantId}/mobile?neo.authToken={{profile.neostoreJwt}}`

Replace `{{profile.neostoreJwt}}` with the tool’s merge tag syntax.
{% endstep %}
{% endstepper %}

## Add the CTA to the emails

In practice, the link sits behind a button such as “Add to Wallet”. This can be done in the marketing tool (campaign templates) or in transactional emails sent by The Wallet Crew.

### CTA examples

<figure><img src="https://831874859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlFokgwgJiwLXu7G8MVSJ%2Fuploads%2FQs7AjOSvyumn1S5ZXskt%2Fenroll-readme-email-cta-example-add-wallet-button-inside.png?alt=media&#x26;token=d372e061-6216-43bc-9cea-f85a47b38cbb" alt="Branded email containing an Add to Wallet button"><figcaption><p>Check that the button is high-contrast and sits above the fold on mobile.</p></figcaption></figure>

<figure><img src="https://831874859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlFokgwgJiwLXu7G8MVSJ%2Fuploads%2FGue4JCXqcuzWJRBeNTKB%2Fenroll-readme-email-cta-example-add-wallet-link-presented.png?alt=media&#x26;token=d4674e8e-0530-4a21-934c-99c3d0f04b16" alt="Email presenting the Add to Wallet action as a secondary link"><figcaption><p>When several CTAs are present, check that the wallet CTA stays visually distinct.</p></figcaption></figure>

## Keep links secure (recommended rules)

Signed links and tokens prevent tampering and reduce pass enumeration risk. They also keep personal data out of URLs that can be logged by proxies, mailbox scanners, or analytics tools.

Use these rules:

* Prefer an **opaque identifier** (`passId`) whenever possible.
* Keep token lifetimes short for email campaigns, and treat the link as a password. See [Download pages](https://docs.thewalletcrew.io/guides-enrolment/enrolment/download-pages.md#build-a-delivery-url).
* Assume emails can be forwarded. If forwarding must not work, add an email challenge or another verification step in the journey.

[Download pages](https://docs.thewalletcrew.io/guides-enrolment/enrolment/download-pages.md#build-a-delivery-url) gives the URL syntax. [Wallet card security](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/wallet-card-security.md) gives the security options. For broader organizational controls, see the [Security insurance plan](https://docs.thewalletcrew.io/policies/privacy-and-security/security-insurance-plan.md).

## Segment sends and measure adoption

Email works best when customers who already installed the pass are excluded. Segment on “pass installed” status whenever possible, then only target customers who are still not installed.

If install status must be synced back into the CRM, use the installation status events (`Pass:Installed` and `Pass:Uninstalled`) described in [Send wallet events to your tools](https://docs.thewalletcrew.io/guides-monitoring/monitor/send-wallet-events-to-your-tools.md).

Installs can also be tagged for attribution. For distribution via web pages, see how tagging works with `neo.src` in [Download pages](https://docs.thewalletcrew.io/guides-enrolment/enrolment/download-pages.md#add-campaign-tracking).

## Supported tools and connectors

Emails can be sent from a brand's own email platform, with The Wallet Crew links embedded in the templates. The Wallet Crew can also send the transactional emails of enrolment and verification journeys (registration, verification, pass delivery). In that case, start with [Email provider](https://docs.thewalletcrew.io/connectors/email-provider.md).

**Transactional email connectors (The Wallet Crew sends):**

* [SendGrid](https://docs.thewalletcrew.io/connectors/email-provider/sendgrid.md)
* [Mailchimp](https://docs.thewalletcrew.io/connectors/email-provider/mailchimp.md) (Transactional / Mandrill)
* [Salesforce Marketing Cloud](https://docs.thewalletcrew.io/connectors/email-provider/salesforce-marketing-cloud.md)
* [Adobe Marketing Cloud](https://docs.thewalletcrew.io/connectors/email-provider/adobe-marketing-cloud.md)

**Marketing automation connectors (the brand sends and embeds the links):** these integrations typically orchestrate journeys and personalization. The brand keeps full control of deliverability and campaign performance, and places The Wallet Crew links behind its own calls to action.

* [Actito](https://docs.thewalletcrew.io/connectors/marketing-automation/actito.md)
* [Adobe Campaign Classic](https://docs.thewalletcrew.io/connectors/marketing-automation/adobe-campaign.md)
* [Batch.com](https://docs.thewalletcrew.io/connectors/marketing-automation/batch.com.md)
* [Bloomreach](https://docs.thewalletcrew.io/connectors/marketing-automation/bloomreach.md)
* [Brevo](https://docs.thewalletcrew.io/connectors/marketing-automation/brevo.md)
* [Klaviyo](https://docs.thewalletcrew.io/connectors/marketing-automation/klaviyo.md)
* [Salesforce Marketing Cloud](https://docs.thewalletcrew.io/connectors/marketing-automation/salesforce-marketing-cloud.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thewalletcrew.io/guides-enrolment/enrolment/via-email.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
