It's Thursday afternoon and you have two pricing pages open. One shows four plans in a row. The other shows a sum: number of pass templates, plus number of active passes, equals your monthly price. You have 5,000 gym members, four pass designs, and a manager who wants a number by Friday.
That second page belongs to PassNinja. If you've searched for a wallet pass API, you've seen it, usually next to the word NFC. This post sets it beside Passmint on the things that decide a project: what each one bills you for, whose certificate signs the pass, what happens at the reader, and how the API feels. PassNinja is the better answer for one kind of project, and we'll say which.
Every PassNinja figure below comes from its own pricing page, documentation and GitHub repositories, read on 20 November 2026. We're a competitor, so check anything that matters to you against the source.
Two products in one category, built for different doors
Both companies sell the same basic thing. You design a template, call an API with a few field values, and get back a pass your customer can add to Apple Wallet or Google Wallet. Neither asks you to assemble a .pkpass by hand or run the web service Apple uses for updates.
The difference is what each one was built around. PassNinja's homepage opens with the line "PassNinja helps build NFC experiences across mobile." It says it has handled NFC scans since 2018, and its GitHub repositories live under an organization called Flomio. The site sells NFC readers next to the API, lists reader certification as a professional service, and files eight of its tutorials under hardware. PassNinja is a tap-to-redeem company that also issues passes.
Passmint starts from the pass and the code that issues it. It's a REST API with a typed Node SDK, test and live keys, webhooks, a visual template designer, and a free scanner app that checks barcodes at the door. It doesn't sell hardware and it doesn't do NFC.
So before you compare prices, answer one question. Will your customers tap a phone on a reader, or show a code to a scanner? If it's the tap, most of this post is context and you can skip to the NFC section. If it's the code, the pricing section is the one to read.
What each one puts on the invoice
PassNinja's formula has two parts. Its pricing page lists $21 a month per pass template, and $0.11 a month per active pass. It defines a template as the design all your installed passes share, and an active pass as "any pass that has been installed and has not yet expired in a given month." Every verified account starts with $10 in credits.
Delivery is extra. If you include a phone number or an email address when you create a pass, PassNinja will send it for you and charge per message. The pricing page FAQ says $0.10. The API reference says $0.05 for a text. We don't know which is current, so ask before you budget for it.
Passmint prices by plan. You pick the one that covers your active passes.
| Plan | Price per month | Active passes | Templates |
|---|---|---|---|
| Free | $0 | 10 | 3 |
| Hobby | $15 | 500 | 5 |
| Pro | $49 | 5,000 | 25 |
| Scale | $149 | 25,000 | 100 |
Paid plans let you run past the included count at $0.01 per extra active pass, up to twice the included amount. Free is for building. It gives you the full API in test mode, and live issuance starts on Hobby.
Here's the same program on both meters, with one template and every pass installed.
| Passes | PassNinja at list price | Passmint |
|---|---|---|
| 100 | $32 | $15 |
| 500 | $76 | $15 |
| 5,000 | $571 | $49 |
| 25,000 | $2,771 | $149 |
The PassNinja column is $21 plus $0.11 a pass. We found no published volume discount, though large accounts may get one by asking.
The meters also count different things, and this cuts in PassNinja's favor. PassNinja bills a pass only while it sits in a wallet. Passmint counts a pass from the moment you issue it until you void it, installed or not. If you issue 5,000 passes and a third of your members never tap the button, PassNinja bills you for the two thirds who did. Passmint counts all 5,000.
Templates cut the other way. On PassNinja each design is a $21 line whether or not anyone installs it. On Passmint a handful come with the plan.
A 5,000-member gym, priced both ways
Consider a representative gym group, based on an anonymized example. It has 5,000 members and four pass designs: a membership card, a guest pass, a class pack and a staff badge. Assume 60 percent of members install the pass, which is our assumption and not a measured rate. That gives you 3,000 installed passes.
On PassNinja, four templates cost $84. The 3,000 installed passes cost $330. The bill is $414 a month.
On Passmint, all 5,000 issued passes count as active. Pro covers 5,000 passes and 25 templates for $49.
You can rerun that with your own numbers. The script below encodes both price lists as they stood on the day we read them.
const PLANS = [
{ name: 'Hobby', price: 15, included: 500 },
{ name: 'Pro', price: 49, included: 5000 },
{ name: 'Scale', price: 149, included: 25000 },
]
// $21 per template, plus $0.11 per installed, unexpired pass.
function passNinja(templates, installed) {
return templates * 21 + installed * 0.11
}
// Cheapest plan that covers the issued passes, with $0.01 overage
// allowed up to twice the included count.
function passmint(issued) {
const bills = PLANS.filter((p) => issued <= p.included * 2).map(
(p) => p.price + Math.max(0, issued - p.included) * 0.01,
)
return Math.min(...bills)
}
const members = 5000
const installRate = 0.6
console.log(passNinja(4, members * installRate).toFixed(2)) // 414.00
console.log(passmint(members).toFixed(2)) // 49.00Push the install rate down and the gap narrows. It doesn't close. With one template, PassNinja's formula starts at $21 before the first pass, which is already above Passmint's $15 Hobby plan. At list prices we couldn't find a volume where the PassNinja sum comes in under the Passmint plan that covers the same passes.
That isn't the whole comparison, because the two bills don't buy the same thing. PassNinja's price includes NFC and the option to sign with its certificate. If you need either, a cheaper plan that lacks them is no bargain.
Whose certificate signs the pass
This is the second real difference, and it matters more than it looks on launch day.
PassNinja's pricing FAQ answers the question "I don't have an NFC certificate, can I still make passes with your service?" with a yes. It says customers can "sign and issue NFC passes using our certificate," and that you can later swap in your own Pass Type ID or Google collector ID. Its homepage promises a maintenance-free service, and tells you to "never worry about expiring certificates."
For a first launch, that removes a real chore. You don't create an identifier in Apple's developer portal, generate a signing request, or put a renewal date in your calendar. You sign up and issue.
Passmint splits it by mode. Test passes are signed with Passmint's certificate, so you can go from an API key to a pass on your own phone with no Apple account. For live Apple passes you connect a Pass Type ID certificate from your own developer account. Passmint generates and holds the private key, bundles Apple's intermediate certificate, signs every pass and shows the expiry date in the dashboard. You still own the renewal, and an expired certificate stops every update.
So PassNinja gets you live faster. What you give up is ownership on day one. An Apple pass is identified by its pass type identifier and serial number, and it only accepts updates signed for that same identifier. Passes issued under a vendor's identifier belong to that identifier. Before you rely on the later swap, ask PassNinja what happens to passes already sitting in wallets when you move to your own. We didn't find that answer in the pages we read.
If your brand's name is on the pass and you expect the program to outlive any one vendor, start with your own identifier. If you're running a pilot or a single event, borrowing one is a reasonable shortcut.
NFC is where PassNinja pulls ahead
If your project needs a tap, pick PassNinja. Passmint's hosted API doesn't issue NFC passes today.
NFC is hard for reasons that have little to do with code. Apple's documentation for the pass format says "Adding NFC to a Pass requires a special entitlement issued by Apple." Its page on contactless loyalty passes says you'll need to request an NFC certificate, and that the terminals in your stores "must already accept Apple Pay and be certified for VAS," the Value Added Services protocol. Google's version is Smart Tap, and its overview says the NFC terminal must be compatible with the Smart Tap protocol.
That's a lot to line up before the first tap. You apply to Apple, you wait, and you may find out your readers aren't certified.
PassNinja's product is built to get you past that:
- The certificate. You can issue NFC passes under PassNinja's certificate while you sort out your own.
- The payload. The API reference documents an endpoint that decrypts what a reader receives, for Apple VAS and for Google Smart Tap.
- The readers. Its hardware page lists eight NFC readers from $99 to $425, and the FAQ says the service works with any Apple VAS or Google Smart Tap compatible reader, so you aren't tied to the ones it sells.
- The fleet. Premium accounts get endpoints for registering readers, issuing reader tokens and recording scans.
One limit is worth knowing. The same FAQ says opening doors with Apple passes is typically not possible on the self-service product, and tells you to contact support. Access control on iPhone is a separate Apple program, so don't assume a loyalty-style NFC pass will open a turnstile.
Passmint's answer at the door is the barcode. The free Passmint Scanner app for iPhone and iPad reads QR, PDF417, Aztec and Code 128, works offline, and syncs when the phone reconnects. The same scanner API is open to a till or a kiosk. For tickets, check-ins and most loyalty programs, that's enough. For a tap at a payment terminal, it isn't.
The two APIs, side by side
Both APIs are small enough to learn in an afternoon. Here's the create call on each.
PassNinja, from the README of its Node library:
const { PassNinjaClient } = require('@passninja/passninja-js')
const passNinjaClient = new PassNinjaClient(accountId, apiKey)
const pass = await passNinjaClient.pass.create(
'ptk_0x14', // pass template key
{ discount: '50%', memberName: 'John' },
)Passmint, from the quickstart:
import { Passmint } from "@passmint/node"
const passmint = new Passmint({
apiKey: process.env.PASSMINT_API_KEY!,
})
const pass = await passmint.passes.create({
templateId: "tmpl_xxx",
holderEmail: "alice@example.com",
fieldValues: { seatNumber: "A12", section: "Floor" },
})
console.log(pass.url)The shape is the same. A template identifier and a bag of field values go in, and a pass comes out. The differences show up around that call.
Languages. PassNinja's SDK page lists Python, Ruby, Node.js, Swift, Java, C# and PHP, plus a command-line tool. Passmint ships one typed SDK, for Node 20 and later, Bun and Deno, and an OpenAPI spec for everything else. If your backend is Ruby or PHP and you want an official client, PassNinja has one and Passmint doesn't.
Authentication. PassNinja sends two headers on every request, an API key and an account ID. Passmint uses one bearer key. A pmk_test_ or pmk_live_ prefix sets the mode, and you can limit a key to scopes such as passes:write and give it an expiry.
Updates. PassNinja documents both PATCH and PUT on a pass. PATCH changes the fields you send. PUT replaces the pass, and its docs warn that fields you leave out "will revert to their pass template default values." Reach for the wrong verb and you'll wipe a member's points balance. Passmint has PATCH only, and you can send an idempotency key so a retry never applies twice.
Deleting. On both platforms DELETE voids the pass and stops it counting toward your bill. PassNinja's docs note that it doesn't remove the pass from the phone and can't be undone.
Webhooks. PassNinja's API reference documents webhooks in the CloudEvents format, with events for a pass being created, installed, updated, uninstalled, deleted, expired and scanned, and up to 15 delivery attempts across about 24 hours. They require a premium account, and the docs point you to pricing without stating a figure. In our October roundup we said we couldn't confirm customer webhooks on PassNinja. They are documented, so consider that corrected. Passmint includes signed webhooks on every plan, Free included.
Templates from code. Creating a PassNinja template through the API needs an entitlement its docs tie to premium and enterprise plans. Otherwise you build templates in its editor. Passmint lets any key with the templates:write scope create and edit them.
A test mode. We didn't find a sandbox or test mode in PassNinja's API reference. The $10 credit covers your first experiments. Passmint's test keys work on every plan, and test passes install on a real phone.
Who should pick which
Pick PassNinja when one of these describes you.
Your customers will tap. NFC loyalty at a payment terminal, contactless check-in, anything that depends on Apple VAS or Google Smart Tap. This is PassNinja's home ground.
You can't wait on Apple. If the certificate is the thing between you and a demo on Monday, issuing under PassNinja's certificate gets you there.
You want readers and software from one vendor. One company to call when a tap fails is worth money, more so when nobody on your team has configured a reader before.
Your stack isn't JavaScript. Seven SDK languages against one.
Your data can't leave your network. PassNinja says its software can be licensed to run inside your own infrastructure. Passmint's hosted platform has no on-premises version, though the open-source passmint library lets you sign passes on your own servers.
You want PassNinja to send the pass. Text or email delivery is one field on the create call.
Pick Passmint when the list looks more like this.
Your passes are scanned by barcode. Tickets, memberships, coupons and most loyalty cards. You don't pay for NFC plumbing you won't use.
Your volume is past a few hundred passes. A flat plan with a one-cent overage is easier to forecast than eleven cents a pass. See the pricing page for the current plans.
You run more than one design. Five templates come with Hobby and 25 with Pro.
You want webhooks and a test mode from the first day. Both are on the Free plan, so you can wire the whole integration before you spend anything.
You want to own your identifier from the start. Your Pass Type ID, in your Apple account, with the private key managed for you.
If you're weighing more than these two, the wallet pass API landscape covers seven platforms on the same terms, and the comparison with PassKit goes deeper on the broadest one.
What we couldn't verify
We didn't run PassNinja's API against a real device or a real reader, so everything here about its behaviour comes from its own pages. We couldn't find the price of a premium account, a published volume discount, a rate limit for ordinary API calls, or what the certificate swap does to passes already installed. The two message prices we found disagree. And no page we read carries a pricing effective date, so the figures could change the week after this is published. If one of them is wrong, tell us and we'll correct it with the date.
The quickest way to settle it is to issue one pass on each. PassNinja gives you $10 in credit. The Passmint quickstart gets a test key issuing a signed pass in about five minutes, with no Apple account and no card. Put both passes on your own phone, change a field, and see which update arrives first. More at Passmint.
Primary sources
Common questions
Technical content writer, Passmint
Julio is a technical content writer at Passmint. He writes about Apple PassKit, the Google Wallet API, and what breaks when wallet passes meet production traffic.
More from Julio Song →