Payment enhancement - behavior changes between Release 9.2.1 and Release 9.3

In earlier releases, when the cashback amount is requested, the payment method is charged with order total plus the cashback amount and there was no method to reduce the cashback amount when enough funds are not available. In Release 9.3, when enough funds are not available on the Payment method, the “CashBackAmount” field on the charge record indicates the cashback amount that should be given to the customer. Eventually this field must be used to reduce the requested Cashback amount on the payment method accordingly.

In earlier releases, when the Payment Collection user exit returns the Offline Status for the Charge as true, we could not identify the offline scenario and would assume that the communication to the bank was not successful. This would imply that the charge did not occur. But there could be multiple offline scenarios. For example, the payment gateway or the Bank could be not contacted and the charge never occurred, or the payment gateway may have been contacted but no successful response was received. In Release 9.3, the Payment Collection user exit's output is enhanced to differentiate such offline scenarios. A new Boolean flag named “ChargeMayHaveOccurred" is exposed. This flag indicates that the communication with the payment gateway did not receive a successful response. If this flag is passed as true along with Offline Status as true, then the charge transaction's user exit status is set as "Invoked" instead of blank value.

How it affects you

This enhancement is used to reduce the requested cash back amount on the payment method. When the cashback amount is requested and if there is a shortage of funds, the application indicates the reduced cashback amount that should be given to the customer.

Migration strategy

None.

Automated migration processes

None.

Manual migration processes

None.