ExecutionAcknowledgement/ 35=BN is commonly supported by most ECNs to ACK or NACK a client's ExecutionReportand is considered the end of the trade life cycle in the maker workflow(, where the MF Whisperer clients are the market makers).
However, Integral is an anomaly and does not send anExecutionAcknowledgementto notify the client that their their ExecutionReportis accepted Acceptedor rejectedRejected.
To normalise the order lifecycle in the maker workflow, MarketFactory will introduce a synthetic synthetic ExecutionAcknowledgementin the maker gateways, if the venue API natively does not support the message.
In order to address a normalisation gap in the maker workflow order lifecycle, in the absence of a venue ACK in response to our client's s ExecutionReport, MarketFactory will introduce a synthetic synthetic ExecutionAcknowledgementin maker gateways.
Timeline
- UAT - MarketFactory will introduce the synthetic synthetic ExecutionAcknowledgementmessage for clients to test the affected venues in UAT.
- PROD - Whisperer release 2025.08.XX.WE to expose the synthetic synthetic ExecutionAcknowledgementchange in PROD.
Whisperer Client Impact
...
Whisperer clients trading on Integral will see the following change:
In response to a client client ExecutionReportwith ExecType = Filled or Rejected, a synthetic ExecutionAcknowledgement/ 35=BN will be sent to the client with ExecAckStatus= Accepted.
A syntheticsynthetic ExecutionAcknowledgementwill not be sent to the client in the following scenarios:
Whisperer gateway received a replayed replayed ExecutionReportfrom a client with PossDupFlag= Y during the recovery/ replay at session synchronisation.
Integral did not receive the client ExecutionReportby the end of the preconfigured OrderTimeout interval. In this scenario, the client will receive an OrderTimeout/ 35=OT.
The client sent an an ExecutionReportafter it received an OrderTimeout. In this scenario, the client will receive an ExecutionAck ExecutionAcknowledgementwith IsSyntheticflag set to N.