Finalisation of registration Sample Clauses

Finalisation of registration. In case of approving the previous personal identification described in the Approval of previous personal identification section, the organiser finalises identification immediately. In case of providing the personal identification documents described in Document-based identification, the Customer Service administrator of the organiser shall check the copies of documents and compare them with the previously provided personal data of the Player. In case of errors, spelling mistakes and mismatches, the Customer Service assistant shall correct the discrepancies according to the documents submitted by the Player, and notify the Player thereof via e-mail. If the Player does not approve the corrections, then the Customer Service assistant shall suspend access to real cash games until the issue is completely resolved. In case of a match, the Customer Service administrator finalises the registration of the Player. Registration is thus completed, the control of the existence of any reasons disqualifying the Player from real cash games can commence. After the personal identity of the Player is verified, he can no longer change his personal data in the user account. In the user account of the Player, only the mobile phone number and the password required for logging in can be changed (by the Player). In case the Player is the citizen of a third country posing high-level risk, or has his permanent address in such country, the head of Customer Service shall decide on finalising registration and document it properly.
AutoNDA by SimpleDocs
Finalisation of registration. After entering into the Framework Contract, the User must provide all of the information and proof that are requested by the Distributor. By giving their consent to the terms of the Framework Contract, the User accepts that the Distributor will transfer to the Issuer their request for registration as a User and all the proof documents received by it. The Issuer alone has the power to accept the registration of an interested party as a User for an Account in their name. This acceptance will be indicated to the User by the Distributor by any means under the terms established on the Site. The Issuer, without motivation, or right to an indemnity in favour of the User, may refuse a request to open an Account. This refusal will be indicated to the User by the Distributor by any means under the terms established on the Site.
Finalisation of registration. After entering into the Framework Contract, the Account Holder must provide all of the information and proof that are requested by the Platform. By giving their consent to the terms of the Framework Contract, the Account Holder accepts that the Platform will transfer to the Service Provider their request for registration as an Account Holder and all the proof documents received by it. The Service Provider alone has the power to accept the registration of an interested party as an Account Holder for a Payment Account in their name. This acceptance will be indicated to the Account Holder by the Platform by any means under the terms established on the Site. The Service Provider, without motivation, or right to an indemnity in favour of the Account Holder, may refuse a request to open an Account. This refusal will be indicated to the Account Holder by the Platform by any means under the terms established on the Site.

Related to Finalisation of registration

  • Expenses of Registration All expenses incurred in connection with registrations, filings or qualifications pursuant to Sections 2 and 3, including, without limitation, all registration, listing and qualifications fees, printers, legal and accounting fees shall be paid by the Company.

  • Delay of Registration No Holder shall have any right to obtain or seek an injunction restraining or otherwise delaying any registration pursuant to this Agreement as the result of any controversy that might arise with respect to the interpretation or implementation of this Section 2.

  • Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).

  • NERC Registration If and to the extent any of the NTO’s facilities are NERC jurisdictional facilities, the ISO will register for certain NERC functions applicable to those NTO facilities. Such functions may include, without limitation, those functions designated by NERC to be “Reliability Coordinator” and “Balancing Authority” and “Transmission Planner” and “Planning Coordinator.” The Parties agree to negotiate in good faith the compliance obligations for the NERC functions applicable to, and to be performed by, each Party with respect to the NTO’s facilities. Notwithstanding the foregoing, the ISO shall register for the “Transmission Operator” function for all NTO Transmission Facilities under ISO Operational Control identified in Appendix A-1 of this Agreement.

  • Transition of Registry upon Termination of Agreement text for intergovernmental organizations or governmental entities or other special circumstances: “Transition of Registry upon Termination of Agreement. Upon expiration of the Term pursuant to Section 4.1 or Section 4.2 or any termination of this Agreement pursuant to Section 4.3 or Section 4.4, in connection with ICANN’s designation of a successor registry operator for the TLD, Registry Operator and ICANN agree to consult each other and work cooperatively to facilitate and implement the transition of the TLD in accordance with this Section 4.5. After consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the TLD to a successor registry operator in its sole discretion and in conformance with the Registry Transition Process. In the event ICANN determines to transition operation of the TLD to a successor registry operator, upon Registry Operator’s consent (which shall not be unreasonably withheld, conditioned or delayed), Registry Operator shall provide ICANN or such successor registry operator for the TLD with any data regarding operations of the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such successor registry operator in addition to data escrowed in accordance with Section 2.3 hereof. In the event that Registry Operator does not consent to provide such data, any registry data related to the TLD shall be returned to Registry Operator, unless otherwise agreed upon by the parties. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event of a transition of the TLD pursuant to this Section 4.5. In addition, ICANN or its designee shall retain and may enforce its rights under the Continued Operations Instrument, regardless of the reason for termination or expiration of this Agreement.”]

  • Registration of Contractor All contractors and subcontractors must comply with the requirements of Labor Code Section 1771.1(a), pertaining to registration of contractors pursuant to Section 1725.5. Bids cannot be accepted from unregistered contractors except as provided in Section 1771.1. This project is subject to compliance monitoring and enforcement by the Department of Industrial Relations. After award of the contract, Contractor and each Subcontractor shall furnish electronic payroll records directly to the Labor Commissioner in the manner specified in Labor Code Section 1771.4.

  • REGISTRATION OF EZ2BID 3.1 E-bidders will log in into ESZAM AUCTIONEER SDN BHD secured website. E-bidders shall provide true, current and accurate information to register as a user.

  • Registration of Agreement The registration of License agreements should be done within 30 days of signing of agreement, the licensee/ lessee (registration fees, stamp duty etc to be fully borne by the licensee/lessee) and the duly registered documents to be submitted to Maha-Metro for records. Any amendment in the contract agreement, if required to be registered, shall also be registered within 30 days from the date of amendment and duly registered documents shall be submitted to Maha-Metro for record. In case the registration of the license/lease agreement /amendment is not done within the 30 days of signing of license/lease agreement/ amendment, it shall be treated as “Material Breach of Contract”. The Licensee will be given 30 days time to cure the defaults In case Licensee fail to remedify the default to the satisfaction of the Maha-Metro within the cure period, Maha-Metro may terminate the License agreement after expiry of cure period duly forfeiting the security deposit/ any other amount paid by Licensee.

  • Termination of Registration Rights The right of any Holder to request registration or inclusion of Registrable Securities in any registration pursuant to Subsections 2.1 or 2.2 shall terminate upon the earliest to occur of:

  • Registration of Contractors Contractor and all subcontractors must comply with the requirements of labor code section 1771.1(a), pertaining to registration of contractors pursuant to section 1725.5. Registration and all related requirements of those sections must be maintained throughout the performance of the Contract.

Time is Money Join Law Insider Premium to draft better contracts faster.