Agmt15 Wells Fargo Bank - Laserfiche WebLink

Browse Search

Machine-to-Machine ("M2M"). This transmission method may use an XML message interface that is based on the Interactive Financial eXchange (IFX) message standard using SOAP structured messages or other formats and protocols such as JSON and REST. Data is communicated via the Internet using 128-bit encryption and Secure Socket Layers (SSL). IBM� Connect:Direct� with Secure Plus+. Secure Plus+ is an add-on to Connect Direct to enhance security by means of Secure Socket Layer ("SSL") or Transport Layer Security ("TLS"). Connect Direct� is a registered trademark of Sterling Commerce, Inc. an IBM company. Value-Added Network ("VAN"). With this transmission method, a third party serves as an intermediary for transmitting data between Company and Bank. Procedures for transmitting Payment Orders may vary by VAN. Bank follows the procedures of the VAN selected by Company to authenticate each File transmitted to Bank through the VAN in Company's name. SWIFT� File Act. SWIFT has established procedures for controlling access to SWIFT messaging services that may include access codes, message authentication codes, secure card readers, digital signatures, and Hardware Security Modules. In addition, SWIFT authenticates certain messages including without limitation Files based on SWIFT message type prior to accepting them for routing as SWIFT messages. This authentication may include confirming the sender and recipient of the message have exchanged bilateral keys ("BKE"), entered into a relationship management application ("RMA") agreement, or taken other steps to secure the transmission of SWIFT messages befinreen them as SWIFT requires from time to time. 6.4. Security Procedure Elected by Company's Third Party Service Provider. Company is utilizing a Third Party Senrice Provider ("TPSP") as defined in the ACH Rules to originate Entries and Files on Company's behalf. Bank will authenticate each File transmitted to Bank in Company's name in accordance with the security procedure the Company's TPSP has elected. Company will notify Bank of any change to Company's TPSP in a manner affording Bank a reasonable opportunity to act on the information. 6.5. Non-Standard Security Procedure. If Company has refused to utilize any of the security procedures described above, then the Security Procedure Company will use is described on Attachment B to the Treasury Management Product Enrollment form. 7. Company's Payment Obligations. As of the applicable settlement date, Company will maintain available funds in each Account sufficient to cover the credit Entries originated against it. Company's obligation to pay Bank for each credit Entry matures when Bank transmits the credit Entry to the ACH or gateway operator or posts an on-us Entry. Bank is authorized to debit the Account for the total amount of all credit Entries originated from it at any time. If requested by Bank, Company will pay to Bank, in immediately available funds, an amount equal to all credit Entries Company originates through Bank before the date Bank delive�s the credit Entries to the ACH or gateway operator or posts an on-us Entry. If Company fails to comply with Bank's request, Bank may refuse to send the Entries to the ACH or gateway operator or post an on-us Entry. Bank may take such other actions as it deems necessary or appropriate to ensure Bank receives payment for Company's credit Entries including without limitation (a) upon notice to Company, placing a hold on funds in any account at Bank or any a�liate of Bank that Company owns in whole or in part sufficient to cover Company's credit Entries and (b) setting TM-1423 ACH Origination Services EDOCS-#3784910 Page 3 of 7 Revised 10-30-2014