Payment Card Industry (PCI) Data Security Standard Sample Clauses

Payment Card Industry (PCI) Data Security Standard. All Payment Networks including Visa, MasterCard and Discover Network have collaborated in creating common industry requirements, known as the Payment Card Industry (PCI) Data Security Standard, to protect Cardholder data. This program is an alignment of Visa’s Cardholder Information Security Program (CISP), MasterCard’s Site Data Protection (SDP) and Discover Information Security and Compliance (DISC) Security Standards. For purposes of this Agreement, reference to the PCI Data Security Standard includes also CISP, SDP, DISC and/or any successor standards. The PCI Data Security Standard applies to Merchants that store, process, or transmit Cardholder data. All Merchants that accept Cards must comply with the following security requirements:  Merchant will implement and maintain all security requirements, as specified in the PCI Data Security Standards, copies of which may be obtained by visiting the Payment Networks’ web sites at xxx.xxxxxxxxxxxxxxxxxxxx.xxx, xxx.xxxx. com/cisp, xxx.xxxxxxXxxx.xxx/xxx or xxx.xxxxxxxxxxxxxxx.xxx/xxxxxxxxxxxxx/xxxx.xxxx . Xxxxxxxx will be responsible for all fees and expenses at the inception of this Agreement and during on-going processing under this Agreement related to meeting the PCI Data Security Standard, including meeting the standards summarized below, initial and ongoing security audits, or as may be required by Bank or by other Payment Network Rules.  Merchant will immediately notify Bank, by giving written notice, of its use of all Qualified Security Assessor (QSA) or Approved Scanning Vendor (ASV) to bring it into compliance with the PCI Data Security Standards as well as to perform the required security audits meeting the requirements of the PCI Data Security Standards. Xxxxxxxx agrees to use only Payment Network-approved QSA or ASV vendors.  Merchant must validate compliance with PCI Data Security Standards by submitting required documentation to Bank. Documentation must also be made available to the Payment Networks upon request. Merchant agrees to provide documentation required to validate PCI Data Security Standard compliance at the time of Account opening and on an ongoing basis, consistent with the frequency standards under the PCI Data Security Standards. The documentation must include validation from a Payment Network-approved QSA or ASV vendor. Merchant acknowledges and agrees that in connection with PCI Data Security Standard audits performed by the QSA or ASV vendor, Bank will supply the vendor with ...
Sample 1
AutoNDA by SimpleDocs

Related to Payment Card Industry (PCI) Data Security Standard

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

  • Security Standards The Provider shall implement and maintain commercially reasonable security procedures and practices that otherwise meet or exceed industry standards designed to protect Student Data from unauthorized access, destruction, use, modification, or disclosure, including but not limited to the unauthorized acquisition of computerized data that compromises the security, confidentiality, or integrity of the Student Data (a "Security Breach"). For purposes of the DPA and this Exhibit G, "Security Breach" does not include the good faith acquisition of Student Data by an employee or agent of the Provider or LEA for a legitimate educational or administrative purpose of the Provider or LEA, so long as the Student Data is used solely for purposes permitted by SOPPA and other applicable law, and so long as the Student Data is restricted from further unauthorized disclosure.

  • PROCUREMENT CARD The State has entered into an agreement for purchasing card services. The Purchasing Card enables Authorized Users to make authorized purchases directly from a Contractor without processing Purchase Orders or Purchase Authorizations. Purchasing Cards are issued to selected employees authorized to purchase for the Authorized User and having direct contact with Contractors. Cardholders can make purchases directly from any Contractor that accepts the Purchasing Card. The Contractor shall not process a transaction for payment through the credit card clearinghouse until the purchased Products have been shipped or services performed. Unless the cardholder requests correction or replacement of a defective or faulty Product in accordance with other Contract requirements, the Contractor shall immediately credit a cardholder’s account for Products returned as defective or faulty.

  • Financial Management System Subrecipient shall establish and maintain a sound financial management system, based upon generally accepted accounting principles. Contractor’s system shall provide fiscal control and accounting procedures that will include the following:

  • PERFORMANCE MANAGEMENT SYSTEM 5.1 The Employee agrees to participate in the performance management system that the Employer adopts or introduces for the Employer, management and municipal staff of the Employer.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • HMG Baseline Personnel Security Standards 8.1 The authority will review the Contractor’s HMG Baseline Personnel Security Standards Declaration in accordance with HMG Baseline Personnel Security Standard – A Guide For DWP Contractors. 9 Health and Safety Responsibilities of the Authority Visiting Officers

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized purchasers specified herein during the term of the Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: For Calendar Quarter Ending Master Contract Sales Report Due March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 0.74 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0074. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. the sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing.

  • Local Interconnection Data Exchange for Billing 7.7.1 There are certain types of calls or types of Interconnection that require exchange of Billing records between the Parties, including, for example, alternate billed and Toll Free Service calls. The Parties agree that all call types must be routed between the networks, accounted for, and settled among the Parties. Certain calls will be handled via the Parties' respective operator service platforms. The Parties agree to utilize, where possible and appropriate, existing accounting and settlement systems to xxxx, exchange records and settle revenue.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

Time is Money Join Law Insider Premium to draft better contracts faster.