Additional Requirements for Completion of Electronic Commerce Transactions Sample Clauses

Additional Requirements for Completion of Electronic Commerce Transactions. Merchant must notify Bank in writing of its intent to accept Card Transactions over the Internet and obtain Bank approval prior to initiating the Transactions. Xxxxxxxx agrees to comply with the requirements of this Agreement and those requirements of the Payment Networks for each Card Transaction processed over the Internet. The Merchant shall take all steps necessary to ensure all credit Card information received and transmitted via the Internet is encrypted to meet Payment Network Secure Electronic Transaction (SET) standards. Additionally, each Internet Discover Network Card Transaction accepted by Merchant and submitted to Bank shall comply with Discover Network standards, including, without limitation, Discover Network standards governing the formatting, transmission, and encryption of data, referred to as the “designated protocol.” The designated protocol for the encryption of data is Secure Socket Layer (SSL). Merchant must not accept any Internet Card Transactions unless the Transaction is sent by an Internet browser that supports the protocol. Electronic Commerce Merchants must provide Bank with (1) the name of the company that issued their Digital Certificate; (2) their Digital Certificate Number; and (3) the expiration date of their Digital Certificate before engaging in any Internet commerce Transactions. In addition, the Electronic Commerce Indicator must be used to identify electronic commerce Transactions in the authorization request and clearing record. Penalties can be assessed for failure to use the correct Electronic Commerce Indicator. Xxxxxxxx agrees that for Internet Transactions, copies of Transaction records will be delivered to the Cardholder electronically or in paper format. Cardholder account numbers will not be transmitted to Cardholders for Internet purchases. Merchant may not store or maintain the 3-digit CVV2/CVC2/CID value obtained from a Cardholder. As to each Electronic Commerce Transaction, Merchant warrants to Bank that the person whose name is submitted to Bank as Cardholder either made or authorized another to make the purchase. Upon breach of this warranty, Bank may charge back the Transaction to Merchant. If Bank charges back the Transaction to Merchant, Merchant shall pay Bank the amount of the Transaction, any chargeback fee in the attached fee schedule, plus any Payment Network fine or assessment imposed on Bank. Bank may charge all such amounts to the Operating Account without prior notice to Merchant. If Merch...
Sample 1
AutoNDA by SimpleDocs

Related to Additional Requirements for Completion of Electronic Commerce Transactions

  • CONTRACTOR’S SUBMISSION OF CONTRACT MODIFICATIONS In connection with any Contract modification, OGS reserves the right to:  request additional information  reject Contract modifications  remove Products from Contract modification requests  request additional discounts for new or existing Products

  • Change Orders and Contract Amendments 33.1 The Procuring Entity may at any time order the Supplier through notice in accordance GCC Clause 8, to make changes within the general scope of the Contract in any one or more of the following:

  • Additional Requirements for Sleeping Rooms The Contractor shall provide departing Attendees a secured area for storing belongings.

  • Implementation Specifications 1. The accounting shall contain the date, nature, and purpose of such disclosures, and the name and address of the person or agency to whom the disclosure is made.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

  • Forecasting Requirements for Trunk Provisioning Within ninety (90) days of executing this Agreement, Reconex shall provide Verizon a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Local Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the Verizon CLEC Interconnection Trunking Forecast Guide and shall include, at a minimum, Access Carrier Terminal Location (“ACTL”), traffic type (Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Reconex-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).

  • Subsidy Requests and Reporting Requirements 1. The Grantee or Management Company shall complete a CRF Subsidy Request Report - Recap of Tenant Income Certification, which provides a unit-by-unit listing of all units in the Development for whom assistance is being requested and gives detailed information including the occupants’ eligibility, set-aside requirements, amount of household rent paid, utility allowance and amount of CRF Rental Subsidy requested.

  • Specific Order Processes and Requirements 1. Distributor will order Software from SAP using and filling out completely such forms and minimum order requirements as SAP may prescribe from time to time and must comply with any then-current order process for the specific Software product. Where applicable, Distributor agrees to use the electronic means provided by SAP for placing orders.

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

Time is Money Join Law Insider Premium to draft better contracts faster.