Submitting Transactions Clause Samples
Submitting Transactions. The Company is responsible for:
(a) properly transmitting the transaction data (including all transaction detail required by the Networks) to First Data’s systems using the format and specifications provided by First Data (the Company will maintain and update the systems that it uses to accommodate changing Network requirements and industry requirements as specified by First Data);
(b) all payment transactions submitted for processing under its merchant identification numbers (MIDs), including, without limitation, all returns, refunds, or chargebacks, whether charged back by Cardholders or Card issuers;
(c) preventing its employees and others from submitting returns or refunds that do not reflect valid returns or refunds corresponding to prior transactions; and
(d) retaining transaction records according to the timelines required by the Network Rules, Industry Regulations or applicable Laws.
Submitting Transactions. 3.1. You must comply with the System Instructions including any Certification and Test Bed Processes, and any appropriate Policy in force at the relevant time, including for the avoidance of doubt the Acceptable Use Policies, and the System Instructions. (These Policies and System Instructions will change over time as our systems develop and you must regularly check which are the most recent versions and comply with them).
3.2. You must not request a Transaction if any of the following apply or you have reason to believe that they apply:
3.2.1. you know, or reasonably should know, that some or all of the information provided by or through you to us is false, deceptive, misleading, inaccurate or incomplete;
3.2.2. some or all of the Registrant identity information does not meet the requirements of the System Instructions;
3.2.3. the Registrant you identify to us in the Transaction has not instructed or requested you (directly or indirectly) to act on its behalf or does not exist;
3.2.4. the System Instructions or Policies prohibit making that Transaction on behalf of the Registrant;
3.2.5. you no longer have authority to Transact with us on behalf of the Registrant;
3.2.6. the service requested is one for which we require Registrants to enter into terms and conditions with us (e.g. the registration or renewal of a domain name) and you have not received positive confirmation that they are aware of, and accept in full, the current terms and conditions we offer for that service or Transaction at the date of the request for it;
3.2.7. your Tag Classification or contract status (e.g. you are in Special Status) does not entitle you to submit such a Transaction; or
3.2.8. you are aware that the Transaction is criminal in nature or is likely to further criminal activity.
3.3. Unless clauses 2.3 (limits on your authority) or 3.2 (Transactions you must not request) apply or the System Instructions require otherwise: you must request the relevant Transaction (as set out in the System Instructions) promptly if:
3.3.1. the Service Level Requirements mandate it;
3.3.2. Your Customer provides you with a name or contact information which is different from those recorded on the Register, whether or not Your Customer asks you to update the Register;
3.3.3. you are aware that there is duplicate information on the Register in relation to Your Customer that can be amalgamated or improved; or
3.3.4. we inform you that the Transaction is required (for example, we tell you that th...
Submitting Transactions. 4.1. Each Transaction. Each transaction submitted for processing must include a Sales Draft or Credit Draft and a receipt or copy of the Draft that is provided to the Cardholder at the time the Card transaction is completed. Failure to provide this documentation may result in fines or termination of this Agreement.
Submitting Transactions. You will only submit Transactions for processing that meet the following requirements;
i. the Transaction represents a genuine sale of your goods or services to the customer;
ii. the Transaction is not materially different than the transactions described in your application for services;
iii. the Transaction complies with all requirements of the applicable Network Rules, applicable Laws, and all other requirements of this Agreement;
iv. the Transaction is not a duplicate of any other Transaction;
v. the Transaction is authorized by the customer for the amount of the transaction in satisfaction of the customer’s obligations to you;
vi. 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 authorized by us in writing);
vii. the Transaction is not a refinancing of an existing obligation;
viii. the Transaction is valid, collectible, and is not subject to any dispute, setoff, or counterclaim; and
ix. in the case of a refund, the Transaction is submitted to reimburse the customer for a sale transaction that was previously submitted.
Submitting Transactions. The Company is responsible for:
2.9.1 properly transmitting the transaction data (including all transaction detail required by the Networks) to First Data’s systems using the format and specifications provided by First Data (the Company will maintain and update the systems that it uses to accommodate changing Network requirements as specified by First Data);
2.9.2 all payment transactions submitted for processing under its merchant identification numbers (MIDs), including, without limitation, all returns, refunds, or chargebacks, whether charged back by Cardholders or Card issuers;
2.9.3 preventing its employees, agents, and others from submitting returns or refunds that do not reflect valid returns or refunds corresponding to prior transactions;
2.9.4 retaining transaction records according to the timelines required by the Network Rules or applicable Laws; and
2.9.5 maintaining transaction fraud and chargeback rates below thresholds established by the Networks.