Transaction Acceptance Sample Clauses

Transaction Acceptance. The Company will only accept and submit transactions where: (a) the transaction represents a genuine sale of the Company’s goods or services to the Cardholder; (b) the transaction is not materially different than the transactions the Company has described to First Data with regard to the products or services sold, the procedures for payments acceptance, or the fulfilment of obligations to the Cardholder; (c) the transaction complies with all requirements of the applicable Network Rules and Industry Regulations, the laws of all relevant jurisdictions, and all other requirements of this Agreement; (d) the transaction is not a duplicate of any other transaction; (e) the transaction is authorised by the rightful Cardholder for the amount of the transaction in satisfaction of the Cardholder’s obligation to the Company; (f) the transaction is in payment of goods or services provided simultaneously with the payment transaction (except for delayed delivery, advance deposit, or other partial transactions specifically allowed under the Network Rules and Industry Regulations and explicitly authorised by First Data in writing); (g) the transaction is not a refinancing of an existing obligation; (h) the transaction is valid, collectible, and is not subject to any dispute, setoff, or counterclaim; and (i) in the case of a refund, the transaction is submitted to reimburse the Cardholder for a sale transaction that was previously submitted.
View SourceView Similar (10)
Transaction Acceptance. The Company will only accept and submit transactions where: a. The transaction represents a genuine sale of the Company’s goods or services to the Cardholder; b. The transaction is not materially different than the transactions the Company has described to Fiserv with regard to the products or services sold, the procedures for payments acceptance or the fulfilment of obligations to the Cardholder; c. The transaction complies with all requirements of the applicable Network Rules and Industry Regulations, the laws of all relevant jurisdictions, and all other requirements of this Agreement; d. The transaction is not a duplicate of any other transaction; e. The transaction is authorised by the rightful Cardholder for the amount of the transaction in satisfaction of the Cardholder’s obligation to the Company; f. The transaction is in payment of goods or services provided simultaneously with the payment transaction (except for delayed delivery, advance deposit or other partial transactions specifically allowed under the Network Rules and Industry Regulations and explicitly authorised by Fiserv in writing); g. The transaction is not a refinancing of an existing obligation; h. The transaction is valid, collectible and is not subject to any dispute, setoff or counterclaim; and i. In the case of a refund, the transaction is submitted to reimburse the Cardholder for a sale transaction that was previously submitted.
View SourceView Similar (7)
Transaction Acceptance. Company will only accept and submit transactions where: (1) the transaction represents a genuine sale of Company's goods or services to the Cardholder; (2) the transaction is not materially different than the transactions Company has described to First Data with regard to the products or services sold, the procedures for payments acceptance, or the fulfillment of obligations to the Cardholder; (3) the transaction complies with all requirements of the applicable Network Rules, the laws of all relevant jurisdictions, and all other requirements of this Agreement; (4) the transaction is not a duplicate of any other transaction; (5) the transaction is authorized by the rightful Cardholder for the amount of the transaction in satisfaction of the Cardholder's obligations to Company; (6) the transaction is in payment of goods or services provided simultaneously with the payment transaction (except for delayed delivery, advance deposit, or other partial transactions specifically allowed under the Network Rules and explicitly authorized by First Data in writing); (7) the transaction is not a refinancing of an existing obligation; (8) the transaction is valid, collectible, and is not subject to any dispute, setoff, or counterclaim; and (9) in the case of a refund, the transaction is submitted to reimburse the Cardholder for a sale transaction that was previously submitted. Company represents and warrants that each transaction that it submits will comply with this Section.
View SourceView Similar (2)
Transaction Acceptance. The Company or the Agent may, upon notice to the other such party by either email (with receipt confirmed by telephone or appropriate, non-automated email) or telephone (confirmed promptly by e-mail), suspend or terminate the offering of the Shares pursuant to Agency Transactions for any reason; provided, however, that such suspension or termination shall not affect or impair the parties’ respective obligations with respect to the Shares sold hereunder prior to the giving of such notice or their respective obligations under any Terms Agreement. Notwithstanding the foregoing, if the terms of any Agency Transaction contemplate that Shares shall be sold on more than one Purchase Date, then the Company and the Agent shall mutually agree to such additional terms and conditions as they deem reasonably necessary in respect of such multiple Purchase Dates, and such additional terms and conditions shall be set forth in or confirmed by, as the case may be, the relevant Transaction Acceptance and be binding to the same extent as any other terms contained therein.
View Source
Transaction Acceptance. For every transaction listed in the document entitled that is scheduled to be delivered in the set of deliverables being tested: 1. From a workflow perspective, the transaction must work as specified in the detailed workflow specifications (Exhibit 3-A, Task #3, Exhibit 6-C and its accompanying spreadsheet entitled SampleTransactionDetail.xls). 2. From a data-processing perspective, for a set of inputs, whether hand-entered or downloaded from a third-party system, the transaction must process the data as specified in the detailed workflow specifications (Exhibit 3-A, Task #3, Exhibit 6-C and its accompanying spreadsheet entitled SampleTransactionDetail.xls ). For implementing these tests, we propose to: · Use a set of test scenarios that utilize EVERY transaction in the release to test the system from the workflow and data-processing perspectives. · Use a sample of 100 existing insureds extracted from the POINT database, and apply ALL of the transactions associated with these insureds to the pilot implementation to confirm that transactions are functioning as specified.
View Source
Transaction Acceptance. The Merchant will only accept and submit transactions where: a. The transaction represents a genuine sale of the Merchant’s goods or services to the Cardholder; b. The transaction is not materially different than the transactions the Merchant has described to Fiserv with regard to the products or services sold, the procedures for payments acceptance or the fulfilment of obligations to the Cardholder; c. The transaction complies with all requirements of the applicable Network Rules and Industry Regulations, the laws of all relevant jurisdictions, and all other requirements of this Agreement; d. The transaction is not a duplicate of any other transaction; e. The transaction is authorised by the rightful Cardholder for the amount of the transaction in satisfaction of the Cardholder’s obligation to the Merchant; f. The transaction is in payment of goods or services provided simultaneously with the payment transaction (except for delayed delivery, advance deposit or other partial transactions specifically allowed under the Network Rules and Industry Regulations and explicitly authorised by Fiserv in writing); g. The transaction is not a refinancing of an existing obligation; h. The Merchant has conducted proper checks to ensure that there is valid and legal use of the card being used and Merchant has no wilful knowledge of any suspicious, improper or illegal circumstances surrounding the card and the transaction. i. The transaction is valid, collectible and is not subject to any dispute, set-off or counterclaim; and j. In the case of a refund, the transaction is submitted to reimburse the Cardholder for a sale transactionthat was previously submitted.
View Source

Related to Transaction Acceptance

  • Inspection; Acceptance If defective or incorrect material is delivered, Region 4 ESC may make the determination to return the material to the Contractor at no cost to Region 4 ESC. The Contractor agrees to pay all shipping costs for the return shipment. Contractor shall be responsible for arranging the return of the defective or incorrect material.

  • NON-ACCEPTANCE OF SETTLEMENT AGREEMENT If, for any reason whatsoever, this Settlement Agreement is not accepted by the Hearing Panel or an Order in the form attached as Schedule “A” is not made by the Hearing Panel, each of Staff and the Respondent will be entitled to any available proceedings, remedies and challenges, including proceeding to a disciplinary hearing pursuant to sections 20 and 24 of By- law No. 1, unaffected by this Settlement Agreement or the settlement negotiations.

  • CONTRACT ACCEPTANCE By acceptance of this order, ▇▇▇▇▇▇ agrees that the scope of the work required is understood by ▇▇▇▇▇▇; that there are no informal commitments by Buyer that in any way affect the work under this order; that there are no open or unresolved issues related to this order except as explicitly stated herein; and that ▇▇▇▇▇▇ therefore understands and agrees that this order states the complete agreement of the parties. CAS requirements do not apply if the order does not exceed $650,000 or if the Seller claims an exemption per the Proposal Representation and Certification, or if certified cost or pricing data was not provided.

  • Order Acceptance ▇▇▇▇▇▇▇’▇ acceptance of the Order and consequent agreement to the Contract by either: (a) delivering the Goods, Services, or Digital Services; or

  • PRODUCT ACCEPTANCE Unless otherwise provided by mutual agreement of the Authorized User and the Contractor in the Authorized User Agreement, Authorized User(s) shall have sixty (60) days from the date of delivery to accept all Product. Where the Contractor is responsible for installation, acceptance shall be from completion of installation. Title or other property interest and risk of loss shall not pass from Contractor to the Authorized User until the Products have been accepted. Failure to provide notice of acceptance or rejection or a deficiency statement to the Contractor by the end of the period provided for under this clause constitutes acceptance by the Authorized User(s) as of the expiration of that period. The License Term shall be extended by the time periods allowed for trial use, testing and acceptance unless the Commissioner or Authorized User agrees to accept the Product at completion of trial use. Unless otherwise provided by mutual agreement of the Authorized User and the Contractor, Authorized User shall have the option to run testing on the Product prior to acceptance, such tests and data sets to be specified by User. Where using its own data or tests, Authorized User must have the tests or representative set of data available upon delivery. This demonstration will take the form of a documented installation test, capable of observation by the Authorized User, and shall be made part of the Contractor’s standard documentation. The test data shall remain accessible to the Authorized User after completion of the test. In the event that the documented installation test cannot be completed successfully within the specified acceptance period, and the Contractor or Product is responsible for the delay, Authorized User shall have the option to cancel the order in whole or in part, or to extend the testing period for an additional thirty