Cardholder File. Contractor must maintain a cardholder file for each designated cardholder which must contain at a minimum the following information for each:
Cardholder File Sample Clauses
Related to Cardholder File
Cardholder Any person authorized to use a Card by the Card Issuer.
Secondary Cardholder You may not request an additional Card for another person.
Customer Data 5.1 The Customer shall own all right, title and interest in and to all of the Customer Data and shall have sole responsibility for the legality, reliability, integrity, accuracy and quality of the Customer Data.
Unbundled Voice Loop – SL2 (UVL-SL2 Loops may be 2-wire or 4-wire circuits, shall have remote access test points, and will be designed with a DLR provided to NewPhone. SL2 circuits can be provisioned with loop start, ground start or reverse battery signaling. OC is provided as a standard feature on XX0 Xxxxx. The OC feature will allow NewPhone to coordinate the installation of the Loop with the disconnect of an existing customer’s service and/or number portability service. In these cases, BellSouth will perform the order conversion with standard order coordination at its discretion during normal work hours.
T-4 Slips The Employer shall include on each employee’s T-4 slip the amount of monies deducted in the previous year, and remitted to the Union, for income tax purposes where such information is or becomes readily available through the Employer’s payroll system.
Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Month, Assuming Institution shall provide Receiver:
ATM Card If approved, you may use your card and personal identification number (PIN) in automated teller machines (ATMs) of the Credit Union, Instant Cash, and Cirrus® networks, and such other machines or facilities as the Credit Union may designate. For ATM transactions, you must consent to the Credit Union’s overdraft protection plan in order for the transaction amount to be covered under the plan. Without your consent, the Credit Union may not authorize and pay an overdraft resulting from these types of transactions. Services and fees for ATM overdrafts are shown in the document the Credit Union uses to capture the member’s opt-in choice for overdraft protection and the Schedule of Fees and Charges. At the present time, you may use your card to: - Make deposits to your savings and checking accounts. - Withdraw funds from your savings and checking accounts. - Transfer funds from your savings and checking accounts. - Obtain balance information for your savings and checking accounts. - Make point-of-sale (POS) transactions with your card and personal identification number (PIN) to purchase goods or services at POS terminals that carry Instant Cash, and Cirrus® network logo(s). - Access your Overdraft Protection account. The following limitations on ATM Card transactions may apply: - There is no limit on the number of cash withdrawals you may make in any one (1) day. - You may withdraw up to a maximum of $500.00 in any one (1) day, if there are sufficient funds in your account. - There is no limit on the number of POS transactions you may make in any one (1) day. - For security purposes, there are other limits on the frequency and amount of transfers available at ATMs. - You may transfer up to the available balance in your accounts at the time of the transfer. - See Section 2 for transfer limitations that may apply to these transactions. Because of the servicing schedule and processing time required in ATM operations, there may be a delay between the time a deposit (either cash or check) is made and when it will be available for withdrawal.
Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.
Unbundled Voice Loops (UVLs) 2.2.1 BellSouth shall make available the following UVLs:
Product Information EPIZYME recognizes that by reason of, inter alia, EISAI’s status as an exclusive licensee in the EISAI Territory under this Agreement, EISAI has an interest in EPIZYME’s retention in confidence of certain information of EPIZYME. Accordingly, until the end of all Royalty Term(s) in the EISAI Territory, EPIZYME shall keep confidential, and not publish or otherwise disclose, and not use for any purpose other than to fulfill EPIZYME’s obligations, or exercise EPIZYME’s rights, hereunder any EPIZYME Know-How Controlled by EPIZYME or EPIZYME Collaboration Know-How, in each case that are primarily applicable to EZH2 or EZH2 Compounds (the “Product Information”), except to the extent (a) the Product Information is in the public domain through no fault of EPIZYME, (b) such disclosure or use is expressly permitted under Section 9.3, or (c) such disclosure or use is otherwise expressly permitted by the terms and conditions of this Agreement. For purposes of Section 9.3, each Party shall be deemed to be both the Disclosing Party and the Receiving Party with respect to Product Information. For clarification, the disclosure by EPIZYME to EISAI of Product Information shall not cause such Product Information to cease to be subject to the provisions of this Section 9.2 with respect to the use and disclosure of such Confidential Information by EPIZYME. In the event this Agreement is terminated pursuant to Article 12, this Section 9.2 shall have no continuing force or effect, but the Product Information, to the extent disclosed by EPIZYME to EISAI hereunder, shall continue to be Confidential Information of EPIZYME, subject to the terms of Sections 9.1 and 9.3 for purposes of the surviving provisions of this Agreement. Each Party shall be responsible for compliance by its Affiliates, and its and its Affiliates’ respective officers, directors, employees and agents, with the provisions of Section 9.1 and this Section 9.2.
