My WebLink
|
Help
|
About
|
Sign Out
Home
Search
2000-047 Council Resolution
LinoLakes
>
City Council
>
City Council Resolutions
>
2000
>
2000-047 Council Resolution
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/2/2015 1:51:02 PM
Creation date
12/2/2015 9:41:28 AM
Metadata
Fields
Template:
City Council
Council Document Type
Resolutions
Meeting Date
04/24/2000
Council Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
33
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).
View images
View plain text
to have agreed to be bound by any such Payment Order, whether or not authorized, which is issued in Customer's name <br />and accepted by Bank in good faith. Bank offers the following Security Procedures: <br />(a) Bank shall not accept any Payment Order unless issued by an Authorized Representative or a person purporting <br />to be an Authorized Representative. No Payment Order shall instruct Bank to debit any deposit account o <br />Customer at Bank other than a Covered Account. If a dollar limit is listed next to the name of any Authorized <br />Representative, Bank shall not accept any Payment Order issued by such Authorized Representative or a person <br />purporting to be such Authorized Representative in excess of such limit. <br />(b) Bank shall assign to each Authorized Representative a unique personal identification number ("PIN"). Such PIN <br />shall be furnished to Bank whenever a Payment Order is issued and shall be conclusive identification of the sender. <br />(c) If Bank or Customer determines that certain funds transfers have become Repetitive Transfers, Bank may assign <br />a repetitive code to Payment Orders pertaining to such Repetitive Transfers. If Bank does so, Customer may use <br />such repetitive code as part of an expedited procedure in issuing any such Payment Order in the future, and Bank <br />may execute any Payment Order containing such repetitive code. <br />(d) If a Payment Order instructs Bank to pay more than a dollar amount established by Bank from time to time in <br />its sole discretion to a Beneficiary other than Customer, or if an Authorized Representative or a person purporting <br />to be an Authorized Representative issues a Payment Order in a dollar amount in excess of the dollar limit assigned <br />to such Authorized Representative, or if any special instructions of Customer so require, Bank shall call back an <br />Authorized Representative, without regard to any dollar limit assigned to such Authorized Representative receiving <br />such call, but other than the Authorized Representative issuing or purportedly issuing such Payment Order if <br />reasonably possible, to verify such Payment Order. If reasonably possible, the Bank officer or employee making <br />such call shall not be the Bank officer or employee to whom such Payment Order was issued. <br />(e) This subparagraph applies only if Bank provides CDL to Customer. Customer shall provide, on its premises <br />and at its sole expense, a data terminal linked to CDL. Customer agrees to maintain such data terminal in proper <br />working condition and repair. Customer shall follow all procedures relating to CDL contained in any supplemental <br />materials, users guides, or the like from time to time provided to Customer by Bank, but only to the extent not <br />inconsistent with the provisions of this Agreement. Customer shall provide such additional information an, <br />execute such additional documentation relating to CDL as Bank may from time to time require. The provisions of <br />this subparagraph are in addition to, and not in substitution of, subparagraphs (a) through (d) above. <br />Any special instructions of Customer respecting Security Procedures shall be in writing delivered to Bank and, <br />if expressly agreed to by Bank, shall be deemed incorporated by reference into this Agreement. <br />4. Execution of Payment Orders. Bank in its sole discretion may execute Payment Orders in any order convenient to Bank <br />and may select such means and routes for the transfer of funds as Bank considers appropriate under the circumstances. <br />Without any limitation of the foregoing, unless Bank notifies Customer to the contrary, Bank shall use Fedwire to effect <br />all funds transfers to deposit accounts maintained at financial institution offices or branches located in the United States. <br />Unless Bank and Customer otherwise agree with respect to any Payment Order, Bank shall execute each Payment Order <br />on the business day when received by Bank, provided that Customer shall have transmitted such Payment Order to Bank <br />prior to the daily cutoff time established by Bank from time to time. Bank in its sole discretion may attempt to execute <br />on a same-day basis a Payment Order received after such daily cutoff time, but shall have no obligation to do so. <br />Customer acknowledges that if a Payment Order describes the Beneficiary or any financial institution inconsistently by <br />name and account or other identifying number, Bank and the Beneficiary's financial institution may execute and accept <br />such Payment Order on the basis of the account or other identifying number, even if such number identifies a person other <br />than the named Beneficiary or financial institution, and Customer's obligation to pay the amount of such Payment Order <br />is not excused in such circumstances. Bank has no duty to detect any such inconsistency in identification. <br />5. Rejection of Payment Orders; Overdrafts. Bank has the right to refuse to execute any Payment Order for any reason. <br />If a Payment Order creates an overdraft in the Covered Account to which such Payment Order relates, Bank is authorized <br />to charge any deposit account of Customer at Bank to the extent of any insufficiency in the applicable Covered Account <br />without any obligation to give prior notice thereof to Customer. If more than one Payment Order is made at or about the <br />same time and the available funds in the applicable Covered Account(s) do not cover all of such Payment Orders, Bank <br />may at its option execute as many of such Payment Orders as possible within the dollar limits of such available funds in <br />any order convenient to Bank and not to Customer. Bank's rejection of any Payment Order is effective when given if the <br />notice of rejection is given either by the same means by which such Payment Order was transmitted to Bank or by any <br />other means reasonable under the circumstances. <br />(0 <br />
The URL can be used to link to this page
Your browser does not support the video tag.