Support #4603
SCP : ##2350## : IBG Trx Failed & Account Debited
| Status: | Work Completed-End life cycle | Start date: | August 05, 2014 | |
|---|---|---|---|---|
| Priority: | Urgent | Due date: | ||
| Assignee: |  Hafizudin MD | % Done: | 100% | |
| Category: | MY IBG | Spent time: | - | |
| Target version: | - |
Description
Please attend below request
We received 2 complaints from customers regarding their IBG transactions which perform today were unsuccessful and their accounts have been debited. Upon checking in CORUS, the reason given was due to "Failed to Transfer Fund". Please assist to further check this issue immediately & attached the details of the transactions for your reference.
History
#1
Updated by Ahmad Hazri about 10 years ago
- Assignee changed from Hafizudin MD to Siti Norahayu Mohd Desa
#2
Updated by Ahmad Hazri about 10 years ago
- Assignee changed from Siti Norahayu Mohd Desa to Hafizudin MD
#3
Updated by Nurul Akmal about 10 years ago
Hi Hafiz,
There are no update on this cases until today, please help to follow up to see whether we can closed this case or update the status.
#4
Updated by Hafizudin MD about 10 years ago
we suspect that the issue occurred is because of ESB. This is due to error Connection has been administratively disabled & charges return: 9999.
also found the similar error at same time (10:54:36 AM) on other transaction response.
<Aug 5, 2014 10:54:36 AM MYT> <Error> <ALSB Logging> <000000> < [Logging, Logging_response, Outbound Error Logging, RESPONSE] <Msg>
<MsgHeader>
<ErrorMessage>Connection has been administratively disabled. Try later.</ErrorMessage>
<ServicesID>41</ServicesID>
<ReferenceNo>20140805105102765</ReferenceNo>
<Version>3.0</Version>
<TranCode>905</TranCode>
<ResponseCode>9999</ResponseCode>
</MsgHeader>
<MsgBody>
<Records/>
</MsgBody>
</Msg>>
#5
Updated by Zahir Abd Latif almost 10 years ago
- Status changed from New - Begin Life Cycle to Work Completed-End life cycle
- % Done changed from 0 to 100
The Problem resolved after IT restart ESB to establish connection from Internet Banking to Phoenix Core Banking. Root cause is IB session disconnected from/to Phoenix Core Banking.
Recommend to close the case.