A member list from your CRM
Export members with their number, tier, and renewal date. Each row becomes a member card, and the renewal date is a field you can update later from Pass Manager.
Batch import
Upload a CSV, design one template with your columns as tokens, and every row becomes a pass with its own share link. Download the results and mail merge the links.
An Atlanta nonprofit issued 199 passes from one batch on the day it signed up.
Any list with one row per person becomes one pass per person.
Export members with their number, tier, and renewal date. Each row becomes a member card, and the renewal date is a field you can update later from Pass Manager.
Name, ticket type, and seat from your ticketing export. Each guest gets a ticket with a barcode of their own, and the batch CSV gives you the link to email them.
A column for the photo URL, one for the ID number, one for the year. Revoke a card from Pass Manager the day someone leaves.
Points and tier from your till or shop platform. The passes carry the balance, and the API or Pass Manager moves it as customers buy.
A header row and one row per pass, with your own column names. The file is read in your browser and you see the columns it found and a few sample rows before anything is created.
Every column becomes a {{token}} you can drop into any field, the barcode, or the logo text. The preview fills the template with real rows as you build it.
The batch runs in the background and reports each row. When it finishes you download a CSV with every pass's serial and share link, ready for a mail merge.
What customers learned running their first batches.
Four duplicate rows in the sheet gave four members two cards each. Remove duplicates from the CSV before you upload it.
A student club
The roster stays in a Google Sheet. The club exports it as CSV when it needs new cards, so the member list never leaves its own account.
A 250-member motorcycle club
The gym imported about 900 members over three days, then added the 30 to 50 new members a day one at a time.
A gym
A header row and one row per pass. Column names are yours, and each becomes a token in the template.
{{name}} in a field, {{member_no}} in the barcode, {{tier}} in the logo text. The preview substitutes real rows.
100 on Free and the trial, 1,000 on Pro and Business. Run as many batches as you need.
The whole file is validated first. A bad row stops the batch before anything is created and is named, so you fix the sheet and upload again.
Once it runs, each row is its own pass. A row that fails is reported with its error and the other rows finish.
Row number, status, serial, and share link for every row, so a mail merge sends each person their own link.
Each row is capped at 2KB, so a photo or logo comes from a URL in a column rather than the file itself.
Every pass from a batch is a normal pass: it shows in Pass Manager, updates by serial, and can be revoked.
Search the batch in Pass Manager and send a Campaign to exactly those passes.
Something else? Write to us from the chat in the dashboard, or at hello@walletwallet.dev.
A header row, then one row per pass. Any column names, in any order. Keep the values that go on the pass short, and put image addresses in a column as URLs.
The results CSV has a share link for every row. Send it in a mail merge, an SMS, or a QR code. The link opens Apple Wallet on an iPhone and Google Wallet on Android, and it stays the same through every update.
Yes. Each pass has a serial, so you edit it from Pass Manager or with a PUT over the API. A new batch with the same people creates new passes, not updates.
A problem the check can see, such as a field that is too long, stops the batch before it starts and names the row. A row that fails while the batch runs is reported with its error, and the other rows finish.
Yes, one pass per row, against the same monthly count as the API. Pro includes 100,000 pass operations a month.
Free under 1,000 passes a month. $39 flat above that, with a 30-day trial on every new account.