On authorization of the Interim action, the system does the below listed processing steps:

• A gSRP Response message is generated if the recall request is a gSRP request message. Otherwise, a non-gSRP MT n96 response message is generated
• A Recall response is logged to show in the Inbound Transaction view – Under Exception – screen
• Queue action is logged for the Interim action against the transaction reference

The details of the gSRP response message / non-gpi MT n96 response message are explained in the following section

On authorization of the Accept action, the following changes are done:

• A gSRP Response message is generated if the recall request is a gSRP request message. Otherwise, a non-gSRP MT n96 response message is generated
• A gCCT reject response message is generated if the recall request is a gSRP request and last queue code is not blank
• Inbound Cancellation queue level Current Status field is updated as ‘Accepted’
• Last Response action at Cancellation browser is updated as ‘Accepted’
• Recall status at transaction is updated as ‘Accepted’
• Recall response is logged to show in the Inbound Transaction view – Under Exception – screen
• Transaction is moved out of the cancellation request queue
• Queue action is logged for the ‘Accepted’ action at the transaction level
• Cancellation processing for the transaction initiated if the transaction status is not Processed / Cancelled / Seized [i.e. Transaction Status is ‘In Progress’]

On authorization of the Reject action, the following changes are done:

• A gSRP Response message if the recall request is a gSRP request message is generated. Otherwise, a non-gSRP MT n96 response message is generated.
• Inbound Cancellation queue level Current Status field is updated as ‘Rejected’
• Last Response action at Cancellation browser is updated as ‘Rejected’
• Recall status at transaction is updated as ‘Rejected’.
• Recall response is logged to show in the Inbound Transaction view – Under Exception – screen
• Transaction is moved out of the queue
• Queue action is logged for the ‘Reject’ action at the transaction level
• If the transaction has not been processed [Last queue code is not blank]
  • Transaction is reprocessed same as future valued transaction processing done on the value date. During reprocessing, FX Request is not resent if Reject action was taken on same day.
  • Value date/Activation date is re-derived.