WalletWallet API

Digital punch cards for Apple and Google Wallet

Put your stamp card in every customer's phone, where the count updates the moment they buy, with no app to install and no paper card to lose.

Apple Wallet Google Wallet

A whole stamp program runs on $39 a month.

The self-serve alternative to PassKit, PassSlot, or Pass2U, with public pricing.

From a paper punch card to one on their phone.

  1. 1

    Design the card

    Set your brand color, logo, fields, and barcode in the visual editor, with a live preview and no code. The field reference has the full list.

  2. 2

    Get your customers on it

    Each customer's card is one POST /api/passes. Issue them whichever way fits:

    Sign them up at the counter

    Add a customer in the Pass Manager, right from the phone behind the till. Right for a steady trickle of regulars.

    Issue from a signup form

    Connect a simple form through Zapier, n8n, or a plain HTTP request, and everyone who fills it in gets a card automatically.

    A developer runs a short loop

    Loop a script over your newsletter list, one POST per customer. See the create call.

  3. 3

    Hand them one link

    Every card gets a branded link that opens the right wallet for whoever taps it. Text it, email it, or show it as a QR at the register; it stays the same through every stamp.

  4. 4

    Stamp at the counter

    Scan the code or go by the name on the card; each stamp is one update to the count field, and the card refreshes on the customer's phone. Barcodes come as QR, PDF417, Aztec, or Code128, so an existing scanner reads them.

Run the whole card, first stamp to free coffee.

Stamps, rewards, resets, and nudges, each one update to the card the customer already holds, from the Pass Manager or your own system.

  1. A stamp lands

    Add a stamp with one update to the card the customer already holds, and notify their lock screen while the new count appears in their wallet.

    The seventh stamp reaches the lock screen

  2. The card fills

    When the card fills, use the same update to reveal the reward so staff can see it at the till without counting holes in a paper card.

    The same card, ready to redeem

  3. The reset

    When a customer buys another pack, reset the count on the card they already carry while keeping the same link and serial.

    The same pack, refilled

  4. The nudge

    Bring an inactive customer back with one update that puts a reminder on the card already in their wallet and reaches their lock screen directly.

    An inactive card gets a nudge

  5. The duplicate

    When a completed card appears on two phones, revoke it once so it greys out across both wallets and every device, then issue the customer a fresh card.

    One card, revoked everywhere

Punch card software that runs beside your till.

A stamp is one plain HTTP call, so there is no POS plugin to install or keep updated.

Export anytime

Pull your customer list out of the Pass Manager as a CSV. Each row carries the card's share URL, ready for a mail merge.

No plugins to maintain

The card runs beside Square, SumUp, or whatever runs the till: wire the stamp into a Zapier or n8n flow, or add it from the Pass Manager on your own phone at the counter.

The math for a real stamp program.

Billing counts each new card and each stamp that changes one. One card covers both wallets and counts once, and a revoke is free. PassKit runs around $1,300/month for the same lifecycle.

A cafe stamping 200 cards a day

WalletWallet
New cards per month
~150
Stamps added per month
~6,000
Pro allowance
100,000/month
Total $39/month, flat

The whole program uses about 6% of the allowance, well under a cent per stamp, Pass Manager and full branding included.

Thank you

A three-location bakery

WalletWallet
Cards in circulation
2,500
Stamps across three counters
~15,000/month
Pro allowance
100,000/month
Total $39/month, flat

All three locations share one plan and one allowance. Even a 150,000-pass month is $39 + 50,000 x $0.00039 = $58.50.

Thank you

One pass covers both Apple and Google and counts once. Creations and content updates count, revokes do not. Full pricing.

Frequently asked questions

Do customers need to download an app?

No. Apple Wallet and Google Wallet are built into every iPhone and Android phone. The customer taps Add to Wallet on the card's page and the stamp card sits next to their boarding passes and tickets.

Can I set this up without a developer?

Yes. Design the card in the visual editor, then run the program from the Pass Manager: add a customer, bump a stamp count, or revoke a card, all by clicking. The API is optional.

How does a stamp get added to the card?

Each card has a serial number. You PUT the new count to that serial and the card updates in place on every phone it is installed on, same link, no reissue. The count is a text field on the card, like 7 of 8, rather than a printed grid of stamp holes. Set a changeMessage on the field and the customer sees a note with the new count.

Can whoever is at the counter add stamps without a computer?

Yes. The Pass Manager works in a phone browser, so the person on the till opens the customer's card, changes the count, and saves. For a busier counter, wire the PUT into a Zapier or n8n flow once so a single tap adds the stamp.

Can we scan the card at the counter?

Yes. Put the customer ID in barcodeValue and pick the format your scanner reads: QR, PDF417, Aztec, or Code128. The barcode renders in both wallets and scans like any plastic card. Without a scanner, the name on the card works too.

Does this work on both Apple and Google Wallet?

Yes. One POST /api/passes returns the signed .pkpass and a Save to Google Wallet link for the same card, and it counts as one pass. Updates and push work on both. Your stamp message shows on the Apple lock screen; Google's banner is generic and the new count shows inside the card.

What if a customer loses their phone?

The card lives on our servers, so nothing is lost. Resend the same install link and the card, with the current stamp count, adds to the replacement phone under the same customer ID.

What happens when a customer gets a new phone?

Passes usually transfer automatically when the new phone restores from an iCloud or Google backup. If one does not, or the customer switched platforms, resend the same install link and the card adds in a tap.

Can someone screenshot a full card and claim the reward twice?

Cards ship with the Apple Wallet share button hidden (sharingProhibited), so a customer cannot hand the live pass to a friend. A screenshot is still possible, but the barcode resolves to one customer ID, so a shared image reads as the same person twice at the counter, and you can revoke a card that misbehaves.

What happens when the card is full?

The customer redeems the reward and you PUT the count back to zero. The same card in their wallet starts the next round without a reissue, on the same link and serial.

Punch card or points card, which do I want?

A punch card counts visits toward one fixed reward, then resets: eight stamps, then a coffee on the house. A points card accrues a spendable balance, tiers, or cashback; for that, see digital loyalty cards. Both are the same two API calls, just a different field.

What does it cost to run a stamp program?

Pro is $39 a month flat with 100,000 passes a month included (creations plus updates), then $0.00039 per pass beyond that. A cafe stamping 200 cards a day logs about 6,000 passes a month, around 6 percent of the allowance. One card covers both wallets and counts once, and revokes do not count.

Issue your first pass in five minutes.

Build a stamp card and install it on your own phone tonight, with 30 days of Pro on every new account.

curl -X POST https://api.walletwallet.dev/api/passes …