Verification and Security Procedures. (a) X.X. Xxxxxx and the Customer shall comply with any applicable Security Procedures with respect to the delivery or authentication of Instructions and shall ensure that any codes, passwords or similar devices are reasonably safeguarded.
(b) Either party may record any of their telephone communications.
Verification and Security Procedures. (a) Bank and Customer shall from time to time agree upon security procedures to be followed by Customer upon the issuance of an instruction and/or by Bank upon the receipt of an instruction, so as to enable Bank to verify that such instruction is authorized (“Security Procedures”). A Security Procedure may, without limitation, involve the use of algorithms, codes, passwords, encryption and telephone call backs. The Customer acknowledges that Security Procedures are designed to verify the authenticity of, and not detect errors in, instructions. For the avoidance of doubt, the parties agree that a SWIFT message issued in the name of the Customer through any third party utility agreed upon by the parties as being a method for providing Instructions and authenticated in accordance with that utility’s customary procedures, shall be deemed to be an authorised Instruction.
(b) Bank and Customer shall ensure that any codes, passwords or similar devices are reasonably safeguarded.
(c) Either party may record any of their telephone communications.
Verification and Security Procedures. (a) Bank and the Customer shall comply with any applicable Security Procedure to permit Bank to verify the authenticity of Instructions.
(b) Either party may record any of their joint telephone communications as long as such recording is in compliance with Applicable Laws.
(c) The Customer acknowledges that the Security Procedure is designed to verify the authenticity of, and not to detect errors in, Instructions. The Customer shall promptly notify Bank if it does not believe that any relevant Security Procedure is commercially reasonable, and its adherence to any Security Procedure without objection constitutes its agreement that it has determined the Security Procedure to be commercially reasonable.
(d) The Customer and its Authorized Persons are solely responsible for ensuring that the User Codes are reasonably safeguarded and known to and used by only the respective Authorized Persons to whom such User Codes apply. If (i) the User Codes are (or the Customer or its relevant Authorized Person reasonably suspects that the User Codes may be) lost, stolen, damaged, altered, unduly disclosed, known in a manner inconsistent with its purposes or compromised, (ii) the Customer’s or any Authorized Persons’ access to Bank’s systems, applications or products, or any third party messaging platform through which the Instructions are transmitted, is revoked or suspended, or (iii) the Customer or an Authorized Person reasonably suspects any technical or security failure relating to any systems, applications or products of Bank or any third party messaging platform through which the Instructions are transmitted, the Customer shall immediately cease using such system, application, product or platform and promptly notify Bank. Notwithstanding the foregoing, Bank shall be responsible for ensuring that User Codes maintained in Bank’s systems or records are reasonably safeguarded and shall take appropriate action to remediate any technical or security failure confirmed by Bank, that is the subject of the notification provided by Customer or an Authorized Person referenced in this section 3.2(d).
Verification and Security Procedures. (a) J.X. Xxxxxx and the Customer shall comply with any applicable Security Procedures to permit J.X. Xxxxxx to verify the authenticity of Instructions.
(b) The Customer acknowledges that the Security Procedure is designed to verify the authenticity of, and not to detect errors in, Instructions. The Customer shall promptly notify J.X. Xxxxxx if it does not believe that any relevant Security Procedure is commercially reasonable, and its adherence to any Security Procedure without objection constitutes its agreement that it has determined the Security Procedure to be commercially reasonable.
(c) The Customer and its Authorized Persons are solely responsible for ensuring that the User Codes are reasonably safeguarded and known to and used by only the respective Authorized Persons to whom such User Codes apply. If (i) the User Codes are (or the Customer or its relevant Authorized Person reasonably suspects that the User Codes may be) lost, stolen, damaged, altered, unduly disclosed, known in a manner inconsistent with its purposes or compromised, (ii) the Customer’s or any Authorized Persons’ access to J.X. Xxxxxx’x systems, applications or products, or any third party messaging platform through which the Instructions are transmitted, is revoked or suspended, or (iii) the Customer or an Authorized Person reasonably suspects any technical or security failure relating to any systems, applications or products of J.X. Xxxxxx or any third party messaging platform through which the Instructions are transmitted, the Customer shall immediately cease using such system, application, product or platform and promptly notify J.X. Xxxxxx. Global Custody Agreement - New York - General February 2018 version
Verification and Security Procedures. (a) ABIS and the Fund shall comply with any applicable security procedures with respect to the delivery or authentication of Instructions and shall ensure that any codes, passwords or similar devices are reasonably safeguarded.
(b) Either party may record any of its telephone communications.
Verification and Security Procedures. All transactions by both parties (Originator and Beneficiary) are carried out through their respective banks. Appropriate verification and security procedures are the responsibility of each party and its bank.
Verification and Security Procedures. Instructions Contrary To Applicable Law/Market Practice.
Verification and Security Procedures. (a) JPMorgan and the Customer shall from time to time agree upon security procedures to be followed by the Customer upon the issuance of an Instruction and/or by JPMorgan upon the receipt of an Instruction, so as to enable JPMorgan to verify that such Instruction is authorized (“Security Procedures”). A Security Procedure may, without limitation, involve the use of algorithms, codes, passwords, encryption and telephone callbacks. The Customer acknowledges that Security Procedures are designed to verify the authenticity of, and not detect errors in, Instructions. The parties agree that a message issued in the name of the Customer through any third party utility agreed upon by the parties as being a method for providing Instructions and authenticated in accordance with that utility’s customary procedures, shall be deemed to be an authorized Instruction.
(b) JPMorgan and the Customer shall ensure that any codes, passwords or similar devices are reasonably safeguarded.
(c) Either party may record any of its telephone communications.
Verification and Security Procedures. (a) Bank and City shall comply with any applicable Security Procedures with respect to the delivery or authentication of Instructions and shall ensure that any codes, passwords or similar devices are reasonably safeguarded.
(b) Either party may record any of their telephone communications.
Verification and Security Procedures. (a) Bank and Customer shall from time to time agree upon security procedures to be followed by Customer upon the issuance of an Instruction and/or by Bank upon the receipt of an Instruction, so as to enable Bank to verify that such Instruction is authorized ("Security Procedures"). A Security Procedure may, without limitation, involve the use of algorithms, codes, passwords, encryption and telephone call backs. Customer acknowledges that Security Procedures are designed to verify the authenticity of, and not detect errors in, Instructions. For the avoidance of doubt, the parties agree that a SWIFT message issued in the name of Customer through any third party utility agreed upon by the parties as being a method for providing Instructions and authenticated in accordance with that utility's customary procedures, shall be deemed to be an authorized Instruction.
(b) Bank and Customer shall ensure that any codes, passwords or similar devices are reasonably safeguarded.
(c) Either party may record any of their telephone communications.