Description
Your customer books an appointment or an event, and Amelia’s confirmation screen offers
them an Add to Apple Wallet and Add to Google Wallet button, right below the booking
details. The pass carries the service or event, the customer’s name, the date and time, the
employee and location, with a barcode staff can scan.
Design the pass
The Pass design tab is a visual editor with a live Apple Wallet and Google Wallet
preview, front and back, filled in with your latest booking.
- Your business name, logo and colour.
- A header line, the pass title and up to three fields on the front.
- Sections on the back: text, links, phone numbers, email addresses and addresses.
- “+ Data Field” puts each booking’s details on the pass: the customer’s name, the service
or event, employee, location and address, date, start and end time, duration, number of
people, price, booking number, online meeting link, your business contact details and more. - A hero image, with a different image per service or per event if you like.
- The barcode format, and a Wallet reminder before the appointment.
How it works
- The buttons appear inside Amelia’s own booking forms, on their confirmation screen:
step-by-step booking, catalog booking, the booking button, and the events list and
calendar. - The pass is created on your server with your AddToWallet API key. The key never reaches
your visitors’ browsers. - The browser sends only the booking id and Amelia’s own booking token, and the booking
details are read from Amelia’s tables, so nobody can create a pass for someone else’s
booking or put made-up details on one. - Reloading the confirmation screen never creates a second pass.
Cancellations and changes
When a booking is canceled, rejected or marked a no-show, by you, an employee or the
customer’s own cancel link, the pass in their wallet is marked expired straight away. When
an appointment is rescheduled, or you change its time, employee or location, the pass is
updated to match, without using another credit. All of this happens on your server, from
Amelia’s own notifications, even if nobody has the booking page open.
Requirements
- Amelia (the free Amelia Lite from WordPress.org, or a paid edition)
- An AddToWallet account and API key
Coming from the “AddToWallet for Amelia Bookings” zip?
That plugin (version 1.x, folder amelia-addtowallet) was handed out as a download. This
plugin installs into a new folder, so WordPress treats it as a separate plugin. When you
activate it, it copies your 1.x settings and the record of every pass 1.x issued, and from
then on it creates, updates and expires the passes. Then deactivate and delete the 1.x
plugin. Until you do, it stays switched off and you will see a reminder.
External services
This plugin connects to the AddToWallet API at https://app.addtowallet.co to create,
update and expire Apple Wallet and Google Wallet passes. Without this service it cannot
issue passes.
- When you save an API key, the plugin checks it by reading your credit balance
(/api/payment/usage), sending only the key. The balance is read again when you open the
Settings tab. - When a customer’s booking qualifies for a pass, the plugin sends the details you put on
the pass from your server to AddToWallet (/api/card/create). With the default design
that is the service or event name, the date and time, the customer’s name, the employee’s
name, the location’s address, the booking id, your business name, email and phone (from
Amelia’s company settings), and the logo, image and colors you configured. The customer’s
own email address, phone number or the price are only sent if you add them to the pass
design. - When a booking is canceled, rejected, marked a no-show or deleted, it sends the pass id
and your logo so the pass can be expired; when a booking is rescheduled or changed, it
sends the pass id with the updated pass details (/api/card/edit). - The Help tab’s contact form sends the name, email address and message you type, plus your
site address and the plugin version, to AddToWallet support (/api/admin/contactus),
only when you press Send.
Every request to /api/card/* and /api/payment/usage carries your API key to
authenticate it. Your API key is never sent to the customer’s browser.
The service is provided by AddToWallet: Terms of Service,
Privacy Policy.
FAQ
Which bookings get a pass?
Approved bookings, unless you choose otherwise. You can also issue passes for pending
bookings (services that need your approval) and waiting-list places, though those may never
happen.
No buttons appear. What should I check?
- You are out of AddToWallet credits.
- The booking has a status you do not issue passes for.
- The customer is sent to another page after booking (a WooCommerce checkout, or Amelia’s
“Redirect URL after booking”), so Amelia never shows its confirmation screen.
The Bookings & passes tab lists every booking and whether it received a pass.
Do package and recurring bookings get a pass?
A package purchase has no single date, so it gets no pass of its own. A recurring
appointment gets one pass, for the first occurrence.
Does expiring a pass refund the credit?
No. Each pass costs one credit when it is created.
Screenshots




Changelog
2.0.0
- First release on WordPress.org, as “AddToWallet for Amelia”. Replaces the “AddToWallet for Amelia Bookings” 1.x zip: settings and issued passes are copied over on activation.
- New admin screen, with Pass design, Bookings & passes, Settings and Help tabs.
- Pass design: a visual editor with a live Apple Wallet and Google Wallet preview, front and back.
- Choose the business name, header line, pass title and up to three front fields, using “+ Data Field” to add booking details: service or event, employee, location, date and time, price, number of people and more.
- Add sections to the back of the pass: text, links, phone numbers, email addresses and addresses.
- Hero image variations per service and per event.
- Event bookings get a pass with the event’s own dates, location and organizer.
- When an appointment is rescheduled or its details change, the pass already in the wallet is updated, without using another credit.
- Fixed: the pass showed Amelia’s stored UTC time as if it were your site’s time, so on any site outside UTC the appointment time on the pass was wrong by the time-zone offset.
- Fixed: expiring a pass on cancellation failed with “Image cannot be loaded … logo-placeholder.png”. The logo each pass was made with is now sent with the expiry.
- Passes also expire when a booking or its appointment or event is deleted, and when an event is canceled.
- The API key is checked with AddToWallet before it is saved.
- Bookings & passes shows why a pass could not be created (for example, no credits left), and when a pass was updated or failed to update or expire.
- Times on the pass follow Amelia: the site’s time zone, or the customer’s when Amelia is set to show customers their own.
1.13.0
- Passes report which integration created them. Requests identify the plugin and its version.
