PassFast vs WalletWallet

Same job (wallet passes). Different meter — know which fits your usage.

Start freeDocsMCP
Compare

PassFast and WalletWallet

PassFastWalletWallet
SigningManaged (PassFast)Managed (WalletWallet)
Apple+GoogleOne API; counts as 1One API; both wallets count as 1
Pricing model$0.015 / active / moOps quota (anti-active — operations, not live passes). Pro $39 · 100,000 create+update / mo. Business $99 · 1,000,000 create+update / mo (soft limit past). Scale from $379.
Free tier100 generates once$0 · 1,000 create+update / mo
MCPRemote HTTPS, sk_live_ bearerTBD
TemplatesVisual template builderTBD

Same facts in markdown: passfa.st/compare/walletwallet.md

Meters

Which meter fits

When PassFast fits

  • You keep passes alive (loyalty, membership, tickets) and want a predictable per-active meter.
  • You want Apple + Google from one API call, billed as one unit.
  • You want managed signing and remote MCP with a secret key (`sk_live_`).

When ops-quota may fit

  • You create and update in bursts against a monthly operations budget, then do not keep a large live set.
  • Your usage maps to a create+update quota ($0 · 1,000 / $39 · 100,000 / $99 · 1,000,000, per WalletWallet public pricing).
  • You prefer an operations cap over an active-pass meter.

Start issuing wallet passes

First 100 generates are free. No seats, tiers, or minimums.

Start freeDocsMCP