Mobile Banking Integration

i-Con enables banks to give their clients the ability to perform transactions from mobile devices.

The user can initiate a transaction from the institution’s application on their mobile device which is then received by i-Con. i-Con then routes the transaction to the various systems, the core banking system and Switches, in real-time.

i-Con invokes the Reserve Bank web services and validates the mobile number.

Case Example 1
A Bank allows users to do transactions from a mobile device. In this interface a transaction was initiated from the mobile device and passed to i-Con via a web service. From i-Con the transaction was routed to the various systems, namely T24, Postillion and the Reserve Bank.

The interface utilised Microsoft Message Queues (MSMQ), Web service host components, a scheduler and other custom components.

i-Con invoked the Reserve Bank web services and passed the mobile number that was extracted from the XML being passed by either mobile, IB or Teller channels. For the IB/Teller channel an OFS message was constructed for response to T24 from the Bankers Association.

Case Example 2
A Bank opened up a new channel to enable their clients to do banking from their mobile devices. Client banking needed to be catered for on devices that support platforms like USSD, Android, iOS and Blackberry. The frontend was available, however it was designed to consume a certain set of service contracts and could not integrate into the complexity that the backend presented. Which, in this case, was Oracles’ Flexcube Direct Banking (FCDB).

The Bank required a solution where they could integrate into FCDB using a Contract-First approach. The solution was solved using i-Con’s Web Service Host component and was configured based on the service contracts provided from the Mobile development team. i-Con integrated into FCDB by mapping the contract values to the required values expected by FCDB.

Using components like the Oracle, Microsoft Message Queues, WebServiceHost, WebService, RESTFull service, Custom components and the XmlTranslator component, the solution was delivered fast and efficiently.