Blaze mobile banking using a non-browser based application
A method and system for customizing a mobile application running on a mobile communication device of a user. In one implementation, the method includes providing the mobile application to the mobile communication device of the user, the mobile application having a generic platform; determining a special interest group (SIG) that is affiliated with the user; and customizing the generic platform of the mobile application based on information specific to the special interest group (SIG) that is affiliated with the user.
1. A method for processing a mobile banking transaction using a mobile device, comprising:
receiving, at a non-browser based application information related to a userID and information related to a password, wherein the non-browser based application is a mobile operating system platform based mobile application with a graphical user interface that is preinstalled or downloaded and installed on the mobile device, wherein the graphical user interface includes a graphical icon, the mobile device including a mobile device display, a mobile device processor, a mobile device memory, a mobile device radio transceiver that supports voice and data interactions through a first communication channel, and a mobile device wireless fidelity (Wi-Fi) transceiver;
transmitting, by the non-browser based application, the information related to the userID and the information related to the password to a remote management server which authenticates the user;
after user authentication, receiving, at the non-browser based application, a request for a mobile banking transaction, wherein the non-browser based application receives the request for the mobile banking transaction through user input via the mobile device display;
after receiving the request for the mobile banking transaction, transmitting, from the non-browser based application to the remote management server, the request for the mobile banking transaction;
after the request for the mobile banking transaction has been processed by the remote management server using a payment method that corresponds to the userID, receiving a digital artifact from the remote management server at the non-browser based application, wherein the payment method is maintained at the remote management server; and
displaying the digital artifact within the non-browser based application.
2. The method of claim 1 , wherein the request for the mobile banking transaction comprises one of bill pay, funds transfer, depositing a check, viewing transaction history, checking account balance, withdrawing funds from an ATM.
3. The method of claim 1 , where the payment method is a bank account, credit card, debit card, or prepaid card.
4. The method of claim 1 , further wherein no sensitive data is stored on the mobile device.
5. The method of claim 4 , wherein the sensitive data is information related to the payment method.
6. The method of claim 1 , wherein the digital artifact comprises one of an account balance, last number of transactions, receipt, advertisement, coupon, ticket, media, or content.
7. The method of claim 1 , wherein the non-browser based application enables the user to access the digital artifact even if the mobile device is not connected a wireless network.
8. The method of claim 1 , further wherein the non-browser based application is operative even if the mobile device is not connected a wireless network.
9. The method of claim 1 , wherein the non-browser based application receives the digital artifact through a connection of the mobile device to a wireless network;
the non-browser based application displays the digital artifact while the mobile device maintains the connection to the wireless network; and
the method further comprises:
losing the connection of the mobile device to the wireless network while the non-browser based application displays the digital artifact; and
after losing the connection, continuing to display the digital artifact within the non-browser based application.
10. The method of claim 1 , further wherein the non-browser based application is not Short Messaging Service (SMS).
11. The method of claim 1 , further wherein the remote management server is configured to store the userID for a user for a plurality of mobile devices and a plurality of payment methods, and further wherein a configuration means the remote management server scales.
12. The method of claim 1 , further wherein the information related to the password is information related to a Personal Identification Number (PIN).
13. The method of claim 1 , further, wherein the information related to the password is information related to biometric data.
14. The method of claim 1 , further wherein the remote management server sends the digital artifact to the non-browser based application based on the geographical location of the mobile device.
15. The method of claim 1 , further wherein the non-browser based application monitors for access to a wireless network and automatically reconnects to the wireless network when the wireless network is available.
16. A mobile device for processing a mobile banking transaction, the mobile device comprising:
a mobile device input interface configured to:
receive, at a non-browser based application information related to a userID and information related to a password, wherein the non-browser based application is a mobile operating system platform based mobile application with a graphical user interface that is preinstalled or downloaded and installed on the mobile device, wherein the graphical user interface includes a graphical icon, the mobile device including a mobile device display, a mobile device processor, a mobile device memory, a mobile device radio transceiver that supports voice and data interactions through a first communication channel and a mobile device wireless fidelity (Wi-Fi) transceiver;
after user authentication, receive, at the non-browser based application, a request for the mobile banking transaction, wherein the non-browser based application receives the request for the mobile banking transaction through user input via the mobile device display;
after the request for the mobile banking transaction has been processed by the remote management server using a payment method that corresponds to the userID, receive a digital artifact from the remote management server at the non-browser based application, wherein the payment method is maintained at the remote management server;
a mobile device output interface configured to
transmit the information related to the userID and the information related to the password to the remote management server which authenticates the user;
after receiving the request for the mobile banking transaction, transmit, from the non-browser based application to the remote management server, the request for the mobile banking transaction.
17. The mobile device of claim 16 , wherein the request for the mobile banking transaction comprises one of bill pay, funds transfer, depositing a check, viewing transaction history, checking account balance, withdrawing funds from an ATM.
18. The mobile device of claim 16 , where the payment method is a bank account, credit card, debit card, or prepaid card.
19. The mobile device of claim 16 , further wherein no sensitive data is stored on the mobile device.
20. The mobile device of claim 19 , wherein the sensitive data is information related to the payment method.
21. The mobile device of claim 16 , wherein the digital artifact comprises one of an account balance, last number of transactions, receipt, advertisement, coupon, ticket, media, or content.
22. The mobile device of claim 16 , wherein the non-browser based application enables the user to access the digital artifact even if the mobile device is not connected a wireless network.
23. The mobile device of claim 16 , further wherein the non-browser based application is operative even if the mobile device is not connected a wireless network.
24. The mobile device of claim 16 , wherein the non-browser based application receives the digital artifact through a connection of the mobile device to a wireless network; the non-browser based application displays the digital artifact while the mobile device maintains the connection to the wireless network; and
the method further comprises:
losing the connection of the mobile device to the wireless network while the non-browser based application displays the digital artifact; and
after losing the connection, continuing to display the digital artifact within the non-browser based application.
25. The mobile device of claim 16 , further wherein the non-browser based application is not Short Messaging Service (SMS).
26. The mobile device of claim 16 , further wherein the remote management server is configured to store the userID for a user for a plurality of mobile devices and a plurality of payment methods, and further wherein a configuration means the remote management server scales.
27. The mobile device of claim 16 , further wherein the information related to the password is information related to a personal identification number (PIN).
28. The mobile device of claim 16 , further, wherein the information related to the password is information related to biometric data.
29. The mobile device of claim 16 , wherein the remote management server sends the digital artifact to the non-browser based application based on the geographical location of the mobile device.
30. The mobile device of claim 16 , further wherein the non-browser based application monitors for access to a wireless network and automatically reconnects to the wireless network when the wireless network is available.