Third Party Computer And Funds Transfer Fraud. Loss occurring during the Policy Period up to the amount specified in the Declaration Pages and within the Territory as specified in the Declaration Pages, resulting directly from:
Third Party Computer And Funds Transfer Fraud Sample Clauses
Related to Third Party Computer And Funds Transfer Fraud
designated Trademark Clearinghouse If there is a conflict between the terms and conditions of this Agreement and the Trademark Clearinghouse Requirements, the terms and conditions of this Agreement shall control.
Certification Regarding Business with Certain Countries and Organizations Pursuant to Subchapter F, Chapter 2252, Texas Government Code, PROVIDER certifies it is not engaged in business with Iran, Sudan, or a foreign terrorist organization. PROVIDER acknowledges this Purchase Order may be terminated if this certification is or becomes inaccurate.
Third Party Data Any statistical, industry-related and market-related data, which are included in the Disclosure Package and the Prospectus, is based on or derived from sources that the Company reasonably and in good faith believes to be reliable and accurate, and such data agrees with the sources from which it is derived, and the Company has obtained the written consent for the use of such data from such sources to the extent required.
Foreign Terrorist Organizations Contractor represents and warrants that it is not engaged in business with Iran, Sudan, or a foreign terrorist organization, as prohibited by Section 2252.152 of the Texas Government Code.
Trademark Clearinghouse 4.1 Notwithstanding the requirements of Section 2.8 of the Agreement, Section 1 of Specification 7 to the Agreement and Section 2 of the Trademark Clearinghouse Rights Protection Mechanism Requirements (the “TMCH Requirements”), Registry Operator is not required to provide a Sunrise Period (as defined in the TMCH Requirements) or, except as set forth herein, otherwise comply with the obligations set forth in Section 2 of the TMCH Requirements (collectively, the “Sunrise Requirements”) so long as the TLD continues to be qualified as a .Brand TLD by ICANN. 4.2 Registry Operator must comply with all other provisions of the TMCH Requirements, including completing the Integration Testing required by Section 1 of the TMCH Requirements and providing the Claims Services required by Section 3 of the TMCH Requirements. Registry Operator will provide ICANN (i) confirmation of completion of Integration Testing and (ii) notice of the start date (the “Claims Commencement Date”) and end date for the Claims Period (as defined in the TMCH Requirements) for the TLD, in each case via the customer services portal at xxxx://xxxxxxx.xxxxxx.xxxxx.xxx/. Registry Operator may not Allocate (as defined in the TMCH Requirements) or register a domain name in the TLD (except for “NIC” and self-‐allocation or registration to itself of domain names pursuant to Section 3.2 of Specification 5) prior to the Claims Commencement Date. 4.3 Registry Operator must comply with the Sunrise Requirements effective as of the Disqualification Date and commence a Sunrise Period within 60 calendar days of the Disqualification Date. If, at the Disqualification Date, the Trademark Clearinghouse or any successor or alternative trademark validation authority appointed by ICANN is not in operation, Registry Operator must implement the Sunrise Requirements through an alternative mechanism developed by Registry Operator that is reasonably acceptable to ICANN. As of the Disqualification Date, Registry Operator may not Allocate or register any additional domain names to third parties prior to the Allocation or registration of all Sunrise Period registrations except as permitted by Section 2.2.4 of the TMCH Requirements. In the event ICANN develops an alternative version of the TMCH Requirements specifically for .Brand TLDs or former .Brand TLDs, Registry Operator agrees to comply with such alternative requirements if such requirements are similar to the TMCH Requirements in effect as of the date hereof as modified by this Specification 13.
Electronic Funds Transfer (EFT) The recipient/cooperator shall designate a financial institution or an authorized payment agent through which a federal payment may be made in accordance with US Treasury Regulations, Money and Finance at 00 XXX 000, which requires that federal payments are to be made by EFT to the maximum extent possible. A waiver may be requested and payments received by check by certifying in writing that one of the following situations apply: 1. The payment recipient does not have an account at a financial institution. 2. EFT creates a financial hardship because direct deposit will cost the payment recipient more than receiving a check. 3. The payment recipient has a physical or mental disability, or a geographic, language, or literacy barrier. In order to receive EFT payments the recipient/cooperator shall register in the System for Award Management (XXX). You may register by going to xxx.xxx.gov and following the instructions provided online. For assistance, contact the XXX User Help by contacting the supporting Federal Service Desk at (000)000-0000 or xxx.xxx.xxx .
OBLIGATIONS AND ACTIVITIES OF CONTRACTOR AS BUSINESS ASSOCIATE 1. CONTRACTOR agrees not to use or further disclose PHI COUNTY discloses to CONTRACTOR other than as permitted or required by this Business Associate Contract or as required by law. 2. XXXXXXXXXX agrees to use appropriate safeguards, as provided for in this Business Associate Contract and the Agreement, to prevent use or disclosure of PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY other than as provided for by this Business Associate Contract. 3. XXXXXXXXXX agrees to comply with the HIPAA Security Rule at Subpart C of 45 CFR Part 164 with respect to electronic PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY. 4. CONTRACTOR agrees to mitigate, to the extent practicable, any harmful effect that is known to CONTRACTOR of a Use or Disclosure of PHI by CONTRACTOR in violation of the requirements of this Business Associate Contract. 5. XXXXXXXXXX agrees to report to COUNTY immediately any Use or Disclosure of PHI not provided for by this Business Associate Contract of which CONTRACTOR becomes aware. CONTRACTOR must report Breaches of Unsecured PHI in accordance with Paragraph E below and as required by 45 CFR § 164.410. 6. CONTRACTOR agrees to ensure that any Subcontractors that create, receive, maintain, or transmit PHI on behalf of CONTRACTOR agree to the same restrictions and conditions that apply through this Business Associate Contract to CONTRACTOR with respect to such information. 7. CONTRACTOR agrees to provide access, within fifteen (15) calendar days of receipt of a written request by COUNTY, to PHI in a Designated Record Set, to COUNTY or, as directed by COUNTY, to an Individual in order to meet the requirements under 45 CFR § 164.524. If CONTRACTOR maintains an Electronic Health Record with PHI, and an individual requests a copy of such information in an electronic format, CONTRACTOR shall provide such information in an electronic format. 8. CONTRACTOR agrees to make any amendment(s) to PHI in a Designated Record Set that COUNTY directs or agrees to pursuant to 45 CFR § 164.526 at the request of COUNTY or an Individual, within thirty (30) calendar days of receipt of said request by COUNTY. XXXXXXXXXX agrees to notify COUNTY in writing no later than ten (10) calendar days after said amendment is completed. 9. CONTRACTOR agrees to make internal practices, books, and records, including policies and procedures, relating to the use and disclosure of PHI received from, or created or received by CONTRACTOR on behalf of, COUNTY available to COUNTY and the Secretary in a time and manner as determined by COUNTY or as designated by the Secretary for purposes of the Secretary determining COUNTY’S compliance with the HIPAA Privacy Rule. 10. CONTRACTOR agrees to document any Disclosures of PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, and to make information related to such Disclosures available as would be required for COUNTY to respond to a request by an Individual for an accounting of Disclosures of PHI in accordance with 45 CFR § 164.528. 11. CONTRACTOR agrees to provide COUNTY or an Individual, as directed by COUNTY, in a time and manner to be determined by COUNTY, that information collected in accordance with the Agreement, in order to permit COUNTY to respond to a request by an Individual for an accounting of Disclosures of PHI in accordance with 45 CFR § 164.528. 12. XXXXXXXXXX agrees that to the extent CONTRACTOR carries out COUNTY’s obligation under the HIPAA Privacy and/or Security rules CONTRACTOR will comply with the requirements of 45 CFR Part 164 that apply to COUNTY in the performance of such obligation. 13. If CONTRACTOR receives Social Security data from COUNTY provided to COUNTY by a state agency, upon request by COUNTY, CONTRACTOR shall provide COUNTY with a list of all employees, subcontractors and agents who have access to the Social Security data, including employees, agents, subcontractors and agents of its subcontractors. 14. CONTRACTOR will notify COUNTY if CONTRACTOR is named as a defendant in a criminal proceeding for a violation of HIPAA. COUNTY may terminate the Agreement, if CONTRACTOR is found guilty of a criminal violation in connection with HIPAA. COUNTY may terminate the Agreement, if a finding or stipulation that CONTRACTOR has violated any standard or requirement of the privacy or security provisions of HIPAA, or other security or privacy laws are made in any administrative or civil proceeding in which CONTRACTOR is a party or has been joined. COUNTY will consider the nature and seriousness of the violation in deciding whether or not to terminate the Agreement.
Permitted Uses and Disclosures of Phi by Business Associate Except as otherwise indicated in this Agreement, Business Associate may use or disclose PHI, inclusive of de-identified data derived from such PHI, only to perform functions, activities or services specified in this Agreement on behalf of DHCS, provided that such use or disclosure would not violate HIPAA or other applicable laws if done by DHCS.
Certain Additional Actions Regarding Intellectual Property If any Event of Default shall have occurred and be continuing, upon the written demand of the Collateral Agent, each Pledgor shall execute and deliver to the Collateral Agent an assignment or assignments of the registered Patents, Trademarks and/or Copyrights and Goodwill and such other documents as are necessary or appropriate to carry out the intent and purposes hereof. Within five (5) Business Days of written notice thereafter from the Collateral Agent, each Pledgor shall make available to the Collateral Agent, to the extent within such Pledgor’s power and authority, such personnel in such Pledgor’s employ on the date of the Event of Default as the Collateral Agent may reasonably designate to permit such Pledgor to continue, directly or indirectly, to produce, advertise and sell the products and services sold by such Pledgor under the registered Patents, Trademarks and/or Copyrights, and such persons shall be available to perform their prior functions on the Collateral Agent’s behalf.
Certification Regarding Prohibition of Certain Terrorist Organizations (Tex Gov. Code 2270) Certification Regarding Prohibition of Boycotting Israel (Tex. Gov. Code 2271) 5 Certification Regarding Prohibition of Contracts with Certain Foreign-Owned Companies (Tex. Gov. 5 Code 2274) 5 Certification Regarding Prohibition of Discrimination Against Firearm and Ammunition Industries (Tex.
