CARD ACCEPTANCE REQUIREMENTS Sample Clauses

CARD ACCEPTANCE REQUIREMENTS. 5.1 You must: (a) use reasonable care to detect forged or unauthorised signatures or the unauthorised use or forgery of a Card; and (b) notify PayFac if You become aware of or suspect fraud on the part of a Cardholder; and (c) not deliberately reduce the value of any one transaction by: (i) splitting a transaction into two or more transactions; or (ii) allowing a Cardholder to purchase items separately; and (d) establish a fair policy for dealing with refunds and disputes about transactions and include information about that policy on Transaction Receipts as required by PayFac; and (e) only submit a transaction as a refund to a Cardholder if it is a genuine refund of a previous sale transaction. The refund must be processed to the same card that was used in the original sales transaction and be for the original sale amount; and (f) give refunds for transactions by means of credit and not in cash or cheque; and (g) not process a refund transaction as a way of transferring funds between Your accounts; and (h) if a transaction for a sale does not cover the full amount of the sale: (i) in the situation in which the Card is used to make a deposit or pay an instalment You may accept the Card in payment of all or part of the outstanding balance; and (ii) in any other circumstance You must obtain the balance due at the time the sale is completed in cash; and (i) not state or set a minimum or maximum amount for a Card transaction without our prior written consent; and (j) not ask a Cardholder to reveal their PIN or any other secret identifier; and (k) contact PayFac for instructions if the identification of a Cardholder or the validity of the Card is uncertain; and (l) not knowingly submit for processing any transaction that is illegal or that You should have known is illegal. 5.2 For remote transactions, you must: (a) take reasonable steps to verify the identity of the Person You are dealing with, in order to confirm that they are the genuine Cardholder; and (b) record reasonable identification details of the Person You are dealing with, as well as the commencement and expiry dates of the Card.
Sample 1Sample 2See All (7)
CARD ACCEPTANCE REQUIREMENTS. 5.1 You must: (a) use reasonable care to detect forged or unauthorised signatures or the unauthorised use orforgery of a Card; and (b) notify Latipay if You become aware of or suspect fraud on the part of a Cardholder; and (c) not deliberately reduce the value of any one transaction by: (i) splitting a transaction into two or more transactions; or (ii) allowing a Cardholder to purchase items separately; and (d) establish a fair policy for dealing with refunds and disputes about transactions and includeinformation about that policy on Transaction Receipts as required by Latipay; and (e) only submit a transaction as a refund to a Cardholder if it is a genuine refund of a previous sale transaction. The refund must be processed to the same card that was used in the original sales transaction and be for the original sale amount; and (f) give refunds for transactions by means of credit and not in cash or cheque; and (g) not process a refund transaction as a way of transferring funds between Your accounts; and (h) if a transaction for a sale does not cover the full amount of the sale: (i) in the situation in which the Card is used to make a deposit or pay an instalment You may accept the Card in payment of all or part of the outstanding balance; and (ii) in any other circumstance You must obtain the balance due at the time the sale is completed in cash; and (iii) not state or set a minimum or maximum amount for a Card transaction without our prior written consent; and
Sample 1Sample 2
CARD ACCEPTANCE REQUIREMENTS. You must:
Sample 1Sample 2
CARD ACCEPTANCE REQUIREMENTS. 4.1 You must: (a) use reasonable care to detect forged or unauthorised signatures or the unauthorised use or forgery of a Card; and (b) notify PayFac if You become aware of or suspect fraud on the part of a Cardholder; and (c) not deliberately reduce the value of any one transaction by: (i) splitting a transaction into two or more transactions; or
Sample 1
CARD ACCEPTANCE REQUIREMENTS. Licensee and its Affiliates shall, at all times during the Initial Term and any Renewal Term (as applicable) accept payment products issued by Licensor or any of its Affiliates as a form of payment for goods or services offered by Licensee and any of its Affiliates. Additionally, Licensee and its Affiliates shall not apply a [***] for payment with any payment product issued by Licensor or any of its Affiliates, except as otherwise specified in agreements governing Licensee’s and its Affiliates’ acceptance of the payment products issued by Licensor or any of its Affiliates.
Sample 1

Related to CARD ACCEPTANCE REQUIREMENTS

  • 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.

  • Support Requirements If there is a dispute between the awarded vendor and TIPS Member, TIPS or its representatives may assist, at TIPS sole discretion, in conflict resolution or third party (mandatory mediation), if requested by either party. TIPS, or its representatives, reserves the right to inspect any project and audit the awarded vendors TIPS project files, documentation and correspondence. TIPS Members stand in the place of TIPS as related to this agreement and have the same access to the proposal information and all related documents. TIPS Members have all the same rights under the awarded Agreement as TIPS.

  • Minimum Customer Support Requirements for TIPS Sales Vendor shall provide timely and commercially reasonable support for TIPS Sales or as agreed to in the applicable Supplemental Agreement.

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • Maintenance Requirements The Contractor shall ensure and procure that at all times during the Maintenance Period, the Project Highway conforms to the maintenance requirements set forth in Schedule-E (the “Maintenance Requirements”).

  • Match Requirements There is no match required on the part of the Grantee under this Agreement.

  • Service Level Agreement 6.1 NCR Voyix will use commercially reasonable efforts to make the Service available to you at or above the Availability Rate set forth at xxxxx://xxx.xxx.xxx/support/aloha-sla. If NCR Voyix does not meet the Availability Rate, you are entitled to request a service-level credit subject to the terms of this Agreement. This credit is calculated as a percentage of the monthly recurring bill (or monthly pro rata share of billing, if billing does not occur monthly) for the Service for the month in which the Availability Rate was not met. The Availability Rate is determined by: (a) dividing the total number of valid outage minutes in a calendar month by the total number of minutes in that month; (b) subtracting that quotient from 1.00; (c) multiplying that difference by 100; and (d) rounding that result to two decimal places in accordance with standard rounding conventions. The number of outage minutes per day for a given service is determined by the lesser of the number of outage minutes. 6.2 Unavailability due to other conditions or caused by factors outside of NCR Voyix’s reasonable control will not be included in the calculation of the Availability Rate. Further, the following are expressly excluded from the calculation of the Availability Rate: (a) service unavailability affecting services or application program interfaces that are not used by you; (b) cases where fail-over to another data center is available but not utilized; (c) transient time-outs, required re-tries, or slower-than-normal response caused by factors outside of NCR Voyix’s reasonable control; (d) Scheduled Downtime, including maintenance and upgrades; (e) force majeure; (f) transmission or communications outages outside the NCR Voyix- controlled environment; (g) store-level down-time caused by factors outside of NCR Voyix’s reasonable control; (h) outages attributable to services, hardware, or software not provided by NCR Voyix, including, but not limited to, issues resulting from inadequate bandwidth or related to third-party software or services; (i) use of the Service in a manner inconsistent with the documentation for the application program interface or the NCR Voyix Product; (j) your Point of Sale (“POS”) failure or the failure to properly maintain the POS environment, including updating the POS firmware or version of the software running on the POS as recommended by either NCR Voyix, a third-party POS reseller or servicer; and (k) issues related to third party domain name system (“DNS”) errors or failures. 6.3 To obtain a service-level credit, you must submit a claim by contacting NCR Voyix through the website at xxxxx://xxx.xxx.xxx/support/aloha-sla Your failure to provide the claim and other information will disqualify you from receiving a credit. NCR Voyix must receive claims within 60 days from the last day of the impacted month. After that date, claims are considered waived and will be refused. You must be in compliance with the Agreement in order to be eligible for a service-level credit. You may not unilaterally offset for any performance or availability issues any amount owed to NCR Voyix. If multiple Services experience an outage in a given month, the total credit for that month will be the highest credit allowed for any single Service which failed; there is no stacking of credits. 6.4 The remedies set forth in the Section are your sole and exclusive remedies for performance or availability issues affecting the Services, including any failure by NCR Voyix to achieve the Availability Rate.

  • Vehicle Requirements The following shall be considered minimum Vehicle requirements. The Authorized User shall include supplemental required specifications for Vehicles specified in a Mini-Bid. Unless otherwise indicated, all items specified which are listed on the OEM Pricelist as standard or optional equipment shall be factory installed and operative. Vehicles delivered to an Authorized User in a condition considered to be below retail customer acceptance levels will not be accepted. Items which determine this acceptance level shall include, but not be limited to, the general appearance of the interior and exterior of the vehicle for completeness and quality of workmanship, lubrication and fluid levels, with any leaks corrected, mechanical operation of the vehicle and all electrical components operational. Product specified to be furnished and installed which is not available through the OEM shall conform to the standards known to that particular industry, both product and installation.

  • Licensing Requirements (a) Employer and Employee hereby covenant and agree that this Agreement and/or Employee’s employment may be subject to the approval of one or more gaming regulatory authorities (the “Authorities”) pursuant to the provisions of the relevant gaming regulatory statutes (the “Gaming Acts”) and the regulations promulgated thereunder (the “Gaming Regulations”). Employer and Employee hereby covenant and agree to use their best efforts to obtain any and all approvals required by the Gaming Acts and/or Gaming Regulations. In the event that (i) an approval of this Agreement or Employee’s employment by the Authorities is required for Employee to carry out Employee’s duties and responsibilities set forth in Section 3 of this Agreement, (ii) Employer and Employee have used their best efforts to obtain such approval, and (iii) this Agreement or Employee’s employment is not so approved by the Authorities, then this Agreement shall immediately terminate and shall be null and void, thus extinguishing any and all obligations of either party, subject to any surviving obligations of Employee under Sections 9, 10 and 21. (b) If applicable, Employer and Employee hereby covenant and agree that, in order for Employee to discharge the duties required under this Agreement, Employee must apply for or hold a license, registration, permit or other approval (the “License”) as issued by the Authorities pursuant to the terms of the relevant Gaming Act and as otherwise required by this Agreement. In the event Employee fails to apply for and secure, or the Authorities refuse to issue or renew Employee’s License, Employee, at Employer’s sole cost and expense, shall promptly defend such action and shall take such reasonable steps as may be required to either remove the objections or secure or reinstate the Authorities’ approval, respectively. The foregoing notwithstanding, if the source of the objections or the Authorities’ refusal to renew or maintain Employee’s License arise as a result of any of the acts, omissions or events described in Section 1(c) of this Agreement, then Employer’s obligations under this Section 8 also shall not be operative and Employee shall promptly reimburse Employer upon demand for any expenses incurred by Employer pursuant to this Section 8. (c) Employer and Employee hereby covenant and agree that the provisions of this Section 8 shall apply in the event Employee’s duties require that Employee also be licensed by governmental agencies other than the Authorities.

  • License Requirements The Hotel’s alcoholic beverage license requires that the Hotel shall: (i) request proper identification (photo ID) of any person of questionable age and refuse alcoholic beverage service if the person is either under age or proper identification cannot be produced, and (ii) refuse alcoholic beverage service to any person who, in the Hotel’s judgment, appears to be intoxicated; and (iii) instruct its personnel to avoid encouraging patrons to consume alcoholic beverages (commonly referred to as “over-pouring”).