P2P Transfer Transaction descriptions Sample Clauses

P2P Transfer Transaction descriptions. We may, in our sole discretion, permit you to add a description or comment concerning the P2P Transfer Transaction that will be transmitted to the recipient. You agree that if we permit you to add a description or comment concerning the payment to your recipient that you will not include inappropriate or abusive language, messages or content in the description or comment. You agree that we may monitor the contents of the description or comment and may delete or edit the message if we believe any of the content is inappropriate or abusive, in our sole and absolute discretion.
AutoNDA by SimpleDocs

Related to P2P Transfer Transaction descriptions

  • Information Transfer and Storage Supplier will use Industry Standard encryption to encrypt Accenture Data that is in transit. Supplier will also use Industry Standard encryption to restrict access to Accenture Data stored on physical media that is transported outside of Supplier facilities.

  • Transaction Terms Product: Firm (LD) Energy Delivery Point: MISO CP Node AMIL.BGS6, or any successor thereto Quantity: See Table 1 below.

  • Agreement to Purchase and Sell On the terms and subject to the conditions set forth in this Agreement, each Originator, severally and for itself, agrees to sell to the Buyer, and the Buyer agrees to purchase from such Originator, from time to time on or after the Closing Date, but before the Purchase and Sale Termination Date (as defined in Section 1.4), all of such Originator’s right, title and interest in and to:

  • Deliverables for an Authorized User Agreement (Transaction Deliverables must be identified, as a measure of progress in the Authorized User Agreement. A Deliverable as a bulk number of hours is not permissible under the OGS Centralized Contract. Retainage As part of the Mini-Bid, the Authorized User may elect to retain a percentage of each individual Deliverable payment of no more than 20% until the acceptance of the complete Deliverable or project. This retainage may be reduced as described in the Mini-Bid, when the Contractor substantially reduces the time required from the timeframes negotiated between the Authorized User and the Contractor for the completion and acceptance of a Deliverable.

  • Purchase and Sale Agreement The Participating Investors and the selling Key Holder agree that the terms and conditions of any Proposed Key Holder Transfer in accordance with Subsection 2.2 will be memorialized in, and governed by, a written purchase and sale agreement with the Prospective Transferee (the “Purchase and Sale Agreement”) with customary terms and provisions for such a transaction, and the Participating Investors and the selling Key Holder further covenant and agree to enter into such Purchase and Sale Agreement as a condition precedent to any sale or other transfer in accordance with this Subsection 2.2.

  • Red Hat Enterprise Linux Desktop Software Subscriptions Software Subscriptions for Red Hat Enterprise Linux Desktops and Workstations are subject to the parameters set forth in Table 6 below. Each Red Hat Enterprise Linux Desktop and Workstation Software Subscription includes one Red Hat Network system entitlement and one Smart Management Module, each to be used solely with a single Red Hat Enterprise Linux Desktop or Workstation System. Production Support for Red Hat Enterprise Linux Desktop subscriptions is limited to web-based support only for your helpdesk support personnel. Red Hat is not obligated to support your end users directly.

  • Recurring Transactions If you intend to use the Card for recurring transactions, you should monitor your Balance and ensure you have funds available in your Card Account to cover the transactions. “Recurring transactions” are transactions that are authorized in advance by you to be charged to your Card at substantially regular intervals. We are not responsible if a recurring transaction is declined because you have not maintained a sufficient Balance in your Card Account to cover the transaction. If these recurring transactions may vary in amount, the person or merchant you are going to pay should tell you, 10 days before each payment, when it will be made and how much it will be. You may choose instead to get this notice only when the payment would differ by more than a certain amount from the previous payment, or when the amount would fall outside certain limits that you set with that person or merchant. If you have told us in advance to make regular payments (i.e., Recurring Transactions) from your Card Account, you can stop the payment by notifying us orally or in writing at least three (3) Business Days before the scheduled date of the transfer. If you call, we also may require you to put your request in writing and get it to us within 14 days after you call. If you order us to stop one of these payments three (3) Business Days or more before the transfer is scheduled, and we do not do so, we will be liable for your losses or damages. If you have authorized a merchant to make the recurring payment, you should also contact the applicable merchant in order to stop the transaction. Fraudulent Card Account Activity. We may block or cancel your Card Account if, as a result of our policies and procedures, we reasonably believe your Card Account is being used for fraudulent, suspicious, or criminal activity or any activity that is inconsistent with this Agreement. We will incur no liability because of the unavailability of the funds that may be associated with your Card Account.

  • Split Transactions You can instruct a merchant to charge your Card for part of a purchase and pay any remaining amount with cash or another card. This is called a “split transaction.” Some merchants do not permit split transactions. If you wish to conduct a split transaction, you must tell the merchant the exact amount you would like charged to your Card. If you fail to inform the merchant you would like to complete a split transaction and you do not have sufficient available funds in your Account to cover the entire purchase amount, your Card is likely to be declined.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. OGS CENTRALIZED CONTRACT MODIFICATIONS Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

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