It seems like the world is going wireless these days, including the banking and trading industries. Wireless banking and trading is still in its infancy stage, and one must keep up with new products, new technological breakthroughs, and developmental aids to help with transitions from the old to the new. Standards are changing for APIs (interfaces), gateways, security methods, screens, operating systems, browsers, handheld devices, and different bandwidth requirements.
All these changes reveal risks to systems and consumers. Wireless banking and trading can be risky, lengthy, and complicated to develop and use. Interfaces must be able to connect backend systems already in place, and application servers have to accommodate all protocols and devices. This is a must because manufacturers do not know which device users plan to use. This is true for application servers – they must be able to communicate with all gateways like WAP, GSM, two-way pagers, and other devices. Wireless networks function independently, and many devices, especially handheld, utilize their own standards to deliver data over data channels. Users personalize by customizing screens, alerts, notifications, and messaging devices easily. Systems should be capable of sending notices to users as needed regardless of devices types and brands. Platform selection is important and challenging for banking institutions and should not be done independently. Platforms should have the ability to integrate easily and reliably with new gateways to the backend or existing system. Some banking institutions outsource the development, implementation, and hosting of their systems and some may choose to use a third party to implement and host their system. All are viable options. Continue reading “Security Issues – Wireless Banking & Trading”