WEB Entries Sample Clauses

WEB Entries. You can submit ACH Orders for internet-initiated/mobile entries (“WEB Entries”). You may initiate single or recurring WEB entries only to consumer accounts. A WEB Entry must be based on (i) an authorization that is communicated (but not by oral communication) by the Receiver to you via the Internet or a Wireless Network; or (ii) any form of authorization otherwise permissible under the Rules if the Receiver’s instruction to initiate the individual debit entry is designed by you to be communicated (but not by oral communication) to you via a Wireless Network. You agree to submit such entries in accordance with the technical specifications and formatting requirements set forth in the Rules and as directed by us from time to time. You may not use the WEB Standard Entry Class (SEC) Code in connection with authorizations obtained from customers by mail or verbal telephone communication. The WEB SEC code may not be used to initiate credit entries except for reversals of WEB debit entries.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
WEB Entries. If Bank authorizes Client to use the Origination Services to originate WEB Entries, then: (i) Client will take all actions and obtain all consents and authorizations required under the NACHA Rules to allow Bank to meet its obligations as ODFI of WEB Entries, and you agree to retain the originals of such consents and authorizations for at least two (2) years after expiration, revocation, or termination thereof, or such other timeframe required by the NACHA Rules or Applicable Law; (ii) Client agrees it has performed or will perform an annual audit that satisfies the NACHA Rules before initiating a WEB Entry; and (iii) Pursuant to the NACHA Rules, Client will establish and implement commercially reasonable: (A) fraudulent transaction detection systems to screen debit WEB Entries; (B) methods of authentication to verify the identity of Receivers of debit WEB Entries; (C) procedures to verify that the routing number used in the debit WEB Entry is valid; and (D) security technology for communications between Client and Receivers over the internet or wireless networks. (iv) Each time Client initiates a WEB Entry, in addition to its other representations and warranties under this Agreement, Client warrants that the WEB Entry was screened by its fraudulent transaction detection system and that Client has used commercially reasonable methods to authenticate and verify the Receiver’s identity and to verify that the account number used in the WEB Entry is valid.
Sample 1Sample 2
WEB Entries. If Bank authorizes Client to use the Origination Services to originate WEB Entries, then: (i) Client will take all actions and obtain all consents and authorizations required under the NACHA Rules to allow Bank to meet its obligations as ODFI of WEB Entries, and you
Sample 1

Related to WEB Entries

  • Trademark Clearinghouse 4.1 Notwithstanding the requirements of Section 2.8 of the Agreement, Section 1 of Specification 7 to the Agreement and Section 2 of the Trademark Clearinghouse Rights Protection Mechanism Requirements (the “TMCH Requirements”), Registry Operator is not required to provide a Sunrise Period (as defined in the TMCH Requirements) or, except as set forth herein, otherwise comply with the obligations set forth in Section 2 of the TMCH Requirements (collectively, the “Sunrise Requirements”) so long as the TLD continues to be qualified as a .Brand TLD by ICANN. 4.2 Registry Operator must comply with all other provisions of the TMCH Requirements, including completing the Integration Testing required by Section 1 of the TMCH Requirements and providing the Claims Services required by Section 3 of the TMCH Requirements. Registry Operator will provide ICANN (i) confirmation of completion of Integration Testing and (ii) notice of the start date (the “Claims Commencement Date”) and end date for the Claims Period (as defined in the TMCH Requirements) for the TLD, in each case via the customer services portal at xxxx://xxxxxxx.xxxxxx.xxxxx.xxx/. Registry Operator may not Allocate (as defined in the TMCH Requirements) or register a domain name in the TLD (except for “NIC” and self-­‐allocation or registration to itself of domain names pursuant to Section 3.2 of Specification 5) prior to the Claims Commencement Date. 4.3 Registry Operator must comply with the Sunrise Requirements effective as of the Disqualification Date and commence a Sunrise Period within 60 calendar days of the Disqualification Date. If, at the Disqualification Date, the Trademark Clearinghouse or any successor or alternative trademark validation authority appointed by ICANN is not in operation, Registry Operator must implement the Sunrise Requirements through an alternative mechanism developed by Registry Operator that is reasonably acceptable to ICANN. As of the Disqualification Date, Registry Operator may not Allocate or register any additional domain names to third parties prior to the Allocation or registration of all Sunrise Period registrations except as permitted by Section 2.2.4 of the TMCH Requirements. In the event ICANN develops an alternative version of the TMCH Requirements specifically for .Brand TLDs or former .Brand TLDs, Registry Operator agrees to comply with such alternative requirements if such requirements are similar to the TMCH Requirements in effect as of the date hereof as modified by this Specification 13.

  • Company’s Accounting System The Company maintains a system of accounting controls sufficient to provide reasonable assurances that (i) transactions are executed in accordance with management's general or specific authorization; (ii) transactions are recorded as necessary to permit preparation of financial statements in conformity with generally accepted accounting principles and to maintain accountability for assets; (iii) access to assets is permitted only in accordance with management's general or specific authorization; and (iv) the recorded accountability for assets is compared with existing assets at reasonable intervals and appropriate action is taken with respect to any differences.

  • Books and Records (a) Maintain proper books of record and account, in which full, true and correct entries in conformity with GAAP consistently applied shall be made of all financial transactions and matters involving the assets and business of the Borrower or such Subsidiary, as the case may be; and (b) maintain such books of record and account in material conformity with all applicable requirements of any Governmental Authority having regulatory jurisdiction over the Borrower or such Subsidiary, as the case may be.

  • Records The Administrator shall maintain appropriate books of account and records relating to services performed hereunder, which books of account and records shall be accessible for inspection upon reasonable written request by the Issuer, the Seller and the Indenture Trustee at any time during normal business hours.

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