Digital Wallet Specific Terms

1. General

These Digital Wallet Specific Terms govern the provision of the Voyado Engage Component “Digital Wallet” (the “Digital Wallet”) to Customer and Customer’s use thereof. These terms form an integral part of the Product Specific Terms for Voyado Engage and supplements the General Terms. In the event of conflict between these terms and the Product Specific Terms for Voyado Engage, these terms shall prevail.

2. Definitions

Any terms defined in the Agreement shall have the same meaning when used herein. The following terms shall have the meaning ascribed below:

“Apple VAS” means Apple’s value added services made available to end users through Apple Wallet, using Apple’s proprietary Wallet and VAS frameworks, APIs and related technologies, and subject to the Apple Developer Program, Apple Wallet and other applicable Apple terms, policies and technical requirements in force from time to time. Apple VAS uses a proprietary near-field communication (NFC) protocol to enable secure and efficient communication for value added services and to facilitate the transmission of data from compatible passes to supported NFC terminals, as made available by Apple from time to time. The Apple VAS protocol may be integrated into third-party contactless terminals or implemented within iPhone applications.

“Google Smart Tap” means the Google Smart Tap protocol, a proprietary near-field communication (NFC) protocol developed by Google to facilitate the transfer of data between mobile devices and NFC terminals, as made available by Google from time to time.

“PSP” means Payment Service Provider.

“Push Notifications” means short electronic messages or alerts delivered via the Digital Wallet to end users’ devices, intended to provide information about Customer’s offerings, updates, promotions or other relevant content, and which may appear on the device lock screen, notification centre or within the application interface.

“Wallet Pass(es)” means  a unique, digital card, ticket or similar digital item created, issued or managed via the Digital Wallet, which can be stored in an end user’s digital wallet application (such as Apple Wallet or Google Wallet) and used to present offers, identification, membership, tickets, loyalty credentials or comparable content. For the avoidance of doubt, each individual Wallet Pass (each uniquely issued instance), regardless of whether multiple Wallet Passes contain identical content or design, shall be counted separately for the purposes of calculating any fees based on the number of Wallet Passes.

3. Fees and Payment

3.1 Scope and Payment. The right of access to the Digital Wallet is subject to Customer’s payment of the applicable fees and is limited to the applicable user limits, as specified in the Agreement. Fees consist of a fixed monthly fee, and variable fees for usage-based overages of Wallet Passes and Push Notifications, if applicable.

3.2 Included Wallet Passes and Overages. The included number of Wallet Passes is stated in the Order Form. Any overage above the Wallet Passes included in the fixed fees shall be invoiced monthly in arrears as a variable fee at the overage price set out in the Agreement.

3.3 Included Push Notifications and Overages. The included number of Push Notifications is stated in the Order Form. Any overage above the Push Notifications included in the fixed fees shall be invoiced monthly in arrears as a variable fee at the overage price set out in the Agreement.

4. Integrations with Third Party Services

The Digital Wallet integrates with third party platforms, including but not limited to Apple Wallet and Google Wallet. Such platforms constitute Third Party Services within the meaning of Section 18 of the General Terms, and shall apply in full to Customer’s use of the Digital Wallet. Accordingly, Customer is responsible for entering into and maintaining any agreements required with Apple, Google and other third-party providers for such platforms, and for complying with their applicable terms, policies and guidelines. Without limiting Section 18 of the General Terms, Supplier does not control and shall not be responsible or liable for the functionality, availability, compatibility, or continued operation of any such third-party platforms. If any third-party platform ceases to function, limits compatibility or modifies its operations in a manner that affects the Digital Wallet or the Product(s), Supplier shall not be liable for any resulting loss, disruption or reduced functionality.

5. Digital Wallet Prerequisites

As a prerequisite to the provision and use of the Digital Wallet, Customer shall, at its own cost, maintain such accounts, configurations, certificates, identifiers and other technical or administrative prerequisites as set forth in Apple’s and Google’s then‑current official documentation, terms, policies and technical requirements for Apple Wallet and Google Wallet in connection with the Digital Wallet (the “Digital Wallet Requirements”). Customer acknowledges and agrees that the Digital Wallet Requirements may require Customer to set up and use its own memberships, business accounts, payment/merchant identifiers or similar arrangements with Apple or Google. The Digital Wallet Requirements may be updated from time to time by Apple or Google, and Customer shall comply with the Digital Wallet Requirements and cooperate with Supplier to implement any necessary changes following such updates.

6. Apple VAS and Google Smart Tap Prerequisites

6.1 VAS Prerequisites. The prerequisites outlined in this Section 6 are applicable only if Customer elects to implement VAS. Supplier may update the prerequisites as necessary to accommodate updates from Apple, Google or other relevant entities, or to incorporate new information pertinent to the implementation of VAS. Such updates may include, but are not limited to, changes in technical requirements, certification processes or configuration procedures. In the event of any such modifications, Supplier shall notify Customer in writing, specifying the nature of the changes and the effective date thereof. Customer acknowledges that, upon such notification, the modified prerequisites shall supersede any prior versions, and Customer’s continued use of VAS shall constitute acceptance of the modified terms. No further action, including re-execution of the Agreement, shall be required from Customer to validate such modifications.

6.2 Customer and Supplier Responsibilities. In order for VAS to be implemented and function properly, the following sequential prerequisites must be met:

1. Hardware Provider Requirements: The hardware provider of the payment terminals must have a certified implementation of Apple VAS and/or Google Smart Tap.
2. Payment Service Provider Certification: The payment service provider supplying the payment terminals to Customer must have obtained certification from Apple for the hardware to support Apple VAS. Even if the hardware manufacturer has implemented Apple VAS, the payment service provider must independently certify the payment terminals for Apple VAS functionality.
3. Supplier Configuration and Distribution Obligations: Supplier shall configure and distribute necessary configurations, including private keys for encryption, pass type identifiers, and enrolment URLs, to each payment terminal designated for VAS use. To facilitate this, the payment service provider shall provide Supplier with appropriate software interfaces, such as APIs or other integration methods, to enable remote configuration of the terminals. This may involve Supplier acting independently, in conjunction with Customer, or in coordination with the payment service provider. Supplier shall not be held liable for any lack of implementation in locations or regions where payment terminals cannot be updated with such configurations.
4. Point of Sale (POS) System Requirements: Customer’s POS system must: (i) to ensure proper identification functionality, be capable of processing the VAS, loyalty object or ID included in the payment response from the payment service provider during a transaction; (ii) if customer identification is to be applied during a purchase, implement logic to process the ID returned in the payment response; and (iii) if manual member benefits, such as vouchers, are to be applied during the purchase cycle, support (together with the payment service provider) either Apple VAS and/or Smart Tap Two Tap functionality or an agreed-upon Single Tap workflow with the necessary functionality implemented. Further, the POS system must have the necessary integration with any loyalty systems or other platforms where such vouchers or member benefits are applied.
5. Premium Enrolment Requirements: To facilitate Premium enrolment, Customer’s POS system must possess the necessary functionality, in collaboration with the payment service provider, to deliver the VAS enrolment URL to the Apple Wallet during the purchase process.
6. Apple Pay Requirements: If Customer permits sales through an online store, the implementation of Apple VAS shall require the availability of Apple Pay as a payment option. These prerequisites are designed to ensure the seamless integration and functionality of VAS offerings, and the Parties agree to collaborate in good faith to meet these requirements.
7. Apple Merchant Agreement Requirement: In order to implement Apple VAS, Customer must sign the Merchant Agreement provided by Apple, as supplied by Supplier.
8. Registration Information Requirement: Customer shall provide Supplier with information regarding every registration made using VAS in a timely manner via the Supplier’s API, ensuring Supplier can maintain accurate records and provide efficient services. Such information will be forwarded to Apple and Google as required. Customer shall ensure that the API integration is properly configured and maintained to facilitate seamless data transfer to Supplier. The specific format and details of the transmitted information shall be as specified in the Documentation or otherwise agreed upon between the Parties.

7. Onboarding

Customer may choose between different onboarding options for the Digital Wallet. Supplier shall provide reasonable assistance to Customer with the configuration and setup of the Digital Wallet in accordance with the configuration option selected by Customer. If Customer wishes to implement VAS, a separate and specific configuration of the Digital Wallet and related systems is required. Customer acknowledges that such configuration may differ from the configuration used for the Digital Wallet without VAS. Supplier’s assistance with such configuration, including any configuration required for VAS, shall be charged in accordance with Supplier’s applicable price list in force from time to time.

8. Performance

Customer acknowledges and agrees that Supplier’s system is designed to support a maximum request volume of forty (40) requests per second. If Customer exceeds this limit, system performance, including response times and stability, may be negatively impacted. Supplier shall not be responsible or liable for degraded performance, errors, or service interruptions resulting from usage beyond this limit. Supplier reserves the right to implement reasonable technical measures (including rate limiting or throttling) to protect the stability of the Digital Wallet in the event that Customer exceeds the permitted request rate.

* * *