iOS-Based Devices Sample Clauses

iOS-Based Devices. Transact’s provision of the Mobile Credential Service for iOS-based devices is contingent on the approval and authorization by Apple to provide such service for iOS-based devices. If Apple (1) does not provide the necessary approval and/or authorization for Transact to provide the Mobile Credential Service for iOS-based devices; or (2) withdraws its approval and/or authorization for Transact to provide the Mobile Credential Service for iOS-based devices at any time after it is granted, Transact will not be required to provide the Mobile Credential Service for iOS-based devices and will not be liable to Customer for any damages, losses, claims, or expenses arising from such suspension of the Mobile Credential Service for iOS-based devices. Further, for so long as Customer allows Users to provision a Customer-issued identification to an iOS-based device, Customer agrees to the following conditions. a. Customer will comply with the terms and conditions set forth in the Guidelines. b. Absent prior written notice to Transact, Customer will not implement changes to its systems, procedures, processes or functionality, which, as the case may be, may reasonably be expected to result in changes to or otherwise impact: (i) the Apply Pay Technology; (ii) the manner in which Credentials are provisioned on the Apple Pay Technology, or (iii) the manner in which Credentials provisioned to an iOS-based device function or are processed on the Apple Pay Technology (these changes to systems, procedures, processes or functionality will be referred as to "System Changes"). In addition, and not by way of limitation, Customer will notify Transact not less than ninety (90) days prior to any System Changes that Transact reasonably believes will disable core functionality of the Apple Pay Technology or introduce material additional security exposure to Apple, merchants and consumers and provide support to Transact to work in good faith with Apple to address any bona fide concerns of Apple with regard to such proposed change. If Apple objects to any System Changes, the System Changes will not go forward until the objection is resolved. c. Customer will authorize Transact to provide Apple with the identifiers for credentials assigned to any Credentials issued by Customer. d. Customer will ensure that all Users will be offered the ability to receive an iOS Provisioned Credential so that such device may be used to initiate a Payment Transaction or an Access Transaction. e. Customer will...
Sample 1
AutoNDA by SimpleDocs
iOS-Based Devices. Transact’s provision of the Transact Mobile Credential service for iOS-based Devices is contingent on the approval and authorization by Apple Inc. (“Apple”) to provide such service for iOS-based Devices. For so long as Customer allows Users to provision a Customer-issued identification to an iOS-based Device, Customer agrees to comply with the terms of Exhibit A. Customer specifically acknowledges that the terms set forth in Exhibit A and any addenda or documents attached thereto or referenced therein are required to be incorporated herein by Apple, and further, that if Apple requires Transact to implement any change to the terms set forth in such Exhibit or any such addenda or documents, Transact hereby reserves the right to modify such terms effective upon notice from Transact to Customer. Further, if Apple makes any updates to any external
Sample 1

Related to iOS-Based Devices

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Registry Performance Specifications Registry Performance Specifications for operation of the TLD will be as set forth in Specification 10 attached hereto (“Specification 10”). Registry Operator shall comply with such Performance Specifications and, for a period of at least one (1) year, shall keep technical and operational records sufficient to evidence compliance with such specifications for each calendar year during the Term.

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference.

  • SHOP DRAWINGS, PRODUCT DATA AND SAMPLES 4.12.1 Shop Drawings are drawings, diagrams, schedules and other, data specially prepared for the Work by the Contractor or any Subcontractor, manufacturer, supplier or distributor to illustrate some portion of the Work. 4.12.2 Product Data are illustrations, standard schedules, performance charts, instructions, brochures, diagrams and other information furnished by the Contractor to illustrate a material, product or system for some portion of the Work. 4.12.3 Samples are physical examples which illustrate materials, equipment or workmanship and establish standards by which the Work will be judged. 4.12.4 The Contractor shall review, approve and submit, with reasonable promptness and in such sequence as to cause no delay in the Work or in the work of the State or any separate contractor, all Shop Drawings, Product Data and Samples required by the Contract Documents. 4.12.5 By approving and submitting Shop Drawings, Product Data and Samples, the Contractor represents that he / she has determined and verified all materials, field measurements, and field construction criteria related thereto, or will do so, and that he / she has checked and coordinated the information contained within such submittals with the requirements of the Work and of the Contract Documents. 4.12.6 The Contractor shall not be relieved of responsibility for any deviation from the requirements of the Contract Documents by the Architect's approval of Shop Drawings, Product Data or Samples under Subparagraph 2.2.7 of these General Conditions unless the Contractor has specifically informed the Architect and the State in writing of such deviation at the time of sub- mission and the Architect and the State has given written approval to the specific deviation. The Contractor shall not be relieved from responsibility for errors or omissions in the Shop Drawings, Product Data or Samples by the Architect's approval thereof. 4.12.7 The Contractor shall direct specific attention, in writing or on resubmitted Shop Drawings, Product Data or Samples, to revisions other than those requested by the Architect on previous submittals. 4.12.8 No portion of the Work requiring submission of a Shop Drawing, Product Data or Sample shall be commenced until the submittal has been approved by the Architect as provided in Subparagraph 2.2.7 of these General Conditions. All such portions of the Work shall be in accordance with approved submittals.

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

  • Contract Database Metadata Elements Title: Great Neck Union Free School District and Great Neck Paraprofessionals Association (2011) Employer Name: Great Neck Union Free School District Union: Great Neck Paraprofessionals Association Local: Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 5132 Unit Size: Number of Pages: 28 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ ARTICLE# TITLE PAGE# Preamble 2 Article 1 Association Rights 2 Article 2 Board-Administration-Association Relationship and Procedures 4 Article 3 Exchange of Proposals 6 Article 4 Professionals Duties and Responsibilities of Paraprofessionals 7 Article 5 Work Assignments 8 Article 6 Annual Appointment 10 Article 7 Selection and Promotion 10 Article 8 Evaluations and Standards 11 Article 9 Procedures for Termination of Employment 11 Article 10 Conferences 12 Article 11 Human Resource File 12 Article 12 Professional Growth 13 Article 13 Sick Leave 14 Article 14 Personal Leave 16 Article 15 Other Leaves 17 Article 16 Grievance Procedures 18 Article 17 Legal Assistance 19 Article 18 Conformity to Law 19 Article 19 Health Insurance 20 Article 20 Retirement Plan 20 Article 21 Salary Schedule 21 Article 22 Seniority Policy 23 Article 23 Compensation for Financial Loss 24 Article 24 Duration of Agreement 25 Appendix A Determination of Negotiating Unit 25 Appendix B Payroll Deduction Authorization 26 Appendix C Bus Aides 26 Appendix D Salary Schedules 27

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!