Transferring Wallet Passes to The Wallet Crew

The Wallet Crew offers a seamless way to migrate active wallet passes from an external system. This guide will walk you through the configuration, export, and import process for transferring your passes to The Wallet Crew.

Prerequisites and Overview

Before importing passes, ensure that The Wallet Crew is set up to emit passes that align with your system’s configuration.

Key Points to Remember:

• No Personal Data Storage: The Wallet Crew does not store personal information. Each pass is linked to external identifiers, enabling real-time connectivity with your system.
• Multiple Identifiers: A single pass can be associated with multiple external identifiers.

1. Configure The Wallet Crew for Your Environment

Apple Configuration

1. Pass Type Identifier:

   • Use the same Pass Type Identifier for both the previous system and The Wallet Crew.
   • The Wallet Crew requires a certificate linked to this identifier.

2. Access to Apple Developer Account:

   • If you do not have access to the account owning the Pass Type Identifier, request the account owner to release it. Afterward, create a new Pass Type Identifier in your account.

3. Certificate Configuration:

   • Follow the Apple Wallet Certificates Guide for detailed setup instructions.

Google Configuration

1. Google Pay and Wallet Account:

   • Passes are linked to a Google Pay and Wallet account. You must have access to this account to proceed with the migration. It is not possible transfer passes from Google Pay and Wallet account to another account.

2. Account Management:

   • Access your account through the Google Business Console.

2. Export Passes from the Previous System

Request the following information from your previous pass provider. For each pass, you’ll need:

• Serial Number (Apple): The unique identifier of the pass.
• Authentication Token (Apple): A secret used for securing the pass, required for updating passes in The Wallet Crew.
• Resource ID (Google): The unique identifier for the pass within Google.
• External Identifiers: Identifiers linking the pass to external systems.

3. Import Passes to The Wallet Crew

Using the Import Feature

Import passes into The Wallet Crew using the provided details.

Apple Passes

1. Post-Import Configuration:

   • Request your previous pass provider to update the webServiceURL for all passes to:

     https://api-passd.neostore.cloud/api/<tenantId>/passes/apple
     

   • This change ensures passes fetch updated versions from The Wallet Crew.

2. Pass Updates:

   • Once the webServiceURL is updated, all passes will download their latest version directly from The Wallet Crew.

Google Passes

1. Automatic Updates:

   • After import, The Wallet Crew will automatically update Google passes when changes occur.

2. Force Updates:

   • Initiate a “push update” in The Wallet Crew to refresh all Google passes instantly.

Conclusion

By following these steps, you can efficiently migrate wallet passes to The Wallet Crew, ensuring uninterrupted service for your users. If you encounter issues during the process, consult our support documentation or reach out to The Wallet Crew technical team.