Add wallet passes to WordPress

The free WalletPassBuilder plugin for WordPress adds Add to Apple Wallet and Add to Google Wallet buttons to your site. It can also give every booking, ticket or order from your booking or event plugin its own pass, and keep that pass up to date.

Set up the plugin

In WordPress, go to Plugins > Add New, search for WalletPassBuilder, then install and activate it. You can also get it from WordPress.org.

In your WalletPassBuilder dashboard, open API and copy your API key. If you don't have an account yet, you can create one for free.

In WordPress, open WalletPassBuilder in the admin menu and paste the key to connect your account.

On the Pass Template tab, design your pass and create it.

Add the Add to Wallet block to a page, or use the shortcode [wallet_pass_builder].

To show a different pass from your account, pick it in the block's settings, or use [wallet_pass_builder pass="PASS_ID"]. The Add to Wallet button tab lists your passes with their shortcodes.

Each new pass uses pass credits from your account. When you change the template and update the pass, everyone who already saved it gets the new version on their phone.

Connect a booking or event plugin

Turn your plugin on under the Integrations tab, and each booking or ticket gets its own pass. You design it in the same editor, with data fields such as the event, date, time and place. When a booking or its event changes or is cancelled, the pass on the customer's phone updates. See every plugin it works with.

LatePoint

Every appointment gets a pass with the service, date, time, place, agent and booking code. Buttons appear on the booking confirmation and in the customer's bookings. To add them to LatePoint's emails, use {{wallet_pass_buttons}} or {{wallet_pass_link}}. See the LatePoint page for screenshots and questions.

Amelia

Every appointment and every event booking gets a pass, with a separate design for each. Buttons appear on the booking form's confirmation. To add them to Amelia's customer emails, use %wallet_pass_buttons% or %wallet_pass_link%. See the Amelia page for screenshots and questions.

Bookly

Every booking gets a pass, on Bookly Lite or Pro, with one per customer in a group booking. Buttons appear on the booking form's last step. To add them to Bookly's email notifications, use [wallet_pass_buttons {booking_number}] or [wallet_pass_link {booking_number}]. These emails must be sent through WordPress, which is Bookly's default, not its own SMTP setting. See the Bookly page for screenshots and questions.

Sugar Calendar

Every ticket sold or claimed gets its own pass, with the ticket code as a QR code, so tickets can be shared and scanned one by one. Buttons appear on the order receipt. To add them to Sugar Calendar's ticket and receipt emails, use {wallet_pass_buttons} or {wallet_pass_link}. See the Sugar Calendar page for screenshots and questions.

Events Manager

Every space in a booking gets its own pass, so a booking for three is three tickets, each with its own QR code. Passes are issued once a booking is pending approval or approved. Buttons appear in the booking form's success message and on "My Bookings". To add them to Events Manager's emails, use #_WALLETPASSBUTTONS or #_WALLETPASSLINK. See the Events Manager page for screenshots and questions.

EventON

Every upcoming event gets one pass that everyone shares, added from an Add to Wallet box on the event card. It follows the event's next date when the event repeats. Each event uses one pass credit, however many people add it. If you've arranged the event card yourself, add the box in EventON > Settings > EventCard. See the EventON page for screenshots and questions.

Event Espresso

Every registration gets a pass, one per ticket in an order, with the registration code as a QR code. Passes are issued once a registration is approved or awaiting review. Buttons appear on the thank-you page. To add them to Event Espresso's messages, use [WALLET_PASS_BUTTONS] or [WALLET_PASS_LINK]. See the Event Espresso page for screenshots and questions.

WooCommerce

Tick Wallet pass on a product, and each unit bought gets its own pass once the order is paid, with its own QR code. A cancelled or refunded order shows as cancelled on the pass. Buttons appear on the order received page, in My Account and in order emails. See the WooCommerce page for screenshots and questions.

Event Tickets

Every ticket and RSVP gets a pass, with the security code as a QR code. This covers Tickets Commerce and RSVPs, on The Events Calendar's events or any page. Passes are issued once a ticket is paid for or an RSVP is "Going", and check-ins and refunds show on the pass. Buttons appear on the order confirmation, on the "My Tickets" page and in Event Tickets' ticket emails. See the Event Tickets page for screenshots and questions.

WP Event Manager

Every registration gets a pass, so with Sell Tickets each ticket bought gets a pass for its attendee. The QR code is WP Event Manager's own ticket code, so its check-in app scans it, and check-ins show on the pass. Passes are issued once the order is paid. Buttons appear on the order received page, in My Account and in order emails. To add them to WP Event Manager's emails, use [wallet_pass_buttons] or [wallet_pass_link]. You need its Registrations add-on. See the WP Event Manager page for screenshots and questions.

If a booking didn't get a pass

Check that the integration is on under Integrations, then look in Activity. A failed entry says why, and Retry sends it again once that's fixed. The plugin also checks every 15 minutes, which retries anything that failed and catches changes made outside your booking plugin's normal screens.