My WebLink
|
Help
|
About
|
Sign Out
Browse
Search
AgdaPkt 2015-08-24 Joint SA and PAF
RedwoodCity
>
City Clerk
>
Agenda Packets
>
2010-2019
>
2015
>
AgdaPkt 2015-08-24 Joint SA and PAF
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/8/2015 9:02:17 AM
Creation date
8/20/2015 7:19:56 PM
Metadata
Fields
Template:
CC Index
CC Index - Document Type
Agenda Packet
Meeting Type
Joint
Agency Type
City Council and Successor Agency and Public Financing Authority
Date
8/24/2015
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
551
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
TM-1423 ACH Origination Services EDOCS-#3784910 Page 2 of 7 <br />Revised 10-30-2014 <br />completed and authenticated in compliance with the Security Procedure. If Bank receives a File after <br />Bank’s applicable cutoff time or on a day when the ACH is not open for business, the File will be treated <br />as having been received prior to Bank’s applicable cutoff time on the next Business Day on which the <br />ACH is open for business. A “Business Day” is every day except Saturday, Sunday and federal <br />holidays. <br /> <br />5. Inconsistency of Name and Number. If an Entry describes a “Receiver” (as defined in the ACH <br />Rules), both by name and identifying number, the RDFI may pay the Entry on the basis of the <br />identifying number, even if the number identifies a person different from the named Receiver. If an <br />Entry describes the RDFI both by name and identifying number, Bank, a gateway operator or another <br />financial institution handling the Entry may rely on the identifying number to identify the RDFI, even if <br />the identifying number refers to an institution other than the named RDFI. <br /> <br />6. Initiation Methods and Security Procedures. This section lists the Initiation Methods and describes <br />the Security Procedures Bank offers for ACH origination. Company’s elections regarding Initiation <br />Methods and Security Procedures are set forth in the Acceptance. <br /> <br />6.1. Commercial Electronic Office® (CEO®) Initiation Method. <br /> <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 ID, <br />user ID, password, token, and any other authentication or authorization process Bank requires <br />from time to time. Bank’s standard CEO® security procedures also include dual custody for <br />select, high-risk ACH activities. With dual custody, an authenticated second user approves <br />these activities. There is no additional charge for dual custody. <br /> <br />6.2. Direct Origination Initiation Method. <br /> <br />Secure Application File Exchange Transmission (“SAFE-T”). This transmission platform <br />offers a variety of transmission protocols including hypertext transfer protocol secured (https), <br />FTP over SSL (FTP/S), secure FTP (S-FTP), and Applicability Statement 2 (AS2). <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 />SWIFT® FileAct. 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.3. Payment Manager® Initiation Method. <br /> <br />Secure Application File Exchange Transmission (“SAFE-T”). This transmission platform <br />offers a variety of transmission protocols including hypertext transfer protocol secured (https), <br />FTP over SSL (FTP/S), secure FTP (S-FTP), and Applicability Statement 2 (AS2). <br />6.1.D. - Page 34
The URL can be used to link to this page
Your browser does not support the video tag.