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.
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.
1
Welcome screen
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 welcome screen carries the program's branding — here the Mintleaf demo program.
2
Personal details
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.
Mintleaf asks for email, phone, and name — your program defines its own set of fields.
3
Already a member? Verification
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.
4
Consents
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 required consent must be switched on before the customer can join.
5
Add the pass to the wallet
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.
On an iPhone the customer gets the Apple Wallet badge; Android shows Google Wallet instead.
6
Confirmation
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 confirmation explains how to use the pass — here for an NFC program, where the pass works through Apple Pay.
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.
