Passmint
TemplatesDocsPricingBlog
Log inGet started
Passmint

Apple and Google Wallet passes from one API. Built for people who ship.

Product
  • Pass Designer
  • Developers
  • Distribution
  • Analytics
  • Templates
  • Pricing
Developers
  • Documentation
  • API reference
  • Node SDK
  • Webhooks
Company
  • Changelog
  • About
  • Contact
  • Support
  • Security
  • Terms
  • Privacy
Social
  • GitHub
  • X

© 2026 Passmint. Built for indie makers.

Apple Wallet & Google Wallet, one API.

Issuing & managing passes

Issuing a pass

Updated June 29, 2026

Issuing turns a template into a single, real pass for one person. The template supplies the design; you supply the details that change from pass to pass.

1
Choose a template

Open the template you want to issue from. Everything about the look of the pass comes from here, so it should already be designed the way you want.

2
Pick the platform

Choose Apple Wallet, Google Wallet, or both. If you don't specify, Passmint issues an Apple pass. For a Google pass to work in live mode, your Google issuer must be connected first.

3
Add the holder

Optionally add the holder's name and email. The email lets Passmint deliver the pass automatically and ties per-person analytics to that recipient.

4
Fill in the field values

Enter the values for this specific pass: the name, seat, balance, or code. Any field marked required must have a value, or issuing won't complete.

5
Issue

Passmint generates the pass and gives you a share link and a QR code. The pass is now live and ready to send.

What you get back

Each issued pass has its own stable share link, a QR code, and a unique serial number. The link doesn't change even when you update the pass later, so you can print a QR code with confidence that it will keep working.

In test mode the pass carries a [TEST] watermark and costs nothing. In live mode it counts toward your plan once someone installs it. See test mode vs live mode.

Issuing in volume

Issuing one pass at a time in the dashboard is right for small numbers and one-offs. For larger volumes, issue passes through an integration or the API, which can create a pass automatically whenever someone buys a ticket, signs up, or joins.

Next steps

  • Share the pass by link or QR code.
  • Update it any time and the change reaches every installed copy.
  • Void it if it should no longer be valid.

Related articles

Sharing a pass: link and QR codeHow the share link behaves on phones versus desktops, and how to send it.Updating a pass after it's issuedHow over-the-air pass updates work and when they appear.Voiding a passWhat voiding does, why it can't be undone, and when to update instead.

On this page

  • What you get back
  • Issuing in volume
  • Next steps