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.

Apple Wallet & certificates

The default Passmint certificate

Updated June 29, 2026

Every Apple Wallet pass must be signed. So that you can issue passes without any setup, Passmint provides a built-in certificate that it uses on your behalf.

When it's used

  • Always in test mode. Test passes are signed with Passmint's certificate so you can build and try the full flow before arranging your own. These passes carry a [TEST] watermark.
  • In live mode when you haven't connected your own certificate, depending on your plan. This lets you ship real Apple passes quickly.

If you've set up your own Apple Pass Type ID certificate, Passmint uses that for your live passes instead.

What it means in practice

Passes signed with the default certificate are signed under Passmint's Apple identity rather than yours. For many use cases that's completely fine. If you want live passes signed under your own Apple Pass Type ID, that's available on the Pro and Scale plans. See do I need an Apple Developer account?

Moving from the default certificate to your own doesn't require redesigning your templates. The certificate is chosen at the account level, so your passes keep their look.

Related articles

Do I need an Apple Developer account?When Passmint's built-in certificate is enough, and when to use your own.Set up your Apple Pass Type ID certificateGenerate a signing request, create a Pass Type ID at Apple, and upload the result.

On this page

  • When it's used
  • What it means in practice