My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
BANCORP BANK (THE); PHOENIX PAYMENT SYSTEMS, INC. DBA ELECTRONIC PAYMENT EXCHANGE (EPX)
Clerk
>
Contracts / Agreements
>
B
>
BANCORP BANK (THE); PHOENIX PAYMENT SYSTEMS, INC. DBA ELECTRONIC PAYMENT EXCHANGE (EPX)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/21/2013 11:34:01 AM
Creation date
12/10/2012 2:05:37 PM
Metadata
Fields
Template:
Contracts
Company Name
BANCORP BANK (THE); PHOENIX PAYMENT SYSTEMS, INC. DBA ELECTRONIC PAYMENT EXCHANGE (EPX)
Contract #
N-2012-146
Agency
FINANCE & MANAGEMENT SERVICES
Expiration Date
1/1/2014
Destruction Year
0
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).
View images
View plain text
8. A setoff or counterclaim of any kind exists in favor of any Cardholder against Merchant that <br />may be asserted in defense of an action to enforce 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 />1 O. The Transaction otherwise violates the terms of this Agreement or any other Association or <br />Issuer bylaw, rule, regulation, policy or guideline; <br />1 1. A Transaction is charged 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 Operating <br />Account. If Bank has credited the Operating Account or Reserve Account for such a Transaction, Bank <br />may return the Transaction to the Merchant, and Bank shall recover the amount of the Transaction from <br />either aforementioned account. Merchant agrees that Bank, without prior notice to Merchant, may: <br />1. Charge the amount of the Transaction to the Operating Account or Reserve Account; <br />2. Recoup the amount of the Transaction by adjustment 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 />behalf of Merchant. <br />5. Compliance. <br />5.1. Associations' and Issuers' Requirements. Merchant shall comply with all bylaws, rules, regulations, <br />policies and guidelines of the Associations and any Issuer whose Cards are 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. Use 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 through EPX. Subject to the prior <br />written consent of Bank and upon such conditions as authorized by Bank, Merchant may use Card <br />service marks or design marks in its own advertisement and promotional materials. <br />53. Payment Card Industry Securit?quirements. Merchant agrees to be compliant, ,with applicable PCI <br />requirements, in accordance with Payment Card Industry Data Security Standards (PCI) for protecting <br />Cardholder data as amended by the Associations from time to time. <br />i. Visa, MasterCard and Discover have implemented a program to ensure the protection of <br />cardholder data, whether processed, transmitted or stored, through a program of validation and <br />compliance. Known as PCI, information about the program and specific requirements can be <br />obtained at www.visa.com/cisn. The program is comprised of 12 major requirements: <br />1. Install and maintain a firewall configuration to protect data <br />2. Do not use vendor-supplied defaults for system passwords and other security parameters <br />3. Protect stored data <br />4. Encrypt transmission of cardholder data and sensitive information across public <br />networks <br />5. Use and regularly update anti-virus software <br />6. Develop and maintain secure systems and applications <br />7. Restrict access to data by business need-to-know <br />8. Assign a unique ID to each person with computer access <br />9. Restrict physical access to cardholder data <br />1 O. Track and monitor all access to network resources and cardholder data <br />1 1. Regularly test security systems and processes <br />12. Maintain a policy that addresses information security <br />Initials Page 6 of 19
The URL can be used to link to this page
Your browser does not support the video tag.