Network Compliance violations by Merchant Sample Clauses

Network Compliance violations by Merchant. Servicer shall file compliance violation reports to the Networks where appropriate and necessary when charge backs and auto-charge backs do not exist. For Transactions that meet all agreed upon criteria, compliance will be filed in order to recover funds from a merchant that has either made an error or charged an amount not authorized by Servicer or Bank when no charge back right exists and the amount is in direct violation of an applicable Network Rule. Servicer shall notify Bank of any such violation, as well as file reports, as appropriate, in accordance with Network requirements.
AutoNDA by SimpleDocs

Related to Network Compliance violations by Merchant

  • Policy Compliance Violations The Requester and Approved Users acknowledge that the NIH may terminate the DAR, including this Agreement and immediately revoke or suspend access to all controlled-access datasets subject to the NIH GDS Policy at any time if the Requester is found to be no longer in agreement with the principles outlined in the NIH GDS Policy, the terms described in this Agreement, or the Genomic Data User Code of Conduct. The Requester and PI agree to notify the NIH of any violations of the NIH GDS Policy, this Agreement, or the Genomic Data User Code of Conduct data within 24 hours of when the incident is identified. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification(s), the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.

  • CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.

  • Penalties for Non-compliance to Service Level Agreement Where the Supplier/Service Provider fails to deliver the Goods/Services within the agreed and accepted milestone timelines and provided that the cause of the delay was not due to a fault of Transnet, penalties shall be imposed at …………………………………………………… .

  • Compliance with Accessibility Standards All parties to this Agreement shall ensure that the plans for and the construction of all projects subject to this Agreement are in compliance with standards issued or approved by the Texas Department of Licensing and Regulation (TDLR) as meeting or consistent with minimum accessibility requirements of the Americans with Disabilities Act (P.L. 101-336) (ADA).

  • Child Support Compliance Act If the Contract Amount is $100,000 or more, this section is applicable. Contractor recognizes the importance of child and family support obligations and fully complies with (and will continue to comply with during the Term) all applicable state and federal laws relating to child and family support enforcement, including disclosure of information and compliance with earnings assignment orders, as provided in Family Code section 5200 et seq. Contractor provides the names of all new employees to the New Hire Registry maintained by the California Employment Development Department.

  • Contractual and Operational Compliance Audits (a) ICANN may from time to time (not to exceed twice per calendar year) conduct, or engage a third party to conduct, contractual compliance audits to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and (b) use commercially reasonable efforts to conduct such audit during regular business hours and in such a manner as to not unreasonably disrupt the operations of Registry Operator. As part of such audit and upon request by ICANN, Registry Operator shall timely provide all responsive documents, data and any other information reasonably necessary to demonstrate Registry Operator’s compliance with this Agreement. Upon no less than ten (10) calendar days notice (unless otherwise agreed to by Registry Operator), ICANN may, as part of any contractual compliance audit, conduct site visits during regular business hours to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. ICANN will treat any information obtained in connection with such audits that is appropriately marked as confidential (as required by Section 7.15) as Confidential Information of Registry Operator in accordance with Section 7.15.

  • PUBLIC RECORDS COMPLIANCE (APPLICABLE FOR SERVICE CONTRACTS Orange County is a public agency subject to Chapter 119, Florida Statutes. The Contractor agrees to comply with Florida’s Public Records Law. Specifically, the Contractor shall: 1. Keep and maintain public records required by Orange County to perform the service. 2. Upon request from Orange County’s custodian of public records, provide Orange County with a copy of the requested records or allow the records to be inspected or copied within a reasonable time at a cost that does not exceed the cost provided in this chapter or as otherwise provided by law. 3. Ensure that public records that are exempt or confidential and exempt from the public records disclosure requirements are not disclosed except as authorized by law for the duration of the contract term and following completion of the contract if the Contractor does not transfer the records to Orange County. 4. Upon completion of the contract, Contractor agrees to transfer at no cost to Orange County all public records in possession of the Contractor or keep and maintain public records required by Orange County to perform the service. If the Contractor transfers all public record to Orange County upon completion of the contract, the Contractor shall destroy any duplicate public records that are exempt or confidential and exempt from public records disclosure requirements. If the Contractor keeps and maintains public records upon completion of the contract, the Contractor shall meet all applicable requirements for retaining public records. All records stored electronically must be provided to Orange County, upon request from Orange County’s custodian of public records, in a format that is compatible with the information technology systems of Orange County. 5. A Contractor who fails to provide the public records to Orange County within a reasonable time may be subject to penalties under section 119.10, Florida Statutes. 6. IF THE CONTRACTOR HAS QUESTIONS REGARDING THE APPLICATION OF CHAPTER 119, FLORIDA STATUTES, TO THE CONTRACTOR’S DUTY TO PROVIDE PUBLIC RECORDS RELATING TO THIS CONTRACT, CONTACT THE CUSTODIAN OF PUBLIC RECORDS AT : Procurement Public Records Liaison

  • Notification of Breach / Compliance Reports The Adviser shall notify the Trust immediately upon detection of (i) any material failure to manage any Fund in accordance with its investment objectives and policies or any applicable law; or (ii) any material breach of any of the Funds’ or the Adviser’s policies, guidelines or procedures. In addition, the Adviser shall provide a quarterly report regarding each Fund’s compliance with its investment objectives and policies, applicable law, including, but not limited to the 1940 Act and Subchapter M of the Code, as applicable, and the Fund’s policies, guidelines or procedures as applicable to the Adviser’s obligations under this Agreement. The Adviser agrees to correct any such failure promptly and to take any action that the Board may reasonably request in connection with any such breach. Upon request, the Adviser shall also provide the officers of the Trust with supporting certifications in connection with such certifications of Fund financial statements and disclosure controls pursuant to the Xxxxxxxx-Xxxxx Act. The Adviser will promptly notify the Trust in the event (i) the Adviser is served or otherwise receives notice of any action, suit, proceeding, inquiry or investigation, at law or in equity, before or by any court, public board, or body, involving the affairs of the Trust (excluding class action suits in which a Fund is a member of the plaintiff class by reason of the Fund’s ownership of shares in the defendant) or the compliance by the Adviser with the federal or state securities laws or (ii) an actual change in control of the Adviser resulting in an “assignment” (as defined in the 0000 Xxx) has occurred or is otherwise proposed to occur.

  • Standards Compliance Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

  • COMPLIANCE WITH LICENSING REQUIREMENTS CONTRACTOR shall comply with all necessary licensing requirements and shall obtain appropriate licenses and display the same in a location that is reasonably conspicuous, as well as file copies of same with the County Executive Office.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!