My WebLink
|
Help
|
About
|
Sign Out
Browse
Search
Agmt16 Wells Fargo Bank
RedwoodCity
>
City Clerk
>
Agreements
>
2010-2019
>
2016
>
Agmt16 Wells Fargo Bank
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/30/2016 1:00:51 PM
Creation date
8/30/2016 12:49:11 PM
Metadata
Fields
Template:
Agreement
Contractor Name
Wells Fargo Bank
PROJECT NAME
Banking Services
Date
8/28/2016
MO Ref
16-138
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
114
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
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 /> IBllllm Connect:Directm with Secure Plus+. Secure Plus+ is an add-on to Conneot 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 /> Value-Added Network ("VAN"). Wth 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 th�ough the VAN in Company's name. <br /> SWIF1'� 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 addidon, SWIFT <br /> authenticates certain messages including without limitation Files based on SWIFT message <br /> type prior to accepting them for�outing 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 /> 6.4. Security Procedure Elected by Company's Third Party Service Provider. <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 wiil authenticate each File transmitted <br /> to Bank in Company's name in accordance with the security procedu�e 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 infortnation. <br /> 6.5. Non-Standard Securlty Procedure. <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 /> 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 operato�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 ope�ator 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 a�y 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 /> 7M-1423 ACH Oiiy�inatiaf Seivices EDOCS-�M37849f0 Page 3 0!7 <br /> ReNsed fa34�2014 <br /> ATTY/AGR/2016.186M/ELLS FARGO BANKING AGREEMENT <br />
The URL can be used to link to this page
Your browser does not support the video tag.