Handling Performance Issues in Payment Cancellation
There might be business scenarios wherein you face performance issues while cancelling a payment having a large number of payment segments. A new algorithm type named C1-CNCLPAYMT is introduced which enables you to address or overcome the performance issues faced while cancelling a payment having a large number of payment segments. It can be used independently or in conjunction with the C1-STMPREVFT algorithm. If you attach both the C1-STMPREVFT and C1-CNCLPAYMT algorithms to the FT Freeze and Payment Cancellation system events of the customer class, respectively, the system checks the following while executing the C1-STMPREVFT algorithm:
-
Whether the number of payment segments in the payment exceeds the limit specified in the Optimize Payment Cancel Process Count option type of the C1-PAYPORTAL feature configuration.
If the number of payment segments in the payment exceeds the specified limit, the system executes the C1-CNCLPAYMT algorithm. However, if the number of payment segments in the payment is less than or equal to the specified limit, the system executes the logic defined in the C1-STMPREVFT algorithm.
The C1-CNCLPAYMT algorithm cancels a payment, its corresponding payment segments, and the respective financial transactions (FTs). When a payment FT is canceled, it creates a new match event which links the original payment FT with its payment cancellation FT. The status of the new match event is set to Balanced. If the original match event is linked to any other payment FT, the status of the original match event is changed to Open. However, if the original match event is not linked to any other payment FT, the status of the original match event is changed to Canceled. While cancelling the match event, the system considers the cancel reason specified in the Match Event Cancel Reason parameter. In addition, a message is added to the canceled match event using the given message category and message number. The message is then shown in the Remarks field in the Match Event screen. This algorithm also creates FT extension records for the payment cancellation FTs.
While cancelling a payment, this algorithm considers the Batch Update Size option type of the C1-PAYPORTAL feature configuration. The Batch Update Size option type indicates the number of transactions that you want to commit in the database at once during the payment cancellation. This significantly reduces the overhead of multiple round trips, leading to improved performance, especially when dealing with payments having large number of payment segments.
This algorithm contains the following parameters:
-
Match Event Cancel Reason - Used to specify the cancel reason. The system uses the specified reason while canceling a match event. Here, you must specify a match event cancel reason which is already defined in the system.
-
Message Category - Used to specify the message category whose message you want to append to the canceled match event.
-
Message Number - Used to indicate the message that you want to append to the canceled match event.
All the above parameters are mandatory.
Related Topics
| For more information on... | See... |
|---|---|
| How to set the C1-PAYPORTAL feature configuration | Setting the C1-PAYPORTAL Feature Configuration |
Parent Topic: The Big Picture of Payments
