Payment Card Acceptance Policies and Prohibitions. Merchant must Sample Clauses

Payment Card Acceptance Policies and Prohibitions. Merchant must. (a) notify Chase Paymentech, on its Application or otherwise in writing, of all of Merchant’s Payment Card acceptance methods (e.g. card-present, card-not-present, recurring transactions, etc.); (b) accept all categories of Visa and MasterCard Payment Cards, unless Xxxxxxxx has notified Chase Paymentech on its Application or otherwise in writing of Merchant’s election to accept one of the following “limited acceptance” options: i. Visa and MasterCard consumer credit (but not debit) cards and Visa and MasterCard commercial credit and debit cards only; or ii. Visa and MasterCard debit cards only; (c) honor all foreign bank-issued Visa or MasterCard Payment Cards; (d) publicly display appropriate signage to indicate all Payment Cards accepted by Merchant, including any limited acceptance categories; (e) examine each Payment Card (credit, debit, etc.) presented at the point of sale to ensure the Payment Card is valid, has not expired and that the Customer’s signature on the Transaction Receipt corresponds to the authorized signature on the back of the Payment Card; (f) in situations where the Payment Card is not physically presented to Merchant at the point of sale (e.g. on-line, mail order, telephone order, pre- authorized, or recurring transactions), have appropriate procedures in place to ensure that each Transaction is made only to the Customer; and (g) provide the Customer with a Transaction Receipt for each Transaction. All Transaction Receipts must conform to Payment Brand Rules. Except to the extent permitted by law or the Payment Brand Rules, Merchant must not: (h) engage in any practice that unfavorably discriminates against or provides unequal treatment of any Payment Brand relative to any other Payment Brand; (i) set a dollar amount above or below which Xxxxxxxx refuses to honor otherwise valid Payment Cards; (j) issue a Refund in cash or a cash equivalent (e.g. checks) for any Transaction originally conducted using a Payment Card; (k) request or use a Payment Card account number for any purpose other than to process a payment for goods or services sold; or (l) add any tax or surcharge to a Transaction; if any tax or surcharge amount is permitted, such amount shall be included in the Transaction amount and shall not be collected separately.
Sample 1
AutoNDA by SimpleDocs

Related to Payment Card Acceptance Policies and Prohibitions. Merchant must

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Customer Agreement I certify that the information provided in this application is true and complete and declare that the Firm may rely upon such information until it receives written notice of any changes. I acknowledge that the intended use of my account is for investing or savings purposes unless notified otherwise.

  • End User Agreement This publication is distributed under the terms of Article 25fa of the Dutch Copyright Act. This article entitles the maker of a short scientific work funded either wholly or partially by Dutch public funds to make that work publicly available for no consideration following a reasonable period of time after the work was first published, provided that clear reference is made to the source of the first publication of the work. Research outputs of researchers employed by Dutch Universities that comply with the legal requirements of Article 25fa of the Dutch Copyright Act, are distributed online and free of cost or other barriers in institutional repositories. Research outputs are distributed six months after their first online publication in the original published version and with proper attribution to the source of the original publication. You are permitted to download and use the publication for personal purposes. All rights remain with the author(s) and/or copyrights owner(s) of this work. Any use of the publication other than authorised under this licence or copyright law is prohibited. If you believe that digital publication of certain material infringes any of your rights or (privacy) interests, please let the University Library know, stating your reasons. In case of a legitimate complaint, the University Library will, as a precaution, make the material inaccessible and/or remove it from the website. Please contact the University Library through email: xxxxxxxxx@xxx.xx.xx. You will be contacted as soon as possible. University Library Radboud University

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

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

  • END USER AGREEMENTS (“EUA GAC acknowledges that the END USER may choose to enter into an End User Agreement (“EUA) with the Contractor through this Agreement, and that the term of the EUA may exceed the term of the current H-GAC Agreement. H-GAC’s acknowledgement is not an endorsement or approval of the End User Agreement’s terms and conditions. Contractor agrees not to offer, agree to or accept from the END USER, any terms or conditions that conflict with those in Contractor’s Agreement with H-GAC. Contractor affirms that termination of its Agreement with H-GAC for any reason shall not result in the termination of any underlying EUA, which shall in each instance, continue pursuant to the EUA’s stated terms and duration. Pursuant to the terms of this Agreement, termination of this Agreement will disallow the Contractor from entering into any new EUA with END USERS. Applicable H-GAC order processing charges will be due and payable to H-GAC

  • Unbundled Voice Loops (UVLs) 2.2.1 BellSouth shall make available the following UVLs:

  • Service Level Agreements If a Service or a Plan includes a Service Level Agreement (SLA): (a) we are liable for any remedy or rebate specified by the SLA; and (b) subject to clauses 40 to 42, and to the express terms of the SLA, our liability for breach of the SLA is limited to such remedy or rebate.

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

  • Program Location A. Unless otherwise agreed upon in writing, the parties acknowledge and agree that the Work of this Agreement will be performed at the following Property address: Ktr Address1 Address2

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