Passmint
TemplatesIntegrationsDocsPricing
Log inGet started
Passmint

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

  • GitHub
  • X
Product
  • Pass Designer
  • Developers
  • Distribution
  • Analytics
  • Templates
  • Integrations
  • Pricing
Resources
  • Free tools
  • Wallet card generator
  • pkpass validator
  • Pass anatomy
  • Live demo
  • Blog
  • Glossary
  • Compare
Developers
  • Documentation
  • API reference
  • Node SDK
  • Webhooks
  • MCP server
Company
  • Changelog
  • About
  • Contact
  • Support
  • Security
  • Terms
  • Privacy

© 2026 Passmint.

Apple Wallet & Google Wallet, one API.

Apple Wallet & certificates

Do I need an Apple Developer account?

Updated September 15, 2026

Apple Wallet passes have to be cryptographically signed, and Apple's developer terms say who may sign them: the brand on the pass. Every live pass must be signed with a Pass Type ID certificate that belongs to the organization issuing it. A platform can't legitimately sign your commercial passes with its own certificate, whatever its pricing page says.

The short answer

  • Building and testing? No Apple Developer account needed. Test passes are signed with Passmint's own certificate and carry a [TEST] watermark.
  • Issuing live passes to real customers? You need an Apple Developer Program membership and your own Pass Type ID certificate. This applies on every Passmint plan, including Free.

What Passmint does for you

Owning the certificate doesn't mean doing the certificate work. Passmint handles everything around it:

  • Generates the private key and keeps it encrypted. You never download a .p12 or touch Keychain Access.
  • Produces the signing request you upload to Apple, then pairs Apple's .cer with the key it is holding.
  • Signs every pass and bundles the correct WWDR intermediate.
  • Pushes updates to installed passes through Apple's push service.
  • Reminds you before expiry. Organization owners get an email 30, 14, 7, and 1 day out, and the dates are in Settings → Certificates, so renewal is the same short exchange rather than a surprise.

Your part is a one-time exchange with Apple's developer portal that takes a few minutes. Apple charges an annual fee for the Developer Program.

Templates don't care which certificate signs them. Build everything in test mode first, then connect your certificate and switch to live. Nothing in the design or the API calls changes.

When you're ready, follow set up your Apple Pass Type ID certificate.

Related articles

Set up your Apple Pass Type ID certificateGenerate a signing request, create a Pass Type ID at Apple, and upload the result.The Passmint test certificateWhat Passmint's built-in signing certificate is, and why it only signs test passes.

On this page

  • The short answer
  • What Passmint does for you