Specific Entry Types Sample Clauses

Specific Entry Types. The Rules contain special requirements and impose additional obligations on EVO when it acts as ODFI with respect to certain Entry types. As a result, EVO must obtain additional agreements and representations from ACH Merchant with respect to those Entry types, as such, ACH Merchant agrees to the following with regard to EVO’s Approved SEC Codes: a) PPD Credit Entries - Direct Deposit i) Transmittal of Entries by XXX Xxxxxxxx. ACH Merchant shall transmit PPD credit Entries to EVO in compliance with the formatting and other requirements set forth in this Agreement. ii) Exposure Limits. The total dollar amount of Entries transmitted, frequency of origination and payment application (debits or credits) originated by ACH Merchant to EVO shall comply with exposure limits as approved by EVO, in its sole discretion, on the Application, which may be amended from time to time. iii) Authorization. XXX Xxxxxxxx will obtain Authorization for PPD credit Entries in accordance with the Rules and U.S. law. (1) Consumer Credit Entries are not required to be in writing. (a) However, if XXX Xxxxxxxx obtains a written authorization for a PPD Credit, XXX Xxxxxxxx will retain a record of the Authorization for a period of two (2) years from the termination or revocation of the Authorization. ACH Merchant shall, upon request within no more than five (5) business days, provide EVO an original or copy of the Receiver’s Authorization for PPD Entries. iv) Prenotifications. Merchant may not send prenotifications prior to initiating the first Entry to a Receiver’s account. EVO_ACH ADDENDUM_1021 b) PPD Debit Entries - Direct Payment i) Transmittal of Entries by XXX Xxxxxxxx. ACH Merchant shall transmit PPD debit Entries to EVO in compliance with the formatting and other requirements set forth in this Agreement. ii) Exposure Limits. The total dollar amount of Entries transmitted, frequency of origination and payment application (debits or credits) originated by ACH Merchant to EVO shall comply with the exposure limits as approved by EVO, in its sole discretion, on the Application, which may be amended from time to time. iii) Authorization. XXX Xxxxxxxx will obtain Authorization for PPD Debit Entries in accordance with the Rules and U.S. law. (1) PPD Debit Entries must be authorized in writing and signed or similarly authenticated by the Receiver.
Sample 1
AutoNDA by SimpleDocs

Related to Specific Entry Types

  • Country-Specific Provisions Argentina

  • License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license. (b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. (e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.

  • License Type Your license to a Product will be under a Named User or CPU license type, as specified on an order. Each Named User license to a Product entitles a Named User to access and use that Product in one production environment and up to two non-production environments. Each CPU license to a Product entitles you to assign the Product to a single CPU in one production environment and up to two non-production environments, for use in support of an unspecified number of Named Users.

  • Specific Conditions If applicable, specific conditions required after a risk assessment will be included in Exhibit G. Grantee shall adhere to the specific conditions listed therein.

  • Specific Provisions 4.1 Unless the CERT otherwise agrees, based on exceptional circumstance and sufficient justification, Implementing Agreements shall be for an initial term of up to, but no more than, five years. 4.2 An Implementing Agreement may be extended for such additional periods as may be determined by its Executive Committee, subject to approval of the CERT. Any single extension period shall not be greater than five years unless the CERT otherwise decides, based on exceptional circumstances and sufficient justification. 4.3 Notwithstanding Paragraph 4.2, should the duration of the programme of work of an Annex exceed the term of the Implementing Agreement to which it relates, the CERT shall not unreasonably withhold approval to extend the Implementing Agreement for such additional period to permit the conclusion of the work then being conducted under the Annex. 4.4 Either the Contracting Parties or the Executive Committee of each Implementing Agreement shall: 4.4.1 approve the programme activities and the annual programme of work and budget for the relevant Implementing Agreement; 4.4.2 establish the terms of the contribution for scientific and technical information, know-how and studies, manpower, capital investment or other forms of financing to be provided by each participant in the Implementing Agreement; 4.4.3 establish the necessary provisions on information and intellectual property and ensure the protection of IEA copyrights, logos and other intellectual property rights as established by the IEA; 4.4.4 assign the responsibility for the operational management of the programme or project to an entity accountable to the Executive Committee of the relevant Implementing Agreement; 4.4.5 establish the initial term of the Implementing Agreement and its Annexes; 4.4.6 approve amendments to the text of the Implementing Agreement and Annexes; and 4.4.7 invite a representative of the IEA Secretariat to its Executive Committee meetings in an advisory capacity and, sufficiently in advance of the meeting, provide the Secretariat with all documentation made available to the Executive Committee members for purposes of the meeting.

  • Trunk Types 2.2.1 In interconnecting their networks pursuant to this Attachment, the Parties will use, as appropriate, the following separate and distinct trunk groups: 2.2.1.1 Interconnection Trunks for the transmission and routing of Reciprocal Compensation Traffic, translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic, and IntraLATA Toll Traffic, between their respective Telephone Exchange Service Customers, Tandem Transit Traffic, and, Measured Internet Traffic, all in accordance with Sections 5 through 8 of this Attachment; 2.2.1.2 Access Toll Connecting Trunks for the transmission and routing of Exchange Access traffic, including translated InterLATA toll free service access code (e.g., 800/888/877) traffic, between Ymax Telephone Exchange Service Customers and purchasers of Switched Exchange Access Service via a Verizon access Tandem in accordance with Sections 9 through 11 of this Attachment; and 2.2.1.3 Miscellaneous Trunk Groups as mutually agreed to by the Parties, including, but not limited to: (a) choke trunks for traffic congestion and testing; and, (b) untranslated IntraLATA/InterLATA toll free service access code (e.g. 800/888/877) traffic. 2.2.2 Other types of trunk groups may be used by the Parties as provided in other Attachments to this Agreement (e.g., 911/E911 Trunks) or in other separate agreements between the Parties (e.g., directory assistance trunks, operator services trunks, BLV/BLVI trunks or trunks for 500/555 traffic). 2.2.3 In accordance with the terms of this Agreement, the Parties will deploy One-Way Interconnection Trunks (trunks with traffic going in one direction, including one-way trunks and uni-directional two-way trunks) and/or Two-Way Interconnection Trunks (trunks with traffic going in both directions). 2.2.4 Ymax shall establish, at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA, separate Interconnection Trunk group(s) between such POI(s) and each Verizon Tandem in a LATA with a subtending End Office(s) to which Ymax originates calls for Verizon to terminate. 2.2.5 In the event the volume of traffic between a Verizon End Office and a technically feasible Point of Interconnection on Verizon’s network in a LATA, which is carried by a Final Tandem Interconnection Trunk group, exceeds (a) the Centium Call Seconds (Hundred Call Seconds) busy hour equivalent of one (1) DS1 at any time; (b) 200,000 minutes of use for a single month; and/or; (c) 600 busy hour Centium Call Seconds (BHCCS) of use for a single month: (i) if One-Way Interconnection Trunks are used, the originating Party shall promptly establish new or augment existing End Office One-Way Interconnection Trunk groups between the Verizon End Office and the technically feasible Point of Interconnection on Verizon’s network; or,

  • Preparatory Contract Negotiations Meetings Where operational requirements permit, the Employer will grant leave without pay to an employee to attend preparatory contract negotiations meetings.

  • Country Specific Terms Appendix A contains additional terms and conditions of the Agreement applicable to Participants residing in those countries. In addition, Appendix A also contains information and notices of exchange control and certain other issues of which the Participant should be aware.

  • State Specific Provisions N/A. ATTACHED EXHIBIT. The Exhibit noted below, if marked with an "X" in the space provided, is attached to this Note: X Exhibit A Modifications to Multifamily Note

  • Specific Requirements compensation insurance with statutory limits required by South Dakota law. Coverage B-Employer’s Liability coverage of not less than $500,000 each accident, $500,000 disease-policy limit, and $500,000 disease-each employee.

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