PaymentExceptionChange

A payment exception change event is sent when a transaction in the FTM database is updated from being an exception to not being an exception (the exception column in the payment table changes from 1 to 0). Configure the Transaction Server to send the Distribution engine a paymentReady message when a transaction is updated by configuring a PaymentExceptionChange event in the Scheduler.xml file:

<EVENT>
   <NAME>Distribution Profile - Payment Ready</NAME>
   <TYPE>PaymentExceptionChange</TYPE>
   <EXEC>
      com.ibm.paydir.ima.txsvr.event.appbridge.PaymentReadyEventHandler
   </EXEC>
   <PARAMETER name="msgType">paymentReady</PARAMETER>
   <PARAMETER name="parmFileName">DistributionProfile.properties</PARAMETER>
   <PARAMETER name="minPresStates">BALANCED</PARAMETER>
</EVENT>

Configure the event in the scheduler XML file so that the class is called when the event occurs. The class name is:

com.ibm.paydir.ima.txsvr.event.appbridge.PaymentReadyEventHandler

The PaymentReadyEventHandler class creates the paymentReady message to be sent to the Distribution engine. When the Distribution engine receives a paymentReady message, it maps the transaction to an outbound bundle if the transaction is eligible. The msgType parameter should be set to paymentReady. The parmFileName parameter defines the properties necessary for sending a message to the Distribution engine. For more information about using parameter files, see Distribution Parameter File. The minPresStates parameter defines the state(s) the transaction’s batch (ICL) must be in before a message is sent to the Distribution engine. Using the above example, if a transaction is updated before its batch (ICL) is balanced, a message is not sent. If the transaction is updated and its batch (ICL) is balanced, a message is sent to Distribution.

Note: Do not use the payment exception change event if creating administrative return item transmissions and running Image Compliance Suspect Image Review or Duplicate Detect. These components do not call the Business Rules Server to assign return reasons and endpoints. Exception items handled by Suspect Image Review or Duplicate Detect do not immediately have the correct attributes. Configure a presentment state change event to run after AutoAdjust assigns return reasons and endpoints to the adjusted items.