Support #13659
[SCP ID :##6793##] : FPX transaction error "This FPX Transaction ID was already processed" but successfully debited
| Status: | Work Completed-End life cycle | Start date: | September 20, 2023 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Zahir Abd Latif | % Done: | 100% | |
| Category: | RIB | Spent time: | - | |
| Target version: | - |
Description
Hi,
Kindly attend below request:-
Today, 1 of our staff made an FPX transaction through cuckoo apps. When he receives the push notification on OTP approval, and clicks approve, at the FPX confirmation page, error ‘This FPX Transaction ID was already processed’ popped out and the page was not directed to result page and stuck at the confirmation page. When he check on the transaction history, his account was debited and confirmation email on successful transaction also received from the merchant.
I have placed the logs at below path for your further investigation.
\\172.16.49.7\prod logs\FPX\FPX error This FPX Transaction ID was already processed
History
#1
Updated by Siti Balqis Othman 12 months ago
- Status changed from New - Begin Life Cycle to Pending UAT Deployment
- % Done changed from 0 to 100
Finding:
According to the log file, we find the customer performs approved action at the final 15 seconds interval within 60 seconds.
For your further understanding, our program will perform the following process
1) 15 seconds interval
Checking every 15 seconds within 60 seconds, which means there will be 4 cycles of checking.
The objective of checking is to check on the action status if status is approved/ rejected/ fail, the program will redirect the customer to the result page.
2) 60 seconds
Other than that, we also have a program to perform checking at 60 seconds.
The objective of the checking is to check for scenarios where no further action from the customer until reaching 60 seconds timeout.
Root cause:
As per customer action, the redirect process happens twice due to 15 seconds interval and 60 seconds checking has executed redirect action at the same time.
This happens, because the checking on pending status at 60 seconds was not in place as per expected objective.
Resolution:
Add checking to only redirect for pending status at 60 seconds method as we already check the redirect for action approved/ rejected/ fail at 15 seconds interval method.
#2
Updated by Siti Balqis Othman 8 months ago
- Status changed from Pending UAT Deployment to Code Review
#3
Updated by Siti Balqis Othman 8 months ago
- Status changed from Code Review to Development / Work In Progress
#4
Updated by Siti Balqis Othman 8 months ago
- Status changed from Development / Work In Progress to Work Completed-End life cycle
- Assignee changed from Siti Balqis Othman to Zahir Abd Latif
Hi Zahir,
Migrated to production on 10/01/2024 under migration id 217.
Kindly, help to close this ticket.