How Walletap works

Walletap puts your business's cards into the wallet that is already on your customers' phones. You set things up in the browser and run the counter from an app. Your customers install nothing: they keep your card in Apple Wallet or Google Wallet.

Where each part runs#

Walletap also hosts the pages your customers see: the sign-up page where they join, and the pass page where they add the pass to their wallet. Both follow your template's design, and pass pages can be served from your own domain.

All three working surfaces sign in to the same account, so a template designed in the browser is ready to scan on the phone straight away. For which app suits which job, see Which app do I need?

Templates, passes and members#

A template is the design and the rules of one kind of card: the Coffee Card, the Northside Membership, the Summer Jazz Night ticket. It sets the pass type, the colours and images, which fields appear, how the card is scanned and what the sign-up form asks for.

A pass is one card issued from a template to one person, kept in their wallet. It carries that person's own values: their name, their stamps, their points or their balance.

A member is the person a pass belongs to, listed on the template's Members tab. One member can hold more than one pass.

How a pass reaches a customer#

A pass can be issued in several ways, and they all end on the same pass page:

• The customer signs up. They scan your sign-up QR code or open its link, fill in the form and get the pass straight away. See Sign-up page.
• You add them. Add a member in the dashboard or an app, and Walletap can send them the pass link by email or message. See Add members.
• You import a list. Upload your existing customers in one go. See Import and export.
• They buy a membership. A customer who buys a membership in your webshop gets the pass when the payment goes through. See Webshop.
• Your own system issues it. Over the API, a new pass is emailed or texted to its holder whenever you include their contact details. See Issue your first pass.

The life of a pass#

Issued#

The pass exists in Walletap and has a pass page, but it is not in anyone's wallet yet.

Added to a wallet#

The customer taps Add to Apple Wallet or Add to Google Wallet and confirms in the wallet. The wallet tells Walletap, and the Devices column on the member's pass counts how many wallets hold it. If the customer removes the pass, the count drops again. See Apple Wallet and Google Wallet.

Used#

Staff scan the pass with the mobile app's camera or with a card reader at the front desk. A valid scan is recorded against the pass, and the app offers what fits the card: stamps, points, a reward or a membership renewal. See Scanning a pass.

Updated#

When anything on the pass changes, such as a stamp, a points balance or a field you edit, Walletap sends the new version to the customer's wallet, usually within seconds. Campaigns use the same channel to put a message on the pass and raise a notification. See Campaigns.

Expired or invalidated#

A pass stops working in one of two ways:

• It expires. Its native Valid until date passes, the wallet moves it to its expired passes, and scans are refused with "Pass expired". Extending the date brings it back. Renewable memberships show their end date in a custom field instead, so the pass stays in the wallet between renewals. See Pass types.
• You invalidate it. Choose Invalidate on the member's pass. Apple Wallet marks the pass as void, Google Wallet marks it inactive, and scans are refused with "Pass has been invalidated". Activate reverses it.

An invalidated pass shows as Invalid on the template's Members tab straight away; an expired one does once the daily expiry check has run.

Next steps#