Apple & Google Wallet Passes

A ScaanMe wallet pass is your digital business card living right inside the phone's wallet app — Apple Wallet on iPhone and Google Wallet on Android — next to the customer's boarding passes and loyalty cards. Unlike a saved contact that gets buried in thousands of phone numbers, a wallet pass is a beautiful, branded card with your logo, colors, a tappable QR/link, and your key details on the front and back. From a single editor, ScaanMe issues both an Apple pass and a Google pass, so every customer can save you no matter which phone they carry.

The single biggest reason a pass beats a saved contact is auto-sync: the pass never stores your details directly — instead it carries one private pointer (a /w/{token} link) that always resolves to your latest card. When you change your phone number, add a new service, or update your hours, you edit your card once and the pass silently updates on every holder's phone — no reissuing, no asking customers to re-save. A paper card or a saved contact freezes the moment it's captured; a wallet pass stays correct forever.

This guide is for any ScaanMe card owner who wants to be saved, found, and remembered — sales reps, clinics, real-estate agents, retailers, founders. It walks through the whole flow: picking a luxury template, designing the pass field-by-field in the 3-room editor (Shared, Apple Wallet, Google Wallet), the Add-to-Wallet buttons your customers tap, how auto-sync keeps every pass fresh, and how each wallet save lands in your CRM as a distinct Apple or Google engagement event. Where a wallet feature depends on your plan, we call it out.

What & why: Before designing, you choose the overall look. ScaanMe ships 21 photoreal luxury templates — designed materials like Onyx, Carrara marble, Brushed Gold, Damascus steel, Carbon, Saffiano leather, Mashrabiya and Arabesque heritage patterns — each with a locked, contrast-correct palette. Picking a template replaces a plain colored background with a premium textured one and guarantees your text stays perfectly legible, because the colors are pre-tuned by designers, not by you.

From the owner dashboard, open Wallet (user/wallet) — this is your wallet command center, listing every card with its save, scan, and removal counts. Find the card you want to issue a pass for and click Edit (user/wallet/{card}/edit) to open the customize screen titled "Customize wallet." If you don't see the Wallet area at all, your current plan doesn't include wallet passes yet — upgrade to unlock issuance.

Inside the editor, open the Apple Wallet room (more on rooms in Step 2) and look at Strip material — the luxury collection. The first card, Standard (Theme cover), keeps your brand color or cover photo. Click any material tile (Onyx, Carrara, Gold…) to apply it; the live preview updates instantly. The luxury collection is part of the top tier, so if the gallery is greyed out or a selection won't stick, it isn't included in your plan — ScaanMe quietly drops a non-entitled template rather than saving a broken pass.

When a luxury template is active, an optional Foil monogram (your initial) checkbox appears — it embosses your first initial in the template's accent color, kept clear of the name area for a bespoke, debossed-foil finish. Monograms render in Latin script in this version (Arabic shaping is being added). Once a template is chosen, its palette locks the brand and label colors so you can't accidentally break the contrast — those controls show a "Locked by the template palette" note.

What & why: The editor is split into three rooms (tabs at the top): Shared (settings that apply to both passes — logo, brand color, QR action, which fields show, cover banner), Apple Wallet (Apple-only finishing — strip material, label color, back-of-pass order, update notification), and Google Wallet (Google-only background override and a note of what Google controls). This split exists because the two platforms render passes differently; the Shared room saves you doing the work twice, while each platform room lets you fine-tune the bits only it controls.

Shared → Logo. Click Choose file to upload a PNG or JPG logo (it applies to both passes). Leave it empty to reuse your card logo automatically. Then pick a Logo style: Fit (whole logo) keeps the entire mark visible with padding — and reveals a Logo size slider (50–100%) to zoom it; Circle (fill) and Square (fill) crop edge-to-edge, best for photos or full-bleed marks. Note Google always displays the logo in a circle and pads it automatically so nothing is clipped. If you've uploaded a custom logo before, a Remove custom logo (use card logo) checkbox lets you revert.

Shared → Brand color sets the base color of both passes via a color picker and a hex field (e.g. #015AC4). This is the foreground of a Standard pass. Important edge case: if you selected a luxury template, this control is dimmed and shows "Locked by the selected template palette" — the template owns the colors. Shared → When the QR is scanned controls where the pass's QR/link sends people: Open my card (default — the full vCard), Save my contact (vCard) (downloads a .vcf straight to their phone), or Open WhatsApp (jumps into a chat with you). You can change this anytime without reissuing the pass.

Shared → Show on the pass is a grid of checkboxes choosing which details appear: Phone numbers, Emails, Links & socials, Address, plus (when your card has them) a WhatsApp button, a "Book now" link, and Business hours, and an "Open my card" button. Untick anything you'd rather keep private on the pass. Shared → Cover banner toggles whether your cover photo becomes the visual band — the Apple strip and Google banner — with a smart crop and a legibility scrim so your name stays readable on top. Leave it on to use your card cover, or Upload cover (a wide ~3:1 image) for a wallet-specific banner. A luxury template replaces this banner with its material.

Apple Wallet room. Besides Strip material (Step 1), set the Label color — the tiny field labels on the Apple pass; it's checked for WCAG legibility (4.5:1 contrast) before saving and rejected if too faint, or you can hit Reset to automatic to let ScaanMe pick light/dark by luminance. Back of the pass — order lets you drag the back fields (Bio, WhatsApp, Website, Booking, Address, Business hours) into your preferred order; "Powered by ScaanMe" always stays last. Update notification is the short line iPhone holders see on the lock screen when your pass changes — e.g. New from {name} — %@ (the %@ is where the change text appears; ScaanMe adds it if you forget).

Google Wallet room. Google passes inherit your Brand color, but you can set a different Google background here just for Google via its color picker, or click Use shared color to fall back. The room also lists what Google decides for you: text and label colors are chosen by Google for contrast (you can't override them), links and detail rows render in the details view below the card, the logo is masked to a circle (padded so nothing is cut off), and images are fetched and cached by Google — so a change can take a few minutes to appear. Both rooms show a true-placement live preview so you see exactly what holders will see before saving.

What & why: "Issuing" doesn't mean generating a file you have to send — it means saving your design so the pass becomes available the instant a customer taps to add it. ScaanMe builds the actual pass on demand: a signed Apple .pkpass (Pass Type ID pass.com.scaanme.card, team Y438GGXPQ3) and a live Google Wallet object created through Google's API. Your card and pass share one identity, so issuing is really just "save your design."

When your design looks right in both previews, click Save & update both wallets at the bottom. ScaanMe persists your settings and notes that "Saving updates the card on every phone that saved it — Apple and Google." Behind the scenes it composes the artwork once (for visual parity across both passes) and queues a sync to Apple devices and a patch to the Google object — so existing holders update too, not just new ones.

Now customers need a way to add the pass. On your public card page, ScaanMe shows the Add to Apple Wallet and Save to Google Wallet buttons. A customer simply opens your card (by QR, NFC tap, or link) and taps the button for their phone — Add to Apple Wallet on iPhone, Save to Google Wallet on Android. iPhone receives the .pkpass and shows Apple's native "Add" sheet; Android opens Google's pay.google.com save flow. No app install, no account, no friction.

Edge case — which button works on which phone: the Apple button only completes on iOS/Safari (iPhone, iPad), and the Google button completes on Android or any browser signed into Google. If a customer taps the "wrong" one for their device the platform simply won't add it, so it's fine to show both buttons everywhere. Tip: because the pass QR points to your live card, you can hand out the same pass at an event and update the destination later (Step 2's "When the QR is scanned") — e.g. switch it from your card to a booking link for a campaign.

What & why: The magic of a ScaanMe pass is that it is a permanent pointer, not a snapshot. The pass holds only a private token (/w/{token}); your name, number, hours, and links live on your card and are resolved live every time. That's why editing your card — or your pass design — propagates to every holder's phone automatically. You never re-send anything, and customers never have a stale card.

Concretely: change your phone number on your card and Save & update both wallets. On Android, ScaanMe patches the Google object so the change appears (sometimes after a few minutes, since Google caches images). On iPhone, ScaanMe rebuilds the signed pass and sends a silent push so Apple Wallet pulls the new version — and if you wrote an Update notification (Step 2), the holder sees that line on their lock screen. Auto-sync is smart: if nothing visible actually changed, no push is sent, so you never spam holders with empty notifications.

Edge case — revoking a pass. If you delete a wallet pass from the dashboard, ScaanMe expires the Google object (it disappears from the holder's wallet) and marks the pointer revoked, so its QR immediately answers "gone" — instantly, because the link is resolved server-side, not baked into the pass. The reverse is just as powerful: you can re-point or re-activate without ever asking customers to re-save. The pass and its pointer outlive any single change.

What & why: A wallet save is one of the strongest buying signals you can get — someone chose to keep you in their phone's wallet. ScaanMe treats every save, scan, and removal as a tracked engagement event feeding your CRM, so wallet activity isn't a vanity number — it's pipeline. Crucially, Apple and Google are tracked distinctly: each pass has its own pointer, so a save lands as either an Apple Wallet or a Google Wallet event, never a blurred "wallet" lump.

Open the Wallet dashboard to see the intelligence view: per-card and total KPIs for saved, scanned, save-click, and removed, with a selectable window (7/14/30/90 days) and a platform filter (All / Apple / Google). You get daily sparklines, period-over-period deltas, a net audience figure (saves minus removals per platform), a save rate (saves ÷ taps), wallet-sourced visits, repeat openers, and the count of identified holders — contacts the CRM has put a name to. Badges flag cards that are top, growing, or need attention (issued, had engagement, but quiet for a week).

How identity works differs by platform — an important honest detail. Apple registrations tie a save to a device, and ScaanMe can often link that activity to a known contact, so an Apple save can be an identified holder. Google's save callback is anonymous by design — Google doesn't reveal who saved — so a Google save lands as an anonymous engagement edge that later gets linked if the same person interacts in a recognizable way. Either way, the scan events (every time someone taps the pass QR) carry a ?s=awallet or ?s=gwallet stamp, so your visit attribution always knows the traffic came from a wallet, and which one.

Pick a luxury template that matches your trade. ScaanMe maps verticals to sensible defaults — real estate to Onyx, jewellery to Gold, clinics to Carrara marble, mechanics and construction to Carbon — because the texture sets an instant tone. A photoreal material makes the pass look like a premium membership card rather than a generic colored rectangle, which directly lifts save rates.

Keep the front lean, push detail to the back. The Apple pass front shows your name on the strip plus up to three small fields (title, primary phone, short hours). Use Show on the pass to surface only what matters at a glance, and let the back of the pass carry the long list — bio, links, address, booking. A cluttered front reads as noise; a clean front with a rich back reads as designed.

Use the QR action deliberately. If your goal is bookings, set When the QR is scanned to your booking flow or Save my contact to capture the lead; if relationships matter most, keep Open my card. Because this is repointable live, you can run the pass as a campaign tool — point it at a launch page this week, back to your card next week — with zero reissue.

Check both previews before saving, and mind Google's caching. The Apple and Google rooms render true-placement previews, but the platforms differ: Google chooses its own text colors for contrast and masks the logo to a circle, so confirm your mark survives a circular crop. After saving, give Google a few minutes to refresh fetched images before judging the result on a real device.

Treat wallet removals as feedback, not failure. A small removal rate is normal. Watch the dashboard's attention badge and the audience trend: a spike in removals right after a change usually means the change confused holders — for example a notification that felt like spam. Update thoughtfully, write a clear Update notification, and removals stay low.

Do I need to make two passes, one for Apple and one for Google? No. You design once in the 3-room editor and ScaanMe issues both an Apple pass and a Google pass from that single design. The Shared room covers everything common (logo, brand color, fields, cover, QR action), and the Apple/Google rooms only fine-tune the platform-specific bits. Your customers each tap the button for their own phone.

If I update my card, do customers have to re-save the pass? Never. The pass is a live pointer to your card, so changes flow automatically — Google patches the object, Apple pushes the rebuilt pass — to every phone that already saved it. The only time a holder loses the pass is if they delete it, or you deliberately revoke it from the dashboard.

What does the customer actually see when they save it? On iPhone, the pass slides into Apple Wallet with your strip image, name, a couple of fields, and a scannable QR — accessible from the lock screen. On Android, it appears in Google Wallet with your circular logo, banner, brand color, and the same QR; tapping it opens a details view with your links and rows. Whatever the QR is set to (open card, save contact, WhatsApp) is what fires when scanned.

Why does a Google save sometimes show no name in my CRM, but an Apple one does? Because Google's save notification is anonymous by design — it tells ScaanMe a save happened, not who did it — so it lands as an anonymous engagement event and gets linked later if that person interacts identifiably. Apple registrations are tied to a device and can more often be matched to a known contact. Both still count fully toward your audience and save metrics.

Can I change the QR's destination after people have saved the pass? Yes — that's a core advantage. In the Shared room, When the QR is scanned can be switched between Open my card, Save my contact, and Open WhatsApp at any time, and it takes effect on already-saved passes instantly, because the destination is resolved on our server, not stored inside the pass. No reissue, no re-save.

The luxury templates or the Add-to-Wallet buttons aren't showing — why? Wallet features are plan-gated. The 21 luxury templates require the top tier; Apple and Google issuance each have their own plan flag, and Apple additionally requires the signing certificate to be configured. If a control is greyed out, a selection won't save, or a platform's button is missing, that capability isn't in your current plan — upgrade to unlock it. Note that scan/save tracking still runs regardless, so your analytics are never lost.