17 CFR 37.9 - Methods of execution for required and permitted transactions.

Beta! The text on the eCFR tab represents the unofficial eCFR text at ecfr.gov.
§ 37.9 Methods of execution for required and permitted transactions.

(a) Execution methods for required transactions.

(1) Required transaction means any transaction involving a swap that is subject to the trade execution requirement in section 2(h)(8) of the Act.

(2) Execution methods.

(i) Each Required Transaction that is not a block trade as defined in § 43.2 of this chapter shall be executed on a swap execution facility in accordance with one of the following methods of execution:

(A) An Order Book as defined in § 37.3(a)(3); or

(B) A Request for Quote System, as defined in paragraph (a)(3) of this section, that operates in conjunction with an Order Book as defined in § 37.3(a)(3).

(ii) In providing either one of the execution methods set forth in paragraph (a)(2)(i)(A) or (B) of this section, a swap execution facility may for purposes of execution and communication use any means of interstate commerce, including, but not limited to, the mail, internet, email, and telephone, provided that the chosen execution method satisfies the requirements provided in § 37.3(a)(3) for Order Books or in paragraph (a)(3) of this section for Request for Quote Systems.

(3) Request for quote system means a trading system or platform in which a market participant transmits a request for a quote to buy or sell a specific instrument to no less than three market participants in the trading system or platform, to which all such market participants may respond. The three market participants shall not be affiliates of or controlled by the requester and shall not be affiliates of or controlled by each other. A swap execution facility that offers a request for quote system in connection with Required Transactions shall provide the following functionality:

(i) At the same time that the requester receives the first responsive bid or offer, the swap execution facility shall communicate to the requester any firm bid or offer pertaining to the same instrument resting on any of the swap execution facility's Order Books, as defined in § 37.3(a)(3);

(ii) The swap execution facility shall provide the requester with the ability to execute against such firm resting bids or offers along with any responsive orders; and

(iii) The swap execution facility shall ensure that its trading protocols provide each of its market participants with equal priority in receiving requests for quotes and in transmitting and displaying for execution responsive orders.

(b) Time delay requirement for required transactions on an order book -

(1) Time delay requirement. A swap execution facility shall require that a broker or dealer who seeks to either execute against its customer's order or execute two of its customers' orders against each other through the swap execution facility's Order Book, following some form of pre-arrangement or pre-negotiation of such orders, be subject to at least a 15 second time delay between the entry of those two orders into the Order Book, such that one side of the potential transaction is disclosed and made available to other market participants before the second side of the potential transaction, whether for the broker's or dealer's own account or for a second customer, is submitted for execution.

(2) Adjustment of time delay requirement. A swap execution facility may adjust the time period of the 15 second time delay requirement described in paragraph (b)(1) of this section, based upon a swap's liquidity or other product-specific considerations; however, the time delay shall be set for a sufficient period of time so that an order is exposed to the market and other market participants have a meaningful opportunity to execute against such order.

(c) Execution methods for permitted transactions.

(1) Permitted transaction means any transaction not involving a swap that is subject to the trade execution requirement in section 2(h)(8) of the Act.

(2) Execution methods. A swap execution facility may offer any method of execution for each Permitted Transaction.

Title 17 published on 2015-04-01

The following are ALL rules, proposed rules, and notices (chronologically) published in the Federal Register relating to 17 CFR Part 37 after this date.

  • 2016-09-19; vol. 81 # 181 - Monday, September 19, 2016
    1. 81 FR 64272 - System Safeguards Testing Requirements
      GPO FDSys XML | Text
      COMMODITY FUTURES TRADING COMMISSION
      Final rule.
      Effective date: This rule is effective September 19, 2016. Compliance dates: (1) Designated contract markets, swap execution facilities, and swap data repositories must be in full compliance with the vulnerability testing requirements of this rule within 180 calendar days after the effective date. (2) Designated contract markets, swap execution facilities, and swap data repositories must be in full compliance with the penetration testing requirements of this rule within one year after the effective date. Such compliance must include having conducted and completed penetration testing that complies with this rule within one year after the effective date. In the case of covered designated contract markets and swap data repositories, such compliance must include penetration testing conducted and completed by an independent contractor as required by this rule. (3) Designated contract markets, swap execution facilities, and swap data repositories must be in full compliance with the controls testing requirements of this rule within one year after the effective date. Covered designated contract markets and swap data repositories must have testing of key controls by an independent contractor as required by this rule completed within three years after the effective date. (4) Designated contract markets, swap execution facilities, and swap data repositories must be in full compliance with the security incident response plan testing requirements of this rule within 180 calendar days after the effective date. Such compliance must include having created and completed testing of a security incident response plan within 180 days after the effective date. (5) Designated contract markets, swap execution facilities, and swap data repositories must be in full compliance with the enterprise technology risk assessment requirements of this rule within one year after the effective date. Such compliance must include having completed an enterprise technology risk assessment that complies with this rule within one year after the effective date. (6) Designated contract markets, swap execution facilities, and swap data repositories must be in full compliance with the requirements of this rule for updating their business continuity-disaster recovery plans and emergency procedures within one year after the effective date. Such compliance must include having completed an update of such plans and procedures within one year after the effective date. (7) Designated contract markets must be in full compliance with the requirements of this rule respecting required production of annual total trading volume within 30 calendar days of the effective date. (8) Designated contract markets, swap execution facilities, and swap data repositories must be in full compliance with the system safeguards-related books and records requirements of this rule, which are part of such entities' current books and records requirements under current Commission regulations and statutory core principles, as of the effective date. (9) Designated contract markets, swap execution facilities, and swap data repositories must be in full compliance with all other provisions of these final rules within one year after the effective date.
      17 CFR Parts 37, 38, and 49