Registration for Mobile Banking Sample Clauses

Registration for Mobile Banking. 58.1 In order to use Mobile Banking, Member must: (a) be enrolled in Navigant’s Business Online Banking Services (as described in Part I above); and (b) have a web- enabled cell phone or other handheld mobile device whose network allows secure SSL traffic using the technology that supports Mobile Banking. Although Mobile Banking is phone device agnostic and will work with any web-enabled cell phone, tablet or other handheld mobile device whose network allows secure SSL traffic using the Mobile App (“Mobile Device”), the registration process may require Member to provide information about the cell phone or other handheld Mobile Device that Member will generally use for Mobile Banking, as well as the telephone number for Member’s Mobile Device, the telecommunications carrier that provides service to Member’s Mobile Device, and Member’s email address. It is Member’s responsibility to provide Navigant with accurate, complete and current information about Member and Member’s Mobile Device (including its telephone number, the telecommunications carrier, and Member’s email address), and to notify Navigant immediately if any of this information changes or if service to Member’s Mobile Device is terminated. Navigant reserves the right to refuse or cancel Member’s registration for Mobile Banking if Navigant cannot verify information about Member and/or Member’s Mobile Device.
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs
Registration for Mobile Banking. To access Mobile Banking, you must register for Mobile Banking while logged on to Online Banking or through your Mobile Device. As part of the registration process, you may be required to provide information about your Mobile Device, as well as the telephone number for your Mobile Device and the telecommunications carrier that provides service to your Mobile Device. It is your responsibility to provide us with accurate, complete and current information about you and your Mobile Device and to notify us immediately if any of this information changes or if service to your Mobile Device is terminated. It is also your responsibility to update such information as necessary to ensure that the information you have provided to us is current and accurate, including the telephone number and telecommunications carrier for your Mobile Device, your name, address, other phone numbers, and email address. We reserve the right to refuse or cancel your registration for Mobile Banking if we cannot verify information about your Mobile Device. Once you have registered, your Mobile Device may be used to access Mobile Banking. You are responsible for maintaining the security of your Mobile Device. You acknowledge that your Mobile Device is subject to the same security risks as computers that are attached to the Internet and agree that it is your responsibility to maintain anti-virus and anti-spyware programs on your Mobile Device. Except as otherwise provided in this Agreement, you are responsible for all transactions made using your Mobile Device. Mobile Banking will display sensitive information about your Mobile Accounts, including balances and transfer amounts. Anyone with access to your Mobile Device may be able to view this information. By participating in Mobile Banking, you agree that Mobile Banking may require the use of your Mobile Device's data and text messaging capabilities. You agree that we are not responsible for any charges you may incur while using Mobile Banking. Message and data rates may apply. For help, text “HELP” to 48179. To cancel, text “STOP” to 48179 at any time. In case of questions, please contact customer service at (000) 000-0000 or visit our website.
Sample 1

Related to Registration for Mobile Banking

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

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

  • Registration Data Upon placing an order for Pilot Voice, and at subsequent times as requested by Pilot, Customer agrees to provide Pilot with its (i) true, accurate, current, and complete business name, (ii) physical addresses where Voice Service will be used, (iii) 911 registered address for each applicable endpoint, (iv) a designated Account Administrator, and (v) user email addresses, phone numbers, and any other requested data which may be necessary to administer its Voice Service account (the “Account”) (collectively, “Registration Data”). Customer represents and warrants that the information it provides is accurate, current, and complete, and agrees to promptly update any of the information if it changes. If Customer provides Registration Data that is false, inaccurate, not current, incomplete, fraudulent, or otherwise unlawful, Pilot has the right, in its sole discretion, to suspend or terminate the Voice Services and refuse any and all current or future use of all Voice Services by Customer, its business(es), affiliates and all users of its Account. Upon provision of all Registration Data and acceptance of Customer’s Service Order, Pilot may provide Customer’s designated Account Administrator and other Pilot Voice users with, as applicable, administrator or user web portal logins and other Account information. Customer is solely liable for any transactions or activities by it or any third- party that occurs on its Account. Customer shall immediately notify Pilot of any unauthorized use of its Account or if any other breach of security has occurred. In no event shall Pilot be liable for any unauthorized, third-party use of your Account.

  • Domain Name Registration If Customer submits a Service Order(s) for domain name registration services, the following terms shall also apply:

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

  • Service Registration Certain of our Services require you to register to use them. In such case, you agree that a l information you provide is truthful, current and complete. If there is any change to your registration information, you agree to provide us with updated information immediately. To the extent any of the Services are password protected, you agree to keep such password confidential and not to share it with any third party. You also agree that you wil not access any Services for which a password is required by using any third party’s password. If you discover any use of your password other than by you, you agree to immediately notify us. If you become aware of unauthorized account access, you similarly agree to immediately notify us. At the end of any use of a password protected Service, you agree to exit and logout out of your user session. Under no circumstances sha l we be responsible for any loss or damage that may result if you fail to comply with these requirements.

  • Registration Process In connection with the registration of the Registrable Securities pursuant to Section 4.1, the Company shall:

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

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

  • USER REGISTRATION You may be required to register with the Site. You agree to keep your password confidential and will be responsible for all use of your account and password. We reserve the right to remove, reclaim, or change a username you select if we determine, in our sole discretion, that such username is inappropriate, obscene, or otherwise objectionable.

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