Explicit User Confirmation Sample Clauses

Explicit User Confirmation. Paymentus shall confirm the dollar amount of all Payments to be charged to a Card and electronically obtain the User approval of such charges prior to initiating Card authorizations transaction. Paymentus will provide User with electronic confirmation of all transactions.
AutoNDA by SimpleDocs
Explicit User Confirmation. First Billing shall confirm the dollar amount of all Payments and electronically obtain User approval of such charges prior to initiating Card or other authorizing transactions. First Billing will provide User with electronic confirmation of all transactions.
Explicit User Confirmation. Web - Nexcheck shall confirm the dollar amount of all Payments to be charged to a Card or checking account and electronically obtain the User approval of such charges prior to initiating transaction. Telephone - Nexcheck shall confirm the dollar amount of all Payments and the corresponding Nexcheck Service fees to be charged to a Card or checking account and electronically obtain the User approval of such charges prior to initiating transaction. Processing Terms and Conditions- Customer is required to meet if applicable a $75 monthly minimum after 60 days, once customer is actively processing the services selected.

Related to Explicit User Confirmation

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • END USER AGREEMENTS (“EUA H-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

  • DATA/ACCESS/CONFIDENTIALITY/ PRESERVATION 10.1 As used in this Agreement, the word “data” shall mean all information and things developed or obtained during the performance of, or acquired or developed by reason of, this Agreement, including, but not limited to, all studies, reports, files, formulae, surveys, maps, charts, sound recordings, video recordings, pictorial reproductions, drawings, analyses, graphic representations, computer programs, computer printouts, notes, letters, memoranda, papers, and documents, all whether finished or unfinished.

  • Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.

  • Unauthorized Access Notification LEA shall notify Provider promptly of any known or suspected unauthorized access. LEA will assist Provider in any efforts by Provider to investigate and respond to any unauthorized access.

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