Email provider
Choose how The Wallet Crew sends transactional emails (SendGrid, connectors, or custom gateway) and secure your sender identity (SPF/DKIM/DMARC).
The Wallet Crew can send transactional emails as part of your customer journey. These emails are sent on behalf of your Brand, so customers recognize the sender and trust the message.
This matters for conversion and security. A branded, authenticated sender reduces phishing risk. It also increases confidence when customers click an “Add to Wallet” link.
What emails The Wallet Crew can send
Email sending depends on the journey you enable. Common examples include pass distribution and enrolment flows.
A link to download a customer loyalty card in Apple & Google Wallet.
A registration email when a customer enrols through a form.
A challenge email to authenticate a customer (verification code or link).
A confirmation email after registration or verification.
Why you should configure the sender identity
When your emails use a sender identity that matches your 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.
If you want customers to see [email protected] (or [email protected]), plan SPF/DKIM and a DMARC policy. This is what mailbox providers use to validate the sender.
Choose your email provider strategy
The Wallet Crew uses SendGrid by default. You can keep this default, switch to another supported provider, or plug your own gateway.
Default: SendGrid
This is the fastest option. It covers most use cases. See the dedicated page for exact parameters and supported modes: SendGrid.
SendGrid is included in The Wallet Crew license, as long as your usage stays within fair use. If you expect high volumes, confirm the limits with The Wallet Crew.
Even if you keep The Wallet Crew SendGrid account, you can still enable a custom sending domain to match your Brand. The security side (SPF/DKIM/DMARC setup) is covered here: Configuring Custom Domain.
Built-in connectors
Use this when your Brand already has a provider, templates, reporting, or compliance processes in place.
Supported built-in connectors:
Custom connector
Use this when you need a provider that is not supported by built-in connectors, when you must route through an internal mail relay, or when you want to fully control sending from your backend.
The Wallet Crew still renders the email content. Your implementation is responsible for the final “send” call and its delivery lifecycle.
Where the configuration lives
The active email provider is selected in /server/emails.yml in the advanced configuration. Each connector page tells you exactly what values to set for its provider type.
FAQ
Are these marketing emails?
No. These are transactional emails tied to a customer journey, like pass download links or verification messages.
If you want marketing campaigns, use your marketing tools. Then embed The Wallet Crew links in their templates.
Can The Wallet Crew send from our domain?
Yes, as long as the sender domain is properly authenticated. For SendGrid, this typically means configuring SPF/DKIM and a DMARC policy for the domain (or subdomain) you use as the sender.
Last updated