Loyverse Loyalty Alternative for Wallet Cards

Loyverse offers a basic digital loyalty card, but PassHive is a stronger alternative for shops that want wallet passes in Apple Wallet and Google Wallet. PassHive creates native mobile wallet cards that customers can save and tap at the counter, without needing a separate app.

See also: Square Loyalty Alternative if You Want Wallet Cards · Stamp Me Alternative for Digital Stamp Cards

This guide compares PassHive and Loyverse loyalty across pricing, setup time, best use cases, and ideal users. You will also find practical switching steps and a clear list of limitations, so you can decide whether PassHive fits your shop better than Loyverse for wallet-based loyalty.

Pricing Model Differences

Loyverse positions its customer loyalty feature as part of a free point-of-sale package. That matters because a shop owner can start recording sales, building a customer list, and issuing points without a separate monthly loyalty subscription. The trade-off is that the loyalty module is tied to the Loyverse POS ecosystem. If a salon or cafe later wants to switch POS providers, the loyalty balances and customer history do not automatically move with them.

A wallet-card loyalty system usually works the other way around. The wallet card is often independent of the POS. A car wash can sell prepaid washes on a plastic card, top it up at the counter, and deduct value at the wash bay terminal. The card balance lives in the wallet system, not in the POS. That means the owner can replace the POS without losing card balances. It also means the loyalty program can run alongside any register, barcode scanner, or payment terminal already in the shop.

The cost structure differs in practice. With a free POS loyalty feature, the main expenses are hardware, payment processing, and staff time to set up and explain the program. There is no loyalty line item on the monthly bill. For a small restaurant with one register, that can be enough. The owner creates a points-per-spend rule, staff tap the customer profile at checkout, and the system tracks everything.

Wallet cards usually involve a physical card cost and often a per-card or per-transaction fee from the wallet provider. A gym selling a 10-visit pass on a wallet card pays for the blank cards and possibly a small fee each time a visit is deducted. That cost is predictable and scales with usage. A cafe that issues 200 wallet cards for a prepaid coffee program knows the card expense up front. The benefit is that the wallet card holds prepaid value, which many free POS loyalty modules do not handle natively.

Another practical difference is how the money is recognised. A prepaid wallet card takes payment before the service is delivered. A car wash selling a 5-wash card collects the full amount on day one. The POS records the sale, but the wallet system must track the remaining washes. With a points-based loyalty module, no prepaid value exists. The customer earns points after spending, and the reward is a discount or free item later. The cash flow pattern is different.

For a salon, the choice often comes down to whether the owner wants stored value or simple repeat-visit rewards. A wallet card works well for prepaid packages: five haircuts for the price of four. A free POS loyalty module works well for points: earn points per visit, redeem after ten visits. Both can drive return visits, but the pricing model and the way value is stored are not the same. Owners should check whether their chosen wallet card provider charges monthly fees, per-card fees, or transaction fees, and compare that against the staff time needed to run a free loyalty module inside the POS.

Setup Effort Compared

Getting a loyalty programme running with Loyverse takes a few steps inside the POS back office. You enable the loyalty feature, choose between points or a simple visit counter, set the reward threshold, and then train staff to search for the customer at the till before closing the sale. For a single-location cafe or small salon, this can be done in an afternoon. The main ongoing effort is staff discipline: someone has to remember to open the customer record on the POS screen for every transaction. If a customer pays without being identified, the visit does not count and no points are added. That sounds minor, but during a busy lunch rush it is easy to skip.

A wallet-card alternative works differently. The customer carries a physical card with a QR code or barcode, and the shop either scans it with a barcode scanner or types a short card number into a separate app or web page. Setup often means creating a simple account, uploading a logo, choosing the number of stamps or points per visit, and printing a batch of cards. Many small shops can have cards ordered and the system ready within a week. There is no deep integration with the POS required, because the loyalty action happens outside the till. Staff scan the card, the system records the visit, and the customer sees their balance on the card or via a link.

The practical difference shows in daily use. With Loyverse, loyalty is tied to the sale screen. Staff must find the customer first, then ring up the order. With a wallet card, the order can be rung up normally, and the card scanned at any point before or after payment. In a car wash or gym where customers often pay at a counter and then move to a service area, scanning a card at a separate tablet or phone can be faster than searching a customer database on the main till.

Training is also different. Loyverse requires staff to understand the customer search function, how to create a new customer profile, and how to redeem a reward from the POS. That is not difficult, but it is more than scanning a card. A wallet-card system usually needs only one instruction: scan the card at every visit. New staff can learn that in under a minute.

For a shop that already uses Loyverse as its main POS and wants loyalty without any extra hardware or printing, the built-in feature is the obvious first choice. For a shop that wants loyalty to run alongside any POS, or that wants customers to hold something physical, a wallet card takes less integration work and less daily staff attention. The trade-off is that you now manage two systems instead of one, and you need to keep the card database in sync with any customer contact details you collect elsewhere.

Neither option is hard to set up. The bigger question is where the loyalty action happens: inside the till, or beside it.

What Each Tool Does Best

Loyverse works well for a shop that wants one simple system for sales and basic loyalty without adding another subscription. The loyalty feature sits inside the POS, so staff can add points or redeem rewards from the same screen they use for checkout. A small cafe can set a rule like “buy 9 coffees, get the 10th free” and run it without a separate tablet or app. Because Loyverse is built around the register, it suits businesses where loyalty is a secondary task, not the main focus. A car wash that mostly needs fast billing and occasionally stamps a card can use it without much setup.

Wallet card apps, by contrast, put the loyalty card itself at the centre. They are designed for customers to carry a digital card on their phone, see their points, and receive messages from the business. A salon can send a push notification when a client’s points are close to a free treatment, or remind them their prepaid visits are running low. These tools usually include a customer-facing app or Apple Wallet and Google Wallet pass, which Loyverse does not offer in the same way. The customer checks their own balance instead of asking at the counter.

Loyverse is strong when you want the register, stock counts, and loyalty data in one place. A restaurant can track which dishes a regular orders and apply a discount at the same time, all from the POS. Staff training is shorter because there is one system to learn. The loyalty reports are basic but useful: you can see how many points were issued and redeemed over a period, and which customers are most active. For a business that already runs on Loyverse and does not want to add another login, this is a practical fit.

A dedicated wallet card tool does better when the goal is to keep customers engaged between visits. Gyms use these apps to send class reminders, show membership status, and let members book or check in from their phone. A car wash can offer a digital punch card where customers tap to collect a stamp after each wash, without staff handling paper cards or typing phone numbers. The customer experience is more self-service, which reduces queue time at busy counters.

The choice depends on where the loyalty interaction happens. If it happens at the till, Loyverse covers it. If it happens on the customer’s phone before or after the visit, a wallet card app is the more natural fit. Many businesses start with Loyverse because the POS is free and the loyalty feature is already there, then move to a wallet tool when they want customer messaging, digital passes, or a loyalty programme that works without staff involvement.

Who Each Platform Suits

Choosing between Loyverse and a wallet-card loyalty system comes down to how your staff work, how your customers behave, and how much time you want to spend managing the programme.

Loyverse suits businesses that already run on Loyverse POS. If your shop, cafe or salon uses Loyverse for sales, stock and receipts, its built-in loyalty feature is the path of least resistance. Staff see the customer's points balance on the same screen they use to ring up a sale. There is no second device, no separate app to open, no extra login. A busy takeaway coffee counter can add points and redeem rewards without slowing the queue. A small boutique can track loyalty for a handful of regulars without printing cards or buying hardware.

Loyverse also suits owners who want loyalty tied to purchase history. Because the loyalty data lives inside the POS, you can see what a repeat customer actually buys, not just that they scanned a card. A salon owner can check whether a client's last visit was a cut or a colour treatment before offering a reward. A restaurant manager can see whether a loyalty member tends to order lunch or dinner.

The trade-off is reach. Loyverse loyalty works best when the customer is standing in front of you with their phone or when you can look them up by name or number. It is less natural for businesses that want customers to carry something physical.

Wallet-card loyalty suits businesses where the card itself does the work. A car wash, gym, laundromat or quick-service restaurant often has customers who pay fast and leave faster. Staff do not have time to search a database. A wallet card with a barcode or QR code lets the cashier scan, stamp or swipe in a second. The customer keeps the card in a purse, glovebox or phone case and brings it back without needing an app or a login.

Wallet cards also suit businesses that want the card to act as a small advertisement. A gym can print its logo, opening hours and a class schedule on the back. A car wash can put a "buy five washes, get the sixth free" offer directly on the card so the customer sees it every time they open their wallet. A salon can hand a new client a branded card after their first appointment as a quiet nudge to return.

The trade-off is data. A simple stamped or scanned wallet card may not tell you what the customer bought, only that they visited. Unless the card system is linked to your POS or a separate app, you get visit counts rather than purchase detail. For a car wash, that is usually enough. For a boutique that wants to reward high-spending customers differently from occasional browsers, it may not be.

Where the two overlap. A cafe with a steady stream of regulars and a single counter can do well with either. If most customers pay by card or phone and are happy to give a name, Loyverse keeps everything in one system. If the cafe is in a tourist area or serves many one-off visitors, a wallet card with a stamp grid may be easier to hand out and more likely to come back. Some businesses use both: Loyverse for logged-in regulars who want points tied to purchases, and simple wallet cards for walk-ins who just want a stamp toward a free coffee.

How Switching Works

Switching from one loyalty setup to another sounds like a bigger job than it usually is. Most of the work is in the first setup, not in the daily running of the shop. Once the new wallet-card system is live, staff tap a card or scan a phone, and the till does the rest.

What the first week looks like

Start with a small test group before you roll it out to every customer. Pick ten or twenty regulars, issue their wallet cards, and run a few transactions. This catches the practical problems early: a card reader in the wrong spot, a staff member who needs a second run-through, or a till prompt that appears at the wrong step.

For a cafe, the test often happens during a quiet afternoon shift. The owner issues cards to regulars who come in for a second coffee, and the team watches how long each tap takes. If the reader sits behind the till, the customer has to hand over the card. If it sits on the counter, the customer taps it themselves. Both work, but one is faster for a queue.

A salon or barbershop usually tests differently. The card is issued at the front desk, and the stylist or barber is not involved in the tap. The receptionist checks the balance or stamps the visit, and the customer pays as normal. The key question is whether the front desk can handle the extra tap without slowing down the booking flow.

Moving existing points across

If you already run a points scheme, customers will ask what happens to their old balance. The cleanest method is a manual transfer. Export the list of customers and their current points, then load that balance onto each new wallet card as a starting value. This is a one-time spreadsheet job, not a daily task.

A car wash might have hundreds of customers on a wash-count scheme. The owner exports the list, sorts by plate number or phone number, and issues cards with the matching number of washes already loaded. Staff do not need to explain a new system to every driver. The card simply works, and the balance is already there.

A gym or fitness studio often uses visits rather than points. The switch works the same way. The old attendance record becomes the starting balance on the new card, and the front desk staff stop using the old sign-in sheet on the same day.

Staff training without stopping service

The fastest training method is a printed one-page sheet next to each till. It shows three steps: tap the card, check the screen, finish the sale. Staff do not need to memorise menus or codes. After two or three shifts, most teams no longer look at the sheet.

For a restaurant, the card tap usually happens when the bill is presented. The server brings the card reader to the table, the customer taps, and the discount or points are applied before payment. The training focus is on the order of steps: loyalty first, then payment.

A retail shop often trains staff during the handover between shifts. The morning person shows the afternoon person two or three real transactions, and that is enough. No separate training session, no closed hours.

When to make the full switch

Pick a date and switch everyone on the same day. Running two systems side by side for weeks creates confusion at the till and doubles the admin. The test group phase should be short, usually under a week. After that, all new loyalty activity goes through the wallet cards.

Keep the old records for reference, but do not keep issuing old-style points. Customers adapt quickly when the new card is the only option and the balance is already on it.

Where PassHive Falls Short

PassHive focuses on wallet cards and loyalty stamps. That focus creates gaps for some shops. If your business runs on a full point-of-sale system, you may notice missing pieces quickly.

No built-in POS or inventory link

PassHive does not replace your till. You still need a separate POS for sales, receipts, tax totals and stock counts. A cafe owner who rings up a latte on one screen and then manually adds a stamp on another screen adds a step. During a morning rush, that extra step slows the queue. A salon receptionist may forget to apply a visit credit after a long appointment. With Loyverse, the loyalty action sits inside the same sale screen. With PassHive, you manage two systems unless you build a custom connection.

No automatic points on purchase amount

PassHive works best with fixed visits or fixed stamps. A customer buys a coffee, gets one stamp. A customer books a haircut, gets one visit. That is simple.

It gets harder when you want spend-based rewards. A restaurant owner may want one point per pound spent, with a free dessert at 500 points. A car wash may want a free basic wash after £60 of washes across different packages. PassHive does not calculate that from the till total automatically. Staff must read the receipt, work out the points and apply them by hand. That invites errors and slows service.

Limited handling of refunds and voids

Mistakes happen. A customer returns a faulty item. A barista rings up the wrong drink and voids the sale. In a POS-linked loyalty system, the refund or void can reverse the loyalty points or stamps in the same action.

With PassHive, the wallet card is separate. Staff must remember to remove the stamp or credit manually. A gym that refunds a monthly visit pack may forget to claw back the digital credit. A retail shop that accepts a return may leave loyalty points on the customer’s card. Over time, those small gaps cost you margin and confuse customers about their balance.

No single customer view across sales and loyalty

Loyverse keeps purchase history and loyalty activity in one customer record. You can see that a customer bought a facial last month and has three visits toward a free brow wax.

PassHive stores the loyalty side. Your POS stores the sales side. To see both, you compare exports or check two screens. That is workable but manual.

Offline behaviour depends on your setup

Loyverse works offline in many cases because the POS and loyalty data live together. PassHive depends on how you run it. If you use a phone or tablet app without a stable connection, the card may not update until you are back online. A market stall or food truck with patchy mobile signal may find this frustrating. You need to test your specific location before relying on it during busy periods.

Where PassHive still fits

None of these gaps matter for every business. A small cafe that wants a simple buy-nine-get-one-free card may not need POS integration. A car wash with three package types and no refunds may never hit the refund problem. A barber shop with one service price may not care about spend-based points.

The key is to match the tool to your actual workflow. If you expect the loyalty system to mirror sales, refunds and customer history automatically, you will notice the missing links within the first week.

Wallet Card Support Compared

Loyverse loyalty works through the POS screen and a customer directory. Staff look up a customer by name or phone number, check their points balance, and apply rewards at checkout. This works well at a counter where one person handles each sale and has a moment to search. A small cafe with regulars can manage this without much friction. The barista sees a familiar face, taps the name, adds points, and tells the customer they have a free coffee coming.

But wallet cards change the flow. A wallet card is a physical or digital card the customer carries. They present it at the till, the staff scans or taps it, and the system records the visit automatically. No name search, no phone number entry, no scrolling through a list of similar names. For a car wash with a line of vehicles, this matters. The attendant does not want to ask a driver to spell a surname while three cars wait behind. A card scan takes one second and the wash starts.

Salons and barbershops face a similar choice. A receptionist can look up a client in Loyverse while they book the next appointment. That is fine for a calm front desk. But a busy Saturday with walk-ins means the receptionist is also answering calls and taking payments. A wallet card lets the client tap at a small reader or hand over a physical card that gets scanned with the same barcode scanner used for retail products. The loyalty record updates without interrupting the payment.

Restaurants with table service rarely use wallet cards at the table. The server takes the order and handles payment at a terminal. Loyverse loyalty fits this model because the server already interacts with the POS for the bill. Adding points is one extra tap. A wallet card would require the customer to hand over a card or phone, which is awkward mid-meal. The server would need to carry a reader or walk to a fixed scanner. That adds steps, not removes them.

Gyms and fitness studios run on membership cards anyway. Members already carry a key tag or use a phone app to check in. If the loyalty program runs through a wallet card that doubles as the check-in card, the front desk scans once and both attendance and loyalty update. Loyverse loyalty would need a separate lookup step after check-in. For a gym with fifty people arriving in a twenty-minute window before a class, that second step is where queues form.

Retail shops with a physical counter and barcode scanner have the easiest transition to wallet cards. The same scanner that reads product barcodes reads a loyalty card barcode. Staff do not need new hardware. A customer at a boutique buys a dress, the assistant scans the items, then scans the loyalty card from the customer's phone or keyring. The points land on the account without typing. Loyverse loyalty handles the same outcome but through a name or phone search, which takes longer and depends on accurate data entry.

The core difference is not about features. It is about where the customer identity enters the transaction. Loyverse loyalty pulls the identity from the POS customer list. Wallet card support pulls it from the card itself. Shops with fast-moving queues, repeat customers who do not want to give a phone number every time, or staff who need both hands free will feel that difference immediately. Shops with slower, more personal service may not notice it at all.

Free POS Loyalty Limits

A free point-of-sale system with a built-in loyalty module sounds like the easiest possible start. You install the app, add a customer, and award points at checkout. For a single-location cafe or a small salon with one front desk, that often works well. The real limits appear when you try to grow the programme beyond the basic flow.

One programme, one set of rules

Free POS loyalty tools usually give you one earning rule and one reward structure. You might set a simple "spend 10, earn 1 point" and a fixed reward such as a free coffee after 100 points. That covers a straightforward repeat-purchase model.

The friction starts when you want to run different offers for different customer groups. A salon may want to reward new clients with double points on their first three visits, while giving long-term clients a birthday bonus. A car wash might want weekday customers to earn faster than weekend customers. With a single rule set, staff have to track exceptions manually, write notes on tickets, or simply tell customers the system cannot do it. That manual work erases much of the time saved by using a free tool.

Wallet cards and offline redemption

A wallet card is a physical or digital card the customer carries. They expect to see their balance, redeem rewards, and have the card work even when the shop's internet is slow or down. Free POS loyalty modules often depend on the till being online and the customer record being open on screen.

Think about a gym with a small cafe at the front. A member finishes a workout and wants to use loyalty points for a smoothie. If the POS terminal is busy with check-ins, or the loyalty screen takes three taps to reach, the queue slows down. Staff may skip the loyalty step entirely to keep the line moving. The programme then looks unreliable to members, and they stop asking about it.

Reporting and customer insight

Free loyalty features typically show you a list of points balances and redemptions. That is useful for basic bookkeeping. It is less useful for planning promotions. You may not be able to see which customers are close to a reward, which ones have not visited in 60 days, or which staff member drives the most sign-ups.

A restaurant owner might want to send a "you are one visit away from a free dessert" message to 20 specific customers. With a basic loyalty report, finding those 20 people means scrolling through a long list and checking visit dates by hand. That task often gets postponed, and the promotion never happens.

Multiple locations and staff roles

A single-location shop rarely notices permission limits. A cafe owner with two branches often does. Free POS loyalty tools may treat all staff the same. A part-time barista can see the same customer data as the owner, or cannot issue a manual points adjustment when a customer was missed at checkout. Either way, the owner ends up handling loyalty exceptions personally.

A small chain of three salons may want customers to earn and redeem at any branch. If the free loyalty module is tied to one device or one store database, cross-location balances become a manual reconciliation job. Staff at branch two cannot see points earned at branch one without calling or checking a shared spreadsheet.

None of these limits make a free POS loyalty feature bad. They simply define the point where a wallet card programme needs more structure than the free tool provides.

Loyverse vs PassHive Focus

Loyverse builds its loyalty feature as part of a broader free point-of-sale system. The loyalty tools sit inside the POS app, so a shop can scan items, take payment and add points in one screen. That setup works well when the person at the counter runs the whole transaction. The loyalty logic follows the sale: points accrue after checkout, and rewards are redeemed at the register.

PassHive starts from the wallet card itself. The card is the customer’s object, not a line on the till screen. A cafe can hand a physical card to a regular, and that card carries the balance or stamp count. The customer keeps it in a purse or phone case. Staff do not need to open the POS to check a balance. They tap the card on a reader or scan a QR code, and the balance updates on the spot.

Where the difference shows up in a real shift

A small bakery uses Loyverse at the counter. A customer buys four pastries and asks about points. The cashier finishes the sale, then checks the loyalty tab to see the balance. If the customer wants to redeem a free coffee, the cashier applies the reward in the same screen. It is one system, one screen, one flow.

A car wash runs a different rhythm. The driver stays in the car. Staff walk to the window with a handheld reader or a phone. The customer holds up a wallet card. One tap shows the wash credits left. If the card has enough, staff deduct a wash and wave the car through. No till, no receipt, no POS login. PassHive is built for that kind of quick tap at the door or in the lane.

A salon has another pattern. The stylist is not at a counter. The client books, gets a cut, and pays later. With a wallet card, the stylist can add a stamp after the service without walking to the front desk. The card sits in the client’s wallet, and the stylist taps it on a phone in the styling area. That keeps the loyalty moment close to the service, not tied to the payment terminal.

Different jobs, different tools

Loyverse loyalty is a feature inside a free POS. A gym with a simple monthly check-in may not want a full POS. They want members to tap in, earn a visit, and see a free session after ten visits. PassHive fits that without adding a sales screen.

A restaurant with table service might use Loyverse for billing and also want a stamp card for lunch regulars. The two can coexist. The waiter closes the bill in the POS, then taps the customer’s wallet card for a loyalty stamp. That split is common: the POS handles money, the card handles habit.

The choice comes down to where the loyalty action happens. If it always happens at the till, a POS loyalty module is enough. If it happens at the door, in the chair, at the car window or on the gym floor, a wallet card system is easier to run. PassHive focuses on the card and the tap. Loyverse focuses on the sale and the screen.

Why shops look at PassHive instead of Loyverse Loyalty

Shops usually start with Loyverse because it is already there. The moment a business grows beyond that setup, the limits start to show. This site is published by the team that builds PassHive, so we are direct about where we fit and where we do not.

The card lives inside an app or a customer account. It does not sit in Apple Wallet or Google Wallet. That means customers have to open an app, find the right screen, and show a code or name. In a busy cafe or salon, that extra step is enough to make staff skip the loyalty step entirely. PassHive takes a different route. The card is saved to the phone’s wallet, shows the shop’s name, colour and logo, and appears on the lock screen when the customer is near the shop. The phone can remind them, but it is the phone that decides when.

The second difference is how the card updates. With PassHive, a stamp or points balance changes on the customer’s phone after a visit. There is no separate customer portal to check. The card updates itself. Push notifications can be sent to saved cards for offers or a “your reward is ready” message. Google limits this to roughly three messages per card per day, which is still enough for most shops. Apple and Google Wallet are trademarks of their owners, and PassHive is not an official or authorised partner of either company.

Pricing is the other reason shops compare the two. Up to 100 branches is $10 per month. A cafe with 1,000 customers pays the same $10 per month as a cafe with 50 customers. There is no per-customer fee and no card limit. For comparison, PassKit starts at $39.50 per month and includes 250 passes, then charges per pass after that. A cafe with 1,000 customers would pay about $73 per month on PassKit versus $10 on PassHive. A shop with 10,000 customers would pay about $341 per month versus $10. Those numbers come from PassKit’s published pricing pages.

PassHive is not a POS and does not replace Loyverse. It has no named integrations with Shopify, Square, Toast or similar systems. What it does is issue wallet cards. You can design the card and preview it on iPhone and Android for free, and you pay only when you go live. Customers join by scanning a QR code at the counter or opening a link. No app download. Developers can use the public REST API with API keys to create cards, add stamps, add points or send messages from their own POS, app or website. Documentation is at passhive.app/docs.

If you want to see how your own card would look, 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.