Transaction Control Functions Sample Clauses

The Transaction Control Functions clause defines the mechanisms by which transactions are managed and regulated within a system or agreement. It typically outlines procedures for initiating, committing, rolling back, or otherwise controlling the state of transactions, ensuring that operations are completed successfully or reverted in case of errors. By establishing clear rules for transaction management, this clause helps maintain data integrity and consistency, preventing partial or unintended changes and thereby reducing operational risk.
Transaction Control Functions. We may, in our discretion, provide functions within one or more of the Service applications described in this Agreement whereby you may electronically activate settings to restrict, block, limit, or otherwise control certain Service Account transactions automatically (a “Transaction Control Function”). A Transaction Control Function may include, for example, a setting that allows you to prevent your debit card or credit card from being used for online purchases. By enabling or using any Transaction Control Function, you agree to the terms of, and you agree to comply with, all instructional materials, technical requirements, and on-screen guides we disclose or make available to you in connection with the Transaction Control Function, as the same may be amended by us from time to time. You are solely responsible for activating and deactivating any transaction control settings that are available through any Transaction Control Function, and you agree that we will not be liable to you or to any third party as a result of processing or handling Service Account transactions according to your transaction control settings. Any Transaction Control Function may rely on transaction information provided by third parties such as payment networks, merchants, and financial institutions. You agree that we will not be liable to you or to any third party in the event we process or handle any Service Account transaction in conflict with your transaction control settings as a result of erroneous, inaccurate, or incomplete transaction information provided by a third party. Subject to the terms and features we disclose for any particular Transaction Control Function, we will implement the transaction control settings you make as soon as reasonably practicable. However, you agree that we will not be liable to you or to any third party in the event we process or handle any Service Account transaction in conflict with a transaction control setting you have made if we have not had a reasonable opportunity to implement the setting. Our provision and your use of any Transaction Control Function does not relieve you of your responsibility to diligently monitor activity in your Service Account, to promptly review Service Account statements as they are made available to you, and to promptly report any errors or unauthorized transactions, or lost or stolen debit cards or credit cards, according to the terms and conditions of the agreements governing your Service Account.
View SourceView Similar (8)

Related to Transaction Control Functions

  • MANAGEMENT FUNCTIONS B.1 The Association recognizes that the management of the Hospital and the direction of working forces are fixed exclusively in the Hospital and shall remain solely with the Hospital except as specifically limited by the provisions of this Agreement and, without restricting the generality of the foregoing, the Association acknowledges that it is the exclusive function of the Hospital to: (a) maintain order, discipline and efficiency; (b) hire, assign, retire, discharge, direct, promote, demote, classify, transfer, lay- off, recall, and suspend or otherwise discipline nurses, provided that a claim of discharge or discipline without just cause may be the subject of a grievance and dealt with as hereinafter provided; (c) determine, in the interest of efficient operation and high standards of service, job rating and classification, the hours of work, work assignments, methods of doing the work, and the working establishment for the service; (d) generally to manage the operation that the Hospital is engaged in and, without restricting the generality of the foregoing, to determine the number of personnel required, methods, procedures, and equipment in connection therewith; (e) make, enforce, and alter from time to time reasonable rules and regulations to be observed by the nurses which are not inconsistent with the provisions of this Agreement. B.2 These rights shall not be exercised in a manner inconsistent with the provisions of this Agreement.

  • MIXED FUNCTIONS An employee engaged for more than two hours during one day or shift on duties carrying a higher rate than his or her ordinary classification shall be paid the higher rate for such day or shift. If for two hours or less during one day or shift he or she shall be paid the higher rate for the time so worked.

  • Agency Cross Transactions From time to time, the Advisor or brokers or dealers affiliated with it may find themselves in a position to buy for certain of their brokerage clients (each an "Account") securities which the Advisor's investment advisory clients wish to sell, and to sell for certain of their brokerage clients securities which advisory clients wish to buy. Where one of the parties is an advisory client, the Advisor or the affiliated broker or dealer cannot participate in this type of transaction (known as a cross transaction) on behalf of an advisory client and retain commissions from one or both parties to the transaction without the advisory client's consent. This is because in a situation where the Advisor is making the investment decision (as opposed to a brokerage client who makes his own investment decisions), and the Advisor or an affiliate is receiving commissions from both sides of the transaction, there is a potential conflicting division of loyalties and responsibilities on the Advisor's part regarding the advisory client. The Securities and Exchange Commission has adopted a rule under the Investment Advisers Act of 1940, as amended, which permits the Advisor or its affiliates to participate on behalf of an Account in agency cross transactions if the advisory client has given written consent in advance. By execution of this Agreement, the Trust authorizes the Advisor or its affiliates to participate in agency cross transactions involving an Account. The Trust may revoke its consent at any time by written notice to the Advisor.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Additional Functions Upon receipt of Proper Instructions, the Custodian shall take all such other actions as specified in such Proper Instructions and as shall be reasonable or necessary with respect to Repurchase Agreement transactions and the Securities and funds transferred and received pursuant to such transactions, including, without limitation, all such actions as shall be prescribed in the event of a default under a Repurchase Agreement.