Each brand in its own group
Apple Wallet groups passes of the same kind that share a Pass Type ID. With a set per brand, someone holding cards from two of your brands finds each in its own group.
Certificate sets
Platforms, agencies, and multi-brand teams pick a set for each pass. Every brand's cards group separately in Apple Wallet, and its name shows on Google Wallet notifications.
POST /api/passes { "credentials": "bayroast", "organizationName": "Bayroast Coffee", "barcodeValue": "BC-01250", "primaryFields": [...] }
Signed and issued as Bayroast Coffee
One team had its Apple certificate, push key, and Google issuer connected four minutes after creating the set.
What teams use separate sets for.
Apple Wallet groups passes of the same kind that share a Pass Type ID. With a set per brand, someone holding cards from two of your brands finds each in its own group.
Google Wallet names the issuer on a notification. A set with its own issuer puts that brand's name there.
A platform or an agency keeps a set for each client that needs its own identity and picks it per pass with one field. Clients that do not need one share the platform's set.
The Pass Type ID sits in your Apple Developer account and the issuer in your Google Wallet account. The passes your customers hold are signed and issued as you.
A set is one identity: an Apple certificate, its push key, and a Google issuer. Give it a short name such as bayroast. The name is how requests pick the set, and it stays fixed once created.
WalletWallet generates the signing request, you upload it in the Apple Developer portal and send back the certificate Apple issues. Add the push key so updates reach installed passes, then paste your Google issuer ID and its service account key. The setup guide has a screenshot for every step.
Send "credentials": "bayroast" with the create request, or choose the set under Sign with in the Pass Editor. The pass is signed and issued as that identity and keeps it for life.
Starting from zero? Follow the guides to get a Pass Type ID certificate from Apple and open a Google Wallet issuer account.
How the first accounts set theirs up.
One Apple Developer account and one Google issuer cover all seven sets. Each client gets its own Pass Type ID, so one client's cards never group with another's.
An integrator with seven sets
Register the Pass Type ID in the Apple Developer portal before you create the set. The certificate and the push key were then in place two minutes after the set was created.
A software company
A pass keeps the set it was created with. Issue one test pass on the new set, then create every card after that on it.
A food company
A Pass Type ID certificate from your Apple Developer account. The Pass Type ID, team ID, and organization name are read from the certificate when you upload it. How to get one.
The APNs key that pushes updates to installed passes. A set without one signs passes correctly and can never update them, so add it with the certificate.
Your Google Wallet issuer ID and a service account key. One issuer can serve several sets in your account. How to get one.
The Apple key pair is generated on our side, and the private key, the push key, and the Google key are stored encrypted and never shown again.
A set with only an Apple certificate issues Apple passes, and a set with only a Google issuer issues Google passes. Add the other half any time.
The set is chosen when the pass is created and stays with it through every update. An update cannot move a pass to another set.
Deleting a set or replacing its certificate with one for another Pass Type ID is refused while live passes depend on it, with the count of passes it would strand.
Pass Manager, the pass list, and the CSV export show each pass's set and filter to one, so a client's cards are one click away.
Create sets, upload certificates, and connect issuers with your API key, so a platform can onboard a client without opening the dashboard. Your own certificates in the docs.
Something else? Write to us from the chat in the dashboard, or at hello@walletwallet.dev.
For Apple, a membership in the Apple Developer Program, where you register a Pass Type ID and create its certificate and a push key: how to create an Apple Developer account. For Google, a Google Wallet issuer account and a service account with access to it: how to create a Google Wallet issuer account. Once you have both, the setup guide in the dashboard connects them to a set.
No. A pass keeps the set it was created with, because Apple ties an installed pass to its Pass Type ID. It keeps working and updating on that set. Create new passes on the other set and send those links to the people you want to move.
No. One set can issue cards for every business on your platform, each with its own name, logo, and colors. Give a client its own set when its cards should group separately in Apple Wallet or its own name should show on Google notifications.
They keep serving, updating, and pushing. A pass created with a set stays on it after a move to Free. Only new passes that name a set are refused until the plan is back.
Pro at $39 a month and every plan above it, and the trial. An account can hold as many sets as it needs.
Free under 1,000 passes a month. $39 flat above that, with a 7-day trial on every new account.