API and Services Documentation License Sample Clauses

API and Services Documentation License. Subject to the terms of this Agreement, Xxxxxxxxx.Xxx hereby grants to Company and Company hereby accepts from Xxxxxxxxx.Xxx a personal, limited, non-exclusive, non- transferable license and right to the Xxxxxxxxx.Xxx API and accompanying Services Documentation for the following purposes: i. install and use the Xxxxxxxxx.Xxx API on as many machines as reasonably necessary (which machines are and shall be maintained in facilities owned, occupied, or leased by Company) to provide access to Transaction Services, including onboarding, to Approved Merchants and/or to use the Transaction Services on the behalf of Approved Merchant(s); ii. use the accompanying Services Documentation solely for the purpose of using the Xxxxxxxxx.Xxx APIs and providing access to the Transaction Services and/or using Transaction Services on behalf of Approved Merchant(s); and iii. create a reasonable number of copies of the Xxxxxxxxx.Xxx API and Services Documentation, with all copyright notices intact, for archival purposes only.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
API and Services Documentation License. Subject to the terms of this Agreement, CyberSource hereby grants to Customer and Customer hereby accepts from CyberSource a personal, limited, non-exclusive, non-transferable license and right to the CyberSource API and accompanying Services Documentation for the following purposes: i. install and use the CyberSource API on as many machines as reasonably necessary (which machines are and shall be maintained in facilities owned, occupied, or leased by Customer) to use the CyberSource Services for the purpose of selling products and services to End-Users; ii. use the accompanying Services Documentation solely for the purpose of using the CyberSource APIs and CyberSource Services; and, iii. create a reasonable number of copies of the CyberSource API and Services Documentation, with all copyright notices intact, for archival purposes only.
Sample 1Sample 2See All (4)
API and Services Documentation License. Subject to the terms of this Agreement, Xxxxxxxxx.Xxx hereby grants to Customer and Customer hereby accepts from Xxxxxxxxx.Xxx a personal, limited, non-exclusive, non-transferable license and right to the Xxxxxxxxx.Xxx API and accompanying Services Documentation for the following purposes: i. install and use the Xxxxxxxxx.Xxx API on as many machines as reasonably necessary (which machines are and shall be maintained in facilities owned, occupied, or leased by Customer) to use the Transaction Services for the purpose of selling products and services to End-Users; ii. use the accompanying Services Documentation solely for the purpose of using the Xxxxxxxxx.Xxx APIs and Transaction Services; and iii. create a reasonable number of copies of the Xxxxxxxxx.Xxx API and Services Documentation, with all copyright notices intact, for archival purposes only.
Sample 1Sample 2Sample 3
API and Services Documentation License. Subject to the terms of this Agreement, GSPAYTECH hereby grants to Customer and Customer hereby accepts from GSPAYTECH a personal, limited, non-exclusive, non-transferable license and right to the GSPAYTECH API and accompanying Services Documentation for the following purposes: i. install and use the GSPAYTECH API on as many machines as reasonably necessary (which machines are and shall be maintained in facilities owned, occupied, or leased by Customer) to use the GSPAYTECH Services for the purpose of selling products and services to End Users; ii. use the accompanying Services Documentation solely for the purpose of using the GSPAYTECH APIs and GSPAYTECH Services;and, iii. create a reasonable number of copies of the GSPAYTECH API and Services Documentation, with all copyright notices intact, for archival purposes only.
Sample 1Sample 2
API and Services Documentation License. Subject to the terms of this Agreement, Cloud9 hereby grants to Customer and Customer hereby accepts from Cloud9 a personal, limited, non-exclusive, non- transferable license and right to the Cloud9 API and accompanying Services Documentation for the following purposes: i. install and use the Cloud9 API on as many machines as reasonably necessary (which machines are and shall be maintained in facilities owned, occupied, or leased by Customer) to use the Transaction Services for the purpose of selling products and services to End-Users; ii. use the accompanying Services Documentation solely for the purpose of using the Cloud9 APIs and Transaction Services; and iii. create a reasonable number of copies of the Cloud9 API and Services Documentation, with all copyright notices intact, for archival purposes only.
Sample 1
API and Services Documentation License. Subject to the terms of this Agreement, TUNL hereby grants to Customer and API and Services Documentation, with all copyright notices intact, for archival purposes only.
Sample 1

Related to API and Services Documentation License

  • Documentation License Subject to the terms of this Agreement, Flock hereby grants to Agency a non- exclusive, non-transferable right and license to use the Documentation during the Term in connection with its use of the Services as contemplated herein, and under Section 2.5 below.

  • Source Documentation Accounting records must be supported by such source documentation as canceled checks, bank statements, invoices, paid bills, donor letters, time and attendance records, activity reports, travel reports, contractual and consultant agreements, and subaward documentation. All supporting documentation should be clearly identified with the Award and general ledger accounts which are to be charged or credited. (i) The documentation standards for salary charges to grants are prescribed by 2 CFR 200.430, and in the cost principles applicable to the entity’s organization (Paragraphs 7.4 through 7.7). (ii) If records do not meet the standards in 2 CFR 200.430, then Grantor may notify Grantee in PART TWO, PART THREE or Exhibit G of the requirement to submit Personnel activity reports. See 2 CFR 200.430(i)(8). Personnel activity reports shall account on an after-the-fact basis for one hundred percent (100%) of the employee's actual time, separately indicating the time spent on the grant, other grants or projects, vacation or sick leave, and administrative time, if applicable. The reports must be signed by the employee, approved by the appropriate official, and coincide with a pay period. These time records should be used to record the distribution of salary costs to the appropriate accounts no less frequently than quarterly. (iii) Formal agreements with independent contractors, such as consultants, must include a description of the services to be performed, the period of performance, the fee and method of payment, an itemization of travel and other costs which are chargeable to the agreement, and the signatures of both the contractor and an appropriate official of Grantee. (iv) If third party in-kind (non-cash) contributions are used for Grant purposes, the valuation of these contributions must be supported with adequate documentation.

  • Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet

  • Product Documentation You should review the policy documents carefully to ensure they accurately reflect the cover, conditions, limits and other terms that you require. Particular attention should be paid to policy conditions and warranties as failure to comply with these could invalidate your policy. Claims can arise, under certain types of insurance contract, long after the expiry of the policy. It is therefore important that you retain and keep safely all documents associated with your policy.

  • Software and Documentation Licensee may make as many copies of the Software necessary for it to use the Software as licensed. Each copy of the Software made by Licensee must contain the same copyright and other notices that appear on the original copy. Licensee will not modify the Documentation. Documentation may: (a) only be used to support Licensee’s use of the Software; (b) not be republished or redistributed to any unauthorized third party; and (c) not be distributed or used to conduct training for which Licensee, or any other party, receives a fee. Licensee will not copy any system schema reference document related to the Software.

  • Technical Documentation Prior to commencement of the Tests on Completion, the Contractor shall supply to the Engineer the technical documentation as specified in the Employer’s Requirements. The Works or Section shall not be considered to be completed for the purposes of taking- over under sub-clause 10.1 [Taking Over of the Works and Sections] until the Engineer has received the technical documentation as defined in this sub-clause 5.7, the "history file" including design calculations and certain certification as well as any other documents required to meet the CE Marking requirements.

  • Medical Documentation The teacher must supply a letter from a medical 3 doctor, who treated the patient, stating that in his/her opinion, there is a strong 4 probability that the illness was contracted at school.

  • Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.

  • End User License Agreement This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. xxxx://xxxxxxxxxxxxxxx.xxx/licenses/by-nc-nd/3.0/ You are free to: Share: to copy, distribute and transmit the work Under the following conditions: Attribution: You must attribute the work in the manner specified by the author (but not in any way that suggests that they endorse you or your use of the work).

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times. 2) Compliance with the Software License Agreement is the responsibility of the Customer. DIR shall not be responsible for any Customer’s compliance with the Software License Agreement. If DIR purchases software licenses for its own use under this Contract, it shall be responsible for its compliance with the Software License Agreement terms and conditions.

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