Endorsements and Procedures You agree to restrictively endorse any item transmitted through our RDC service by either: • Signing the back of the item with your name and the words “For Mobile Deposit Only” • Following other instructions provided by us. You agree to follow any and all further procedures and instructions for use of our RDC service that we may communicate to you through changes to this agreement or through other notice we provide to you. You agree to securely retain each item for no fewer than 90 days after deposit. Then, no fewer than 90 days after deposit, you agree to mark each item submitted via our RDC service as “Void” and dispose of it using a high degree of care to ensure the item cannot be transmitted, deposited, or presented again. We reserve the right to impose daily limits on the aggregate amount of and/or number of deposits you may make using our RDC service. We may modify these limits at any time and without notice. Current limits are presented to you in our RDC service interface. Your enrollment in our RDC services generally occurs when you become an account owner; however, we reserve the right to deny your enrollment in and terminate your access to RDC service at our sole discretion. You warrant to us that: • You will only transmit eligible items that are properly endorsed. • You will not transmit duplicate items. • All information you provide to us when using our RDC service is accurate and true. • We will not sustain a loss because you have deposited an item. • You will indemnify us from any loss for breach of this warranty provision. In general, if an image of an item you transmit using RDC is received and accepted before 4:00 p.m. ET on a business day we are open, we consider that day to be the day of that deposit, subject to the other terms and conditions herein. Otherwise, we may consider the deposit to be made on the next Business Day we are open. Funds deposited using our RDC service will generally be made available by the third business day from the day of deposit. However, we generally make the first $225 of the aggregate of your checks deposited through our RDC service on each business day available by the next business day. We may delay the availability of your funds for a longer period of time at our discretion if we deem it appropriate in accordance with our policies and procedures.
Amendments, Supplements and Waivers The Company and the Trustee may amend or supplement the Indenture or the Notes or waive compliance with any provision of the Indenture or the Notes in the manner, and subject to the terms, set forth in Section 7.05 and Article 8 of the Indenture.
Statements and Notices Statements and notices will be mailed or delivered to you at the appropriate address you have given the Credit Union. Notice sent to any one of you will be considered notice to all.
Amendments and Supplements The Company shall prepare and file with the Commission such amendments, including post-effective amendments, and supplements to such Registration Statement and the prospectus used in connection therewith as may be necessary to keep such Registration Statement effective and in compliance with the provisions of the Securities Act until all Registrable Securities and other securities covered by such Registration Statement have been disposed of in accordance with the intended method(s) of distribution set forth in such Registration Statement or such securities have been withdrawn.
Authorization of Financing Statements Each Grantor authorizes the Administrative Agent and its Affiliates, counsel and other representatives, at any time and from time to time, to file or record financing statements, amendments to financing statements, and other filing or recording documents or instruments with respect to the Collateral in such form and in such offices as the Administrative Agent reasonably determines appropriate to perfect the security interests of the Administrative Agent under this Agreement, and such financing statements and amendments may described the Collateral covered thereby as “all assets of the debtor”, “all personal property of the debtor” or words of similar effect. Each Grantor hereby also authorizes the Administrative Agent and its Affiliates, counsel and other representatives, at any time and from time to time, to file continuation statements with respect to previously filed financing statements. A photographic or other reproduction of this Agreement shall be sufficient as a financing statement or other filing or recording document or instrument for filing or recording in any jurisdiction.
Amendments; Waivers No provision of this Agreement may be waived or amended except in a written instrument signed, in the case of an amendment, by the Company and each Purchaser or, in the case of a waiver, by the party against whom enforcement of any such waiver is sought. No waiver of any default with respect to any provision, condition or requirement of this Agreement shall be deemed to be a continuing waiver in the future or a waiver of any subsequent default or a waiver of any other provision, condition or requirement hereof, nor shall any delay or omission of either party to exercise any right hereunder in any manner impair the exercise of any such right.
Execution of Financing Statements Pursuant to Section 9-402 of the New York UCC and any other applicable law, each Grantor authorizes the Administrative Agent to file or record financing statements and other filing or recording documents or instruments with respect to the Collateral without the signature of such Grantor in such form and in such offices as the Administrative Agent reasonably determines appropriate to perfect the security interests of the Administrative Agent under this Agreement. A photographic or other reproduction of this Agreement shall be sufficient as a financing statement or other filing or recording document or instrument for filing or recording in any jurisdiction.
Statements and Confirmations The Securities Intermediary will promptly send copies of all statements, confirmations and other correspondence concerning the Collateral Account and any financial assets credited thereto simultaneously to each of the Purchase Contract Agent and the Collateral Agent at their addresses for notices under this Agreement.
Amendments and Waivers (a) If the ICANN Board of Directors determines that an amendment to this Agreement (including to the Specifications referred to herein) and all other registry agreements between ICANN and the Applicable Registry Operators (the “Applicable Registry Agreements”) is desirable (each, a “Special Amendment”), ICANN may adopt a Special Amendment pursuant to the requirements of and process set forth in this Section 7.6; provided that a Special Amendment may not be a Restricted Amendment.
(b) Prior to submitting a Special Amendment for Registry Operator Approval, ICANN shall first consult in good faith with the Working Group regarding the form and substance of such Special Amendment. The duration of such consultation shall be reasonably determined by ICANN based on the substance of the Special Amendment. Following such consultation, ICANN may propose the adoption of a Special Amendment by publicly posting such amendment on its website for no less than thirty (30) calendar days (the “Posting Period”) and providing notice of such proposed amendment to the Applicable Registry Operators in accordance with Section 7.9. ICANN will consider the public comments submitted on a Special Amendment during the Posting Period (including comments submitted by the Applicable Registry Operators).
(c) If, within one hundred eighty (180) calendar days following the expiration of the Posting Period (the “Approval Period”), the ICANN Board of Directors approves a Special Amendment (which may be in a form different than submitted for public comment, but must address the subject matter of the Special Amendment posted for public comment, as modified to reflect and/or address input from the Working Group and public comments), ICANN shall provide notice of, and submit, such Special Amendment for approval or disapproval by the Applicable Registry Operators. If, during the sixty (60) calendar day period following the date ICANN provides such notice to the Applicable Registry Operators, such Special Amendment receives Registry Operator Approval, such Special Amendment shall be deemed approved (an “Approved Amendment”) by the Applicable Registry Operators, and shall be effective and deemed an amendment to this Agreement on the date that is sixty (60) calendar days following the date ICANN provided notice of the approval of such Approved Amendment to Registry Operator (the “Amendment Effective Date”). In the event that a Special Amendment does not receive Registry Operator Approval, the Special Amendment shall be deemed not approved by the Applicable Registry Operators (a “Rejected Amendment”). A Rejected Amendment will have no effect on the terms and conditions of this Agreement, except as set forth below.
(d) If the ICANN Board of Directors reasonably determines that a Rejected Amendment falls within the subject matter categories set forth in Section 1.2 of Specification 1, the ICANN Board of Directors may adopt a resolution (the date such resolution is adopted is referred to herein as the “Resolution Adoption Date”) requesting an Issue Report (as such term is defined in ICANN’s Bylaws) by the Generic Names Supporting Organization (the “GNSO”) regarding the substance of such Rejected Amendment. The policy development process undertaken by the GNSO pursuant to such requested Issue Report is referred to herein as a “PDP.” If such PDP results in a Final Report supported by a GNSO Supermajority (as defined in ICANN’s Bylaws) that either (i) recommends adoption of the Rejected Amendment as Consensus Policy or (ii) recommends against adoption of the Rejected Amendment as Consensus Policy, and, in the case of (i) above, the Board adopts such Consensus Policy, Registry Operator shall comply with its obligations pursuant to Section 2.2 of this Agreement. In either case, ICANN will abandon the Rejected Amendment and it will have no effect on the terms and conditions of this Agreement. Notwithstanding the foregoing provisions of this Section 7.6(d), the ICANN Board of Directors shall not be required to initiate a PDP with respect to a Rejected Amendment if, at any time in the twelve (12) month period preceding the submission of such Rejected Amendment for Registry Operator Approval pursuant to Section 7.6(c), the subject matter of such Rejected Amendment was the subject of a concluded or otherwise abandoned or terminated PDP that did not result in a GNSO Supermajority recommendation.
(e) If (a) a Rejected Amendment does not fall within the subject matter categories set forth in Section 1.2 of Specification 1, (b) the subject matter of a Rejected Amendment was, at any time in the twelve (12) month period preceding the submission of such Rejected Amendment for Registry Operator Approval pursuant to Section 7.6(c), the subject of a concluded or otherwise abandoned or terminated PDP that did not result in a GNSO Supermajority recommendation, or (c) a PDP does not result in a Final Report supported by a GNSO Supermajority that either (A) recommends adoption of the Rejected Amendment as Consensus Policy or (B) recommends against adoption of the Rejected Amendment as Consensus Policy (or such PDP has otherwise been abandoned or terminated for any reason), then, in any such case, such Rejected Amendment may still be adopted and become effective in the manner described below. In order for the Rejected Amendment to be adopted, the following requirements must be satisfied:
(i) the subject matter of the Rejected Amendment must be within the scope of ICANN’s mission and consistent with a balanced application of its core values (as described in ICANN’s Bylaws);
(ii) the Rejected Amendment must be justified by a Substantial and Compelling Reason in the Public Interest, must be likely to promote such interest, taking into account competing public and private interests that are likely to be affected by the Rejected Amendment, and must be narrowly tailored and no broader than reasonably necessary to address such Substantial and Compelling Reason in the Public Interest;
(iii) to the extent the Rejected Amendment prohibits or requires conduct or activities, imposes material costs on the Applicable Registry Operators, and/or materially reduces public access to domain name services, the Rejected Amendment must be the least restrictive means reasonably available to address the Substantial and Compelling Reason in the Public Interest;
(iv) the ICANN Board of Directors must submit the Rejected Amendment, along with a written explanation of the reasoning related to its determination that the Rejected Amendment meets the requirements set out in subclauses (i) through (iii) above, for public comment for a period of no less than thirty (30) calendar days; and
(v) following such public comment period, the ICANN Board of Directors must (a) engage in consultation (or direct ICANN management to engage in consultation) with the Working Group, subject matter experts, members of the GNSO, relevant advisory committees and other interested stakeholders with respect to such Rejected Amendment for a period of no less than sixty (60) calendar days; and (b) following such consultation, reapprove the Rejected Amendment (which may be in a form different than submitted for Registry Operator Approval, but must address the subject matter of the Rejected Amendment, as modified to reflect and/or address input from the Working Group and public comments) by the affirmative vote of at least two-‐thirds of the members of the ICANN Board of Directors eligible to vote on such matter, taking into account any ICANN policy affecting such eligibility, including ICANN’s Conflict of Interest Policy (a “Board Amendment”). Such Board Amendment shall, subject to Section 7.6(f), be deemed an Approved Amendment, and shall be effective and deemed an amendment to this Agreement on the date that is sixty (60) calendar days following the date ICANN provided notice of the approval of such Board Amendment to Registry Operator (which effective date shall be deemed the Amendment Effective Date hereunder). Notwithstanding the foregoing, a Board Amendment may not amend the registry fees charged by ICANN hereunder, or amend this Section 7.6.
(f) Notwithstanding the provisions of Section 7.6(e), a Board Amendment shall not be deemed an Approved Amendment if, during the thirty (30) calendar day period following the approval by the ICANN Board of Directors of the Board Amendment, the Working Group, on the behalf of the Applicable Registry Operators, submits to the ICANN Board of Directors an alternative to the Board Amendment (an “Alternative Amendment”) that meets the following requirements:
(i) sets forth the precise text proposed by the Working Group to amend this Agreement in lieu of the Board Amendment;
(ii) addresses the Substantial and Compelling Reason in the Public Interest identified by the ICANN Board of Directors as the justification for the Board Amendment; and
(iii) compared to the Board Amendment is: (a) more narrowly tailored to address such Substantial and Compelling Reason in the Public Interest, and (b) to the extent the Alternative Amendment prohibits or requires conduct or activities, imposes material costs on Affected Registry Operators, or materially reduces access to domain name services, is a less restrictive means to address the Substantial and Compelling Reason in the Public Interest. Any proposed amendment that does not meet the requirements of subclauses (i) through
Certificate of Insurance/Endorsements A certificate of insurance from an insurer with a Best's rating of no less than A- indicating compliance with the required coverages has been received by State Procurement Bureau, X.X. Xxx 000000, Xxxxxx, XX 00000-0000. The certificates must name the State of Montana as certificate holder and Contractor shall provide copies of additional insured endorsements required by Contractor’s commercial general liability and automobile liability policies. Contractor must notify State immediately of any material change in insurance coverage, such as changes in limits, coverages, change in status of policy, etc. State reserves the right to require complete copies of insurance policies at all times.
