Purchasing and Reloading Gift Cards Sample Clauses

Purchasing and Reloading Gift Cards. You may use an eligible Funding Source to purchase new Gift Cards or reload funds to a Gift Card. Once you have purchased or reloaded a Gift Card using the Gift Card Service, the transaction is final and cannot be reversed. Gift Card purchases and reloads are subject to your Client Card Third Party Payment limits for CAD Deposit Account(s) and the credit limit on your CAD Credit Card Account(s), as applicable.
AutoNDA by SimpleDocs

Related to Purchasing and Reloading Gift Cards

  • Branding for Operator Call Processing and Directory Assistance 8.4.1 BellSouth's branding feature provides a definable announcement to Budget Phone end users using Directory Assistance (DA)/ Operator Call Processing (OCP) prior to placing such end users in queue or connecting them to an available operator or automated operator system. This feature allows Budget Phone's name on whose behalf BellSouth is providing Directory Assistance and/or Operator Call Processing. Rates for the branding features are set forth in Exhibit E.

  • Claims Processing BCBSM will process Provider's Clean Claims submitted in accordance with this Agreement in a timely fashion.

  • Software Subscription Use Case Red Hat Storage Server for On- Premise Red Hat Storage Server for On-Premise is intended to be used as a storage system and will be supported only when used as a storage node. Red Hat Storage Server is not supported on non- server hardware such as desktops or workstations. Red Hat Storage Server for On-Premise is intended for use on a dedicated System, Physical Node, Virtual Node or Virtual Guest; running other applications and/or programs of any type on the System, Physical Node, Virtual Node or Virtual Guest can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server. Red Hat Storage Server for Public Cloud Red Hat Storage Server for Public Cloud is intended to be used as a storage system and will be supported only when used as a storage node. When running in Amazon Web Services, an EC2 M1 Large dedicated instance is required in order to be supported. Running other applications and/or programs of any type on the same instance can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server. Red Hat Storage for Red Hat Enterprise Linux OpenStack Platform Red Hat Storage Server for Red Hat Enterprise Linux OpenStack Platform is intended to be used as a storage system with Red Hat Enterprise Linux OpenStack Platform and will be supported only when used as a storage node. Red Hat Storage Server is not supported on non-server hardware such as desktops or workstations. Red Hat Storage Server for Red Hat Enterprise Linux OpenStack Platform is intended for use on a dedicated Physical Node; running other applications and/or programs of any type on the Physical Node can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server.

  • Skidding and Yarding Methods of skid- ding or yarding specified for particular areas, if any, are indicated on Sale Area Map. Outside Clearcutting Units and construction clearings, insofar as ground conditions permit, products shall not be skidded against reserve trees or groups of reproduction and tractors shall be equipped with a winch to facilitate skidding. B6.421 Rigging. Insofar as practicable, needed rigging shall be slung on stumps or trees desig- nated for cutting.

  • INTRODUCTION TO YOUR SUBSCRIBER AGREEMENT Thank you for choosing Blue Cross & Blue Shield of Rhode Island (BCBSRI) for your healthcare coverage. We appreciate the trust you’ve placed in us and want to help you make the most of your health plan. In this Subscriber Agreement (agreement), you’ll find valuable information about your plan, including: • how your health coverage works; • how BCBSRI processes claims for the health services you receive; • your rights and responsibilities as a BCBSRI member; • BCBSRI’s rights and responsibilities; and • tools and programs to help you stay healthy and save money. We encourage you to read this agreement to learn about all the advantages of being a BCBSRI member. How to Use This Agreement Below are some helpful tips on how to find what you need in this agreement. • As a member, you are responsible for understanding the benefits to which you are entitled under this agreement and the rules you must follow to receive those benefits. • The Table of Contents will help you find the order of the sections as they appear in the agreement. • The Summary of Benefits, included in this agreement, shows the amount you pay out of your own pocket. • Important contact information, such as, telephone numbers, addresses, and websites are located at the end of this document. • Some words and phrases used in this agreement are in italics. This means that the words or phrases have a special meaning as they relate to your healthcare coverage. Please see Section 8 for definitions of these words. • When we use the words “we,” “us,” and “our,” we are referring to BCBSRI. When we use the words “you” and “your” we are referring to the enrolled subscriber and/or member. These words are also defined in the Glossary. • Many sections of this document are related to other sections. You may need to reference more than one section to find the information you need.

  • Billing and Collection Customers BellSouth currently has in effect numerous billing and collection agreements with various interexchange carriers and billing clearing houses and as such these billing and collection customers (“B&C Customers”) query BellSouth’s LIDB to determine whether to accept various billing options from End Users. Until such time as BellSouth implements in its LIDB and its supporting systems the means to differentiate Local Line’s data from BellSouth’s data, the following shall apply:

  • Purchasing Card The State has implemented a purchasing card program using the Visa platform. The Contractor may receive payments via the State’s Purchasing Card in the same manner as any other Visa purchases. Purchasing Card acceptance for purchase is a mandatory requirement for the Contract but is not the exclusive method of payment. If the State changes its Purchasing Card platform during the term of Contract, the Contractor shall make any necessary changes to accommodate the State ‘s new Purchasing Card platform within 30 calendar days of notification of such change.

  • Data Processing Agreement The Data Processing Agreement, including the Approved Data Transfer Mechanisms (as defined in the Data Processing Agreement) that apply to your use of the Services and transfer of Personal Data, is incorporated into this Agreement by this reference. Each party will comply with the terms of the Data Processing Agreement and will train its employees on DP Law.

  • Sub-processing 1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the sub-processor which imposes the same obligations on the sub-processor as are imposed on the data importer under the Clauses. Where the sub-processor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the sub-processor’s obligations under such agreement.

  • Subprocessing 1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the subprocessor which imposes the same obligations on the subprocessor as are imposed on the data importer under the Clauses. Where the subprocessor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the subprocessor's obligations under such agreement.

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