Wallet Pass for Amelia

Wallet Pass for Amelia turns each appointment booked through Amelia into a Google Wallet pass. The customer gets an “Add to Google Wallet” button on the booking confirmation screen and in the booking email. Add the [bbmawp_wallet_passes] shortcode to any page and signed-in customers can also come back later for a list of their upcoming appointments, each with its own button.

The pass shows the service, the provider, the date and time, the location, and a QR code. The customer’s phone then reminds them before the appointment, without you paying for an SMS.

There is no third-party pass-hosting service and no subscription. Passes are built using your own Google Wallet Issuer account and a service-account key you upload on the plugin’s settings screen. The service name, the provider, the appointment date and time, the location, the booking reference, and the customer’s name are the only data placed on a pass.

Passes are generated when the customer taps the button, from the booking’s current state. If the appointment is later rescheduled or cancelled, the pass already in the customer’s phone is updated or voided automatically.

This edition issues Google Wallet passes for Amelia’s appointments. A premium edition is a separate plugin that also covers Amelia’s events, with one pass per ticket, and adds Apple Wallet passes for iPhone and iPad, plus email support.

Wallet Pass for Amelia is an independent, third-party plugin built by Blue Brain Media. It is not affiliated with, endorsed by, or sponsored by the makers of Amelia.

Features

1. Google Wallet pass generation via your own Google Wallet Issuer account
2. “Add to Google Wallet” buttons on the booking confirmation screen and in the booking email
3. A [bbmawp_wallet_passes] shortcode listing a signed-in customer’s upcoming appointments, each with its own button
4. A staff lookup on the settings screen for copying any upcoming appointment’s pass link
5. Passes update automatically when an appointment is rescheduled, and void when it is cancelled
6. Pass styling: organisation name, background colour, barcode format
7. A settings-screen diagnostics panel, and a wp amelia-wallet verify command, that check your credentials and say exactly what is wrong

Requirements

• Amelia – the free edition (Amelia Lite) is enough; nothing here needs a paid Amelia licence
• PHP 8.1+ with the OpenSSL extension
• A Google Cloud project with the Google Wallet API enabled, and a Google Wallet Issuer account

A note on Amelia’s free edition

This plugin works on Amelia Lite. Two things behave differently there, because Amelia itself gates them:

• Locations are a paid Amelia feature. On Lite the pass falls back to the company address from Amelia’s own settings, and omits the venue entirely if that is empty too.
• Per-customer timezones are a paid Amelia feature. On Lite every appointment is shown in your site’s WordPress timezone.

Neither stops passes from working.

External services

This plugin connects to the Google Wallet API to create the pass that a customer saves to Google Wallet. Creating the pass has to happen on Google’s servers, because Google Wallet only accepts passes issued through its own API.

• What it is used for: authenticating with your Google Cloud service account (https://oauth2.googleapis.com/token), then creating and updating a pass class and object (https://walletobjects.googleapis.com/walletobjects/v1). The customer’s “Add to Google Wallet” button opens a link on https://pay.google.com/gp/v/save/.
• What is sent, and when: the first time a customer taps the button for a booking, and again whenever that appointment is rescheduled or cancelled, the plugin sends the service name, the provider’s name, the appointment date and time, the location, your pass styling (organisation name, background colour, barcode format), the booking reference and barcode value, and the customer’s name. Your service-account credentials are used to sign the requests and are sent only to Google’s OAuth endpoint. Nothing is sent when the plugin is idle, and nothing is sent for customers who never tap the button.
• Provider: Google LLC. Google Terms of Service, Google Privacy Policy and Google APIs Terms of Service.

Credits

The pass engine in this plugin descends from CommerceBird – Wallet Pass for Tickera (https://github.com/RoadmapStudios/commercebird-wallet-pass), originally written by Roadmap Studios / CommerceBird and released under GPL-3.0. The CommerceBird SaaS account layer (subscription check, the app.commercebird.com connection, the remote pass-generation API, and the CommerceBird application-password requirement) has been removed; Google Wallet passes are generated and cryptographically signed directly on the site’s own server, using credentials the site owner supplies on the plugin’s own settings screen. The GPL-3.0 obligations from the upstream project carry forward unchanged: source is available and the licence text is distributed verbatim in LICENSE.

The Google Wallet JWT (used for the OAuth2 service-account assertion and the “Add to Google Wallet” link) is RS256-signed with PHP’s own OpenSSL extension; this edition does not bundle any third-party libraries.