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

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.

  • Registration, etc Each Pledgor agrees that, upon the occurrence and during the continuance of an Event of Default hereunder, if for any reason the Collateral Agent desires to sell any of the Pledged Securities of the Borrower at a public sale, it will, at any time and from time to time, upon the written request of the Collateral Agent, use its best efforts to take or to cause the issuer of such Pledged Securities to take such action and prepare, distribute and/or file such documents, as are required or advisable in the reasonable opinion of counsel for the Collateral Agent to permit the public sale of such Pledged Securities. Each Pledgor further agrees to indemnify, defend and hold harmless the Collateral Agent, each other Secured Party, any underwriter and their respective officers, directors, affiliates and controlling persons from and against all loss, liability, expenses, costs of counsel (including, without limitation, reasonable fees and expenses to the Collateral Agent of legal counsel), and claims (including the costs of investigation) that they may incur insofar as such loss, liability, expense or claim arises out of or is based upon any alleged untrue statement of a material fact contained in any prospectus (or any amendment or supplement thereto) or in any notification or offering circular, or arises out of or is based upon any alleged omission to state a material fact required to be stated therein or necessary to make the statements in any thereof not misleading, except insofar as the same may have been caused by any untrue statement or omission based upon information furnished in writing to such Pledgor or the issuer of such Pledged Securities by the Collateral Agent or any other Secured Party expressly for use therein. Each Pledgor further agrees, upon such written request referred to above, to use its best efforts to qualify, file or register, or cause the issuer of such Pledged Securities to qualify, file or register, any of the Pledged Securities under the Blue Sky or other securities laws of such states as may be requested by the Collateral Agent and keep effective, or cause to be kept effective, all such qualifications, filings or registrations. Each Pledgor will bear all costs and expenses of carrying out its obligations under this Section 12. Each Pledgor acknowledges that there is no adequate remedy at law for failure by it to comply with the provisions of this Section 12 and that such failure would not be adequately compensable in damages, and therefore agrees that its agreements contained in this Section 12 may be specifically enforced.

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

  • 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 and Transfer (a) The Registrar shall maintain, as agent of the Issuer for the purpose, at the Registrar’s office in London, a register for (i) registering and maintaining a record of the aggregate holdings of all DTC Global Securities and the International Global Securities, (ii) registering transfers between holders of the Global Securities, (iii) registering and maintaining a record of the aggregate holdings of all definitive registered Securities, (iv) registering transfers between holders of the definitive registered Securities and (v) registering and maintaining a record of any further issues of Securities pursuant to Section 9 hereof and any subsequent transfers thereof. In addition, the Registrar will (i) maintain and promptly update the respective Schedules to the DTC Global Securities and the International Global Securities, and (ii) ensure that the sum of the respective aggregate principal amounts shown by the latest entry in the respective Schedules to the DTC Global Securities and the International Global Securities does not exceed $1,500,000,000, plus the aggregate principal amount of any additional Securities issued by the Issuer in accordance with Section 9 hereof, at any one time. Upon presentation for the purpose at the said office of the Registrar of any Security duly endorsed by, or accompanied by delivery of a written instrument of transfer in form approved by the Registrar duly executed by, the registered holder of the Security, or the registered holder’s attorney thereunto duly authorized in writing, such Security shall be transferred upon such register and a new Security, bearing the guarantee of Japan in the form herein provided for, shall be authenticated and delivered in the name of the transferee. Transfers and exchanges of Securities shall be subject to such reasonable regulations as may be prescribed by the Issuer. Upon presentation for transfer or exchange of any Security in definitive form at any office of any transfer agent accompanied by a written instrument of transfer in a form approved by the Registrar duly executed by the registered holder or such registered holder’s attorney duly authorized in writing, such Security and written instrument shall be forwarded to the office of the Registrar. In addition, any transfer agent shall provide to the Registrar such information as the Registrar may reasonably require in connection with the delivery by such transfer agent of Securities in the definitive form in exchange for other Securities.

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

  • Registration and Listing 15 Section 3.3

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

  • Registration of Agreement 1.04 (1) The City shall be entitled, in its sole discretion, to file and maintain caveats evidencing the City’s interest under this Agreement against each and every Certificate of Title within the Development Area.

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