PassSlot vs WalletWallet API

PassSlot has been generating Apple Wallet passes since 2012, making it one of the longest-running services in this category. WalletWallet is newer, narrower, and cheaper. The two sit on opposite sides of two structural axes: who handles the Apple certificate, and how much of the pass lifecycle is bundled into the platform.

PassSlot is a fuller product, with a no-code pass designer, an iOS SDK, iBeacon support, a scanner app for redemption, and built-in payment integration via Stripe and PayPal. WalletWallet is a REST API for Apple Wallet passes, served sub-200ms from Cloudflare’s global edge, with POST to create and PUT to update with APNs push. The same .pkpass opens in Google Wallet on Android, and it’s $19/month flat. It doesn’t ship NFC, iBeacon, a scanner app, or built-in payments.

The price difference at the top tier is real. PassSlot’s Professional plan is $99/month for 100,000 passes; WalletWallet is $19/month for the same volume. But that’s not the whole picture, because PassSlot bundles features we don’t ship yet, and PassSlot requires you to bring your own Apple Developer certificate while we sign with ours.

This page lays out both products fairly. If PassSlot is the right pick for you, we say so.

A note on activity

We checked PassSlot’s site on 2026-05-20. The pricing page, signup, login, REST API, and support center are all live and reachable. The copyright reads ”© 2012-2026.”

That said, the most recent post on PassSlot’s blog is from November 2013, and the docs and pricing have shown little structural movement in years. The product looks stable rather than actively iterating.

If you’re evaluating PassSlot, that’s not necessarily a problem, since a stable, dormant product can still be the right call for a workload that doesn’t need new features. We mention it once here so you can factor support responsiveness and roadmap expectations into your decision; we won’t repeat it.

Summary

PassSlot has the broader feature set, with a no-code pass designer, iBeacon, an iOS SDK, a free scanner app for redemption, payment integration, and webhooks. It charges $29/month for up to 10,000 passes and $99/month for up to 100,000. You bring your own Apple Pass Type ID and signing certificate for commercial passes, which means an Apple Developer account at $99/year on top.

WalletWallet is a REST API for Apple Wallet passes, served sub-200ms from Cloudflare’s global edge. POST creates a signed .pkpass; PUT updates it and pushes the refresh over APNs. The same file opens in Google Wallet on Android (live updates on Google are on the roadmap). $19/month flat for up to 100,000 passes; 1,000/mo free, indefinite. We sign with our certificate, so there’s no Apple Developer account.

If you need iBeacon, a scanner app, payment integration, or a no-code designer, PassSlot is the better pick today. If you only need Apple-Wallet generation and updates, want a flat $19/mo bill, and don’t want to deal with Apple Developer Program enrollment, WalletWallet is the better pick.

What PassSlot is

PassSlot is a Switzerland-based mobile wallet platform from Simplysoft GmbH, founded in 2012. It bundles a REST API, an iOS SDK, a no-code pass designer, a redemption scanner, pass updates and push notifications (Apple), and iBeacon-triggered display into one tiered subscription.

The product model is template + pass. You define a template (either via the dashboard’s visual designer or via the API) and then create individual passes by filling placeholder values. Each tier has limits on how many Pass Type IDs you can register (1 / 5 / 20 from Free / Basic / Pro), but unlimited API calls and unlimited pass updates across all paid tiers.

For commercial use, PassSlot requires customers to upload their own Apple Pass Type ID and signing certificate, which means you need an Apple Developer Program membership ($99/year). PassSlot does provide test certificates for evaluation, but passes signed with those carry a legal notice on the back, so they’re not suitable for production.

What WalletWallet is

WalletWallet is a REST API for Apple Wallet passes, served from Cloudflare’s global edge. Two write endpoints (POST, PUT), one read endpoint, no template or project state on our side.

• Apple Wallet, fully. POST /api/pkpass creates a signed pass and returns an X-Serial-Number header. PUT /api/pkpass/{serial} updates the pass and fans out an APNs push to every installed device. Identical bodies are free no-ops.
• Google Wallet via .pkpass conversion on Android. The signed pass we return opens directly in Google Wallet on Android, so one API call lands a pass in both wallets. Live push updates on Google Wallet are on the roadmap, not shipped.
• Fast and cheap. Sub-200ms pass generation and instant push, served from Cloudflare’s co-located global edge. $19/mo flat for up to 100,000 passes; 1,000/mo free, indefinite. We sign with our certificate, so no Apple Developer account is required.
• Everything a pass needs. Geofencing (up to 10 locations surface the pass on the lock screen near a coordinate), barcode formats (QR, PDF417, Aztec, Code128), expirationDays, six color presets free plus custom hex on Pro, brand assets (logoURL / thumbnailURL / stripURL / iconURL), changeMessage templates for lock-screen banners, organizationName as the notification title. See /llms.txt for the full list.
• Start simple, stay simple. The Pass Editor on the homepage previews every pass change live, including push updates. Tune the fields, colors, and images, watch the pass update, then copy the equivalent code and run it. The dashboard editor handles signed-in push-to-installed-passes too.
• Agent-ready docs. Point Claude or any LLM at /llms.txt and it knows how to call the API.
• Usable by non-developers. The Pass Editor doesn’t require writing code to design or test a pass.

Side-by-side code

PassSlot is a two-step flow: create a template (once, in the dashboard or API), then create a pass against the template by passing placeholder values.

POST https://api.passslot.com/v1/templates/:id/pass
Authorization: <PassSlot key>
Content-Type: application/json

{
  "firstName": "John",
  "lastName": "Doe",
  "memberSince": "2012"
}

The response is JSON containing the pass URL, which the user opens in iOS to add the pass to their wallet:

{
  "serialNumber": "a187b8e0-e9ee-4b6f-869a-4dca6e277a91",
  "passTypeIdentifier": "pass.example.id1",
  "url": "https://d.pslot.io/p/J_FF0lcTSo2vZLJp-VreOw?t=D0rLkv4"
}

WalletWallet is one step. The response body is the .pkpass file:

curl -X POST https://api.walletwallet.dev/api/pkpass \
  -H "Authorization: Bearer ww_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "barcodeValue": "MEMBER-12345",
    "barcodeFormat": "QR",
    "logoText": "Loyalty Card",
    "primaryFields": [{"label": "BALANCE", "value": "$42.50"}],
    "secondaryFields": [{"label": "MEMBER", "value": "Sarah K."}]
  }' \
  --output member.pkpass

You serve the file however you want, whether that’s an email attachment, an “Add to Apple Wallet” button on a page, or a download link.

Both shapes are valid. PassSlot’s hosted-URL model is convenient for SMS or email distribution and centralizes pass storage; WalletWallet’s stateless model is simpler when you keep the pass file on your side and want full control over delivery.

Pricing at common volumes

PassSlot uses tiered pricing with hard caps per tier. WalletWallet is a single $19/month plan with per-pass overage above 100,000.

Passes per month	PassSlot	WalletWallet
100	$0 (Free)	$0 (free tier)
1,000	$0 (Free)	$0 (free tier)
10,000	$29 (Basic)	$19 (Pro)
100,000	$99 (Professional)	$19 (Pro)
500,000	Contact PassSlot sales	about $95

At 100,000 passes/month, the gap is roughly 5×. Above 100,000, PassSlot doesn’t publish per-pass overage rates, so heavy workloads need a sales conversation. WalletWallet bills $0.00019/pass for everything above 100K, which is published.

The Apple Developer Program line item

PassSlot requires you to bring your own Apple Pass Type ID and signing certificate for commercial use, which means an Apple Developer account at $99/year on top of the PassSlot subscription. WalletWallet signs with our platform certificate by default, so this line item is $0.

Annual cost (10,000 passes/mo)	PassSlot	WalletWallet
Subscription	$29 × 12 = $348	$19 × 12 = $228
Apple Developer Program	$99/yr	$0
Total	$447/yr	$228/yr

At 100,000 passes/month, the gap widens to $1,287/yr (PassSlot) versus $228/yr (WalletWallet), about $1,000 in savings, before factoring in your time setting up and renewing the Apple Developer Program.

What PassSlot’s higher price buys

PassSlot’s paid tiers bundle iBeacon, a no-code designer, a free scanner app, payment integration via Stripe and PayPal, white-label custom URLs, and webhooks. Pass updates and iBeacon are included from Basic up; payment integration and custom URL gate at Professional. Pass updates and push are on both sides; the rest aren’t on ours.

What WalletWallet doesn’t do (yet)

We try to be upfront about this on every comparison page. Compared to PassSlot, WalletWallet today:

• No iBeacon support. PassSlot can trigger pass display when a customer walks near a beacon. We can’t, and it’s not on our near-term roadmap.
• No scanner app or built-in redemption. PassSlot ships the free Pass Verifier app. We don’t, so you’d use any QR/barcode SDK on your side.
• No payment integration. PassSlot lets you sell tickets and store cards directly with PayPal, Stripe, or PAYMILL. We expect you to use your own checkout.
• No webhooks, no SDKs, no no-code designer at PassSlot’s level. REST + JSON only.
• No Google Wallet live updates. Our .pkpass opens in Google Wallet on Android, but Google Wallet doesn’t honor webServiceURL, so PUT updates and APNs push only reach iOS. We couldn’t confirm modern Google Wallet (JWT API) support in PassSlot’s public docs either, so if a Google-Wallet-native lifecycle is a hard requirement, ask PassSlot directly.

If any of these are blocking, PassSlot is the better choice today. We’d rather you find out from this page than mid-implementation.

Feature comparison

	PassSlot	WalletWallet
Apple Wallet pass generation	✓	✓
Pass updates (Apple Wallet)	✓	✓ (PUT /api/pkpass/{serial})
Push notifications (Apple Wallet)	✓	✓ (APNs fan-out on every PUT)
iBeacon support	✓	—
Webhooks	✓	—
Scanner app for redemption	✓ (free Pass Verifier)	—
Payment integration	✓ (Stripe / PayPal / PAYMILL)	—
No-code pass designer	✓	basic
Custom URL / white-label	✓ (Basic+)	—
iOS SDK	✓	—
Apple cert handling	customer brings own ($99/yr Apple)	platform handles
API model	template + pass	POST + PUT, stateless
Free tier	1,000 passes/mo, indefinite	1,000 passes/mo, indefinite
Pricing model	flat tier ($29 / $99)	flat $19/mo + per-generation overage
Public pricing	yes	yes
Edge / global delivery	not stated	Cloudflare Workers

When PassSlot is the better pick

• You need iBeacon-triggered pass display. PassSlot has it; we don’t. Retail and venue workflows where a customer’s pass should pop up when they’re near a beacon.
• You want a no-code designer for non-developers to build and update pass designs in a dashboard.
• You need built-in redemption. The free Pass Verifier scanner app is genuinely useful for retail staff.
• You’re selling passes directly. PayPal, Stripe, or PAYMILL integration for ticket and store-card sales.
• You already have an Apple Developer account. If $99/year and the cert setup are sunk costs for you, PassSlot’s BYO-cert model is no friction.
• You want SDK support for iOS or third-party-listed Node, Java, and .NET clients.

When WalletWallet is the better pick

• You want the fastest pass generation and push. Sub-200ms generation from Cloudflare’s co-located global edge; APNs push lands on every installed device within seconds. Most competitors don’t publish latency numbers, and we do.
• You want a live preview before writing any code. The Pass Editor on our homepage previews every pass change (fields, colors, images, push), and the dashboard editor sends real push updates to installed passes after signup. Copy the equivalent code when you’re ready.
• You want agent-ready docs. Point Claude or any LLM at /llms.txt and it can call the API end-to-end. No SDK plumbing needed; the docs are designed for both humans and agents.
• Non-developers on your team will touch this too. The Pass Editor doesn’t require writing code to design or test a pass.
• You skip the Apple Developer Program entirely. We sign with our certificate by default, with no $99/yr fee, no Pass Type ID setup, and no certificate renewal calendar.
• You only need Apple Wallet passes today. Loyalty cards, memberships, business cards, and event tickets all fit, along with anything else where issuing the pass is the whole job.
• You don’t want to manage an Apple Developer account. Skipping the $99/year fee and the cert renewal calendar is a real ergonomic win for solo developers and small teams.
• You want a flat, predictable bill. $19/month covers up to 100,000 passes. No per-template fee, no per-active-pass fee, no jump from $29 to $99 when you cross 10K.
• You’re price-sensitive at the 100K tier (5× gap).
• You want a small, stateless API. POST for create, PUT for update with automatic push, you handle delivery.

Try it before you decide

Get a free API key for 1,000 passes/month, indefinite, no card. After signup the Pass Editor in the dashboard previews every pass change live (including push updates to installed passes), so you can dial in fields, colors, and images, then copy the equivalent code and run it. Before signup the homepage Pass Editor runs the same preview live.

FAQ

Do I need an Apple Developer account for PassSlot or WalletWallet?

For PassSlot, yes for commercial passes. PassSlot’s certificate documentation explains that their shared certificates are for evaluation only, and production passes carry a legal notice on the back unless you upload your own Pass Type ID, which requires an Apple Developer Program membership at $99/year. For WalletWallet, no, since we sign with our own platform certificate by default. Bring-your-own-cert is supported as an option, but you don’t need it.

Why is PassSlot more expensive at the 100K tier?

PassSlot’s $99/month Professional plan bundles iBeacon, a scanner app, payment integration, white-label custom URLs, and webhooks into one fee. WalletWallet’s $19/month covers Apple-Wallet generation and updates but doesn’t ship the iBeacon, scanner, white-label, payment, or webhook pieces. Whether those are worth the $80/month gap is your call.

Is PassSlot still actively developed?

It’s hard to say definitively. The service is online, the API works, and the support center is staffed. The most recent post on PassSlot’s blog, though, is from November 2013. If active iteration matters to you, ask PassSlot directly about their roadmap before committing.

Can I migrate from PassSlot to WalletWallet?

Apple-Wallet generation, updates, and push translate cleanly. Both APIs produce standard PassKit passes; field mapping is mechanical (PassSlot’s template placeholders become inline values in WalletWallet’s primaryFields / secondaryFields / etc.); the update path maps to PUT /api/pkpass/{serial}. You also drop the Apple Developer Program dependency. Flows that depend on iBeacon, webhooks, the scanner app, or built-in payments don’t have equivalents on our side, so a hybrid migration (keep PassSlot for those pieces, move Apple-Wallet lifecycle to us) is the realistic path.

Does PassSlot support Google Wallet?

We couldn’t confirm modern Google Wallet (JWT API) support in PassSlot’s public docs. If Google Wallet is a hard requirement, ask PassSlot directly. On our side: the .pkpass opens in Google Wallet on Android, but live updates and push only reach iOS, since Google Wallet doesn’t honor webServiceURL.

What’s the right pick for a small loyalty program?

Both products handle pass updates and push, so the question is operational. If you have 1,000 or fewer active members, both free tiers cover you. WalletWallet’s $19/mo handles up to 100,000 generations and PUT-driven updates without an Apple Developer account; PassSlot’s $29/mo Basic covers 10,000 passes and bundles iBeacon and a scanner app but adds the $99/yr Apple Developer fee.

---

Last verified 2026-05-20. PassSlot pricing and features pulled from passslot.com/pricing and the public developer documentation. The activity-status caveat reflects what we found on the public site that day. If you spot something out of date, let us know, since we’d rather correct the page than have it stale.