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

Set up your Apple Pass Type ID certificate

Updated June 29, 2026

This is a one-time setup that lets Passmint sign Apple Wallet passes under your own Apple identity. You'll move a certificate between Passmint and Apple's developer portal. Passmint generates the private parts for you, so you never handle key files by hand.

Before you start, you'll need an active Apple Developer Program membership.

1
Start a certificate in Passmint

Go to Settings → Certificates and begin a new Apple certificate. Passmint generates a certificate signing request (a CSR) for you and keeps the matching private key encrypted on your behalf.

2
Download the signing request

Download the CSR file Passmint produced. This small file is what Apple needs to issue a certificate. It's safe to download and contains no secret.

3
Create a Pass Type ID at Apple

In the Apple Developer portal, create a new Pass Type ID if you don't have one, then create a certificate for it and upload the CSR you just downloaded. Apple issues a certificate file in return.

4
Download the certificate from Apple

Download the issued certificate. It's a .cer file. This is the public half that pairs with the key Passmint is holding for you.

5
Upload it back to Passmint

Return to Settings → Certificates and upload the .cer. Passmint checks that it matches the signing request, reads the Pass Type ID and team details from it, and activates it.

Once activated, new live Apple passes are signed with your certificate. Templates don't need changing; the certificate applies at the account level.

Upload the certificate to the same account that generated the signing request. Passmint pairs the certificate with the private key it created for that request, so a certificate from a CSR generated elsewhere won't activate.

After setup

  • Apple certificates expire. Passmint will prompt you before yours does; see renewing or replacing a certificate.
  • If activation fails, the usual cause is uploading a certificate that doesn't match the signing request. Start a fresh certificate and download the new CSR rather than reusing an old one.

Related articles

Do I need an Apple Developer account?When Passmint's built-in certificate is enough, and when to use your own.Renewing or replacing an Apple certificateWhat expiry means for your live passes and how to swap in a new certificate.The default Passmint certificateWhat Passmint's built-in signing certificate is and when it's used.