> ## Documentation Index > Fetch the complete documentation index at: https://docs.getstell.com/llms.txt > Use this file to discover all available pages before exploring further. # How enrollment works > How customers get their pass through the web or App Clip enrollment flow **Enrollment** is how your customers get their pass: they open an enrollment link, fill in a short form, accept the consents, and the pass lands in their wallet. This page walks through that journey so you and your support staff know exactly what customers see. ## How customers get there | Entry point | How it works | | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------- | | **Link or QR code** | The customer opens your enrollment link in their browser — typically from a QR code in store, your website, or a receipt | | **App Clip** | On iPhone, tapping an App Clip code or NFC tag opens the same flow instantly as a lightweight native experience — no app install | | **Pre-filled link** | Links from your systems can securely pre-fill the customer's details, skipping typing (and sometimes the whole form) | | **Existing-member link** | Customers who already exist in your CRM can get a direct link that just issues their pass | For how to put these entry points in front of customers — emails, social posts, your website, and in-store material — see [promote your program](/promote/overview). ## The customer journey The walkthrough below follows the **Mintleaf Rewards** demo program on an iPhone. Your program shows your own branding, form fields, and consents — the steps stay the same. The customer lands on your program's welcome screen: your header image and branding at the top, a welcome like "Join \[program name]", and a short invitation text. One tap on **Continue** starts the enrollment. The enrollment welcome screen with the Mintleaf Coffee header image, the title Join Mintleaf Rewards, and a Continue button A short form collects the customer's details. Which fields appear — and which are required, marked with an asterisk — depends on your program's configuration: name, email, phone, birth date, address, and so on. Validation happens as the customer types, and the phone field has a country-code picker. Customers arriving through a pre-filled link find these fields already completed. The personal details form with email, phone, first name, and last name fields filled in, and a Continue button When the form is submitted, Stell checks whether the email or phone number matches an existing member. If it does, the customer verifies their identity with a 6-digit code sent by email or SMS, and then goes straight to adding their pass — the consents step is skipped, since they accepted when they first enrolled. New customers skip this step, and programs using Vipps login skip it too — identity is already verified. New members see the consents next. Each consent is a toggle, with required ones labeled — the join button stays inactive until every required consent is given. Below the toggles, a legal note names your company as the consent processor, with links to your terms of use and privacy policy. The consents screen with two toggles, Receive Marketing emails marked required and Receive Marketing SMS optional, legal text, and an inactive Join Mintleaf Rewards button The pass is prepared and the customer is asked to add it: **Add to Apple Wallet** on iPhone, **Add to Google Wallet** on Android. On desktop, the customer picks their wallet. Tapping the badge opens the wallet's own add-pass prompt. The Almost there screen telling the customer their Mintleaf Rewards pass is ready, with an Add to Apple Wallet badge Once the pass is added, the customer sees a confirmation — "Welcome to \[program name]!" — with a short how-it-works guide matched to the program's pass type (see below). If your program has follow-up links configured (like "download our app"), they appear here. The Welcome to Mintleaf Rewards confirmation screen with a green checkmark and a three-step how-it-works guide ## NFC and barcode passes What the customer does at checkout depends on the program's pass type: * **NFC (tap to use)** — the pass works through Apple Pay: the customer taps their phone as usual and the pass is applied automatically. * **Barcode/QR** — the customer opens their wallet and shows the barcode at checkout. The confirmation screen tells the customer which applies to them. ## What's specific to your program The flow's skeleton is the same for everyone, but your program controls: the branding and texts, which form fields are asked, which consents appear, a minimum age requirement, which wallets are offered (Apple Wallet, Google Wallet, or both), whether existing members must verify with a code, whether the pass is also sent by email or SMS, and any follow-up links on the confirmation screen (like "download our app"). If you want any of these changed, [contact support](/support/contact).