Adding Your Card to Apple and Google Wallet

Saving your digital card to your phone wallet puts it in the same place you keep loyalty cards and boarding passes: one swipe away, with no hunting through chat threads for a link or opening a browser. The method is broadly the same on both platforms — open your card page on your phone, press the add-to-wallet button, and a pass is created in Apple Wallet on iPhone or Google Wallet on Android. The real benefit is not the appearance but that your card is ready in a second in exactly the situations that do not tolerate delay.

Why bother, when the link exists?

A fair question, and the answer is friction. The link exists in theory, but reaching it in a real moment takes steps: open WhatsApp, find the thread where you sent the link to yourself, scroll, find it, tap, wait for it to load.

Written down, those steps look trivial. In practice they take twenty seconds while somebody waits. Twenty seconds of silence and phone-fiddling in a professional conversation is a very long time.

A wallet removes the whole chain. The card sits in a fixed, known place that nothing else crowds out, and it opens with a single swipe.

The bigger advantage: it works with poor signal

This is the benefit that makes the setup worthwhile. A wallet pass is stored on the device itself, so it displays even with weak coverage or none at all.

Photo by Emil Kalibradov on Unsplash

And the situations where you need it are precisely the ones where signal degrades: a crowded exhibition hall, a basement floor, a lift, a meeting on an industrial estate. Anyone who has relied on loading a web page in those places knows the awkwardness of a spinner that never resolves.

Here the wallet pass shows your name, your title and a locally stored QR code for the other person to scan — which works because scanning is an optical act that needs no connection on your side. Their phone will need one to open the page afterwards, but the process did not stall on you, and the code reached them.

Steps on iPhone

Apple Wallet ships with the device and needs no installation:

1. Open your card page in the mobile browser — Safari handles wallet passes most reliably.
2. Press the "Add to Wallet" button on the page.
3. A preview appears: check the name and title before confirming.
4. Press "Add" at the top of the screen.
5. Afterwards, open the Wallet app directly for quick access.

One practical note: after adding, confirm the pass actually appears in the app. Anyone who assumes it worked without checking discovers the problem at the worst possible moment — in front of someone who is waiting.

Steps on Android

Google Wallet is present on most modern devices and may need installing on some:

1. Confirm Google Wallet is installed and you are signed in.
2. Open your card page in Chrome.
3. Press the add-to-wallet button.
4. Confirm on the screen that appears.

Android's device diversity means the experience varies slightly between manufacturers. If the pass does not appear, the usual causes are a browser other than Chrome, or a wallet app that needs updating.

What the pass actually shows

A wallet pass is not a full copy of your page but a summary designed for fast display. It typically carries your name and job title, a logo or thumbnail, a QR code leading to your full page, and a link to open the card in a browser.

That simplification is deliberate. A pass is a display and sharing device, not a place to browse a catalogue or a service list. Anyone who wants detail scans the code and lands on the full page.

When it genuinely helps, and when it adds nothing

A wallet is clearly useful for anyone meeting people face to face regularly: sales representatives, consultants, business owners who attend events, job seekers during careers-fair season.

It adds much less for people who mostly share remotely — over email or messaging — because there the link is simply pasted and nothing needs opening.

The honest framing is that a wallet pass does not replace your link or a printed QR code. It is an additional layer covering one specific case: you, with your phone, in front of someone, right now.

Updating: worth understanding

A recurring question: if I change my number, does the pass update itself?

The answer needs unpacking. The QR code on the pass points at your page link, and that link is permanent. So any edit you make to the page is seen immediately by whoever scans the code, with nothing to re-add.

The details printed on the face of the pass — name and title — may need the pass re-adding if you change them substantially. The working rule: after any significant edit to your card, delete the old pass and add it again. It takes half a minute and prevents you showing someone a job title you left behind.

How it differs from an NFC card

People conflate these two. Both work by proximity, but the direction is entirely different.

Photo by suraj kumar on Unsplash

An NFC card is a physical object you carry and the other person taps their phone against. A wallet pass is software on your own phone. With the first you hand something over; with the second you display something.

The practical consequence is that NFC asks nothing of the other person beyond bringing their phone close, while a wallet pass requires them to open a camera and scan. NFC is therefore marginally faster in person — but it depends on you actually having the card with you, a condition that fails often in real life. Cards get left in the car or in a different bag.

A wallet pass does not get left behind, because your phone is always with you. Which is why many people run both: the NFC card when they remember it, and the wallet pass as a fallback that never fails. The full comparison is in NFC vs QR.

A note on privacy

A wallet pass is stored on your device, and it displays what you put on your card — nothing more. It does not pull in data from elsewhere and it does not read your contacts.

The point worth noting is that a lost phone means whoever finds it may see the face of the pass if the device is unlocked. That is no different from any other content on the device, but it is one more reason to have a screen lock enabled if you do not.

Sensitive information does not belong on a wallet pass in the first place. A card is a public introduction shown to strangers by design; anything you would not want a stranger to see should never have gone on it.

Mistakes that happen in use

People relying on a wallet in meetings hit three problems, all avoidable.

First, low screen brightness making the code hard to scan, especially in strong outdoor light. Raise the brightness before you present it, not after a scan fails.

Second, holding the phone at an angle or moving while it is being scanned. Brace your hand or rest the phone on a surface.

Third, and most embarrassing, adding the pass and never testing it. Scan your own code with another phone once after adding, and you will never discover a fault in a moment that cannot absorb one.

For teams and companies

In organisations, wallet passes are easy to adopt because they need no training. An employee adds theirs once and it stays with them.

The larger benefit is administrative. When team cards are managed centrally, changing a head-office address or branch numbers propagates to the pages those wallet codes point at, across every employee, without anyone being asked to do anything. That pattern is covered in NFC cards for teams and employees.

Set it up now

Setup takes a minute, and the payoff arrives at the first meeting where you cannot find your link quickly. Add your card today, test it once, then forget about it — these are tools whose value lies in being ready without being thought about.

If you have not built your card yet, the steps are in how to create a digital business card, and the other sharing methods in NFC vs QR.

With AurCard you can add your card to Apple or Google Wallet from the page itself, and the code stays tied to details you can update at any time.