Title: WalletPassBuilder – Passes for Apple Wallet and Google Wallet Author: walletpassbuilder Published: October 26, 2026 Last modified: October 30, 2026 --- Search plugins ![](https://ps.w.org/walletpassbuilder/assets/banner-772x250.png?rev=3765515) ![](https://ps.w.org/walletpassbuilder/assets/icon-256x256.png?rev=3765515) # WalletPassBuilder – Passes for Apple Wallet and Google Wallet By [walletpassbuilder](https://profiles.wordpress.org/walletpassbuilder/) [Download](https://downloads.wordpress.org/plugin/walletpassbuilder.1.2.0.zip) * [Details](https://mlt.wordpress.org/plugins/walletpassbuilder/#description) * [Reviews](https://mlt.wordpress.org/plugins/walletpassbuilder/#reviews) * [Installation](https://mlt.wordpress.org/plugins/walletpassbuilder/#installation) * [Development](https://mlt.wordpress.org/plugins/walletpassbuilder/#developers) [Support](https://wordpress.org/support/plugin/walletpassbuilder/) ## Description WalletPassBuilder connects your site to your [WalletPassBuilder](https://walletpassbuilder.com) account, so your visitors can save your event pass, ticket or membership card to the wallet on their phone in one tap. * **Connect your account** with an API key, and see your plan and remaining pass credits. * **Design a pass** in WordPress from a ready-made template: business name, title, background colour (text adjusts automatically for contrast), logo (your Site Icon or theme logo to start with, otherwise the WalletPassBuilder icon), up to three fields on the front, a QR code or barcode and details on the back, with live Apple Wallet and Google Wallet previews of the front and back. * **Add the official Add to Apple Wallet and Add to Google Wallet buttons** to any page with a block or a shortcode. Each one opens that wallet with the pass. * **Add a hero image and reminders** in the Advanced section: a hero image across the pass (move and zoom it to frame it, and pick a different one for kids’ tickets or cancelled bookings), and lock-screen reminders when the event starts, before the pass expires, or when people are near your venue. * **Keep the pass current.** Change the template and update the pass: everyone who already saved it gets the new version on their phone. * **See what happened** in the activity log, with the reason for any failure and a Retry button. Use the pass from the plugin’s Pass Template tab, or any other pass from your WalletPassBuilder account. #### Booking and event plugins Turn on any of these on the Integrations tab and each booking or ticket gets its own wallet pass, designed in the same editor as the Generic Pass 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. A check every 15 minutes retries anything that failed and catches changes made outside the plugin’s normal screens. #### LatePoint Every appointment: the service, date, time, place, agent and booking code. Buttons on the booking confirmation and in the customer’s bookings; add `{{wallet_pass_buttons}}` or `{{wallet_pass_link}}` to LatePoint’s emails. #### Amelia Every appointment and every event booking, with a separate design for each. Buttons on the booking form’s confirmation; add `%wallet_pass_buttons%` or `%wallet_pass_link%` to Amelia’s customer emails. #### Sugar Calendar Every ticket sold or claimed: the event, date, time, place, ticket holder and ticket code as a QR code, one pass per ticket so they can be shared and scanned one by one. Buttons on the order receipt; add `{wallet_pass_buttons}` or `{wallet_pass_link}` to Sugar Calendar’s ticket and receipt emails. #### Event Tickets Every ticket and RSVP (Tickets Commerce and RSVPs, on The Events Calendar’s events or any page), with the security code as a QR code. Issued once a ticket is paid for or an RSVP is “Going”; check-ins and refunds show on the pass. Buttons on the order confirmation, the “My Tickets” page and in Event Tickets’ ticket emails. #### Bookly Every booking (Lite or Pro), one pass per customer in a group booking. Buttons on the booking form’s last step; add `[wallet_pass_buttons {booking_number}]` or `[ wallet_pass_link {booking_number}]` to Bookly’s email notifications, which must be sent through WordPress (Bookly’s default), not its own SMTP setting. #### Events Manager Every space in a booking, so a booking for three is three tickets, each with its own ticket code as a QR code. Issued once a booking is pending approval or approved. Buttons in the booking form’s success message and on “My Bookings”; add `#_WALLETPASSBUTTONS` or `#_WALLETPASSLINK` to Events Manager’s emails. #### EventON Every upcoming event gets one pass that everyone shares, added from an Add to Wallet box on the event card, and it follows the event’s next date when it repeats. Each event uses one pass credit, whoever adds it. If you’ve arranged the event card yourself, add the box in EventON › Settings › EventCard. #### Event Espresso Every registration (one per ticket in an order), with the attendee, ticket type and registration code as a QR code. Issued once a registration is approved or awaiting review. Buttons on the thank-you page; add `[WALLET_PASS_BUTTONS]` or `[WALLET_PASS_LINK]` to Event Espresso’s messages. #### WooCommerce Tick “Wallet pass” on a product and each unit bought gets its own pass once the order is paid, with its own code as a QR code; a cancelled or refunded order shows as cancelled. Buttons on the order received page, in My Account and in order emails. Works with HPOS. #### WP Event Manager Every registration, 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. Issued once the order is paid. Buttons on the order received page, in My Account and in order emails; add `[wallet_pass_buttons]` or `[wallet_pass_link]` to WP Event Manager’s emails. Needs the Registrations add- on. #### Requirements A WalletPassBuilder account. You can [create one for free](https://walletpassbuilder.com/signup); each new pass uses pass credits from your account. ### External services This plugin connects to the WalletPassBuilder service (https://walletpassbuilder. com), which creates and signs Apple Wallet and Google Wallet passes. The plugin does not work without it. What is sent, and when: * **When you connect, and when you open the plugin’s Settings tab:** your API key, to check it and show your account name, email address, plan and pass credits. * **When you create or update the pass from the Pass Template tab:** the pass design you entered (business name, title, background colour, logo image, front fields, barcode value and back sections). * **With LatePoint turned on, when an appointment is booked or changed:** the appointment details your booking pass shows (by default the customer’s name, the service, the date, time and location, the booking code and the status; optionally the end time, duration, agent and price), to create or update that customer’s pass. Customer email addresses and phone numbers are never sent. Nothing is sent for appointments made while the integration is off. * **With Amelia turned on, when an appointment or event booking is made or changed:** the booking details its pass shows (by default the customer’s name, the service or event, the date, time and location, the employee or tickets, the booking number and the status), to create or update that customer’s pass. Customer email addresses and phone numbers are never sent. Nothing is sent for bookings made while the integration is off. * **With Sugar Calendar turned on, when a ticket is bought or claimed, or its order or event changes:** the ticket details its pass shows (by default the ticket holder’s name, the event, its date, time and location, the ticket type, the ticket code, the order number and the status), to create or update that ticket’s pass. Email addresses are never sent. Nothing is sent for tickets sold while the integration is off. * **With Event Tickets turned on, when a ticket or RSVP is confirmed, checked in or changed:** the ticket details its pass shows (by default the ticket holder’s name, the event, the ticket type, the security code, the order number and the status, and with The Events Calendar the event’s date, time and venue), to create or update that ticket’s pass. Email addresses are never sent. Nothing is sent for tickets made while the integration is off. * **When you search for an address in the Advanced section:** what you type, to suggest addresses and find the chosen one’s coordinates. WalletPassBuilder looks addresses up with Google Maps Platform (Places); see Google’s [privacy policy](https://policies.google.com/privacy). * **When you send a message from the Help tab (or request an integration):** your reply-to email address, subject, message and any screenshots you attach, and ( unless you untick “Include site details”) your site’s address, the plugin, WordPress and PHP versions, which integrations are on, your Generic Pass id and the last few failed entries from Activity; an integration request also lists your active plugins. The Help tab shows exactly what’s included before you send. It goes to the WalletPassBuilder support team. * **With Bookly turned on, when a booking is made or changed:** the booking details its pass shows (by default the customer’s name, the service, the date, time and location, the staff member, the status and the booking number), to create or update that customer’s pass. Customer email addresses and phone numbers are never sent. Nothing is sent for bookings made while the integration is off. * **With Events Manager turned on, when a booking is made or changed, or its event changes:** each ticket’s details its pass shows (by default who booked it, the event, its date, time and location, the ticket type and number, the ticket code, the booking number and the status), to create or update that ticket’s pass. Email addresses and phone numbers are never sent. Nothing is sent for bookings made while the integration is off. * **With EventON turned on, when an event is published or changed, and every 15 minutes for upcoming events:** the event details its pass shows (by default the event’s name, date, start and end time, location, address, organizer, status and page link), to create or update that event’s pass. Nothing about the people who add it is sent. * **With Event Espresso turned on, when a registration, attendee, event, date, ticket or venue is saved:** each affected registration’s details its pass shows( by default the attendee’s name, the event, its date, time and venue, the ticket type and number, the registration code, the order number and the status), to create or update that registration’s pass. Email addresses, phone numbers and addresses are never sent. Nothing is sent for registrations made while the integration is off. * **With WooCommerce turned on, when an order with a “Wallet pass” product is paid, changed or refunded:** each unit’s details its pass shows (by default the customer’s name, the product and its options, the unit number, its code, the order number and date and the status), to create or update that unit’s pass. Email addresses, phone numbers and addresses are never sent. Nothing is sent for products without“ Wallet pass” ticked. * **With WP Event Manager turned on, when a registration is made or changed, its order is paid, cancelled or refunded, an attendee checks in, or its event changes:** each registration’s details its pass shows (by default the attendee’s name, the event, its date, time and location, the ticket type and number, the ticket code, the registration number and the status), to create or update that registration’s pass. Email addresses and phone numbers are never sent. Nothing is sent for registrations made while the integration is off. * **When a page shows an “Add to Wallet” button, and when you pick a pass in the block editor:** the pass id, to look up the pass’s share link and the list of your passes. Results are cached on your site. Every request also includes your site’s address in its user agent. Apart from the bookings and tickets above, the plugin sends no information about your visitors or customers. When a visitor clicks an Add to Apple Wallet or Add to Google Wallet button, their browser opens the pass on the WalletPassBuilder service (walletpassbuilder. com, gowalletpass.com or your own custom share domain), which hands it to Apple Wallet or Google Wallet. The button images are part of the plugin and load from your site. WalletPassBuilder [terms of service](https://walletpassbuilder.com/terms) and [privacy policy](https://walletpassbuilder.com/privacy). ## Blocks This plugin provides 1 block. * Add to Wallet The official Add to Apple Wallet and Add to Google Wallet buttons for a WalletPassBuilder pass. ## Installation 1. Install and activate the plugin. 2. Open **WalletPassBuilder** in your WordPress admin menu, paste your API key from** API** in your WalletPassBuilder dashboard, and click **Connect**. 3. On the **Pass Template** tab, change the ready-made pass to suit you and click ** Save and create pass**. 4. Add the **Add to Wallet** block to a page, or the shortcode `[wallet_pass_builder]`. ## FAQ ### Can I show a pass I made in WalletPassBuilder? Yes. 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. ### What options does the shortcode take? pass (a pass id; leave it out for the pass from the Pass Template tab), `wallets`(` both`, `apple` or `google`) and `align` (`left`, `center` or `right`). For example:`[ wallet_pass_builder pass="PASS_ID" wallets="both" align="center"]`. ### Does updating the pass change it on people’s phones? Yes. Updating keeps the same pass and link, and phones that saved it receive the new version. The plugin asks you to confirm first. ### Does the plugin delete passes? No. Passes stay in your WalletPassBuilder account. Deleting the plugin removes your API key from the site, and also its settings and activity log if you tick that option on the Settings tab. ### Which workspace are passes created in? Your account’s default workspace. You can change it in WalletPassBuilder under Settings > Workspace. ### Where do the QR code and barcode come from? The preview draws them in your browser with the bundled [QR Code Generator](https://github.com/kazuhikoarase/qrcode-generator) library by Kazuhiko Arase (MIT licence) and a built-in Code 128 encoder, the same formats Apple Wallet and Google Wallet show. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “WalletPassBuilder – Passes for Apple Wallet and Google Wallet” is open source software. The following people have contributed to this plugin. Contributors * [ walletpassbuilder ](https://profiles.wordpress.org/walletpassbuilder/) [Translate “WalletPassBuilder – Passes for Apple Wallet and Google Wallet” into your language.](https://translate.wordpress.org/projects/wp-plugins/walletpassbuilder) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/walletpassbuilder/), check out the [SVN repository](https://plugins.svn.wordpress.org/walletpassbuilder/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/walletpassbuilder/) by [RSS](https://plugins.trac.wordpress.org/log/walletpassbuilder/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.2.0 * WP Event Manager: a wallet pass for every registration (each ticket sold with Sell Tickets), with WP Event Manager’s own ticket code as the QR code so its check-in app scans it. Updated when the order is paid, cancelled or refunded, the attendee checks in, or the event changes, with Add to Wallet buttons on the order received page, in My Account, in order emails and in WP Event Manager’s emails ([wallet_pass_buttons], [wallet_pass_link]). #### 1.1.0 * LatePoint: a wallet pass for every appointment, updated when the appointment changes, with Add to Wallet buttons on the confirmation, in the customer’s bookings and in emails. * Design the LatePoint booking pass in the Pass Template editor, inserting appointment details anywhere. * A scheduled check every 15 minutes retries failed passes and catches missed changes. * Amelia: a wallet pass for every appointment and event booking, updated when it changes, with Add to Wallet buttons on the booking confirmation and in Amelia’s emails. * Sugar Calendar: a wallet pass for every ticket, updated when the event or order changes, with Add to Wallet buttons on the order receipt and in Sugar Calendar’s emails. * Event Tickets: a wallet pass for every ticket and RSVP, updated on check-in, refunds and event changes, with Add to Wallet buttons on the order confirmation,“ My Tickets” and in Event Tickets’ emails. * Events Manager: a wallet pass for every ticket (each space in a booking), updated when the booking or event changes, with Add to Wallet buttons in the booking confirmation, on “My Bookings” and in Events Manager’s emails. * EventON: a wallet pass for every upcoming event, shared by everyone who adds it from the event card, updated when the event changes, is cancelled or moves on to its next date. * Event Espresso: a wallet pass for every registration (each ticket in an order), updated when the registration, attendee, event, date, ticket or venue changes, with Add to Wallet buttons on the thank-you page and in Event Espresso’s messages. * WooCommerce: a wallet pass for every unit bought of the products you tick, issued when the order is paid and cancelled when it’s refunded, with Add to Wallet buttons on the order received page, in My Account and in order emails. * Bookly: a wallet pass for every booking (one per customer in a group), updated when it’s rescheduled, approved or cancelled, with Add to Wallet buttons on the booking form’s last step and in Bookly’s emails. * Advanced section on every pass: a hero image (Apple’s strip, Google’s hero) you can move and zoom to frame, with variations for bookings whose details match ( a kids’ ticket, a cancelled booking), and reminders at the start time, before expiry and near a place. Booking passes remind each customer at their own booking’s start time. * A Header line above the pass title, and one shared layout for every booking pass: the holder’s name, then date, time and place. * Booking passes get the new design automatically after an update to the plugin changes it. * The activity log shows the customer for each pass. * A Help tab with quick answers and a form to message the WalletPassBuilder team( with screenshots), showing exactly which site details go with it. Request an integration from the Integrations tab. #### 1.0.0 * First release: connect your account, design a pass with Apple Wallet and Google Wallet previews, official Add to Wallet buttons as a block and shortcode, activity log with retry. ## Meta * Version **1.2.0** * Last updated **9 hours ago** * Active installations **Fewer than 10** * WordPress version ** 6.4 or higher ** * Tested up to **7.1.4** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/walletpassbuilder/) * Tags * [Apple Wallet](https://mlt.wordpress.org/plugins/tags/apple-wallet/)[booking](https://mlt.wordpress.org/plugins/tags/booking/) [Event Tickets](https://mlt.wordpress.org/plugins/tags/event-tickets/)[google wallet](https://mlt.wordpress.org/plugins/tags/google-wallet/) [wallet](https://mlt.wordpress.org/plugins/tags/wallet/) * [Advanced View](https://mlt.wordpress.org/plugins/walletpassbuilder/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/walletpassbuilder/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/walletpassbuilder/reviews/) ## Contributors * [ walletpassbuilder ](https://profiles.wordpress.org/walletpassbuilder/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/walletpassbuilder/)