Operators are responsible for distributing the elumo digital pass provisioning link to users. This link allows users to authenticate and add their digital pass to Apple Wallet or Google Wallet.
elumo supports multiple ways to share this link, depending on the communication channel and the level of control you want over the user experience.
This article outlines the available options and provides guidance on when to use each.
Provisioning Links and QR Codes
Provisioning URLs and QR codes are supplied by essensys when you first go live with elumo.
If you have not received these, please speak to your Customer Success Manager.
Overview of Available Options
Operators can choose from the following approaches:
Generic provisioning URL (auto‑detects platform on mobile)
Platform‑specific URLs (Apple Wallet or Google Wallet)
QR codes generated from either generic or platform‑specific URLs
Personalised URLs with pre-filled email address
Each option can be used independently or combined, depending on your use case.
Option 1: Generic URL (Recommended for Simplicity)
What it is
A single, generic provisioning URL that automatically detects the user’s device platform when opened on mobile.
iOS users are guided to Apple Wallet
Android users are guided to Google Wallet
When to use it
This option is best when:
You want one link to cover all users
You are unsure which device the user has
You are sharing the link via email, SMS, or printed materials
How to provide it to users
Include the URL directly in an email or SMS
Embed the link behind a button such as “Add Digital Pass”
Convert the URL into a QR code for posters, letters, or on‑site signage
Things to note
Platform detection only works when the link is opened on a mobile device
Option 2: Platform‑Specific URLs (Apple & Google)
What they are
Separate URLs that explicitly target:
Apple Wallet (iOS devices)
Google Wallet (Android devices)
These URLs bypass auto‑detection and send the user directly to the correct wallet flow.
When to use them
This option is recommended when:
You want to include Apple Wallet and Google Wallet badges in emails
You want a more polished, platform‑aware user experience
You already know the user’s device type
How to provide them to users
Use Apple Wallet and Google Wallet badges in email templates
Ensure the correct links are embedded with the badge for user's to select as applicable
Things to note
Users must select the link that matches their device
Opening the wrong link on the wrong platform may result in an error or unsupported flow
Option 3: QR Code Generation
What it is
QR codes generated from either:
The generic provisioning URL, or
Platform‑specific URLs
QR codes can also include platform specifiers
When to use it
QR codes are ideal for:
On‑site distribution (posters, reception desks, outside meeting rooms)
Situations where typing a URL would be inconvenient
How to provide them to users
Display QR codes prominently with a short instruction such as “Scan to add your digital pass”
If using multiple QR codes, label them clearly by platform
Ensure QR codes are large enough to scan easily on mobile devices
Things to note
Users must scan the QR code using their mobile device
Poor lighting or low print quality may affect scannability
Option 4: URL with Pre‑Filled Email Address
What it is
A variation of the provisioning URL that includes the user’s email address as a URL parameter, allowing the email field on the authentication form to be pre‑filled automatically.
This reduces friction for the user and minimises the risk of entering an incorrect email address.
When to use it
This option is recommended when:
You are sending individualised invitations (rather than bulk, generic links)
The user’s email address is already known and verified
You want to streamline the authentication journey and reduce user input
You are issuing links via email, where personalisation is already in place
How it works
The operator appends the user’s email address to the provisioning URL as a parameter.
When the user opens the link:
The email field on the authentication form is automatically populated
The user can proceed directly to verification without re‑entering their email
The user is still required to complete the authentication step (for example, entering a one‑time passcode sent to their email or mobile).
How to provide it to users
Generate the personalised URL dynamically as part of your email invitation
Embed the link behind a call‑to‑action such as “Add Digital Pass”
Ensure each link is sent only to the intended recipient
This option can also be combined with:
The generic URL (with auto‑platform detection), or
Platform‑specific URLs for Apple Wallet or Google Wallet
Things to note
The email address in the URL must exactly match the email stored on the user’s profile
This option should not be used for shared links or publicly visible QR codes
For security and privacy reasons, avoid exposing personalised URLs in:
Posters or signage
Printed materials
Shared inboxes or forwarding workflows
Choosing the Right Option
Scenario | Recommended Option |
Email invitation to mixed devices | Generic URL |
Branded email with wallet badges | Platform‑specific URLs |
On‑site or printed materials | QR code (generic or platform‑specific) |
Unknown user device | Generic URL |
Known device type | Platform‑specific URL |
Personalised user email invitation | Personalised URL |