E-commerce

Add “Add to Wallet” in e-commerce journeys to distribute account-linked Apple Wallet and Google Wallet passes, then connect them to in-store operations through POS scanning.

E-commerce integration is typically an omnichannel topic. The goal is to let customers use the same account online and in-store, without requiring a mobile app. A wallet pass acts as a persistent, scannable credential that links the e-commerce identity to in-store systems through POS integration.

This approach reduces dependency on checkout emails and account logins at the point of sale. It also simplifies customer recognition, loyalty attribution, and benefit redemption across channels.

Real-world examples

• Retail loyalty: a loyalty pass is added from the e-commerce account page, then scanned in-store to attach purchases to the profile.

• Clienteling: a membership pass barcode is scanned to retrieve tier and benefits in POS or clienteling tools.

• Gift cards: a wallet gift card is added from the account area, then updated as balance changes after redemptions.

• Click & collect: a pickup pass is issued for the collection flow, then scanned in-store to release the order.

Core omnichannel use cases

In most retail programs, wallet passes distributed from e-commerce are account-linked, not order-linked. The pass represents an ongoing relationship (loyalty, membership, stored value). It stays stable over time and updates when the customer profile changes.

Common patterns:

• Loyalty / membership pass: customer identifier + points + tier + benefits.

• Wallet gift card: stored value + barcode/QR for redemption + balance updates.

• Customer recognition at POS: scannable identifier that unlocks profile lookup and omnichannel attribution.

• Pickup pass (pick & collect): order-linked, used when an in-store scan is required to release a prepared order.

Where to place “Add to Wallet” in e-commerce

Placement should match the moment the pass becomes useful as an account credential. In practice, this is usually when a customer is authenticated, or when enrollment is completed.

1

My Account / profile area (primary)

The account area is the most stable placement. It works for loyalty and membership, supports reinstall flows, and avoids linking the pass lifecycle to a single order.

2

Post-registration / post-login moments (secondary)

After a signup or login, an “Add to Wallet” CTA can be shown as part of onboarding. This is often the highest-intent moment for new program members.

3

Transactional email (fallback)

Email is useful as a recovery channel. It helps when the web CTA is missed, when purchase is completed on desktop, or when the customer changes device.

4

Pick & collect pages (order-linked exception)

When the pass is used as a pickup token, the best placement is in the pick & collect flow (confirmation page and/or dedicated pickup page). This keeps order-linked passes limited to cases where an in-store scan is operationally required.

Updates and lifecycle (profile events → pass updates)

When profile data changes, the pass can be updated. Wallet apps can surface updates as native notifications. This keeps the pass trustworthy and reduces friction at the point of sale.

Typical update triggers in an omnichannel setup:

• Points and tier changes after purchase (online or in-store)

• Benefit eligibility changes (new perks, expired perks, special statuses)

• Gift card balance changes after redemption or reload

• Store preference changes (preferred store, local store list)

• Pick & collect status changes (ready, delayed, collected) when a pickup pass is used

Wallet notifications are tied to an installed pass. They do not require a mobile app installation.

Pass content checklist (what to include)

The pass should answer “who is this customer account” and “what is currently available”. Everything else belongs behind a link to authenticated pages.

Recommended fields:

• Brand name and support contact (email/phone/URL)

• Membership / loyalty identifier (visible + scannable barcode/QR when needed)

• Points balance, tier, and tier progress (when applicable)

• Benefit summary (what can be used in-store and online)

• Store list or store locator deep link (when relevant)

• Deep links (account page, loyalty dashboard, gift card management, customer service)

If a pick & collect pass is implemented, the pass typically adds:

• Pickup reference (not the full order)

• Pickup location and window

• Pickup QR/barcode used by staff

Implementation with The Wallet Crew

E-commerce integration typically combines distribution, profile linkage, and in-store scanning:

1. Create (or retrieve) the pass from a stable customer identifier (CRM id, loyalty id, e-commerce customer id).

2. Expose an “Add to Wallet” CTA in the e-commerce account journey.

3. Connect POS scanning so the pass can be used for identification and redemption in-store.

4. Send profile events to The Wallet Crew so the pass stays current (points, tier, balances, benefits).

For a website-first implementation of the CTA, see On your website. It covers device detection (Apple/Google) and a desktop fallback.

The same “Add to Wallet” button can be embedded on any website page controlled by the Brand, as long as the page can load the cinto SDK (for example: account area, checkout confirmation, order history, gift card pages, or clienteling portals).

POS integration (what completes the omnichannel loop)

A wallet pass becomes the “missing link” between online and physical channels when it is scannable at the point of sale.

The common pattern is:

• the pass encodes a stable identifier in a barcode/QR (or a secure token resolved server-side)

• staff scan the pass at checkout

• the POS (or a connected loyalty/CRM layer) uses that identifier to retrieve the customer profile, apply benefits, and attribute the transaction

POS integrations are documented under POS.

E-commerce platform guides

Use the platform-specific guides below when a storefront integration is required (typically in account pages or authenticated areas).

• Salesforce Commerce Cloud (SFCC)

• Shopify

• Adobe Commerce (Magento)

• Prestashop

For any other e-commerce stack (or a custom website), use On your website. The same button can be embedded on any page, as long as the cinto SDK can be loaded and a stable identifier (or passId) is available server-side.

FAQ

Is “Add to Wallet” only relevant for tickets or boarding passes?

No. Wallet passes work well as customer credentials. Common examples include loyalty and membership cards, wallet gift cards, pickup confirmations, and service bookings.

Is a mobile app required to use Wallet passes?

No. Wallet passes work independently from a mobile app. This lowers adoption friction for one-time or occasional buyers.

Can a pass be updated after it is added?

Yes. Pass data can be updated after installation. Customers can also receive a Wallet notification when an update occurs, depending on platform behavior and configuration.

Is it compatible with both Apple and Google devices?

Yes. The Wallet Crew supports Apple Wallet and Google Wallet. Distribution and update flows are unified at the platform level.