Set up mobile wallet tickets
Mobile Wallet tickets provide personal edoobox tickets for Apple Wallet, Google Wallet and Samsung Wallet too. Participants open a ticket link generated by edoobox and add the ticket on their mobile device. Availability of each Wallet output also depends on its provider.
A Wallet ticket does not replace booking entitlement: confirmed participation, the selected validity scope and current personal barcode remain decisive at admission.
Check prerequisites
- You can edit barcode settings and the design used.
- Tickets and barcodes are enabled: for every registration or per offer. “Do not create barcodes” is insufficient.
- The relevant participants have a personal barcode and are assigned to the correct booking.
- A booking widget with the Wallet option is configured for the customer area. Alternatively, use a supported placeholder in a suitable template.
Enable Wallet and design the template
- Open Global settings → Barcode.
- Enable Generate Mobile Wallet ticket. Mobile Wallet template appears underneath.
- Maintain the account-wide default values below.
- Then open a specific demonstration booking and check the output. These values style newly generated Wallet tickets.
| Setting | Use |
|---|---|
| Display name | Issuer name in the Wallet ticket, such as your academy. |
| Background colour | Ticket colour. Choose one matching your branding. |
| Text colour | A text colour that clearly contrasts with the background. Check ticket readability on the intended mobile device. |
| Use offer image | Uses the respective offer's image if available. |
| Fallback image URL | Replacement image if no offer image can be used. Use an accessible HTTPS image address. |
| Support URL | HTTPS address for enquiries, such as your contact page. |
Previewing an offer without an image is as important as one with an image. An image available only in a signed-in internal session is unsuitable as a publicly retrievable ticket image.
Display Wallet in the customer area
- In the Design Manager, open the template for the customer area used.
- Edit the widget displaying bookings.
- Enable Show Mobile Wallet and save the design.
- Open the customer area with a suitable demonstration booking and select the person actually participating.
- Open their available Wallet access and check the name, offer and barcode.
Global activation alone does not display a button in a custom widget. The booking widget shows Wallet access only for suitable actual participation; open MustPay reservations, request lists and unnamed places do not receive a normal personal Wallet button through it.
Use Wallet links in templates
Insert a Wallet placeholder through the selector in a suitable booking or ticket template. A preview with sample data does not prove the personal download is available for a specific booking.
| Placeholder | Output |
|---|---|
##MobileWalletTickets## | Prepared Wallet links; the booking context may contain several participants. |
##MobileWalletTicketURL## | Address of the Wallet selection page. |
##MobileWalletAppleURL## | Address for Apple Wallet. |
##MobileWalletGoogleURL## | Address for Google Wallet. |
##MobileWalletAndroidURL## | Uses the same access as Google Wallet. |
##MobileWalletSamsungURL## | Address for Samsung Wallet. |
Use URL placeholders as link destinations and check the generated message in the outbox. Wallet placeholders remain empty when Wallet is disabled. The placeholder overview explains other available contexts.
Distinguish people in group bookings
A company contact may organise the booking without participating. Wallet tickets belong to actual named participants. Assign open places to people first. Check each person separately; a contact person's ticket does not grant access to everyone registered with them.
Replacing a personal barcode invalidates its previous code for all that person's bookings. Then provide the required tickets again and stop old codes being used. Do not assume an already saved Wallet ticket has updated without checking.
If the button or download is missing
- No Wallet button: Check barcode creation, global Wallet activation, the option in the correct booking widget and current booking status.
- A person is missing: Check active named participation. A contact-only person or open place is not a substitute.
- No ticket data: Open the user profile and check the personal barcode. Create a code if none exists. If a code is already present, first check the person and booking assignment. Resetting replaces the code for all of that person’s bookings.
- Wrong image or appearance: Check offer image, fallback and colours. Then open a newly generated download.
- Wallet provider reports an error: Use the current link generated by edoobox and check the output on the intended device. If a provider still fails, tell support the provider, time and affected demonstration booking. Regular Ticket.pdf can serve a previously configured PDF admission process.
Example: academy with several courses
An academy uses its name and colours as defaults. Courses with their own images display those; a general academy image serves as fallback. The administrator enables Wallet in the customer area and checks an individual booking and a company booking with two named people and one open place. A personal ticket for the third place becomes available only after a name is assigned.