addToWallet.co
Workspaces
Pricing
API Docs
Tutorial Blog
Tools
Google Sheet Extension
PDF to Pass
Image to Pass
QR Code Generator
Barcode Generator
Integrations
© 2026 Hazelnut Ventures LLC. All Rights Reserved.
FAQsTrustContact Us
Sugar Calendar logo

Sugar Calendar

WordPress

Every ticket sold through Sugar Calendar becomes an Apple or Google Wallet pass, so it sits on your attendee's phone instead of in an email they have to find at the door.

Download pluginVersion 1.0.0 · 68 KB · .zip

In WordPress go to Plugins → Add Plugin → Upload Plugin, choose the file and activate it.

How it works

  1. 1Install the plugin and paste your AddToWallet API key.
  2. 2Someone buys a ticket to one of your Sugar Calendar events.
  3. 3Their ticket receipt offers Add to Apple Wallet and Add to Google Wallet.

What your attendee sees

The wallet buttons are added directly under Sugar Calendar's ticket receipt, the page buyers land on after checkout and reach again from their receipt email, so the checkout flow is unchanged.

A Sugar Calendar ticket receipt showing Add to Apple Wallet and Add to Google Wallet badges for each ticket
  • Both wallets are offered every time, so someone buying on a laptop can still get the pass onto whichever phone they carry.
  • An order for several tickets shows a set of badges per ticket, labelled with the ticket number and the holder's name.
  • Nothing else on the receipt changes.

What you configure

One settings screen in wp-admin, with a live preview of the pass and tabs for your tickets, the instructions and support.

The plugin settings screen in WordPress admin, showing the Settings, Tickets and passes, Instructions and Support tabs beside a live preview of the pass
API key
Stored on your server and never sent to the browser. Paste it once; leave the replace field blank to keep it.
When to issue
Create passes as soon as the receipt loads, or only when the buyer presses the button.
Heading
The line above the wallet badges on the receipt. Leave blank for none.
Button label
The wording buyers see before the wallet badges load.
Logo
Shown at the top of the pass. Falls back to your site icon if left blank.
Hero image
The wide banner across the pass. Optional, and omitted when blank.
Background colour
The pass colour. Text switches between black and white automatically for contrast.
Barcode
QR, Aztec, PDF417 or Code 128. It encodes the ticket code Sugar Calendar printed on the emailed ticket, so the two always match.
When to expire a pass
Expire passes when an order is refunded, moved to the trash, or both.

What you get

  • Apple and Google buttons on the Sugar Calendar ticket receipt, so nobody is stuck on the wrong device
  • One pass per ticket, each with its own barcode, so a group order gets everyone through the door
  • The barcode is Sugar Calendar's own ticket code, the same one on the emailed ticket
  • The pass carries the event, the date, the time and the venue, pulled from Sugar Calendar
  • Refunded or trashed orders expire their passes straight away
  • Choose the barcode: QR, Aztec, PDF417 or Code 128
  • Match the pass to your brand with a logo, hero image and colour

Requirements

WordPress
5.8 or newer
PHP
7.4 or newer
Sugar Calendar
Lite or Pro, 3.12 or newer (tested against 3.14), with tickets turned on; paid tickets need Stripe connected
AddToWallet
An account with credits available

Good to know

Each pass uses one credit, so an order for four tickets uses four, and reloading the receipt never charges twice. If your balance runs out, ticket sales carry on as normal but no pass is created, so check that first if passes stop appearing. Sugar Calendar needs a Payment Success Page set, since that receipt is where the buttons go. RSVPs have no ticket to put on a pass, so only ticket orders get one, and moving an event does not update passes already issued.