Mobile Banking
With the increased penetration and usage of smart phones, there is a need for advanced on-the-move banking, and hence to allow customers conduct financial transactions remotely. This Mobile Banking APIs offers an intuitive and secure mobile banking experience for retail and corporate customers. Soft token application has been developed for an enhanced two factor authentication thus making the usage more secure. There are different transactions and enquiries available to be performed using Chatbot application. SMS banking is another way of remote banking, where you do not need the smart phone or internet and with just a mobile network connection you can do banking. For this, the bank administrator can save different templates for the SMS for different events to be triggered.
Mobile Application Maintenance
This feature allows user to register the device and avail for push notification,bind its device for alternate login mechanisms.It allows the user to unbind its device in case the device is tampered.It also verifies the mobile device against security threats, including device tampering, bad URLs, potentially harmful apps, and fake users. These are listed below:

Validates if the mobile device/wearable is mapped to the user.

PUT/mobileClient/validateDevice

Registers a mobile device for receiving push notifications.

POST/mobileClient/pushRegistration

List registered devices for a particular user.

GET/mobileClient/registeredDevices

Unbinds and deletes user's mobile devices/wearables against the user.

DELETE/mobileClient/os/{os}

Fetches the registered mobile devices/wearbles for a user id.

GET/mobileClient/registeredDevices/{userId}

Deregisters mobile device for push notifications by supplying OS.

DELETE/mobileClient/pushToken/os/{os}

Lists mobile devices registered for push notifications.

GET/mobileClient/registeredPushToken

Lists mobile devices registered for push notifications by supplying user id.

GET/mobileClient/registeredPushToken/{userId}

Registers the mobile device/wearable with parameters like unique id, make, version, OS. Device registration are used when user sets up alternate login mechanisms in mobile app.

POST/mobileClient

Fetches details of the mobile device/wearable by supplying device id.

GET/mobileClient/{deviceId}

Verifies the mobile device against security threats, including device tampering, bad URLs, potentially harmful apps, and fake users.

POST/mobileClient/verify