Commercial Transaction Refund Fee Sample Clauses

Commercial Transaction Refund Fee. If you refund a Commercial Transaction payment, PayPal will retain the Fixed Fee portion of the Commercial Transaction Fee. The Buyer’s PayPal Account will be credited with the full Commercial Transaction payment amount. Your PayPal Account will be charged with the amount initially credited to your PayPal Account in connection with the Commercial Transaction payment and the Fixed Fee portion of the Commercial Transaction Fee.
AutoNDA by SimpleDocs
Commercial Transaction Refund Fee. If you refund a Commercial Transaction payment, there are no fees to make the refund, but the fees you originally paid to receive the payment are not returned to you.

Related to Commercial Transaction Refund Fee

  • Commercial Transaction Refunds If you refund a Commercial Transaction payment, there are no fees to make the refund, but the fees you originally paid to receive the payment are not returned to you.

  • Commercial Price List Reductions Where NYS Net Prices are based on a discount from Contractor’s list prices, price decreases shall take effect automatically during the Contract term and apply to Purchase Orders submitted on or after the date Contractor lowers its pricing to its customers generally or to similarly situated government customers during the Contract term; or

  • Principal Transactions In connection with purchases or sales of securities for the account of a Fund, neither the Adviser nor any of its directors, officers or employees will act as a principal or agent or receive any commission except as permitted by the 1940 Act.

  • Manual Transactions If the parties choose not to use Fund/SERV, if there are technical problems with Fund/SERV, or if the parties are not able to transmit or receive information through Fund/SERV, any corrections to a Portfolio’s prices should be communicated by facsimile or by electronic transmission, and will include for each day on which an adjustment has occurred the incorrect Portfolio price, the correct price, and, to the extent communicated to Portfolio shareholders, the reason for the adjustment. The Company may send this notification or a derivation thereof to Contract owners whose Contracts are affected by the adjustment.

  • Required Acceptance of Daily Load Deliveries and Notification If the State is harmed by purchaser’s refusal to accept up to 10 truck deliveries of any one sort per day, Purchaser will be in breach of contract and subject to damages as per the D-026.2 and D-027.2 clauses. A truck delivery is all the wood delivered including sorts on super trucks, mule trains and pups brought to the delivery point by a single truck. The Purchaser shall notify the Contract Administrator at least 48 hours in advance if: 1. Purchaser intends to limit the number of truck deliveries accepted on any day to less than that listed above, or 2. Purchaser intends to limit the number of truck deliveries accepted on any day to the number listed above.

  • TRANSACTION PROCESS The RFQ for this Lot will contain a deliverable-based Statement of Work (SOW). The RFQ will include, but is not limited to: Authorized User timeframes; system integration requirements; and other risks that may affect the cost to the Authorized User. All responses to RFQs must include detailed price information, including but not limited to: hours required per title, cost per hour etc. Travel, lodging and per diem costs must be itemized in the total quote and may not exceed the rates in the NYS OSC Travel Policy. More information can be found at xxxx://xxx.xxx.xxxxx.xx.xx/agencies/travel/travel.htm. All costs must be itemized and included in the Contractor’s quote.

  • Material Transactions Prior to the Closing, no Party will (other than (i) as contemplated by the terms of this Agreement and the Related Agreements, (ii) with respect to transactions for which there is a binding commitment existing prior to the date hereof disclosed in the Disclosure Schedules, and (iii) transactions described on Schedule 7.3 which do not vary materially from the terms set forth on such Schedule 7.3, or in the Ordinary Course of Business without first obtaining the written consent of the other Parties): (a) declare or pay any dividend or make any other distribution to shareholders, whether in cash, stock or other property; (b) amend its Governing Documents or enter into any agreement to merge or consolidate with, or sell a significant portion of its assets to, any other Person; (c) except pursuant to options, warrants, conversion rights or other contractual rights, issue any shares of its capital stock or any options, warrants or other rights to subscribe for or purchase such common or other capital stock or any securities convertible into or exchangeable for any such common or other capital stock; (d) directly redeem, purchase or otherwise acquire any of its common or other capital stock; (e) effect a reclassification, recapitalization, split-up, exchange of shares, readjustment or other similar change in or to any capital stock or otherwise reorganize or recapitalize; (f) enter into any employment contract which is not terminable upon notice of ninety (90) days or less, at will, and without penalty except as provided herein or grant any increase (other than ordinary and normal increases consistent with past practices) in the compensation payable or to become payable to officers or salaried employees, grant any stock options or, except as required by law, adopt or make any change in any bonus, insurance, pension or other Employee Benefit Plan, agreement, payment or agreement under, to, for or with any of such officers or employees; (g) make any payment or distribution to the trustee under any bonus, pension, profit sharing or retirement plan or incur any obligation to make any such payment or contribution which is not in accordance with such Party’s usual past practice, or make any payment or contributions or incur any obligation pursuant to or in respect of any other plan or contract or arrangement providing for bonuses, options, executive incentive compensation, pensions, deferred compensation, retirement payments, profit sharing or the like, establish or enter into any such plan, contract or arrangement, or terminate or modify any plan; (h) prepay any debt in excess of Twenty-Five Thousand Dollars ($25,000), borrow or agree to borrow any amount of funds except in the Ordinary Course of Business or, directly or indirectly, guarantee or agree to guarantee obligations of others, or fail to pay any monetary obligation in a timely manner prior to delinquency; (i) enter into any agreement, contract or commitment having a term in excess of three (3) months or involving payments or obligations in excess of Twenty-Five Thousand Dollars ($25,000) in the aggregate, except in the Ordinary Course of Business; (j) amend or modify any material Contract; (k) agree to increase the compensation or benefits of any employee (except for normal annual salary increases in accordance with past practices); (l) place on any of its assets or properties any pledge, charge or other Encumbrance, except as otherwise authorized hereunder, or enter into any transaction or make any contract or commitment relating to its properties, assets and business, other than in the Ordinary Course of Business or as otherwise disclosed herein; (m) guarantee the obligation of any person, firm or corporation, except in the Ordinary Course of Business; (n) make any loan or advance in excess of Twenty-Five Thousand Dollars ($25,000) or cancel or accelerate any material indebtedness owing to it or any claims which it may possess or waive any material rights of substantial value; (o) sell or otherwise dispose of any Real Property or any material amount of any tangible or intangible personal property other than leasehold interests in closed facilities, except in the Ordinary Course of Business; (p) commit any act or fail to do any act which will cause a Breach of any Contract and which will have a Material Adverse Effect on its business, financial condition or earnings; (q) violate any Applicable Law which violation might have a Material Adverse Effect on such Party; (r) purchase any real or personal property or make any other capital expenditure where the amount paid or committed is in excess of Twenty-Five Thousand Dollars ($25,000) per expenditure; (s) except in the Ordinary Course of Business, enter into any agreement or transaction with any of such Party’s Affiliates; or (t) engage in any transaction or take any action that would render untrue in any material respect any of the representations and warranties of such Party contained in this Agreement, as if such representations and warranties were given as of the date of such transaction or action.

  • Agency Cross Transactions From time to time, the Advisor or brokers or dealers affiliated with it may find themselves in a position to buy for certain of their brokerage clients (each an "Account") securities which the Advisor's investment advisory clients wish to sell, and to sell for certain of their brokerage clients securities which advisory clients wish to buy. Where one of the parties is an advisory client, the Advisor or the affiliated broker or dealer cannot participate in this type of transaction (known as a cross transaction) on behalf of an advisory client and retain commissions from one or both parties to the transaction without the advisory client's consent. This is because in a situation where the Advisor is making the investment decision (as opposed to a brokerage client who makes his own investment decisions), and the Advisor or an affiliate is receiving commissions from both sides of the transaction, there is a potential conflicting division of loyalties and responsibilities on the Advisor's part regarding the advisory client. The Securities and Exchange Commission has adopted a rule under the Investment Advisers Act of 1940, as amended, which permits the Advisor or its affiliates to participate on behalf of an Account in agency cross transactions if the advisory client has given written consent in advance. By execution of this Agreement, the Trust authorizes the Advisor or its affiliates to participate in agency cross transactions involving an Account. The Trust may revoke its consent at any time by written notice to the Advisor.

  • Notice to Proceed - Land Acquisition The acquisition of the Land shall not occur until the Director has issued a written Notice to Proceed for land acquisition to the Recipient (the "Notice to Proceed"). Such Notice to Proceed will not be issued until the Director has received a Request to Proceed acceptable to the Director and is assured that the Recipient has complied with all requirements for the approval of a grant under Revised Code Sections 164.20 through 164.27 and any requirements for land acquisition set forth in this Agreement, including without limitation the OPWC's approval of the proposed Deed Restrictions and Title Agent. The Notice to Proceed also shall specify the time frame for the Closing.

  • Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may (i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014. (b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”). (c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-­‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website. (i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i). (ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute. (iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator. (iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below. (e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e). (i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2. (ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11. (iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions. (iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors. (v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder. (f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6. (g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-­‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).

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