Compliance with Security Procedures Sample Clauses

Compliance with Security Procedures. Customer shall have complied with applicable Security Procedures for the Service as may be required by Bank from time to time.
AutoNDA by SimpleDocs
Compliance with Security Procedures. Subject to applicable law and regulations, if an Entry (or a request for cancellation or amendment of an Entry) received by us purports to have been transmitted or authorized by you, it will be deemed effective as your Entry (or request) and you shall be obligated to pay us or the other applicable financial institution the amount of such Entry even though the Entry (or request) was not authorized by you, provided we accepted the Entry in good faith and acted in compliance with the security procedures previously described with respect to such Entry. If an Entry (or request for cancellation or amendment of an Entry) received by us was transmitted or authorized by you, you shall pay us or the other applicable financial institution the amount of the Entry, whether or not we complied with the security procedures previously described with respect to that Entry and whether or not that Entry was erroneous in any respect or that error would have been detected if we had complied with such security procedure.
Compliance with Security Procedures. If an Entry (or a request for cancellation or amendment of an Entry) received by Bank purports to have been transmitted or authorized by Client, it will be deemed effective as Client’s Entry (or request) and Client shall be obligated to pay Bank the amount of such Entry even though the Entry (or request) was not authorized by Client, provided Bank accepted the Entry in good faith and acted in compliance with the Security Procedures with respect to such Entry.
Compliance with Security Procedures a. If an Entry (or a request for cancellation or amendment of a File) received by the Bank purports to have been transmitted or authorized by the Business Entity, it will be deemed effective as the Business Entity's Entry (or request) and the Business Entity shall be obligated to pay the Bank the amount of such Entry (or request) even though the Entry (or request) was not actually authorized by the Business Entity, whether or not the Bank 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 Bank shall be deemed to have complied with that part of such procedure if it compares the signature accompanying a file of Entries (or request) with the signature of an Authorized Representative of the Business Entity and, on the basis of such comparison, believes the signature to be that of such Authorized Representative.
Compliance with Security Procedures. If an Entry (or a request for cancellation or amendment of an Entry) received by the Bank purports to have been transmitted or authorized by the Customer, it will be deemed effective as the Customer's Entry (or request) and the Customer shall be obligated to pay the Bank the amount of such Entry (or request) even though the Entry (or request) was not authorized by the Customer, provided the Bank acted in compliance with the security procedures sent to Customer. If signature comparison is to be used as part of that security procedure, the Bank shall be deemed to have complied with that part of such procedure if it compares the signature accompanying a file of Entries (or request) with the signature of an Authorized Representative of the Customer and, on the basis of such comparison, believes the signature to be that of such Authorized Representative.
Compliance with Security Procedures. 67.1 If an Entry (or a request for cancellation or amendment of an Entry) received by Bank was initiated in accordance with the Security Procedures applicable to the ACH Service and thereby purports to have been transmitted or authorized by Customer, it shall be deemed effective as Customer’s Entry (or request), even if the Entry (or request) was not authorized by Customer. If Bank accepted the Entry (a) in compliance with the Security Procedures with respect to such Entry, (b) in compliance with any written agreement or instruction of Customer restricting acceptance of payment orders issued in Customer’s name, and (c) in good faith, then with respect to a credit Entry, Customer shall be obligated to pay Bank the amount of such Entry, and with respect to a debit Entry, Customer shall maintain sufficient Available Funds in the Settlement Account, as defined in Section 73, to fund the reversal of such Entry, if necessary.
Compliance with Security Procedures. The authorizations in Exhibit 3 (or Exhibit 5-B in the case of third-party processors) and security procedures in Exhibit 3 (or Exhibit 5-B in the case of third-party processors) shall apply equally to Entries and requests for cancellation or amendment of Entries. Accordingly, in this Section 19, “Entry” shall be construed to include requests for cancellation or amendment of Entries. If an Entry received by the Bank was transmitted or authorized by the Company, or if an Entry received by the Bank purports to have been transmitted or authorized by the Company, and the Bank has complied with the security procedures provided for herein, then, in either case, it will be deemed effective as the Company’s Entry. If signature comparison is to be part of that security procedure, the Bank shall be deemed to have complied with that part of such procedure if the signature accompanying a file or Entries bears any resemblance whatsoever to the signature of the Company’s authorized representative for submission of Entries. The Company is responsible for maintaining the confidentiality of the security procedures hereunder and shall promptly report to the Bank any breach thereof. The Bank shall have no liability for losses occasioned by the Company’s failure to maintain the confidentiality of its security procedures. The Bank may change, add, or delete any procedures established pursuant to this Agreement, from time to time, upon notice to the Company.
AutoNDA by SimpleDocs
Compliance with Security Procedures. (a) Except as otherwise required by applicable law, if a Payment Order (or a request for cancellation or amendment of a Payment Order) received by Bank purports to have been transmitted or authorized by Client, it will be deemed effective as Client's Payment Order (or request) and Client shall be obligated to pay Bank the amount of such Payment Order as provided herein even though the Payment Order (or request) was not authorized by Client, provided Bank acted in compliance with the security procedure referred to in Appendix A with respect to such Payment Order.
Compliance with Security Procedures a. If an Entry (or a request for cancellation of an Entry) received by Bank purports to have been transmitted or authorized by Customer, it will be deemed effective as Customer’s Entry (or request) and Customer shall be obligated to pay Bank the amount of such Entry as provided herein even though the Entry (or request) was not authorized by Customer, provided Bank acted in compliance with the Security Procedures. If an Entry (or a request for cancellation of an Entry) received by Bank purports to have been transmitted or authorized by Customer (including, without limitation, any Authorized Representative or Authorized Agent), it will be deemed effective as Customer’s Entry (or request) and Customer shall be obligated to pay Bank the amount of such Entry as provided herein even though the Entry (or request) was not authorized by Customer, provided Bank acted in compliance with the Security Procedures with respect to such Entry. If signature comparison is to be used as a part of those Security Procedures, Bank shall be deemed to have complied with that part of such Security Procedures if it compares the signature accompanying a file of Entries (or request for cancellation of an Entry) received with the signature of an Authorized Representative and, on the basis of such comparison, believes the signature accompanying such file to be that of such Authorized Representative.
Compliance with Security Procedures. Any Payment Order communicated by or on behalf of you shall be effective as your Payment Order and shall be enforceable against you, whether or not authorized and regardless of the actual identity of the signer, sender or transmitter thereof, if such Payment Order is received in accordance with the applicable Security Procedures, and if we accept such Payment Order in good faith. In addition, if any Payment Order was actually communicated or authorized by you or you otherwise benefited from such Payment Order (or resulting Transfer), then you will be obligated to pay us the amount of the related Transfer without regard to whether we complied with the Security Procedures. We may, in our discretion, use additional procedures to verify the authenticity of any Payment Order and you agree to implement any other reasonable authentication or Security Procedures established by us. If you choose to communicate any Payment Order (including any cancellation or amendment thereof) to us in a manner that varies from the Security Procedures, and if we accept such Payment Order in good faith, then you agree to be bound by such Payment Order, whether or not authorized, and you will be deemed to have refused the Security Procedures that we offer and recommend as commercially reasonable, and you will be obligated to pay us the amount of such Transfer. However, we have no obligation to accept any Payment Order that is not communicated in compliance with the Security Procedures. We shall not be responsible for refusal to act upon any Payment Order received which does not comply with these Wire Transfer Service Terms and Conditions, including where our reasonable efforts to verify the Payment Order in accordance with the Security Procedures have failed or where such action is delayed until verification can be obtained.
Time is Money Join Law Insider Premium to draft better contracts faster.