Passmint vs PassKit: Pricing, API Design, and Which One Fits Your Wallet Pass Project

You have a loyalty card to ship by the end of the quarter, and a browser tab open on PassKit's pricing page. The page does not give you a price. It gives you a model, a calculator and a rate card, and you now need an afternoon to work out what 3,000 members will cost.

That is a fair way to start a comparison. PassKit is the established name in this space, and any developer searching for a wallet pass API lands on it sooner or later. This post sets it beside Passmint on the things that decide a project: what it costs at your size, how the API feels, who owns the Apple certificate, and which one you should pick. Where PassKit is the better answer, we say so.

Two companies with almost the same name as Apple's framework

Start with the naming trap. Apple PassKit is the framework and file format behind Wallet. PassKit.com is a company, founded in 2012 by its own account, that sells a hosted platform for designing, issuing, updating and analyzing Apple Wallet and Google Wallet passes. When you search for a way to issue passes, the two blur together.

Passmint sits in the same category as PassKit.com. You describe a pass, call an API, and get back something a customer can add to Apple Wallet or Google Wallet. You do not hand-assemble a .pkpass, run a web service for Apple's registration protocol, or send your own APNs pushes. If you want the long version of what that saves you, our post on what passkit-generator leaves you to build lists the pieces.

So the real question is not hosted versus self-built. You have already decided to buy. You are choosing between two hosted platforms, and they were built for different readers.

What each one is built around

PassKit is a broad platform. Its documentation describes REST and gRPC APIs, official SDKs with QuickStart examples on GitHub, and separate solution areas for membership and loyalty, coupons, flights and event tickets. It has APIs for pass templates, certificates, image assets, analytics and SmartPass distribution links. Passes can also be issued through a batch CSV upload or the dashboard, with no code at all.

That breadth is the point. If you run a large program with marketing staff designing templates, analysts reading dashboards and engineers calling gRPC from a typed client, PassKit has a place for each of them.

Passmint is narrower on purpose. It is a REST API with templates, webhooks and test and live API keys, aimed at the developer who wants to issue a pass from a handler and move on. You can read the quickstart in one sitting. The cost of that focus is real. You will not find the same range of solution-specific APIs or the same depth of tooling for non-engineers.

A fair way to put it: PassKit is a wallet platform you adopt, and Passmint is a wallet API you call. Which one you want depends on how many people on your team will touch it.

The pricing models do not line up

PassKit prices in two parts. The platform fee depends on how many team members you have, and it includes the first 250 multi-use passes and 250 single-use passes each month. After that, each pass is billed at a rate that drops as volume climbs. Its rate card, read this month, lists the platform fee like this:

Multi-use passes, the loyalty and membership kind, start at $0.045 per pass between 251 and 2,500 and fall to $0.0340 between 2,501 and 5,000. Single-use passes such as coupons and tickets cost more per pass at each band. Billing is monthly in arrears, and there is a 45-day trial that does not ask for a payment method.

Passmint prices in one part. You pick a plan by how many active passes you need at once.

Paid plans let you run over the limit at $0.01 per extra active pass, up to twice your included amount. Free has a hard cap and no overage.

Run the same small program through both. Say you have 500 loyalty members and one developer.

On PassKit, the platform fee is $39.50. The first 250 passes are included, and the other 250 land in the first band at $0.045 each, which is $11.25. That is about $50.75 a month. On Passmint, 500 active passes fits inside Hobby at $15.

Now take 5,000 members. On PassKit that is $39.50 plus the per-pass bands. Depending on whether each band prices only the passes inside it or the whole volume, the bill lands somewhere around $200 to $225 a month for one team member. Passmint's Pro plan is $49 for the same count.

Do not read those as a clean win, because the two companies count different things. PassKit bills multi-use passes by records created, minus deletions. Passmint counts active passes, meaning live, non-voided passes installed in at least one wallet. A program with heavy churn or many passes that never get installed will look different on each meter. Your own numbers matter more than ours, so run your member count through PassKit's calculator and through Passmint's pricing page before you decide.

Two things do hold up. PassKit's cost grows with your team size as well as your volume, while Passmint's grows with installed passes only. And both give you a way in before you pay, PassKit through its 45-day trial and Passmint through a free plan.

What happens after the first install

Issuing the pass is the easy half. The half that decides whether a program feels alive is what happens on day 30, when a balance changes or a gate moves and the pass on a customer's phone has to follow.

Both platforms take that on. PassKit says passes update in real time through its API or dashboard, typically within seconds, using Apple's and Google's push services. Passmint runs the same pipeline for you, which means the registration endpoints Apple defines, the APNs push that tells a phone to check for changes, and the Google Wallet side. You change a field and the platform does the rest.

This is the part to test during your trial, because it is where self-built stacks stall and where a hosted platform should be earning its fee. Change a field on an installed pass, lock the phone, and time how long the new value takes to appear. If you have ever chased a pass that would not refresh, our guide to why an Apple Wallet pass is not updating shows what to check when it fails.

The Apple certificate is yours either way

Here is a claim you will see in some comparison pages, and it is worth treating with suspicion: that one platform spares you from Apple's certificate setup. For live Apple Wallet passes, neither one does.

PassKit's own FAQ says Apple Wallet requires you to add your own pass certificate, and that Google Wallet has no equivalent requirement. Its help center lists three files for the Apple credentials: a Pass Type ID certificate, its matching private key and Apple's WWDR intermediate. Passmint works the same way. Apple does not allow one company to sign another company's passes with a shared certificate, so you connect a Pass Type ID certificate from your own developer account.

That means the chores that come with it stay with you on both platforms. You create the identifier, generate the signing request, export the key, and renew the certificate before it lapses. Apple's certificates expire after a year, and an expired one stops new passes and every update. We walk through the full failure in what breaks when your certificate expires, and the setup itself in the certificate chain explained.

So when you compare the two, do not give either one credit for certificate setup. Give credit for what happens after it, which is signing, serving the update protocol and sending the push, because that is where a hosted platform earns its fee.

Where PassKit is the better pick

If any of these describe you, look hard at PassKit.

You need non-engineers in the tool. Marketing designing templates, support staff looking up a member, a campaign team reading analytics. PassKit has a dashboard and analytics APIs built for that, and Passmint is lighter there.

You want gRPC and a typed client. PassKit documents gRPC as a first-class path and publishes official SDKs. If your services already speak gRPC, that fits cleanly, and a plain REST API will feel like a step sideways.

You issue in bulk from a spreadsheet. A batch CSV upload means a program can launch before an engineer writes a line of integration code.

You need the widest range of pass types and solutions. PassKit documents dedicated APIs for flights, event tickets, coupons and membership. If your project crosses several of those, the structure helps.

You value a long track record. A company that has issued passes since 2012 has met more edge cases than most. That counts for something when a pass program is customer-facing.

Where Passmint is the better pick

The other side is just as specific.

You are one developer or a small team. You do not pay for seats, and the entry point is $15 a month for 500 active passes. That price shape suits a side project, a pilot, or a single event.

You want one REST call and a webhook. You describe a pass, post it, and get something both wallets can install. Test and live API keys keep the development loop quick, and webhooks tell you when state changes.

You want to start without a card. Free covers 10 active passes with test-mode API access, which is enough to wire an integration end to end before you spend anything. Note that live issuance starts on Hobby, so the free tier is for building, not for launching.

You want a path that is not a lock-in. The open-source passmint package signs passes for both wallets from Node, Workers, Deno or Bun. If you ever want to self-host the generation step, the library is there, and the pass format is Apple's and Google's rather than ours.

How to decide in an afternoon

Skip the feature matrix and run three checks.

First, count the people. If more than two or three of them will use the tool daily, price PassKit's team tiers and weigh its dashboard seriously. If it is just engineers, the seat-based fee buys you less.

Second, run your real volume. Take your expected members, split them into multi-use and single-use, and put them through PassKit's calculator. Then check the same count against Passmint's plans. Remember the meters differ, and use your churn rate to adjust.

Third, issue one pass on each. Both give you a way to test without paying. Set up the Apple certificate once, then see how long it takes to get a real pass onto your own phone, change a field, and watch the update arrive. Whichever one gets you there with less friction is the one your team will keep using.

If the answer is Passmint, the quickstart takes you from an API key to an installed pass, and the free plan means you can find out before you spend anything. Start at Passmint.

Primary sources

• Apple: Pass Type ID certificate expiration versus revocation
• Google Wallet API documentation
• PassKit gRPC SDK for PHP