Enrolment form
Set up an enrolment form to collect customer data, apply rules, and issue Apple Wallet and Google Wallet passes.
An enrolment form is the web page customers use to join a program and save a pass. It is also the key conversion moment where a customer moves from interest to ownership, for example after scanning a QR code, clicking an email link, or tapping a CTA.
In The Wallet Crew, the enrolment form is the “front door” to the Brand’s Apple Wallet and Google Wallet experience. It collects the required data, applies Brand rules, captures required consents, and then issues the pass with the correct “Add to Wallet” experience.
In The Wallet Crew, an enrolment form can work for new customers and returning customers. If a customer is already known, the form can identify them early and avoid asking the same questions again.
Real-world examples
A retail Brand places a QR code at checkout to enrol customers in loyalty.
An event organizer uses a short form to issue a membership pass before presales.
A luxury Brand sends an email link after an in-store visit to create a client profile.
A ticketing solution embeds a form step to capture missing data before issuing a pass.
From acquisition to Wallet
An enrolment form sits between the Brand acquisition channel and the pass template. Customers reach it from a QR code, a website CTA, an email, a mobile app, or a POS flow. The Wallet Crew then creates or updates the wallet pass information and generates the correct “Add to Wallet” experience.
Enrolment performance depends heavily on timing. The same form can be distributed at high-intent moments, such as in-store QR codes, post-purchase emails, mobile app deep links, POS integrations, or clienteling follow-ups.
To get more information about other distribution channels, see:
What the experience looks like
Most enrolment forms are designed to complete in under a minute on mobile. This matters in real life. Many customers enrol while standing in a store, walking, or switching between apps.
Typical flow
The exact screens depend on the configuration, but the logic stays the same.
The customer opens the form from a link or QR code.
The form optionally identifies the customer early (social sign-in or email check-in).
The customer fills the missing fields and accepts consents if needed.
The Wallet Crew creates or updates the customer profile.
The pass is issued and the customer saves it to Apple Wallet or Google Wallet.
“Minimum viable enrolment” usually converts best. Collect only what is needed to issue the pass and comply. Profiles can be enriched later.
Configure for performance
An enrolment form combines UX choices and data rules. The goal is to remove friction without lowering data quality.
Fields, data, and validation
Each additional field increases drop-off risk. Fields should be added only when they drive a clear business outcome. Typical examples are an email address or a phone number.
Validation rules protect data quality. They also reduce support costs later. To get more information about supported rules like required, minLength, maxLength, email, and phone, see Validation rules.
Branding and design
Customers need to trust the page instantly. The form should display the Brand logo and colors. Copy should match the Brand voice. The main CTA should be visible without scrolling.
To get more information about what can be customized (logo, colors, typography, header image, light/dark palette), see Design.
Identify returning customers
If the customer already exists, the best form is the one that does not ask questions again. The Wallet Crew supports two common patterns.
Social sign-in gives a one-tap identification flow on mobile. It reduces typos. It typically reduces duplicates. To get more information, see Social sign-in.
Email check-in adds an email-first step. It lets existing customers be detected early. It can also add a security step if email verification is required. To get more information, see Enable email check-in on enrolment forms.
Identification is not consent. Marketing consent should be collected explicitly and separately.
In-store context with redirects and stores
Many Brands run the same enrolment form across all stores. They still want store-level tracking and personalization. This is where redirects help.
A redirect is a short, managed URL that can add parameters like storeId, language, or campaign source. The resulting QR code can be printed and deployed in-store. See Redirects.
Store data is the reference list behind storeId. It is useful when a store name or address should be displayed in the journey or on the pass. See Stores.
Data quality
Data quality is a primary outcome of enrolment design. It impacts identity resolution, segmentation, personalization, and reporting. It also reduces operational effort later, especially when customer data is synced to a CRM.
High-quality data usually comes from a combination of short forms, clear intent, and strict rules at capture time.
Why enrolment is a data-quality moment
Enrolment happens when intent is high. This is when customers are most likely to provide accurate identifiers. Self-enrolment also helps because customers know how to write their own personal data. Mobile auto-complete reduces typing effort and common typos, especially on names, emails, and phone numbers.
The same moment can create low-quality data when the form is too long or unclear. Drop-off increases, and placeholder entries become more common.
What improves data quality
The strongest lever is collecting less data, but validating it better. Required fields should be limited to true identifiers needed for profile creation and pass issuance. Optional fields should stay optional, with enrichment happening later through engagement.
Validation should be strict and consistent across channels. This is where most duplicates start. To get more information about supported rules like required, minLength, maxLength, email, and phone, see Validation rules.
Identification patterns also improve data quality. Social sign-in reduces typing and tends to reduce duplicates. Email check-in helps detect existing customers early and prevents re-creating profiles for known customers.
Privacy, GDPR & CCPA compliance
Enrolment forms collect personal data. They must be treated as production-grade identity surfaces, with the same rigor as any other identity entry point.
The Wallet Crew is deployed worldwide. Regional requirements vary by market, industry, and use case. The platform supports structured consent capture designed to align with GDPR (European Union), CCPA (California), and similar regional privacy frameworks. The Wallet Crew also offers a DPO service to help brands operationalize privacy requirements and keep consent practices consistent across regions.
Self-enrolment strengthens compliance
Self-enrolment strengthens transparency because customers see exactly what data is collected and why. Consent language is read directly and in context. Information can be provided privately, which is especially important in-store where personal information would otherwise be shared out loud.
Self-enrolment also improves data quality. Mobile auto-complete reduces typing effort and typos. Customers typically enter personal data more accurately than staff-assisted capture, especially for names, emails, and phone numbers.
This reduces ambiguity, strengthens identity resolution, and improves defensibility during audits, while keeping the enrolment experience fast on mobile.
Explicit and unambiguous consent
Marketing consent must remain separate from identification. Consent language should be clear, readable on mobile, and collected as an explicit opt-in. Pre-checked boxes should be avoided. A visible link to the Brand privacy policy should sit next to the consent field.
For wallet notifications and consent patterns, see Consents & GDPR compliance.
Collect less, but collect better
Data minimization improves both compliance and performance. A small set of high-quality identifiers, validated strictly at capture time, is easier to justify legally and easier to use operationally. For practical guidance on improving capture quality, see Data quality.
Why enrolment matters
Enrolment is not only a step before pass issuance. It is where identity, consent, attribution, and store context can be captured while intent is high.
Optimizing this moment typically improves conversion to Wallet, reduces duplicates, and strengthens compliance posture.
FAQ
Is an enrolment form the same thing as a registration form?
Yes, in practice.
In The Wallet Crew docs, both terms are used. “Enrolment form” is the broader term. It covers registration, identification, profile update, and pass issuance in one journey.
Can one form work for both new and returning customers?
Yes.
Social sign-in or email check-in can identify returning customers early. The form can then skip fields already known and focus on the pass installation step.
What is the best channel for enrolment: QR code, email, website, or app?
Pick based on where customers already are.
QR codes work best when the moment happens in store. Email works best when an address already exists. A website or mobile app works best when the customer is already logged in and identity can be resolved without extra steps.
Should we make all fields mandatory to keep data clean?
No.
Too many required fields increase abandonment and often produce fake data. Only true identifiers should be required. They should be validated strictly. The rest can be collected later.
Last updated