PROCEDURES FOR REPORTING LOST OR STOLEN CARD Sample Clauses

PROCEDURES FOR REPORTING LOST OR STOLEN CARD. (S): You agree to notify us AT ONCE if you believe your Card(s) and/or PIN have been lost or stolen, or if you believe that an electronic fund transfer has been made without your permission using information from your check. Telephoning is one of the best ways of keeping your possible losses down. The address and phone number are shown on the back page of this Agreement. You acknowledge you could lose all the money in your account(s) (plus overdraft privilege). It is agreed that if you tell us within 2 business days of the lost or stolen facts, you can lose no more than $50 on a consumer account if someone used your Card(s) without your permission. It is agreed that if you do NOT tell us within 2 business days after you learn of the loss or theft of your Card(s), and we can prove we could have stopped someone from using your Card(s) without your permission if you had timely told us, you could lose as much as $500. Also, if your statement shows transfers that you did not make, including those made by card, code, or other means, you agree to tell us immediately. You agree that if you do not tell us within 60 days after the statement was mailed to you, you may not get back any money you lost after the 60 days if we can prove that we could have stopped someone from taking the money if you had told us in time. It is agreed that if a good reason kept you from notifying us in a prompt manner, we may, at our discretion, extend the time periods for notifying us. You should also call the number or write to the address listed on the back page of this agreement if you believe a transfer has been made using the information from your check without your permission.
AutoNDA by SimpleDocs

Related to PROCEDURES FOR REPORTING LOST OR STOLEN CARD

  • Procedures for LNP Request The Parties shall provide for the requesting of End Office LNP capability on a reciprocal basis through a written request. The Parties acknowledge that Verizon has deployed LNP throughout its network in compliance with FCC 96-286 and other applicable FCC Regulations.

  • Accounts Not Required to Be Reviewed, Identified, or Reported Unless the Reporting Financial Institution elects otherwise, either with respect to all Preexisting Individual Accounts or, separately, with respect to any clearly identified group of such accounts, where the implementing rules in the jurisdiction provide for such an election, the following accounts are not required to be reviewed, identified, or reported as Reportable Accounts:

  • CUSTOMS PROCEDURES 1. Each Party shall endeavour to apply its customs procedures in a predictable, consistent and transparent manner.

  • Invoice Procedures ‌ Supplier shall remit each invoice to the “bill-to” address provided with the order promptly after all Supplier’s performance obligations have been accepted and in accordance with the milestone payment schedule, if any, in the applicable order or SOW. Payment for any support services, as authorized in the Contract and the Authorized User’s applicable order or SOW, will be annually in arrears unless otherwise stated in this Contract, or in any order or SOW referencing this Contract. No invoice may include any costs other than those identified in the signed order or SOW, and those costs must be in accordance with the schedule of fees listed on Exhibit B. Without limiting the foregoing, all shipping costs are the Supplier’s responsibility except to the extent shipping charges are identified in Exhibit B and noted in any signed order or SOW referencing this Contract. Supplier shall issue invoices that identify, at a minimum:

  • PROCEDURES FOR SUPPLEMENTAL PAYMENT CALCULATIONS All calculations required by this Article VI, including but not limited to: (i) the calculation of the Applicant’s Stipulated Supplemental Payment Amount; (ii) the determination of both the Annual Limit and the Aggregate Limit; (iii) the effect, if any, of the Aggregate Limit upon the actual amount of Supplemental Payments eligible to be paid to the District by the Applicant; and (iv) the carry forward and accumulation of any of the Applicant’s Stipulated Supplemental Payment Amounts unpaid by the Applicant due to the Aggregate Limit in previous years, shall be calculated by the Third Party selected pursuant to Section 4.3.

  • Entity Accounts Not Required to Be Reviewed, Identified or Reported Unless the Reporting Singaporean Financial Institution elects otherwise, either with respect to all New Entity Accounts or, separately, with respect to any clearly identified group of such accounts, where the implementing rules in Singapore provide for such election, a credit card account or a revolving credit facility treated as a New Entity Account is not required to be reviewed, identified, or reported, provided that the Reporting Singaporean Financial Institution maintaining such account implements policies and procedures to prevent an account balance owed to the Account Holder that exceeds $50,000.

  • Grievance Procedures The AGENCY agrees to establish a formal written grievance process with procedures through which clients and recipients of services may present grievances to the governing authority of the AGENCY regarding services being provided under this Contract. Additionally, the AGENCY agrees to establish fair hearing procedures that ensure all persons will be advised of their rights to a fair hearing to appeal a denial or exclusion from services and/or the failure of staff to take into account the individual’s choice of service. The AGENCY’S internal grievance procedure must document and include, at a minimum, the following: date of grievance, a written response to the applicant sent within thirty (30) days, and the opportunity for the applicant to meet with the AGENCY Executive Director or designee. Upon request by the COUNTY, the AGENCY shall provide a written report as to the grievance outcome within five (5) normal COUNTY working days. The AGENCY will maintain these documents on file for review by the COUNTY.

  • SUBMISSION OF THE MONTHLY MI REPORT 4.1 The completed MI Report shall be completed electronically and returned to the Authority by uploading the electronic MI Report computer file to MISO in accordance with the instructions provided in MISO.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Review Procedures for Identifying Entity Accounts With Respect to Which Reporting Is Required For Preexisting Entity Accounts described in paragraph B of this section, the Reporting Finnish Financial Institution must apply the following review procedures to determine whether the account is held by one or more Specified U.S. Persons, by Passive NFFEs with one or more Controlling Persons who are U.S. citizens or residents, or by Nonparticipating Financial Institutions:

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