Annex Technical Prerequisites and Pass Validation 2026.2

1. Purpose

This Annex defines the technical and operational prerequisites applicable to the use of the Services.

It describes the functional scope and allocation of responsibilities without reproducing the full technical specifications of Apple Wallet and Google Wallet, which remain under the exclusive control of their respective providers.

This Annex forms an integral part of the Agreement.

The Technical Prerequisites apply to standard use of the solution, excluding specific developments, specific integrations or technical constraints specific to the Customer that have not been expressly approved by Neostore.

Compliance with the Technical Prerequisites is an essential condition for the proper operation of the Services.

Neostore shall not be liable for any malfunction, degradation in performance or unavailability resulting from non-compliance with these Technical Prerequisites by the Customer, its partners, service providers, Authorized Users and/or Consumers.

2. General Platform Scope

The Customer remains responsible for validating, within the context of its project and actual use cases, the proper operation of the target architecture, including where several devices, networks, browsers, terminals or peripherals interact with The Wallet Crew.

Where The Wallet Crew is used together with other applications, middleware, equipment or software layers operated by the Customer or third parties, the Customer is responsible for ensuring the overall compatibility of such environment with these Technical Prerequisites.

Compliance of an individual component, such as a reader, smartphone, browser, operating system, network, NFC reader or access-control terminal, with the Technical Prerequisites does not by itself guarantee the proper operation of the overall combination of the Customer's hardware, software, networks, peripherals and configurations.

3. Technical Prerequisites Related to Wallet Providers

3.1 Wallet Accounts and Credentials

To use The Wallet Crew, the Customer must maintain valid credentials with the relevant Wallet platforms.

Apple Wallet. A valid Apple Developer Program membership and the required credentials, including in particular pass signing certificates and notification credentials.

Google Wallet. A valid Google Wallet issuer account and the associated credentials required to create and update passes.

All Wallet accounts and credentials remain owned, managed and controlled by the Customer.

The Customer is solely responsible for maintaining its accounts, credentials, certificates, keys and authorizations with Wallet Providers in operational condition, as well as for complying with their contractual terms, security policies and applicable compliance rules.

Any suspension, revocation, expiry, functional limitation or withdrawal of an account, certificate, key or functionality by Apple, Google or any other third-party provider is outside Neostore's control and may affect all or part of the Services without Neostore being held liable in this respect.

3.2 Devices, Operating Systems and Geographic Availability

Access to and use of Wallet passes depend on:

• the availability of Apple Wallet or Google Wallet on the Consumer's device;
• supported operating system versions;
• geographic availability defined by the Wallet Providers.

Wallet availability and features vary depending on device, operating system and country and are defined exclusively by Apple and Google.

The Customer shall ensure that devices, operating systems, browsers, SDKs, libraries and application components used within its scope are maintained on versions that are compatible and supported by their respective publishers.

Neostore does not support configurations relying on software, operating systems, browsers, mobile components, firmware or third-party equipment that are no longer supported by their publisher or manufacturer.

Unless otherwise indicated by Neostore, use of the latest stable versions of supported browsers and operating systems is recommended in order to benefit from optimal performance and compatibility.

The Customer is responsible for ensuring that its activities comply with the requirements of the Wallet Providers.

3.3 Connectivity, Data Flows and Network Access

Use of The Wallet Crew back-office, APIs, enrollment forms, synchronization flows, notifications and, more generally, the online functionalities of the platform requires stable Internet connectivity appropriate to the Customer's usage.

The Customer must allow the outbound data flows required for operation of the Services, including HTTPS/TCP 443, to the domains, URLs, APIs and endpoints communicated by Neostore and, where applicable, to Third-Party Services operated by Wallet Providers and any other third-party components activated within the subscribed scope.

Use of proxies, caches, traffic inspection mechanisms, application filtering systems or other intermediary devices that may modify, slow down, interrupt or rewrite communications with the Services is discouraged.

Where such mechanisms are imposed by the Customer's environment, the Customer shall, where possible, ensure that The Wallet Crew data flows are excluded from such processing or shall validate their impact with Neostore in advance.

4. Pass Validation Methods

Passes issued through The Wallet Crew may be validated using one or more of the following methods, depending on the Customer's configuration and infrastructure.

4.1 Visual Code Validation (Barcode / QR Code)

Passes may include visual codes, such as QR codes or barcodes, displayed on end-user device screens.

Supported code formats are those officially supported by Apple Wallet and Google Wallet.

The Customer is responsible for ensuring that deployed readers are capable of reading and validating 2D codes displayed on backlit screens, including smartphones and smartwatches.

The Wallet Crew does not supply scanning hardware and does not guarantee compatibility with specific reader models.

Before deployment into production, the Customer shall validate the effective compatibility of readers, scanners, access terminals, control applications and keyboard or wedge configurations with the selected code formats and its operational use cases.

Where several peripherals, drivers, reading applications or software layers coexist within the same environment, the Customer shall ensure that their combination does not adversely affect code reading, the stability of validation journeys, or the quality of display or interpretation of scanned data.

4.2 NFC-Based Validation (Optional)

Where enabled, NFC-based validation relies exclusively on Wallet Provider technologies:

• Apple Wallet: Apple Value Added Services (VAS);
• Google Wallet: Google Smart Tap.

NFC validation requires:

• compatible end-user devices;
• NFC readers certified by the Wallet Providers;
• appropriate configuration and, where applicable, commercial arrangements with hardware providers.

The Customer is solely responsible for selecting, deploying and maintaining NFC hardware in accordance with Wallet Provider specifications.

The Customer shall carry out all project tests required to validate the proper operation of the overall environment comprising Consumer devices, NFC readers, security settings, local configurations and business journeys.

Neostore does not guarantee that equipment that is individually certified or compatible will operate satisfactorily within the Customer's overall environment.

5. Pass Scanner Application

5.1 Purpose

Pass Scanner is a mobile application provided by Neostore as part of The Wallet Crew ecosystem, enabling Customers or their partners to scan and validate Wallet passes using barcodes / QR codes and, where supported, NFC.

Pass Scanner is a validation tool only and does not replace a ticketing system, access-control back office or Customer business system.

5.2 Technical Prerequisites

To use Pass Scanner, the Customer must ensure:

• that compatible mobile devices supported by the application are available;
• appropriate network connectivity for online validation scenarios;
• correct configuration of passes and validation rules within The Wallet Crew.

Availability of validation functionalities within Pass Scanner depends on:

• device capabilities;
• operating system support;
• rules defined by the Wallet Providers;
• Customer configuration.

The Customer shall ensure that terminals used for Pass Scanner have appropriate hardware and operating system versions, a compatible camera or NFC module depending on the selected validation mode, and sufficient connectivity where the validation scenario requires network access.

For performance, security and support purposes, Neostore may recommend or require, for certain versions of the application, minimum or recommended versions of mobile operating systems, embedded browsers or related software components.

Any installation, configuration or use on rugged, heavily customized or legacy devices, or on devices relying on software components no longer supported by their publisher, may be subject to limited support or may fall outside the standard support scope.

6. Support and Scope of Intervention in the Event of a Non-Compliant Environment

Where the Customer's Environment does not comply with these Technical Prerequisites, Neostore may:

• limit its analysis to a first-level qualification;
• require the Customer to carry out the necessary remediation;
• make any in-depth investigation conditional upon reproduction of the Defect in a compliant environment;
• treat the intervention as additional professional Services where it falls outside the standard support scope; and/or
• terminate the Agreement in accordance with the conditions set out in the GTC.