Express Authorisation for Collateral Sample Clauses

The Express Authorisation for Collateral clause explicitly grants one party the right to use or deal with collateral provided under an agreement. In practice, this means the party receiving collateral, such as cash or securities, is formally permitted to use, invest, or otherwise dispose of the collateral within the limits set by the contract. This clause is essential for clarifying the rights of the collateral taker, reducing ambiguity, and ensuring both parties understand how collateral may be handled during the term of the agreement.
Express Authorisation for Collateral. Without limiting Global Prime’s right to request transfer of any of the Custodial Assets under clause 11.2, Client expressly authorises Global Prime in its discretion: (a) to identify any Collateral as being held as Margin or security against a particular obligation of Client under this agreement or against an Global Prime Transaction; (b) subject to clauses 11.2 and 11.5, to transfer any Custodial Assets to Global Prime expressly as Collateral for any obligations of Client under this agreement or a Global Prime Transaction; and (c) to transfer the proceeds of a credit advance made to Client to any Related Entity to satisfy any Margin or security requirement of a Related Entity in relation to a Transaction (provided that Client and Global Prime have previously agreed in writing that the Transaction is a Transaction to which this clause 11.3 applies).
View SourceView Similar (2)
Express Authorisation for Collateral. Without limiting UBS’s right to request transfer of any of the Custodial Assets under clause 10.2, the Customer expressly authorises UBS in its discretion to: (a) identify any Collateral as being held as margin or security against a particular obligation of the Customer under this agreement or against an UBS Transaction; (b) subject to clauses 10.2 and 10.5, transfer any Custodial Assets to UBS expressly as Collateral for any obligations of the Customer under this agreement or an UBS Transaction; and (c) transfer the proceeds of a cash advance made to the Customer to any Related Entity to satisfy any margin or security requirement of a Related Entity in relation to a Transaction (provided that the Customer and UBS have previously agreed in writing that the Transaction is a Transaction to which this clause 10.3 applies).
View SourceView Similar (2)
Express Authorisation for Collateral. ‌ Without limiting MILLENNIUM ALPHA GLOBAL HOLDING GROUP Ltd’s right to request transfer of any of the Custodial Assets under clause 11.2, Client expressly authorises MILLENNIUM ALPHA GLOBAL HOLDING GROUP Ltd in its discretion: (a) to identify any Collateral as being held as Margin or security against a particular obligation of Client under this agreement or against an MILLENNIUM ALPHA GLOBAL HOLDING GROUP Ltd Transaction; (b) subject to clauses 11.2 and 11.5, to transfer any Custodial Assets to MILLENNIUM ALPHA GLOBAL HOLDING GROUP Ltd expressly as Collateral for any obligations of Client under this agreement or a MILLENNIUM ALPHA GLOBAL HOLDING GROUP Ltd Transaction; and (c) to transfer the proceeds of a credit advance made to Client to any Related Entity to satisfy any Margin or security requirement of a Related Entity in relation to a Transaction (provided that Client and MILLENNIUM ALPHA GLOBAL HOLDING GROUP Ltd have previously agreed in writing that the Transaction is a Transaction to which this clause 11.3 applies).
View Source
Express Authorisation for Collateral. CapitalFX Account Agreement 26 Without limiting CapitalFX’s right to request transfer of any of the Custodial (a) i Assets under clause 11.2, Client expressly authorises CapitalFX in its discretion: t (a) to identify any Collateral as being held as Margin or security against h CapitalFX Transaction; (b) subject to clauses 11.2 and 11.5, to transfer any Custodial Assets to h CapitalFX expressly as Collateral for any obligations of e
View Source

Related to Express Authorisation for Collateral

  • Maintain Authorisations It will use all reasonable efforts to maintain in full force and effect all consents of any governmental or other authority that are required to be obtained by it with respect to this Agreement or any Credit Support Document to which it is a party and will use all reasonable efforts to obtain any that may become necessary in the future.

  • Authorisation obtain or cause to be obtained, maintain in full force and effect and comply fully with all Required Authorisations, provide the Agent with Certified Copies of the same and do, or cause to be done, all other acts and things which may from time to time be necessary or desirable under any applicable law (whether or not in the Pertinent Jurisdiction) for the continued due performance of all the obligations of the Security Parties under each of the Security Documents;

  • Authorisations Each Obligor shall promptly: (a) obtain, comply with and do all that is necessary to maintain in full force and effect; and (b) supply certified copies to the Agent of, any Authorisation required under any law or regulation of its jurisdiction of incorporation to enable it to perform its obligations under the Finance Documents and to ensure the legality, validity, enforceability or admissibility in evidence in its jurisdiction of incorporation of any Finance Document.

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

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.