Do I need a paid Amelia licence?
No. Everything this plugin depends on is present in Amelia’s free edition. See the note above for the two places a paid Amelia tier changes what appears on the pass.
Do I need a paid third-party plan?
No. The plugin runs entirely on your server. You do need a free Google Cloud project and a Google Wallet Issuer account to obtain the credentials the plugin uses to sign passes.
Why do my Google Wallet passes show a “[TEST ONLY]” banner?
Every Google Wallet Issuer account starts in Google’s own demo mode, and Google adds this banner to every pass – and blocks anyone not on your tester list from adding one – until you request and receive publishing access for that account. This is a one-time approval from Google, free of charge, and applies to every Google Wallet integration; the plugin has no setting to skip it. To remove it:
- 01Sign in to the Google Pay & Wallet Console with the Google account tied to your Wallet Issuer ID.
- 02Under Business profile, complete both the Business identity (payments profile) and Business information sections.
- 03Have at least one pass on file, so there is a class for Google to review.
- 04Under Google Wallet API, click “Request publishing access” and submit for review.
Approval isn’t instant, so do this well before you need real customers to add passes. Once approved, the banner disappears automatically from all your passes – no plugin update or setting change is needed.
Does this include Apple Wallet?
No. This edition generates Google Wallet passes only. Apple Wallet passes, for iPhone and iPad customers, are part of the premium edition .
One difference worth knowing before you buy: Google Wallet passes update themselves on the customer’s phone when an appointment moves, and Apple Wallet passes in the current premium release do not. The customer’s remedy is one tap – opening the same pass link again rebuilds the pass from today’s booking – and the emails say so. Automatic Apple updates need Apple’s push service, which the current release does not include.
Does this work with Amelia’s events?
No. This edition issues passes for appointments. Event bookings are left alone: no button appears on the confirmation screen or in the email, and nothing is added to the customer’s phone. Event passes, one per ticket, are part of the premium edition . Your appointment passes are unaffected either way.
Can I choose where the button appears in my booking emails?
Yes. By default the button is added to the end of Amelia’s own notification, which needs no setup. If you would rather place it yourself, put %wallet_pass% anywhere in the notification template under Amelia > Notifications, and the button appears there instead. The token is removed automatically whenever no button applies, so it never shows up as raw text in a customer’s inbox.
Can customers get their pass again later?
Yes. Put the [bbmawp_wallet_passes] shortcode on any page – the same page as Amelia’s customer panel is the natural home for it – and a signed-in customer sees their upcoming appointments there, each with its own button. It works for customers signed in through Amelia’s own customer panel and for customers signed in to WordPress.
The list only ever shows the appointments of the person actually signed in. There is no way to ask it for somebody else’s: it takes no email address, either as a shortcode attribute or in the URL. Visitors who are not signed in are simply told to sign in.
A customer says they never got the link. Can I send it to them?
Yes. Go to Amelia > Wallet Pass and scroll to “Pass links”. It lists your upcoming appointments, and you can search by customer name, email, service or booking ID. Click Copy next to the right one and paste it into your reply.
Only upcoming appointments that have not been cancelled are listed, because those are the only ones a pass link works for.
What happens if an appointment is rescheduled or cancelled?
The pass already saved on the customer’s phone is updated to the new time, or marked void if the appointment is cancelled. This happens in the free edition too.
Where are the passes stored?
Generated pass data is served directly from Google’s own save link ( https://pay.google.com/gp/v/save/... ); nothing is stored on your server long-term.
Do I need to change anything in my caching plugin or CDN?
Usually not, but it is worth two minutes to check. Pass links are ordinary URLs on your site carrying an awp_pass parameter, and each one is personal to a single customer’s booking. The plugin marks those responses as never-cache, using both the standard WordPress headers and the DONOTCACHEPAGE flag that WP Rocket, W3 Total Cache, WP Super Cache and LiteSpeed all read, so in a normal setup the right thing happens on its own.
What that cannot reach is a cache running in front of WordPress — a CDN set to cache whole pages, or Varnish or nginx caching configured by your host. If you run one of those, exclude any URL containing awp_pass from it. The reason to bother: if such a cache did store one of these responses, the next person to open a pass link would be handed the pass belonging to whoever came before them, complete with their name and appointment.
Is any personal data sent anywhere?
Only to Google, as described under External services below. No data is sent to Blue Brain Media or any other third party.
Where do I get support?
Ask in the support forum on this plugin’s WordPress.org page, or use the form at https://bluebrainmedia.ca/support/ if you would rather write to us directly. Either way, saying which versions of WordPress, this plugin and Amelia you are running saves a round of follow-up questions.
