Access Authorizations & Account Controls Sample Clauses

Access Authorizations & Account Controls. You have the option to establish controls and limitations on the authorized access to your account and the transaction functions and amounts that may be conducted. You are solely responsible for establishing and maintaining these access authorizations and account controls to protect your account. You may establish dual account access controls and you are solely responsible for such designations, the implementation and enforcement of your internal account authorization policies and the actions of the designees of such dual controls. You may authorize multiple users to access and conduct transactions on the account (“Sub Users”) with specific account transaction authorities and limitations and you are solely responsible for such Sub User authorizations, the implementation and enforcement of your internal account authorization policies and the actions of your designated Sub Users.
AutoNDA by SimpleDocs

Related to Access Authorizations & Account Controls

  • ACH Authorization Merchant authorizes Service Provider to initiate debit/credit entries to the Designated Account, the Reserve Account, or any other account maintained by Merchant at any institution, all in accordance with this Agreement. This authorization will remain in effect beyond termination of this Agreement. In the event Merchant changes the Designated Account, this authorization will apply to the new account.

  • Credit Card Authorization TO THE EXTENT PERMITTED BY APPLICABLE LAW, YOU IRREVOCABLY AND UNCONDITIONALLY AUTHORIZE XXXXXXX TO CHARGE ALL AMOUNTS DUE UNDER THIS AGREEMENT TO ANY CREDIT CARD YOU PROVIDE TO US, AND YOU AGREE TO INDEMNIFY, DEFEND AND HOLD HARMLESS XXXXXXX WITH RESPECT TO THE SAME.

  • Dues Authorization Employees covered by the Certification shall as a condition of continuing employment authorize deductions from their monthly salary of union dues, or the amount equivalent to dues. Failure to authorize such deductions shall constitute cause for dismissal.

  • AGREEMENTS WITH EMPLOYEES AND SUBCONTRACTORS Grantee shall have written, binding agreements with its employees and subcontractors that include provisions sufficient to give effect to and enable Grantee’s compliance with Grantee’s obligations under this Article VI, Intellectual Property.

  • Licenses and Similar Authorizations The Contractor, at no expense to the City, shall secure and maintain in full force and effect during the term of this Contract all required licenses, permits, and similar legal authorizations, and comply with all related requirements.

  • Authorization, Etc This Agreement and the Notes have been duly authorized by all necessary corporate action on the part of the Company, and this Agreement constitutes, and upon execution and delivery thereof each Note will constitute, a legal, valid and binding obligation of the Company enforceable against the Company in accordance with its terms, except as such enforceability may be limited by (i) applicable bankruptcy, insolvency, reorganization, moratorium or other similar laws affecting the enforcement of creditors’ rights generally and (ii) general principles of equity (regardless of whether such enforceability is considered in a proceeding in equity or at law).

  • Disclosure Statement for Xxxxxxxxx Education Savings Accounts 1. Who is Eligible for a Xxxxxxxxx Education Savings Account? Anyone may contribute to a Xxxxxxxxx Education Savings Account regardless of his or her relationship to the beneficiary. The beneficiary of a Xxxxxxxxx Education Savings Account

  • Evaluation Licenses Access to the Software may be provided to You for beta, demonstration, test, or evaluation purposes, (collectively, “Evaluation Licenses”). For any Evaluation Licenses, the term shall be limited to thirty (30) days (the “Evaluation Period”), unless otherwise agreed to by Xxxxxxxxx in writing. Evaluation Licenses are limited specifically to use for evaluation or demonstration purposes only, and You agree not to use such Software in a production or non-test environment. Your use of the Software under an Evaluation License is provided as-is, without any representations or warranties of any kind, and is at Your sole risk. Honeywell has no obligation to support, maintain or provide any assistance regarding any Evaluation Licenses. IN NO EVENT WILL HONEYWELL BE LIABLE FOR ANY DAMAGES OF ANY KIND, INCLUDING, WITHOUT LIMITATION, ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, EXEMPLARY, STATUTORY, PUNITIVE, OR CONSEQUENTIAL DAMAGES (INCLUDING, WITHOUT LIMITATION, LOST PROFITS, LOST DATA, DAMAGE TO SYSTEMS OR EQUIPMENT, OR BUSINESS INTERRUPTION). YOU ARE NOT ENTITLED TO ANY DEFENSE, INDEMNIFICATION FOR EVALUATION LICENSES GRANTED PURSUANT TO THIS SECTION.

  • Cloud Computing State Risk and Authorization Management Program In accordance with Senate Bill 475, Acts 2021, 87th Leg., R.S., pursuant to Texas Government Code, Section 2054.0593, Contractor acknowledges and agrees that, if providing cloud computing services for System Agency, Contractor must comply with the requirements of the state risk and authorization management program and that System Agency may not enter or renew a contract with Contractor to purchase cloud computing services for the agency that are subject to the state risk and authorization management program unless Contractor demonstrates compliance with program requirements. If providing cloud computing services for System Agency that are subject to the state risk and authorization management program, Contractor certifies it will maintain program compliance and certification throughout the term of the Contract.

  • Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.

Time is Money Join Law Insider Premium to draft better contracts faster.