My WebLink
|
Help
|
About
|
Sign Out
Browse
Search
Agmt11 EPX-Electronic Payment Exchange
RedwoodCity
>
City Clerk
>
Agreements
>
2010-2019
>
2011
>
Agmt 11 Under 60K
>
Agmt11 EPX-Electronic Payment Exchange
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/30/2011 10:54:20 AM
Creation date
11/30/2011 10:52:49 AM
Metadata
Fields
Template:
Agreement
Contractor Name
EPX-Electronic Payment Exchange
PROJECT NAME
Merchant Agreement
RMP File Number
304.5
Date
11/15/2011
Document Relationships
Agmt11 Infosend, Inc.
(Message)
Path:
\City Clerk\Agreements\2010-2019\2011\Agmt 11 Under 60K
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
19
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
8. A setoff or counterclaim of any kind exists in favor of any Cazdholdcr against Merchant that <br /> may be asserted in defense of an action to enforcc payment against the Cardholder in a <br /> Transaction; <br /> 9. The Transaction was made at or by a Merchant other than Merchant named in this <br /> Agreement; <br /> 10. The Transaction otherwise violates the terms of this Agrccmcnt or any other Association or <br /> Issuer bylaw, rule, reguladon, policy or guidelinc; <br /> 11. A Transaction is chazgcd back by an Issuer; or <br /> 12. Any representation or warranty made by Merchant in connection with the Transaction is <br /> false or inaccurate in any respect <br /> In any such case, Bank shall not be obligated to accept a Transaction for credit to the Opemung <br /> Account. If Bank has credited the Operating Account or Reserve Account for such a Transacpon, Bank <br /> may return the Transaction to the Merchacit, and Bank shall recover [he amount of the Transaction &om <br /> either afoeementioned account. Merchant agrees that Bank, without prior notice to Merchant, may: , <br /> I. Charge the amount of the Transaction to the Operating Account or Reserve Account; <br /> 2. Recoup thc amount of the Transaction by adjusunent of the credits due to Merchant; or <br /> 3. Set off the amount of the Transaction against any account or property Bank holds for or on <br /> bchalf of Merchant. <br /> 5. Compliance. <br /> 5.1. Associations' and Issuers' Requirements. Merchant shalt comply with all bylaws, mles, regulations, <br /> policies and guidelines of the Associations and any Issuer whose Cards aze used to process <br /> Transactions in accordance with this Agreement. EPX agrees to keep Merchant advised of Association <br /> rules and regulations as they are applied. <br /> 5.2. Usc of Marks. Merchant will display prominently at its place of business Card emblems and other <br /> promotional material and literature provided by Bank directly or tivough F,PX. Subject to lhe prior <br /> written consent of Bank and upon such conditions as authorized by Bank, Merchant may use Cazd <br /> service marks or desi�n marks in its own advertisement and promotional materiais. <br /> 53. Pavment Card lndustry Securiry Reguirements. Merchant agrees to bc compliant with applicable PCI <br /> requirements, in accordance with Payment Card Industry Data Securiry Standards (PCI) for protecting <br /> Cardholder data ac amended by the Associations &om time to time. <br /> i. Visa, MasterCard and Discover havc implemented a program to ensure thc protection of <br /> cardholder data, whether processed, transmitted or storcd, through a program of validation and <br /> compliance. Known as PCI, information about the program and specific requiremenu can be <br /> obtained at www.visa.cum/cisn. The program is comprised of 12 major requirements: <br /> l. Install and maintain a firewalt configuration to protect data <br /> 2. Do not use vendor-supplied deFaults for system passwords and other security parameters <br /> 3. Protect storcd data <br /> 4. Encrypt transmission of cardholder data and sensitive information across public <br /> networks <br /> 5. Use and regularly update anti-vitus software <br /> 6. Develop and maintain secure systems and applications <br /> 7. Restrict access to data by business need-to-know <br /> R. Assign a unique ID to each person with computer access <br /> 9. Restrict physical access ro cardholder data <br /> 10. Track and monitor all access to network resources and cardholder data <br /> I1. Rcgularly tcst security systems and processes <br /> 12. Maintain a policy that addresses informa[ion security <br /> iuitiais���yi�\ P;jge G ot' 19 <br /> �•� <br />
The URL can be used to link to this page
Your browser does not support the video tag.