Message Reject (3)

The reject message should be issued when a message is received but cannot be properly processed due to a session-level rule violation. An example of when a reject may be appropriate would be the receipt of a message with invalid basic data which successfully passes de-encryption, CheckSum and BodyLength checks.

Added in protocol FIX.2.7

See in: FIX.4.0, FIX.4.1, FIX.4.2, FIX.4.3, FIX.4.4, FIX.5.0SP1, FIX.5.0SP2, FIX.5.0SP2 EP240, FIXT.1.1.

Field or Component Name Description Is Required Added Is Deprecated
Block StandardHeader MsgType = 3 Y FIX.2.7
45 RefSeqNum MsgSeqNum of rejected message Y FIX.2.7
371 RefTagID The tag number of the FIX field being referenced. FIX.4.2
372 RefMsgType The MsgType of the FIX message being referenced. FIX.4.2
373 SessionRejectReason Code to identify reason for a session-level Reject message. FIX.4.2
58 Text Where possible, message to explain reason for rejection FIX.2.7
354 EncodedTextLen Must be set if EncodedText (355) field is specified and must immediately precede it. FIX.4.2
355 EncodedText Encoded (non-ASCII characters) representation of the Text (58) field in the encoded format specified via the MessageEncoding (347) field. FIX.4.2
Block StandardTrailer Y FIX.2.7