10.2.3 Unprocessed Payments

This topic describes the steps that occurs after a payment status has marked as Unprocessed Payments.

Transaction Status – Future Valued

If the transaction status is ‘Future Valued’ – in ‘Warehouse Queue’, then:
  • Recall Status at transaction is updated as Recall Requested
  • Process Status at Inbound Cancellation Browser is updated as Transaction Locked
  • Transaction is moved out of the Future Dated queue and Transaction is moved to the Inbound Cancellation Request queue
  • Transaction Status is updated as the Future Valued, last queue code as ‘FV’ and Current status as ‘Pending’ in the Inbound Cancellation Request queue
  • Queue action is logged for transaction moving out of the Future Dated and for moving to Inbound Cancellation Request queue

Transaction Status - Exception

If the transaction status is ‘Exception’, then whether the transaction is in an Internal queue or not is checked.

If the transaction is in an Internal exception queue and the last queue action authorization status is ‘Authorized’, then the following actions are taken on the transaction:
  • Recall Status at transaction is updated as Recall Requested.
  • Process Status at Inbound Cancellation Browser is updated as Transaction Locked.
  • Transaction is moved of the internal queue and is moved to the Inbound Cancellation Request queue.
  • Transaction Status is updated as the Future Valued, last queue code as ‘FV’ and Current status as ‘Pending’ in the Inbound Cancellation Request queue.
  • Queue action is logged for transaction moving out of the internal queue and for moving to Inbound Cancellation Request queue.
List of internal queues considered are:
  • Settlement Review
  • Transaction Repair
  • Processing Exception
  • Business Override
  • Authorization Limit 1
  • Authorization Limit 2
  • Exchange Rate
  • Network Cutoff
If the transaction is in an Internal exception queue and the last queue action authorization status is ‘Unauthorized’, then based on the user action cancellation processing happens:

Table 10-16 Transaction Status-User Action

User Action System Action
Delete System checks if any cancellation request is pending for the transaction. If any cancellation request found, then the following actions are taken on the transaction:
  • Recall Status at transaction is updated as Recall Requested
  • Process Status at Inbound Cancellation Browser is updated as Transaction Locked
  • Transaction is moved of the internal queue and is moved to the Inbound Cancellation Request queue
  • Transaction Status is updated as Exception, last queue code as the Internal queue code and Current status as ‘Pending’ in the Inbound Cancellation Request queue
  • Queue action is logged for transaction moving out of the internal queue and for moving to Inbound Cancellation Request queue
Authorize No changes are done to the existing processing. In case, the transaction is moving out the queue, the cancellation request check introduced in key processing steps does the cancellation processing.
List of internal queues considered are:
  • Settlement Review
  • Transaction Repair
  • Processing Exception
  • Business Override
  • Process Cutoff
  • Exchange Rate
  • Network Cutoff

If the transaction is in any external queue, then the cancellation processing is done once the transaction is out of the external queue.

The cancellation request check introduced in key processing steps of inbound transaction processing does cancellation processing as mentioned below:

Table 10-17 System Actions During Processing

Processing Steps System Action
Before Sanctions Check
  • Recall Status at transaction is updated as ‘Recall Requested’
  • Process Status at Inbound Cancellation Browser is updated as ‘Transaction Locked’
  • Transaction is moved of the internal queue and is moved to the Inbound Cancellation Request queue
  • Transaction Status is updated as ‘In Progress’, last queue code as ‘SC’ and Current status as ‘Pending’ in the Inbound Cancellation Request queue
  • Queue action is logged for transaction moving out of the internal queue and for moving to Inbound Cancellation Request queue
Before EAC Check
  • Recall Status at transaction is updated as Recall Requested
  • Process Status at Inbound Cancellation Browser is updated as Transaction Locked
  • Transaction is moved of the internal queue and is moved to the Inbound Cancellation Request queue
  • Transaction Status is updated as In Progress, last queue code as ‘EA’ and Current status as ‘Pending’ in the Inbound Cancellation Request queue
  • Queue action is logged for transaction moving out of the internal queue and for moving to Inbound Cancellation Request queue
Before Accounting
  • Recall Status at transaction is updated as Recall Requested
  • Process Status at Inbound Cancellation Browser is updated as Transaction Locked
  • Transaction is moved of the internal queue and is moved to the Inbound Cancellation Request queue
  • Transaction Status is updated as In Progress, last queue code as ‘EA’ and Current status as ‘Pending’ in the Inbound Cancellation Request queue
  • Queue action is logged for transaction moving out of the internal queue and for moving to Inbound Cancellation Request queue

In the external queues, the ‘Carry Forward’ action is not allowed if a cancellation request is found for a transaction:

Table 10-18 Transaction Status-User Action

User Action System Action Queues
Carry Forward This action is not allowed. An error message is shown to user that a cancellation request is registered for the transaction. Sanctions Check, EAC, Exchange Rate

Parent topic: Inbound Cancellation Request Processing