We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Orders types Sample Clauses

Orders types. 8.1 Buy - An order to buy an instrument at a price available for trading on the Trading Platform provided by the Company at the time of order.
Orders types. 9.1) Client acknowledges and agrees that the Trading Platform made available to the Client by the Company follows the market for the relevant Client, whether the Client is in front of his computer or not and whether the computer itself was switched on or not and exercises the order left by the Client when market conditions satisfy the Client's request.
Orders types. 4.3.1. The following order types are available in the Client’s Terminal: ● Market orders (Buy, Sell); ● Pending orders (Take Profit, Stop Loss, Buy Limit, Buy Stop, Sell Limit, Sell Stop).
Orders types. 4.3.1 The following order types are available in the Exswiss Client’s Terminal: • Market orders (Buy, Sell); • Pending orders (Take Profit, Stop Loss, Buy Limit, Buy Stop, Sell Limit, Sell Stop).
Orders types. 4.3.1 The following order types are available in the Globex360 (PTY)LTD MetaTrader 4 trading terminal: • Market orders (Buy, Sell); • Pending orders (Take Profit, Stop Loss, Buy Limit, Buy Stop, Sell Limit, Sell Stop).
Orders types. 1Buy - An order to buy an instrument at a price available for trading on the Trading Platform provided by the Company at the time of order.
Orders types. 7.1. Client acknowledges and agrees that the Trading Platform made available to the Client by the Company follows the market for the relevant Client, whether the Client is in front of his computer or not and whether the computer itself was switched on or not and exercises the order left by the Client when market conditions satisfy the Client's request. 7.2. Limit Order - A Limit Order is an instruction to trade at a level that becomes more favourable to the Client. A Limit Order can be used to open or close a position. Each Limit Order has a specified price limit set by the Client (but subject to the Company’s agreement). A Limit Order will be triggered if the Company’s bid price (in the case a sell order) or ask price (in the case of a buy order) moves in the Client’s favour to a point where the Client’s order can be executed. Once the limit level is triggered, the Company will seek to execute the order at that price. If the Company cannot do so (e.g. because in attempting to execute the order, the price becomes less favourable to the Client), the limit order will remain operational, waiting for the price to move again in the Client’s favour, such that it is triggered again. 7.3. Stop Order- A Stop Order is generally placed to provide some risk protection, for example, in the event of the Client’s position moving into loss. A Stop Order can also be used to either open or close a position. Each Stop Order has a specific stop level, set by you (but subject to the Company’s agreement). The Stop Order will be triggered only if a transaction takes place on the Company’s trading platform at that stop level. Once the Stop Order is triggered, the Company will seek to execute the order at a level that is the same as the stop level (although it may be at a less favorable level). 7.4. Other orders - such as OCO'S (One Cancels the other), ID's (If Done's- Trailing Stops etc., and more information, is described in the Company's website. 7.5. Rollovers or Swaps - The Company performs all the overnight rollovers (continuation of a trade) automatically, and there is no need for Client intervention. Such rollovers are accommodated with interest debits or credits to the Client's Trading Account. This is based on the interest rate differentials between currency pairs and taking into account the Company’s own costs. All open positions are automatically rolled over by. The Client’s position may either receive or be charged rollover, depending on whether the position is long o...
Orders types 

Related to Orders types

  • 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,

  • 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.

  • Account Types The Financial Institution agrees that each Collateral Account is, and will be maintained as, either a “securities account” (as defined in Section 8-501 of the UCC) or a “deposit account” (as defined in Section 9-102(a)(29) of the UCC).

  • Types of Grievances (A) An Individual Grievance is a grievance initiated by the Union on behalf of an individual employee. (B) A Group Grievance is a grievance initiated by the Union on behalf of a group of employees similarly affected by the Employer’s actions. (C) A Policy Grievance is a grievance by the Union which may involve a matter of general policy or general application of the Collective Agreement. (D) A Union Grievance is a grievance which directly affects the Union. (E) An Employer Grievance is a grievance initiated by the Employer.

  • Particular Methods of Procurement of Goods Works and Services (other than Consultants’ Services)

  • DOMESTIC PREFERENCES FOR PROCUREMENTS To the extent applicable, Supplier certifies that during the term of this Contract will comply with applicable requirements of 2 C.F.R. § 200.322.

  • 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.

  • Other Methods of Procurement of Goods and Works. The following table specifies the methods of procurement, other than International Competitive Bidding, which may be used for goods and works. The Procurement Plan shall specify the circumstances under which such methods may be used: (a) National Competitive Bidding (b) Shopping (c) Direct Contracting

  • Contract Type Full time equivalency (FTE); and,

  • Particular Methods of Procurement of Goods and Works International Competitive Bidding. Goods and works shall be procured under contracts awarded on the basis of International Competitive Bidding.