Compliance with the Security Procedures Sample Clauses

Compliance with the Security Procedures. The Member and the Credit Union shall comply with the security procedures described in the attached Schedule [A] with respect to Entries transmitted by the Member to the Credit Union. • If an Entry (or a request for cancellation or amendment of an Entry) received by the Credit Union purports to have been transmitted or authorized by the MEMBER, it will be deemed effective as the MEMBER’s Entry and the MEMBER shall be obligated to pay the Credit Union the amount of such Entry even though the Entry was not authorized by the MEMBER, provided the Credit Union acted in compliance with the security procedures referenced in Schedule [A]. • Member acknowledges the purpose of the security procedures is for the verification of authenticity and not to detect transmission or content errors of any Entry.
Sample 1Sample 2
AutoNDA by SimpleDocs
Compliance with the Security Procedures. (a) If an entry (or a request for cancellation or amendment of an entry) received by the Financial Institution purports to have been transmitted or authorized by the Originator, it will be deemed effective as the Originator's entry and the Originator shall be obligated to pay the Financial Institution the amount of such entry even though the entry was not authorized by the Originator, provided the Financial Institution acted in compliance with the security procedure referenced in Schedule (A). If signature comparison is to be used as a part of that security procedure, the Financial Institution shall be deemed to have complied with that part of such procedure if it compares the signature accompanying a file of entries with the signature of an authorized representative of the Originator and, on the basis of such comparison, believes the signature to be that of such authorized representative.
Sample 1Sample 2
Compliance with the Security Procedures. (a) If an Entry (or a request for cancellation or amendment of an Entry (“re- quest”)) received by Us purports to have been transmitted or authorized by You, it will be deemed to be effective as Your Entry (or request) and You shall be obligated to pay Us the amount of such Entry even though the Entry (or request) was not authorized by You, provided We accept the Entry (or request) in good faith and acted in compliance with the Security Procedures with respect to such Entry (or request).
Sample 1
Compliance with the Security Procedures. (a) If an entry (or a request for cancellation or amendment of an entry) received by the Financial Institution purports to have been transmitted or authorized by the Company, it will be deemed effective as the Company's entry and the Company shall be obligated to pay the Financial Institution the amount of such entry even though the entry was not authorized by the Company, provided the Financial Institution acted in compliance with the security procedure referenced in Schedule A.
Sample 1
Compliance with the Security Procedures. (i) If a wire transfer request is received by the Bank purports to have been transmitted or authorized by the Company, it will be deemed effective as the Company's entry and the Company shall be obligated to pay the financial institution the amount of such entry even if the entry was not authorized by the Company, provided the financial institution acted in compliance with the security procedure referenced in the Security Procedures.
Sample 1
Compliance with the Security Procedures. (a) If an Entry received by Bank purports to have been transmitted or authorized by Company, it will be deemed effective as Company's Entry and Company shall be obligated to pay Bank the amount of such Entry even though the Entry was not authorized by Company, provided Bank accepted the Entry in good faith and acted in compliance with the Security Procedures referred to in Schedule A with respect to such Entry.
Sample 1

Related to Compliance with the Security Procedures

  • Compliance with the Law The Parties agree to comply fully with all applicable federal, state, and local statutes, ordinances, rules, and regulations applicable to their entity in connection with the programs contemplated under this Agreement.

  • Compliance with Privacy Code The parties acknowledge that the Warrant Agent may, in the course of providing services hereunder, collect or receive financial and other personal information about such parties and/or their representatives, as individuals, or about other individuals related to the subject matter hereof, and use such information for the following purposes:

  • COMPLIANCE WITH THE ACT All matters related to the operations of the Company not specifically addressed herein must be addressed in accordance with the Act. The Company must comply with all other provisions of the Act in order to stay compliant with the law.

  • Compliance with Rules To comply with, and to require the Contractors to comply with, all rules, regulations, ordinances and laws bearing on the conduct of the work on the Improvements, including the requirements of any insurer issuing coverage on the Project and the requirements of any applicable supervising boards of fire underwriters.

  • Security and Validation Procedures The Scheduling Coordinator shall apply to the Meter Data of the Scheduling Coordinator Metered Entities that it represents the security and validation procedures prescribed by the relevant Local Regulatory Authority. If the relevant Local Regulatory Authority has not prescribed any such procedures, the Scheduling Coordinator shall apply the procedures set forth in the CAISO Tariff. Meter Data submitted by a Scheduling Coordinator for Scheduling Coordinator Metered Entities shall conform to these standards unless the CAISO has, at its discretion, exempted the Scheduling Coordinator from these standards.

  • Compliance with Texas Privacy Laws and Regulations In performing their respective obligations under the Agreement, the LEA and the Provider shall comply with all Texas laws and regulations pertaining to LEA data privacy and confidentiality, including but not limited to the Texas Education Code Chapter 32, and Texas Government Code Chapter 560.

  • COMPLIANCE WITH NEW YORK STATE INFORMATION SECURITY BREACH AND NOTIFICATION ACT Contractor shall comply with the provisions of the New York State Information Security Breach and Notification Act (General Business Law Section 899-aa; State Technology Law Section 208).

  • COMPLIANCE WITH BREACH NOTIFICATION AND DATA SECURITY LAWS Contractor shall comply with the provisions of the New York State Information Security Breach and Notification Act (General Business Law § 899-aa and State Technology Law § 208) and commencing March 21, 2020 shall also comply with General Business Law § 899-bb.

  • Safeguarding requirements and procedures (1) The Contractor shall apply the following basic safeguarding requirements and procedures to protect covered contractor information systems. Requirements and procedures for basic safeguarding of covered contractor information systems shall include, at a minimum, the following security controls:

  • Compliance with Privacy Laws NCPS represents and warrants that its collection, access, use, storage, disposal and disclosure of Personal Data does and will comply with all applicable federal and state privacy and data protection laws, as well as all other applicable regulations. Without limiting the foregoing, NCPS shall implement administrative, physical and technical safeguards to protect Personal Data that are no less rigorous than accepted industry, and shall ensure that all such safeguards, including the manner in which Personal Data is collected, accessed, used, stored, processed, disposed of and disclosed, comply with applicable data protection and privacy laws, as well as the terms and conditions of this Escrow Agreement. NCPS shall use and disclose Personal Data solely and exclusively for the purposes for which the Personal Data, or access to it, is provided pursuant to the terms and conditions of this Escrow Agreement, and not use, sell, rent, transfer, distribute, or otherwise disclose or make available Personal Data for NCPS’s own purposes or for the benefit of any party other than Issuer. For purposes of this section, “Personal Data” shall mean information provided to NCPS by or at the direction of the Issuer, or to which access was provided to NCPS by or at the direction of the Issuer, in the course of NCPS’s performance under this Escrow Agreement that: (i) identifies or can be used to identify an individual (also known as a “data subject”) (including, without limitation, names, signatures, addresses, telephone numbers, e-mail addresses and other unique identifiers); or (ii) can be used to authenticate an individual (including, without limitation, employee identification numbers, government-issued identification numbers, passwords or PINs, financial account numbers, credit report information, biometric or health data, answers to security questions and other personal identifiers), including the identifying information on individuals described in Section 12.

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