Handling Business Reject Messages

The exchange can send the Business Message Reject message to reject an application-level message which fulfills session-level rules but fails the business rules.

This message is reported via the InboundApplicationMessage event.

Note

When the sequence number of the rejected message is absent in the received "Business Message Reject" message, this indicates the exchange did not increment the message sequence number of the rejected application-level message and: - The client system should not increment the message sequence number of the next business message to be sent - If the client system increments the message sequence number of the next application-level message to be sent, a NotApplied message will be sent to the customer to let them know that the sequence number has not been applied by the exchange.

Example

session.InboundApplicationMessage += (sender, args) =>
{
    const int BusinessRejectTemplateId = 521;
    const int BusinessRejectReasonTag = 380;
    const int RefSeqNumTag = 45;
    if (args.Message.TemplateID == BusinessRejectTemplateId)
    {
        Console.WriteLine($"Received: {args.Message}");
        Console.WriteLine($"\tReject reason: {args.Message.GetUnsignedShort(BusinessRejectReasonTag)}");

        if (args.Message.Contains(RefSeqNumTag))
        {
            Console.WriteLine($"\tThe sequence number of the rejected message is {args.Message.GetUnsignedInteger(RefSeqNumTag)}");
        }
        else
        {
            // If the sequence number of the rejected message is absent,
            // the client system does not need to increment the sequence number of the next business message to be sent.
            ((Session)sender).OutSeqNum--;
        }
    }
};