Support #12688
[SCP ID :##6065##] : Agrobank FPX Success Rate issue
| Status: | Work Completed-End life cycle | Start date: | December 15, 2021 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Stephanie Sufrapto | % Done: | 100% | |
| Category: | RIB | Spent time: | - | |
| Target version: | - |
Description
Hi,
Kindly attend below request:-
We received information from DBD team that current FPX success rate was not meet paynet expectation. Below is top 3 error code that contributed to the caused of the lowest success rate.
Need your help to check at AGRONet side as imocha confirm that they did not received any request from front end to initiate transaction caused transaction failed / timeout.
We are in progress try restore the previous log file for our checking. If you need further information please let us know.
fpxTransId-76-31102021.txt 
(13.2 KB)
History
#1
Updated by Stephanie Sufrapto over 2 years ago
- Status changed from New - Begin Life Cycle to Work Completed-End life cycle
- % Done changed from 0 to 100
16/12/2021
Based on the email from iMocha, there are 2 causes of 1A error.
- IB to sent 1A in request
- IB team initiated the AR message and there was no further action for the transaction requested from the IB team. As a result, FPX engine timeout the transaction based on the last state of the transaction. If the last state of the transaction is not PAYMENTFPX_CREATE, PAYMENTFPX_CONFIRM and PAYMENTFPX_SAVE then it will be error code 1A.
I have checked the log dated 04/11/2021 and 05/11/2021 provided by ITD, total of transactions IB sent with error code 1A is 3 at both RIB and BIB Server.
As error code 76. Informed to us it was caused by IB didn’t calling the AR message.
If you refer to the chart below. AR message is called before showing the login page.
We suspect the sticky session is the cause of these issues. These issues should be reduced when we implement Sticky session fixes at the websphere on 12 November 2021.