My WebLink
|
Help
|
About
|
Sign Out
Browse
Search
Agmt15 Wells Fargo Bank
RedwoodCity
>
City Clerk
>
Agreements
>
2010-2019
>
2015
>
Agmt15 Wells Fargo Bank
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/27/2015 10:18:12 AM
Creation date
8/27/2015 10:16:26 AM
Metadata
Fields
Template:
Agreement
Contractor Name
Wells Fargo Bank
PROJECT NAME
Banking and Cash Management Services
RMP File Number
304
Date
8/26/2015
MO Ref
15-141
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
117
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
4. Inconsistency of Name and Number. If a Payment Order describes the person to receive the <br /> funds that are the subject of the Payment Orders both by name and identifying number, Bank <br /> may execute the Payment Order on the basis of the identifying number, even if the number <br /> identifies a person different from the named person. If a Payment Order describes a financial <br /> institution both by name and identification number, the identification number may be relied upon <br /> to identify the financial institution, even if the identification number refers to a financial institution <br /> other than the named financial institution. <br /> 5. Initiation Methods and Security Procedures. This section lists the Initiation Methods and <br /> Security Procedures Bank offers for wire transfers. Company's elections regarding Initiation <br /> Methods and Security Procedures is/are set forth in the Acceptance. <br /> 5.1. Commercial Electronic Office�(CEO�) Initiation Method. <br /> The CEO� portal is Bank's electronic banking portal that is accessed via the Internet. The <br /> CEO� security procedures are log-on credentials specified by Bank including a company <br /> ID, user ID, password, token, and any other authentication or authorization process Bank <br /> requires from time to time. Bank's standard CEO� security procedures also include dual <br /> custody for select, high-risk wire transfer activities. With dual custody, an authenticated <br /> second user approves these activities. There is no additional charge for dual custody. <br /> 5.2. Payment Manager�Initiation Method. <br /> Secure Application File Exchange Transmission ("SAFE-T"). This transmission <br /> platform offers a variety of transmission protocols including hypertext transfer protocol <br /> secured (https), FTP over SSL (FTP/S), secure FTP (S-FTP), and Applicability Statement 2 <br /> (AS2). <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 <br /> using SOAP structured messages; or it may use other formats and protocols such as JSON <br /> and REST. Data is communicated via the Internet using 128-bit encryption and Secure <br /> Socket Layers (SSL). <br /> IBM� Connect:Direct�with Secure Plus+. Secure Plus+ is an add-on to Connect:Direct� <br /> to 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"). With this transmission method, a third party serves as <br /> an intermediary for transmitting data between Company and Bank. Procedures for <br /> transmitting Payment Orders may vary by VAN. Bank follows the procedures of the VAN <br /> selected by Company to authenticate each Payment Order transmitted to Bank through the <br /> VAN in Company's name. <br /> SWIFT'� File Act. SWIFT has established procedures for controlling access to SWIFT <br /> messaging services (each, an "Access Control") that may include access codes, message <br /> authentication codes, secure card readers, digital signatures, and Hardware Security <br /> Modules. In addition, SWIFT authenticates certain messages including without limitation <br /> Payment Orders based on SWIFT message type prior to accepting them for routing as <br /> SWIFT messages. This authentication may include confirming that the sender and <br /> recipient of the message have exchanged bilateral keys ("BKE"), entered into a relationship <br /> management application ("RMA") agreement, or taken other steps to secure the <br /> TM-1440 Wire Tiansfer Service Description Page 2 of 5 <br /> Revised 043a2014 <br />
The URL can be used to link to this page
Your browser does not support the video tag.