Customer Tokens: Wallet Pass Downloads & App Session Links

JeriCommerce lets you generate tokens to create two types of links for your customers: download links for their wallet pass (Apple Wallet / Google Wallet) and session links to log them directly into the Customer App.

These links are perfect for sending via email campaigns, SMS messages, or embedding in your own website or app.

‍

‍

What You Need

• Your API Key — find it in JeriCommerce Admin → Settings → API Keys
• Your Program ID (or slug) — visible in your program settings
• The customer's email address

‍

‍

How It Works

1. Call the Get Customer Token endpoint with the customer's email and the type of token you need.
2. The API returns an accessToken.
3. Encode the token in Base64 and build the URL using the formats below.

‍

‍

Wallet Pass Download Links

To generate a link where the customer can download their loyalty card, request a token with token_type=download and build the URL:

https://jeri.link/{program-slug}/download?token={base64Token}

When the customer opens this link, they will see a page to choose between Apple Wallet and Google Wallet.

JeriCommerce already syncs this download URL automatically through integrations. If you use Shopify or Klaviyo, you may not need to generate this link manually. See Synchronize the download URL Loyalty card with Shopify profiles, Sync Custom Fields with Shopify, and Sync Custom Fields with Klaviyo for details.

‍

‍

Customer App Session Links

To generate a link that logs the customer directly into a specific section of the Customer App, request a token with token_type=auth and build the URL with a redirectTo path:

https://jeri.link/{program-slug}/{base64Token}?redirectTo={path}

Available Sections

For example, use the loyalty/rewards path to send customers directly to their rewards page from a promotional email.

‍

‍

URL Formats at a Glance

‍

‍

API Documentation

For the full endpoint specification, request parameters, code examples, and error handling, see the Get Customer Token endpoint in the JeriCommerce API documentation.