Following is the list of exceptions/limitations of the testing tool

1. Direct Reversal of an Indirect transaction
2. Multiple Payment Hold Assessments/Reversals
3. Payment not allocated to Phone Pay Fee

1. Direct Reversal of an ‘Indirect’ transaction

   An Indirect transaction is one that is created by a different transaction. For example, FNSF is an indirect transaction created by the PAYMENT_VOID transaction. The tool replicates the PAYMENT_VOID transaction that in turn creates the FNSF. Along the same lines, reversal of the PAYMENT_VOID transaction will result in the reversal of the FNSF transaction (This is normal Ofsll processing) and will be replicated by the tool.

   However when the FNSF transaction is reversed directly, by using the Reverse button on the Transactions screen, the tool is unable to replicate that.

   Another example is the PAYMENT_NONCASH created by modifying the PAYMENT_ERROR transaction on the Payment Maintenance screen. The non-cash transaction is an indirect transaction and directly reversing it or further modifying it will not get replicated in the Test environment. To summarize direct reversal/modification of the child transaction is not replicated.

   Note, the above restriction applies only for the same dataset. If the database is refreshed after the creation of the child transaction and before its direct reversal, the tool replicates the reversal.

2. Multiple Payment Hold Assessment/Reversals

   Since the tool is not recording the call activities, multiple payment holds applied or removed on the same day is NOT replicated. To paraphrase, the existence/absence of the Payment Hold condition will match that in production, however intermediate changes will not be reflected.

   Examples

• Scenario 1
  
• Scenario 2 – This scenario results in an exception due to mismatch of balances