WalletPassBuilder – Passes for Apple Wallet and Google Wallet

Description

WalletPassBuilder connects your site to your WalletPassBuilder 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; 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.
• 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 and privacy policy.