Transactional Committal Portal and Database Resolution Controller For Mobile Banking Transactions

Mobile banking has become a bulging feature in banking operations in Nigeria as more and more banks are accepting this technology to provide the growing population of their clients with fast, accessible, reliable, and quality services. However, there are numerous problems associated with mobile banking: non-committals and non-reversal is the utmost. In this paper, a few scenarios such as Debit without dispense, Debit without Committal, and Debit without credit were considered. Information has it that it takes some banks 24hrs to 72hrs or more to reverse failed transactions, and some bank customers have forfeited their money through this means. The problem therefore can be narrowed to outright failures due to timeout in the network during committals into a database or failures to resolve transactions since there should be no gain without a loss or vice versa. A controller bridge was developed to mirror or sniff mobile transactions from bank to bank; internally (bank A to A) or externally (bank A to B), ascertain the success (full committals) of the transactions, or initiate a resolution if a transaction fails. The Waterfall software development model was adopted for use. The software bridge was tested by simulation using mockup data. The system was developed with PHP, HTML, CSS, JavaScript (Ajax and jQuery), and Bootstrap framework. The implementation was done on a local host with two different browsers housing the banks and the bridge residing in any of them. The results in time concerning sniffing, confirmation, and resolution were outstanding. Implying that, the bridge can improve transactional resolutions faster than ever. Banks should be encouraged to adopt or integrated this new committal bridge into their existing system so that failed transactions can be resolved within a minutes.