Locking Payments

When a user selects a batch (ICL) to update, Transaction Correction and Reconciliation locks the inbound batch (ICL). The transactions within the batch (ICL) are no longer eligible for outbound distribution processing and Distribution no longer maps transactions from that batch (ICL). The transactions will not appear on the eligible transactions pages. Transactions that are already mapped to an outbound transmissions are not affected by the lock. They are affected only when the user tries to edit or delete them.

Transaction Correction and Reconciliation unlocks the inbound batch (ICL) when the user has completed their changes. Any eligible transactions in the batch (ICL) are once again available for outbound distribution processing.

Distribution will automatically process any eligible transactions when it receives a PresentmentStateChange event after TCR unlocks a batch (ICL). The following example shows the event configuration in the Transaction Server Scheduler.xml file.

<EVENT>
   <NAME>Distribution Profile - States Reached</NAME>
   <TYPE>PresentmentStateChange</TYPE>
   <EXEC>
      com.ibm.paydir.ima.txsvr.event.appbridge.PresentmentReadyEventHandler
   </EXEC>
   <PARAMETER name="msgType">presStatesReached</PARAMETER>
   <PARAMETER name="parmFileName">
      ../profiles/DistributionProfile.properties
   </PARAMETER>
   <PARAMETER name="presStates1">!LOCKED</PARAMETER>
</EVENT>

In this example, a presStatesReached message is sent to Distribution whenever an inbound batch (ICL) is unlocked. Distribution then searches the inbound batch (ICL) for any eligible transactions that need to be mapped to an outbound transmission.