PassKit Alternative: A Flat Monthly Plan Instead of Per-Pass Fees

PassKit charges for every wallet pass you issue, which gets expensive as your list grows.

See also: Stamp Me Alternative for Digital Stamp Cards · Loyverse Loyalty Alternative for Wallet Cards

This article compares PassKit with other wallet-pass platforms on pricing, setup time, and fit for retail chains, cafes, salons, and multi-location businesses. We also cover the main differences in features, limits, and campaign management so you can choose the right tool for your wallet campaigns.

Pricing Model Differences

PassKit charges per pass. Every loyalty card, coupon, ticket or membership you issue counts toward your bill, whether the customer ever opens it or not. That model works for one-off campaigns where you send a fixed number of passes and stop. It gets harder to predict when passes are created automatically at the point of sale, or when staff re-issue a lost card, or when a customer signs up through a QR code on the counter.

You pay the same amount for a cafe with 300 loyalty members as you do for a cafe with 3,000. The cost does not change when you add more passes, re-issue a card, or run a seasonal coupon drop to your whole list.

Consider a salon with two chairs and a steady stream of repeat clients. The owner wants every client to have a digital loyalty card, but also wants to send a birthday coupon each month and a "bring a friend" pass a few times a year. Under a per-pass model, each new client card and each campaign pass adds cost. The owner starts asking questions like "Is this birthday coupon worth the fee?" before the campaign has even run. The salon pays one fee for the location, and the owner decides what to send based on what clients need, not what each pass costs.

A car wash with three locations shows the difference more clearly. The owner runs a monthly unlimited-wash membership. Every new member gets a digital pass, and every renewal may generate a new pass if the old one expires or the customer changes plans. With per-pass pricing, growth means a rising bill every month. The owner cannot easily forecast next quarter's cost because it depends on how many people sign up, renew, cancel, or ask for a replacement. That is it. The owner can budget for the year and focus on getting more members through the door.

Restaurants face a similar pattern with loyalty sign-ups at the till. A busy counter-service restaurant might add dozens of new loyalty passes in a single lunch rush. Per-pass pricing turns a good day into a higher software bill.

Gyms and fitness studios often issue membership passes, class booking confirmations, and referral coupons. A member might receive three or four passes in their first month alone. Per-pass pricing multiplies the cost of onboarding.

The practical question for a shop owner is simple: do you want your software cost to scale with your marketing activity, or with your number of locations? If you run a single shop and send a small number of passes per year, the difference may be modest. A platform that charges per pass rewards restraint.

When comparing a PassKit alternative, ask the vendor to walk through a realistic month: how many passes will you issue, how many will be re-issued, and what does that cost look like at one location, three locations, and ten locations. The answer tells you which pricing model fits your business.

Setup Effort Compared

Setting up a wallet pass platform usually means two separate jobs. First, you design the pass itself: logo, colours, text fields, barcode. Second, you connect that pass to your point of sale, your email tool, or your website. The effort involved depends on how much of that work the platform does for you, and how much you must handle manually.

PassKit is built for flexibility. A cafe owner can have a basic stamp-card pass ready in under an hour without touching code. The trade-off is that PassKit’s design assumes you want fine control over pass templates, distribution links, and update rules. That control takes time to learn. A salon owner who wants to send a birthday voucher with an expiry date and a one-time barcode will need to work through several settings before the pass behaves exactly as expected.

The bigger setup question is integration. If you run a gym and want a membership pass that updates automatically when a member renews, you need a connection between your booking or billing software and PassKit. That means either using a supported third-party connector or writing API calls. For a non-technical owner, this is where setup effort increases. The same applies to a car wash that wants wash credits added to a pass when a customer pays at the counter. Unless your POS already talks to PassKit, you will be exporting data or manually adjusting balances.

The setup flow is usually built around one use case: a loyalty card, a coupon, or a membership pass. You pick the template, add your branding, and the platform generates a QR code or link for your counter. A restaurant owner can print that QR code on table tents and start issuing passes the same day. There is no API requirement for the basic setup.

A cafe group with three locations can clone the same pass design, change the store name and address, and issue each branch its own QR code. That is often faster than configuring one PassKit template to route customers to the correct branch based on location rules.

Where PassKit pulls ahead is when you need deep customisation from day one. If your loyalty programme has unusual rules, tiered rewards, or a specific data structure, PassKit gives you the tools to build that. The setup effort is lower, but only because the platform makes more assumptions about what you need.

The practical difference comes down to this: PassKit rewards owners who have time to configure and test.

Best Use Cases for PassKit

PassKit fits businesses that already have a clear process for issuing wallet passes and want a mature toolset with deep integrations. It works best when pass volume is low per customer but the operational need is high. Think of it as a precision instrument for specific wallet campaigns, not a blunt tool for mass distribution.

Multi-location loyalty with central control

A cafe group with four or five branches can use PassKit to run one loyalty programme across all sites. Head office designs the pass template once, then each branch scans and updates points through the same backend. Staff at any location can see a customer’s balance, add a stamp, or redeem a reward. This matters when a customer buys coffee at the High Street branch on Monday and the station branch on Thursday. The wallet pass updates on their phone, so there is no confusion about how many stamps they have.

For a salon chain, the same logic applies to membership passes. A client who books at different branches still carries one digital membership card. The receptionist scans it, the system logs the visit, and any prepaid balance or loyalty tier stays consistent.

Event and appointment tickets with time limits

A restaurant that runs ticketed tasting evenings can issue wallet passes that display the date, time, and party size. The pass sits in the customer’s Apple Wallet or Google Wallet and shows a QR code for check-in. Because PassKit supports time-based updates, the restaurant can push a notification when the table is ready or when a menu changes. No paper tickets, no email attachments to search for at the door.

A car wash that sells multi-wash bundles can use PassKit to track remaining washes. The customer buys a five-wash pass, and each visit deducts one. The wallet pass shows the updated balance after each scan. This is useful because car wash customers often keep the pass for weeks or months.

Membership programmes with renewal dates

Gyms and fitness studios often need passes that expire on a set date. A monthly membership pass can show the renewal date, membership tier, and a barcode for entry. When the member renews, the pass updates automatically. If they cancel, the pass can be voided remotely. PassKit supports these lifecycle changes, which is why it suits businesses where membership status changes regularly.

A co-working space or a private members’ club can use the same approach. The pass acts as a digital ID card. It shows the member’s name, photo if needed, and access level. Front-desk staff scan it to log entry. Because the pass updates through the cloud, a change in access level or expiry date appears on the phone without the member needing to download anything new.

Where PassKit is less necessary

A small independent shop that simply wants a basic digital loyalty card may find PassKit’s feature set more than it needs. If you issue a few hundred passes a year and only need a simple stamp card, the per-pass pricing model can add up. PassKit charges per pass, so every new customer who downloads your card counts as a pass. For a high-volume, low-margin business like a busy takeaway, that cost can grow quickly.

PassKit also requires some technical comfort. A business without a developer or a technically minded owner may find the learning curve steep. For simple use cases, a simpler tool may do the job. For complex, multi-branch or time-sensitive passes, PassKit earns its place.

Best Use Cases for PassHive

Multi-location cafes and coffee shops

A cafe group with four branches can issue unlimited loyalty passes from each location without watching a counter climb. The owner sets up a template once, then clones it for each branch. Each branch manager can update opening hours, menu links, or special offers without touching the other locations’ passes.

The cost stays the same whether 1,200 or 12,000 customers hold passes. This makes it easier to run aggressive sign-up drives at the counter without worrying about the bill at the end of the month.

Salon and barbershop groups

PassHive lets each salon branch manage its own membership pass with its own branding, contact details, and booking URL. A group with three salons can offer a “10th visit free” stamp card digitally, with each branch tracking its own redemptions.

Because there is no per-pass fee, the salon can add a pass to every booking confirmation email without hesitation.

Restaurant chains with location-specific offers

A restaurant group with five sites can issue a wallet pass for each branch. The city-centre branch might promote a weekday lunch deal, while the suburban branch pushes a family dinner bundle. With PassHive, each branch updates its own pass content. The head office keeps control of the overall design and branding, but day-to-day edits stay local.

This matters for restaurants because offers change frequently. A manager who can update a pass in two minutes is more likely to keep it current than one who must email a head-office marketing team and wait for approval.

Car wash and valeting businesses

Car washes often run on repeat visits. A multi-site car wash operator can give every customer a digital loyalty pass without counting each pass as a cost. Each branch can set its own stamp or points rules, such as “buy five washes, get the sixth free” at one site and a different threshold at another.

Because the cost is predictable, the operator can train every cashier to offer the pass at payment. There is no need to ration passes or worry about high-volume months.

Gyms and fitness studios with several locations

A gym group with two or three studios can issue membership passes that show class schedules, renewal dates, and check-in barcodes. Each studio manages its own pass, so a timetable change at one location does not affect the others. A studio with 800 members pays the same as one with 300.

When PassHive fits best

Single-location businesses can still use it, but the pricing advantage is clearest for operators who would otherwise pay for passes across several sites.

Who PassKit Suits

PassKit appeals to businesses that already think in terms of individual wallet pass records and want a mature, API-first platform. The pricing model charges per pass per month, which shapes the kinds of operations that fit best.

Low-volume, high-value passes

A boutique salon with a membership programme is a good example. If you issue 80 monthly membership passes and each member books treatments worth £60 or more, a per-pass fee is a negligible line item. You are not trying to grow pass numbers aggressively. You simply need a reliable way to put a branded membership card into Apple Wallet and Google Wallet, update the member's points balance, and send a lock-screen notification when their next appointment is due.

The same logic applies to a car wash that sells a limited number of monthly unlimited plans. If 150 customers hold an active plan pass, the owner cares about renewal rates and queue-skipping, not about issuing thousands of new passes. Per-pass pricing is predictable because the pass count tracks the number of paying plan holders.

Pilot programmes and controlled rollouts

PassKit suits a restaurant group testing wallet-based loyalty in two locations before a wider launch. The team can create a small batch of passes, measure redemption behaviour, and keep the monthly cost tied directly to the test size. There is no pressure to offset a large platform fee with high pass volume from day one.

A gym running a referral campaign for 200 existing members fits this pattern too. The marketing manager wants each referred friend to receive a free day-pass with a scannable barcode. The campaign runs for six weeks. PassKit's per-pass structure means the cost ends when the campaign ends and the passes expire.

Businesses with technical staff or agencies

PassKit's API and template system reward teams that can build custom integrations. A retail chain with an in-house developer can connect PassKit to its POS or CRM, sync loyalty points automatically, and trigger pass updates when a customer's tier changes. The per-pass fee is then viewed as a small variable cost within a larger automation project.

A marketing agency managing wallet passes for several restaurant clients can also use PassKit as a white-label or multi-client setup. The agency absorbs the per-pass fees and bills clients a monthly service fee. This works when each client needs only a few hundred active passes.

Seasonal or event-based issuers

A cafe that runs a summer loyalty card, a salon offering a Christmas gift voucher pass, or a restaurant promoting a one-off tasting-menu ticket can all use PassKit without committing to a large annual contract. The pass count rises during the campaign and falls to zero afterwards. Per-pass pricing matches this rhythm.

Where the fit is weaker

A high-footfall coffee shop issuing a new loyalty pass to every customer who buys a drink would see pass counts climb into the thousands within weeks. At that volume, a per-pass fee becomes a recurring cost that grows with every new signup, even for customers who never return. The same applies to a car wash pushing a free points card to every drive-in customer.

Who PassHive Suits

PassHive works best for businesses that operate from more than one location but want a single, predictable bill for their wallet pass program. If your business grows by opening a second or third shop, your pass volume usually grows too. Under a per-pass model, that means your monthly cost climbs with every new customer who saves a loyalty card or coupon to their phone.

That distinction matters most in a few specific situations.

A cafe group with three sites might issue 1,500 loyalty passes in a quiet month and 4,000 in December when holiday stamp cards take off. The owner can push a Christmas punch-card campaign to every customer who has ever saved a pass, without first calculating whether the extra pass distribution will push the bill up. The same applies to a salon chain that wants to send a birthday offer to every client who has a membership pass on file. Sending more passes should not feel like a cost decision.

Restaurants with high table turnover see a similar pattern. A burger bar with two branches may add several hundred new loyalty passes each week during summer. There is no internal debate about whether issuing another pass is worth the per-pass fee. The pass becomes a standard part of service, like handing out a paper menu.

Car washes and gyms often run membership models where the pass is tied to a recurring visit or class booking. A gym with four studios might store a digital membership card in each member’s Apple Wallet or Google Wallet. Members use it to check in, book classes, or access member-only discounts. It does not matter whether each branch has 300 members or 900. The owner can plan the annual marketing budget without forecasting pass issuance.

Franchise and multi-site operators are another clear fit. If you run five convenience stores or a small chain of barber shops, you likely want each location to issue its own passes with local branding, local opening hours, and local offers. The store manager in one suburb can send a rainy-day discount to local pass holders without affecting the budget of another branch.

Single-location businesses can also use PassHive, but the value is less about scale and more about simplicity. That removes the monthly surprise of a variable bill.

In short, PassHive suits owners who think in terms of locations, not individual passes.

Switching From PassKit

Moving your wallet passes to a new platform is a practical decision, not a technical overhaul. The goal is to keep your existing customers’ passes working while you change the billing model behind them. Shops, cafes, salons, car washes, restaurants and gyms all face the same core issue: the number of passes in the field grows over time, and per-pass fees grow with it.

PassKit has served many businesses for years, and its feature set is broad. But if your pass count is climbing, you may be paying for the same customer again and again. A per-pass fee means a loyalty member who joined two years ago still costs you money every month. A gym with 800 active membership passes and a cafe with 1,200 loyalty cards are both paying for passes that were issued long ago and require no ongoing work.

You pay a fixed amount for each physical location, regardless of how many passes that location issues. The cost is tied to your business structure, not to the number of customers who have your pass in their Apple Wallet or Google Wallet.

Here is a simple illustration. Suppose a salon chain has four branches. The number of passes can grow to 3,000 or 5,000 without changing the bill. That is the core difference.

The practical steps for switching are straightforward. First, export your existing pass data. PassKit allows you to download your pass records, including serial numbers, customer names and any custom fields you have stored. Keep that file safe. Second, design your new passes in the alternative platform. Most wallet pass platforms use the same underlying Apple and Google specifications, so the visual layout and barcode types will be familiar. Third, test with a small group. Issue new passes to yourself and a few staff members before sending anything to customers.

The trickiest part is updating existing passes that are already in customers’ wallets. You cannot edit a pass that lives on someone’s phone. Instead, you issue an updated version of the same pass. The new platform should let you use the same serial numbers so that the update replaces the old pass rather than creating a duplicate. When a customer opens their wallet, the pass updates automatically if you have set the change message correctly.

For a car wash with a simple “buy five, get one free” stamp card, the switch might take an afternoon. For a restaurant with a points-based loyalty scheme and birthday rewards, allow a few days for testing. The key is to keep the customer-facing experience identical. The pass should look the same, scan the same and update the same. Only the billing behind it changes.

One common concern is downtime. You do not need to turn off your old passes immediately. Run both systems in parallel for a week or two. Issue new passes from the new platform while old passes continue to work. Then send a push notification through the old system asking customers to update their pass. Most will do so within a few days. After that, you can retire the old system.

The switch is a one-time effort. That makes budgeting simpler and removes the penalty for growing your loyalty programme.

Where PassHive Falls Short

The model gets less comfortable when you operate several venues under one brand. If you add a fourth, your monthly cost steps up again before you have sold a single extra loyalty stamp.

That structure can feel restrictive for businesses that think in terms of one customer base rather than separate shopfronts. A gym chain with two sites in the same city may want a single wallet pass that members can use at either location. PassHive can support that technically, but you still need a plan for each branch. The pricing does not automatically reward you for consolidating your operations or for running a lean head office that manages passes centrally.

Multi-location restaurants face a similar calculation. A franchise network with ten or fifteen outlets will notice the total more clearly. Each new franchisee or company-owned site adds another line to the monthly bill. That is not a hidden charge; it is simply how the pricing is built. But it means PassHive is less attractive when your growth plan involves opening many small locations rather than deepening one large one.

Another limitation appears when a single physical space houses two distinct businesses. A barber who rents a chair inside a salon, or a coffee cart operating inside a bookshop, may want their own wallet pass with their own branding and loyalty rules. The answer depends on how the account is structured, and it can create friction when two independent owners share one address.

A Christmas market stall, a summer beach kiosk, or a food truck that moves between pitches may only operate for a few months. Neither option is ideal for a business that wants a simple annual pass programme without monthly administration.

A car wash group with three sites on the same road may want one wallet pass that tracks washes across all of them. You are paying for the physical footprint, not for the number of customers or passes. For a business whose value comes from a large, mobile customer base rather than a fixed address, that can feel like the wrong unit of measurement.

None of this makes PassHive a poor choice for single-site shops. The shortfall appears only when your operation outgrows that simple structure, or when your business model was never built around fixed branches in the first place.

Wallet Pass Platform Tradeoffs

When you evaluate a wallet pass platform, the pricing model shapes how you run promotions. Some platforms charge a fee each time a pass is issued or updated. That works if you send a small number of passes, but it becomes harder to predict when you run a busy campaign.

A cafe launching a loyalty card for the summer might add hundreds of new customers in a week. If the platform charges per pass, the cost rises with every sign-up. The same happens when you push a location update, change a points balance, or refresh an offer. Each update can count as a new event. For a salon with a client list of 800, sending a booking reminder or a birthday reward to all of them could trigger hundreds of charges in one day.

You pay for each physical location, not for each pass or update. A car wash with three sites can issue as many loyalty passes as it needs across those branches without watching a per-pass meter. A gym with two studios can send weekly class reminders to every member without calculating the cost of each notification.

This difference matters most for businesses that use passes for frequent, small interactions. A restaurant might update a points balance after every meal. A retail shop might change a coupon design each month. Under a per-pass model, the finance team sees a line item for every one of those changes.

There is also a practical side to planning. A small chain with four locations can budget a fixed amount for wallet passes each month. The owner does not need to forecast how many customers will join the loyalty program or how many times the team will send a push notification. The cost is tied to the number of shops, which is stable and known.

A single-location business with a small customer base might find per-pass fees cheaper in a quiet month. A pop-up event that runs for two weekends might prefer to pay only for the passes issued during that short window. The tradeoff is between predictable fixed costs and variable costs that follow customer activity.

For most multi-location operators, the branch model removes a layer of guesswork. The manager of a salon group does not have to ask staff to limit pass updates to save money. The owner of a cafe chain does not have to approve a budget before launching a new loyalty campaign. The wallet pass platform becomes a fixed operational cost, like rent or software for bookings, rather than a marketing expense that grows with every customer action.

That shift changes how teams use the tool. When updates are free within a branch, staff send more relevant offers, refresh pass designs more often, and use location-based messages without hesitation. The platform stops being a cost centre and starts behaving like infrastructure.

Why shops look at PassHive instead of PassKit

Why shops look at PassHive instead of PassKit

This site is published by the team that builds PassHive, so we are direct about the comparison. PassKit is a long-established platform for creating and distributing digital wallet passes, including loyalty cards, tickets, coupons and memberships. PassHive focuses on one job: letting shops, cafes, salons, car washes, restaurants and gyms issue their own branded loyalty cards that customers save to Apple Wallet and Google Wallet.

The main reason a shop owner starts comparing the two is the pricing model. PassKit charges a monthly platform fee and then adds per-pass fees once you go beyond the included 250 passes. For example, a cafe with 1,000 customers would pay about $73 per month on PassKit. A larger business with 10,000 customers would pay about $341 per month. PassHive does not charge per pass or per customer.

PassHive pricing starts at $10 per month for up to 100 branches. A single-location cafe with 1,000 loyalty customers pays $10 per month on PassHive. See PassHive pricing for the full breakdown.

The second reason is that PassHive keeps the card setup simple and visual. You can design the card and preview it on iPhone and Android for free. You pay only when you go live. The card shows your own shop name, colour and logo, and it updates itself on the customer’s phone when a stamp or points are added. You can choose a stamp or visit card, such as buy 9 get the 10th free, or a points card.

PassHive also includes two features that matter for foot traffic. You can send push notifications to saved cards, for example an offer or a “your reward is ready” message. Google limits roughly 3 messages per card per day. You can also set up location-based lock-screen reminders near the shop. Apple supports up to 10 locations per card with a radius of about 200 metres, and Google uses merchant locations. These reminders can appear when the phone decides to show them, so phrase them as “can remind” rather than a guarantee.

For shops with more than one branch, PassHive gives you a simple control: you can turn any branch off at any time, and its cards stop at once. There is also a public REST API with API keys, so developers or agencies can issue and update cards from their own POS, app or website. The API supports creating a card, adding a stamp, adding points and sending a message. Documentation is available at passhive.app/docs. PassHive is not a POS, not an e-commerce plugin, and has no named integrations with Shopify, Square, Toast or similar systems.

Customers join by scanning a QR code at the counter or opening a link. There is no app download for them. If you want to compare the card design and preview before paying, you can start designing your card free.

PassHive is a flat monthly plan for the whole business, not a fee per branch. The plan sets the maximum number of active branches you can run: $10 a month for up to 100 branches, $25 for up to 275, $50 for up to 600 and $100 for up to 1,250. Yearly billing gives two months free ($100, $250, $500 or $1,000 a year). A cafe with one branch pays $10 a month in total, whatever the number of cards or customers. That is what "pay for your branches, not your customers" means: the plan size follows how many branches you run, never how many people save your card.