How to Choose a Wallet Pass Platform: A Buyer's Guide and Scorecard

By · Published · Last updated · 10 min read

To choose a wallet pass platform, decide which of twelve things matter to you, ask every vendor the same question on each, and score the answers on one sheet. The twelve are: pricing model, self-serve signup, Apple and Google support, who holds the Apple certificate, pass updates and messages, loyalty logic, POS and ecommerce integrations, API and webhooks, data location, export and exit, support, and limits. This guide gives you the questions, a scorecard you can copy, a worked example and the red flags. Disclosure: Shakewell Wallet is our product. We write this for a business that wants to evaluate and start on its own, and we say where a demo-led enterprise vendor is the better choice.

Who this guide is for

It suits an owner, marketing lead or agency that wants Apple Wallet and Google Wallet passes (loyalty, stamp cards, memberships, gift cards or event tickets) and would rather test a product than sit through a sales process. If you have a procurement team, a tender or a hardware rollout, read the section on when to pick an enterprise vendor first.

The twelve criteria

For each one you get why it matters and the question to put to every vendor in writing.

1. Pricing model. Platforms charge a flat monthly plan, a fee per pass, a fee per active pass, or a quote. Per-pass pricing grows with every customer you sign up, which is fine for a small or short programme and hard to forecast for a growing one. Flat plans are predictable but have limits. See what a wallet pass platform costs in Australia for the arithmetic. Ask: what exactly do you count (issued, installed or active passes, messages, users, templates), and what is the price in AUD including GST?

2. Self-serve signup. If you cannot create an account, build a card and issue a test pass yourself, you are evaluating a brochure. A trial that starts only after a call is a sales process, not a test. Ask: can I sign up today, design a card and add it to my own phone without talking to anyone? Is a card needed, and when does the trial clock start?

3. Apple and Google both. Most customers are on iPhone or Android, so one wallet is half a programme. Check that one template produces both passes, and ask about Samsung Wallet if your customers use it. Ask: does one design issue both an Apple Wallet and a Google Wallet pass? Which wallets are not supported?

4. Who holds the Apple certificate. Every Apple pass is signed with a certificate tied to a Pass Type ID, and that identifier is permanent once passes are issued under it (certificates explained). If the vendor holds it, setup is faster, but you should know what happens when you leave. If you hold it, you control it, and you also renew it. Ask: whose Apple Developer account owns the Pass Type ID? If I leave, do my installed passes keep working, and can they be moved?

5. Pass updates and lock-screen messages. A pass is useful because it can change after install: a points balance, an offer, an expiry. Both wallets support this, with limits (how updates and push notifications work). Messages cost money on some platforms. Ask: can I update every pass at once, and can I message a segment? Is there a message limit or a per-message charge?

6. Loyalty logic. Some tools only issue passes; you then need another system for points, tiers, stamps and rewards. Others include the rules. Passes only is fine for tickets and gift cards, and a gap for loyalty. Ask: where do points, tiers, stamps and rewards live? Which of them are on my plan?

7. POS and ecommerce integrations. A loyalty card that staff must update by hand will not last. The card has to earn from the till or the online store. Ask: which integrations are live today, not planned? Does the one I need work with my plan and my version of the POS? See our integrations.

8. API and webhooks. Even if you do not need one now, an API decides whether you can connect a custom system later. Ask: is the REST API on my plan, what are its rate limits, and do you send webhooks for events such as a pass being installed? Our documentation shows what a real API reference looks like.

9. Data location and privacy. Your customers' names, emails and activity live on the platform. Know where, who processes it, and whether the vendor will sign a data processing agreement. Ask: where is customer data stored, which sub-processors handle it and where, and do you offer a DPA? Compare with our security page.

10. Export and exit. The day you leave, you want your customer list and a plan for the passes already on phones. Ask: can I export every passholder in a standard format today, and what happens to installed passes if I cancel?

11. Support. Pass problems are often Apple or Google problems that need a person who knows them. Response times matter more than a chat widget. Ask: who answers, how fast, and what does my plan include? Is there a named contact at higher tiers?

12. Limits and overage. Every plan has a ceiling. What matters is what happens at the ceiling: a surprise charge, a block, or a conversation. Ask: what happens the day I pass my limit? Is there a hard stop or an automatic charge?

The scorecard

Copy this into a spreadsheet. Give each criterion a weight from 1 to 3 (3 means you would walk away without it), score each vendor from 0 to 3, and multiply. Keep notes: the vendor's exact words and the date.

CriterionWeight (1-3)Score (0-3)Notes
1. Pricing model fits my growthWhat is counted? AUD and GST?
2. Self-serve signup and test passNo call needed?
3. Apple and Google from one designSamsung needed?
4. Apple certificate ownership and exitWho holds the Pass Type ID?
5. Updates and lock-screen messagesLimits and message costs
6. Loyalty logic (points, tiers, stamps)On my plan?
7. POS and ecommerce integrationsLive today?
8. API and webhooksOn my plan?
9. Data location and privacySub-processors, DPA
10. Export and exitFormat, installed passes
11. SupportResponse time, who answers
12. Limits and overageWhat happens at the ceiling?

Score 0 for "not offered", 1 for "offered with a gap or only on a higher plan", 2 for "meets the need", 3 for "meets it and shown to you in a trial". A 3 should come from something you did, not something you were told.

A worked example

Take a Melbourne group with four cafes, a Shopify store, about 3,000 customers who would hold a card and no developer. It scores two anonymous vendor types. Weights: pricing 3, self-serve 3, loyalty logic 3, integrations 3, Apple and Google 3, certificate 2, updates 2, export 2, data 2, API 1, support 2, limits 2.

CriterionWeightPer-pass enterprise platformFlat-price self-serve platform
Pricing model31 (cost rises with every customer, quote needed)3 (flat, predictable)
Self-serve signup30 (demo first)3 (signed up and added a test pass)
Apple and Google333
Certificate and exit22 (own Pass Type ID, they help migrate)1 (vendor holds it; asked what happens on exit)
Updates and messages232
Loyalty logic31 (passes plus API, we would build rules)3 (points and stamps built in)
Integrations31 (custom work)3 (Shopify live)
Export and exit222
Data location23 (region choice)2
API and webhooks132
Support232
Limits and overage222

Multiply and add. The enterprise platform scores 3+0+9+4+6+3+3+4+6+3+6+4 = 51. The self-serve platform scores 9+9+9+2+4+9+9+4+4+2+4+4 = 69. The gap comes from three heavy weights, self-serve, loyalty logic and integrations, which suit this group. Change the buyer and the result changes: a national chain with an engineering team, a procurement process and 400,000 customers would weight API, data region and support much higher and pricing per pass would matter less than a signed contract. The scorecard is not a verdict. It makes your own priorities visible before a salesperson's priorities replace them.

When an enterprise, demo-led vendor is the better choice

Do not force a self-serve product into a job it was not built for. Prefer a demo-led vendor when:

  • Volumes are very large, such as millions of passes, where negotiated per-pass pricing and a dedicated team beat plan limits.
  • You need NFC. Passes that tap at a reader need NFC certificates from Apple or Google and compatible hardware, which is a specialist project.
  • You need bespoke integrations, for example a custom loyalty back end or a legacy point of sale.
  • Procurement requires it. Tenders, security questionnaires, custom contracts and named account managers are what enterprise vendors are set up to supply. Our Enterprise tier covers some of this, including custom contracts and a DPA, but if your process demands a long evaluation, run it.

A fair test for any vendor: if they cannot tell you which of your twelve criteria they are weak on, they have not understood the question.

Red flags

  • No public pricing and no trial. You cannot compare what you cannot see.
  • "Unlimited" with no definition of what is counted or what happens at the ceiling.
  • Pass-only products sold as loyalty. Ask where the points live.
  • Integrations listed as "coming soon". Treat them as not available.
  • No answer on the Apple certificate, or an answer that your passes stop when you leave.
  • No data export or an export that costs extra.
  • Messages priced per send, which teaches you to send less.
  • Pressure to sign before you have issued a test pass.

Where we sit on the criteria

You should score us too. These are facts from our own pages, so check them there. Plans are flat monthly with no per-pass fees, and only active passes count toward a limit, with no automatic overage charge (pricing). You can sign up with no card, and the 60-day trial starts when you publish your first card. There is also a Free plan for up to 250 customers with a card each month. One template makes Apple Wallet and Google Wallet passes. Passes are signed with our certificates, so you do not need your own developer account. Stamp cards are on every plan, points, tiers and rewards are on Growth and above, and so is the full-access REST API. Shopify, Square, Klaviyo, WooCommerce and Zapier work on every plan. Customer data is stored in AWS Sydney, with some sub-processors outside Australia. Passholders export to CSV. Where we are weaker: Samsung Wallet is not supported yet, and above 25,000 active passes pricing is quoted. On the certificate question, mark us down as well: a pass signed with our certificate can only be updated by us and cannot be moved to another vendor's certificate, so if you leave, your customers add a new card from the new platform. Your customer list exports to CSV to make that possible. A paid plan cancels at the end of the billing period. A card already on a phone stays there until the customer removes it, but once the account is closed it stops changing: no new stamps, balances or messages. Moving down to the Free plan instead keeps cards working inside its limits. We do not publish how long a closed account's cards are kept, so ask us before you rely on it. For direct comparisons see compare, the PassKit alternatives page and best digital wallet pass platforms.

Frequently asked questions

How many platforms should I compare? Three is enough. Shortlist from public pricing pages, then run a real test pass on each.

Should I run a trial on every shortlisted platform? Yes, at the same time, with the same card design. Issue a pass to your own phone and an Android phone, then change it and send a message.

How long should an evaluation take? A week of part-time work is usually enough for a self-serve product. Add time only if procurement, security review or an integration build is involved.

Is per-pass pricing a bad sign? No. It suits small or short programmes, and it can be cheaper than a plan with limits you will not use. It becomes a problem when you cannot forecast customers. Price each model against your twelve-month number.

Do I need my own Apple Developer account? Not always. Some platforms sign passes with their own certificate and others ask for yours. Either can be right. What matters is the answer to what happens to your passes if you leave.

All guides

Guides + product

Ready to ship your first wallet card?

Set up takes minutes. 60-day free trial. No card needed.