Use this search bar to search topics within the CME ClearPort API.
| Page Tree Search | ||
|---|---|---|
|
| Excerpt |
|---|
This page describes exception workflows associated with single sided trades submitted for affirmation and clearing. These are the alternate uses cases where a trade submitted for affirmation and clearing can be rejected by CME ClearPort or can be cancelled before it is cleared or voided after it is cleared. The variation in workflows based on the transport used for submitting these trades is also described here. |
| Table of Contents |
|---|
Pre-Match - Exception Scenarios
Trade Rejected by CME ClearPort
In this scenario, two single-sided trades are submitted using MQ or HTTP as a transport by two different submitters, and CME ClearPort rejects one of the trade submissions.
Unsuccessful Match - Trade Pending
In this scenario, both sides have submitted a single sided trade using MQ or HTTP and a match did not occur.
| Info |
|---|
The API does not automatically send an unmatched notification using. The submitter will have to query CME ClearPort to determine the status of the trade |
Trade Rejected by Counterparty
In this scenario, one side submitted a single sided trade using MQ or HTTP. The other side sends a request for alleged trades and rejects the alleged trade.
| Info |
|---|
The API does not automatically send out trades alleged to the counterparty. The submitter will have to query CME ClearPort by sending a request for alleged trades. |
Trade Cancelled Before Match
In this scenario, one side submitted a single sided trade using MQ or HTTP. The submitter cancelled the trade before the trade is matched.
Post-Match - Exception Scenario
Trade Void Submission - Successfully Voided
| Info |
|---|
Trade submitted using the single sided trade submission cannot be voided using the API. The submitter will have to call the Global Command Center (GCC) to void a trade. |