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