Support #5959
[SCP ID :##2967##] : IBG Charges for Failed Trx.
Status: | Closed - End of life cycle | Start date: | February 03, 2016 | |
---|---|---|---|---|
Priority: | High | Due date: | ||
Assignee: | Zahir Abd Latif | % Done: | 100% | |
Category: | MY IBG | Spent time: | - | |
Target version: | - |
Description
Hi,
Kindly attend below request:
Please help to investigate on IBG charges imposed on the failed IBG transaction
Based on Corus Report dated 31/01/2016, noticed that one of the IBG trx performed on 31/01/2016 was failed with status “Charge Failed”. Upon further checking at BVMC Report, this trx was not captured at all. However, in Phoenix Report there’s additional IBG Charges for this particular transaction.
Details of the failed transaction as per below:
Reference No = 2016013119372971
IBG Transfer Amount = RM3000.00
IBG charges = 0.10
Status = "Charge Failed"
Date / time of transaction = 31 Jan 2016, 18:34
Please investigate and revert accordingly.
History
#1 Updated by Zahir Abd Latif over 8 years ago
- Tracker changed from Task to Support
#2 Updated by Zahir Abd Latif over 8 years ago
- Status changed from New - Begin Life Cycle to Closed - End of life cycle
- Assignee changed from Hafizudin MD to Zahir Abd Latif
- % Done changed from 0 to 100
Update by Hafiz, Feb 18, 2016 11:30 AM:-
Salam Ashikin. From our investigation. we found esb didn't return message for charges. If esb didn't return message or session time out. IBG system will set that transaction as failed and not revert those transaction because the status of transaction is unknown. Log JNDI: PhoenixDS exec atm.dbo.psp_ex_main3 41,'20160131','20160131',null,'Y',null,'N','20160131183434905',null,'N','N',null,null,null,905,'MYR',null,'SV', '102','001102038188','GL','102','01-01-001-01-01-41200010',0.10,null,null,null,'20160131',null,null,null,'IB IBG Fee:Mohammed M Mohammed, to Mohammed, -',null,null,null,'3.0',1,'DP',null,null,1,null,null,null,'MYR',null,null,null,null,null, null,null,152,null,null,null,null,null,null,null,null,null,null,null,0
Issue closed in SCP.