Transaction Monitoring Sample Clauses

Transaction Monitoring. Bank may, in its sole discretion, implement internal monitoring systems to evaluate Customer Transactions and the risk of possible fraudulent activity. Such Transaction monitoring is part of Bank’s internal processing and is not a component of the Security Procedures, and Customer agrees that the Security Procedures will be considered commercially reasonable regardless of whether they incorporate information from Transaction monitoring. Customer agrees that Bank may process Payment Orders and other Instructions verified by the Security Procedures and Bank will be considered to have acted in good faith and in compliance with the Security Procedures, regardless of the results of Transaction monitoring, including the detection of possible fraudulent activity; provided that Bank does not have actual knowledge that the Transaction is unauthorized and a reasonable opportunity to act on that knowledge. However, Bank reserves the right to reject Payment Orders and other Instructions verified by the Security Procedures in the event Bank identifies a risk of possible fraudulent activity and Bank shall not be responsible for its refusal to act upon any Payment Order or other Instructions based upon the results of Transaction monitoring.
AutoNDA by SimpleDocs
Transaction Monitoring. Does your institution have a monitoring program for unusual and potentially suspicious activities that could expose your institution to any ML/FT risks.
Transaction Monitoring. 16.1 The Supplier shall provide the Customer with the functionality to monitor availability, completion rates and Transactions timings. 16.2 The Supplier shall provide Customer with Transaction monitoring and risk assessment services that will enable the Customer to monitor and assess the associated risk of each Transaction. 16.3 The Supplier shall provide the Customer with Transaction monitoring and risk assessment services with the ability to define values and weighting of risk scores for data items within every transaction. 16.4 The Supplier shall provide the Customer with Transaction monitoring and risk assessment services with the ability to vary the relative weight of risk to be applied to a given constituent part of a Transaction. 16.5 The Supplier shall provide the Customer with Transaction monitoring and risk assessment services that shall score the relative risk of every Transaction based on scores derived from assessment of the constituent parts of a given Transaction and across multiple Transactions within one, many and/or all of the Customer’s accounts. 16.6 The Supplier shall provide the Customer with Transaction monitoring and risk assessment services that shall be able to influence the Acceptance Thresholds for Transactions. 16.7 The Supplier shall alert the Customer to suspicious patterns of activity in one or more Transactions, occurring across within one, many and/or all of the Customer’s accounts. 16.8 The Supplier shall provide the Customer with management reporting functionality which includes the ability to report on Transaction monitoring events across within one, many and/or all of the Customer’s accounts. 16.9 The Supplier shall provide the Customer with the option to manage the Transaction monitoring services via a console interface hosted by the Supplier and remotely accessible to the Customer. 16.10 The Supplier shall provide the Customer with remote access to the functions of the Transaction monitoring service for consumption within locally held Transaction monitoring platforms including, but not limited to: 16.10.1 Report out in real time;
Transaction Monitoring. 25.1. All transactions executed and/or attempted to be executed on the Cryptoforce Offering may be monitored by Cryptoforce, both manually and through use of technology, to promptly identify and highlight suspicious activity and/or transactions, which may include without limitation, high value transactions, cross-border transactions and any Suspicious Transactions. 25.2. Cryptoforce may undertake investigations to identify and examine transactions that are inconsistent with any User’s risk profile (see Section 7 (Risk Categorization and Management)), sophistication, and expected usage pattern.
Transaction Monitoring. 8.1. All Transactions executed and/or attempted to be executed on the Platform are regularly monitored by Xxxxx for purposes of identifying and highlighting transactions that may be deemed suspicious. 8.2. Sargo reserves the right to undertake necessary investigations from time to time to identify and examine transactions inconsistent with any user risk profile, sophistication and/or expected usage patterns. 8.3. Sargo may, if necessary, take any of the following actions on reasonable suspicion: 8.3.1. Perform negative name checks to ensure that the user does not transact with themselves; 8.3.2. Impose Transaction limits including the number of Transactions per day, value of the Transaction, the frequency of the limit and any other considerations as may be necessary.
Transaction Monitoring. Ripple Labs will institute AML programmatic transaction monitoring across the entire Ripple protocol, and will report the results of such monitoring to the U.S. Attorney’s Office, FinCEN, and any other law enforcement or regulatory agency upon request. The monitoring and reporting must include, at a minimum: (a) risk rating of accounts based on the particular gateway used; (b) dynamic risk tools to facilitate investigation of suspicious activity, including counterparty reporting, flow of funds reporting, account flagging of suspicious accounts, and degrees of separation reporting; and (c) other reports of protocol-wide activity regarding any unlawful activity.
Transaction Monitoring. All transactions conducted through the Platform are subject to monitoring for compliance with applicable laws. The Company reserves the right to reject, reverse, or cancel any transactions that violate these Terms or that are flagged as suspicious.
AutoNDA by SimpleDocs

Related to Transaction Monitoring

  • Program Monitoring The Contractor will make all records and documents required under this Agreement as outlined here, in OEC Policies and NHECC Policies available to the SRO or its designee, the SR Fiscal Officer or their designee and the OEC. Scheduled monitoring visits will take place twice a year. The SRO and OEC reserve the right to make unannounced visits.

  • Contract Monitoring The criminal background checks required by this rule shall be national in scope, and must be conducted at least once every three (3) years. Contractor shall make the criminal background checks required by Paragraph IV.G.1 available for inspection and copying by DRS personnel upon request of DRS.

  • Compliance Monitoring Grantee must be subject to compliance monitoring during the period of performance in which funds are Expended and up to three years following the closeout of all funds. In order to assure that the program can be adequately monitored, the following is required of Grantee: a. Grantee must maintain a financial tracking system provided by Florida Housing that ensures that CRF funds are Expended in accordance with the requirements in this Agreement. b. Grantee must maintain records on all awards to Eligible Persons or Households. These records must include, but are not limited to: i. Proof of income compliance (documentation from submission month, including but not limited to paystub, Florida unemployment statement, social security and/or disability statement, etc.); ii. Lease; and iii. Documentation of rental assistance payments made.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!