> 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/email-provider.md).

# Email provider

Choose how The Wallet Crew sends transactional emails: SendGrid, Mailchimp Transactional, or a script provider such as Salesforce Marketing Cloud or Adobe.

The Wallet Crew can send transactional emails as part of the customer journey. These emails are sent **on behalf of the brand**, so customers recognize the sender and trust the message.

<figure><img src="https://3852727835-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlP7d71aYydav6e0pRkxc%2Fuploads%2Fgit-blob-0288e95d533c76c27523bab13f87a1dca29fedce%2Femail-provider-transactional-email-example.png?alt=media" alt="Example transactional email containing an Add to Wallet link"><figcaption><p>Transactional emails can distribute a pass or support enrolment and verification flows.</p></figcaption></figure>

## What emails The Wallet Crew can send

Email sending depends on the journeys enabled on the tenant. Common examples include pass distribution and enrolment flows.

* A link to download a customer loyalty card in Apple Wallet and Google Wallet.
* A registration email when a customer enrolls through a form.
* A challenge email to authenticate a customer (verification code or link).
* A confirmation email after registration or verification.

## Why the sender identity matters

When emails use a sender identity that matches the brand, customers are less likely to distrust the message. When the sender is properly authenticated (SPF, DKIM, DMARC), mailbox providers are less likely to flag the email as spoofing.

In practice, this improves deliverability and reduces phishing opportunities around “download your pass” links.

{% hint style="info" %}
To let customers see `no-reply@yourbrand.com` (or `no-reply@wallet.yourbrand.com`), plan SPF/DKIM and a DMARC policy. This is what mailbox providers use to validate the sender.
{% endhint %}

## Where the configuration lives

Select the provider in **Settings → General → Email provider**: **SendGrid**, **Mailchimp Transactional** or **Custom**. The page also holds the sender identity, the provider credentials and, for **Custom**, the custom script.

The choice is stored in `/server/emails.yml`, which can also be edited in the advanced configuration (**Settings → Advanced → Advanced configuration**). `provider.type` takes one of three values:

| `provider.type` | Meaning                                                                                  | Use it when                                                                                                                                                                                                  | Page                                                                                                                |
| --------------- | ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------- |
| `sendgrid`      | SendGrid, with the account of The Wallet Crew (default) or the brand's own               | This is the fastest option. It covers most use cases. Default.                                                                                                                                               | [SendGrid](https://docs.thewalletcrew.io/connectors/email-provider/sendgrid.md)                                     |
| `mailchimp`     | Mailchimp Transactional (Mandrill)                                                       | The brand already has a Mailchimp Transactional account, or needs full ownership of deliverability, reputation, and billing.                                                                                 | [Mailchimp](https://docs.thewalletcrew.io/connectors/email-provider/mailchimp.md)                                   |
| `script`        | A tenant script sends the email, for example through Salesforce Marketing Cloud or Adobe | The brand already has another provider, templates, reporting, or compliance processes in place, sending must route through an internal mail relay, or the brand backend should keep full control of sending. | [EmailSender extensibility](https://docs.thewalletcrew.io/connectors/custom-connector/emailsender-extensibility.md) |

A tenant can use only one provider at a time.

The pages below are reference scripts, not provider types: the code is part of the tenant configuration and the brand maintains it.

* [Salesforce Marketing Cloud as email sender](https://docs.thewalletcrew.io/connectors/email-provider/salesforce-marketing-cloud.md)
* [Adobe](https://docs.thewalletcrew.io/connectors/email-provider/adobe-marketing-cloud.md): Adobe Journey Optimizer, Adobe Campaign Classic and Marketo Engage

## Email providers not listed

An unlisted provider does not prevent wallet email delivery: use a script provider. See [Custom connector](https://docs.thewalletcrew.io/connectors/custom-connector.md#faq).

## Decide which sender domain to use

Prefer a dedicated subdomain such as `wallet.yourbrand.com` or `registration.yourbrand.com`. This keeps email authentication isolated from other mail systems. The same choice applies to [SendGrid](https://docs.thewalletcrew.io/connectors/email-provider/sendgrid.md) and [Mailchimp](https://docs.thewalletcrew.io/connectors/email-provider/mailchimp.md).

Delegating a dedicated subdomain reduces the attack surface and isolates pass-related traffic. Using the same custom domain as the app is recommended when it makes sense for the setup.

## FAQ

<details>

<summary><strong>Are these marketing emails?</strong></summary>

No. These are transactional emails tied to a customer journey, like pass download links or verification messages.

For marketing campaigns, use the brand marketing tools, then embed The Wallet Crew links in their templates.

</details>

<details>

<summary><strong>Can SendGrid be kept in staging and Mailchimp in production?</strong></summary>

Yes, but it is not recommended.

Each tenant has its own configuration, so a different provider can be selected per environment. In practice, using different providers makes troubleshooting harder. It also increases the risk of provider-specific differences between staging and production (sender authentication, deliverability behavior, activity logs, and rate limits).

For a safe test environment, prefer the **same provider** in both environments. Use a different sender subdomain (for example `staging.wallet.yourbrand.com`) and send only to internal addresses.

</details>


---

# 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/connectors/email-provider.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.
