Method and system for mobile banking using a server

Abstract

A method for transmitting data between a mobile communication device and a server. The method includes running a mobile application on the mobile communication device. The mobile application is hosted on the mobile communication device through the server as a Software as a Service (SaaS). The method further includes transmitting data associated with the mobile application between the mobile communication device and the server, in which transmission of the data between the mobile communication device and the server is monitored through the server.

Claims

1. A method for conducting a mobile banking transaction using a server, the method comprising: maintaining, at the server, a payment method; receiving, at the server, user input login information from a non-browser based application stored on a mobile device, wherein the non-browser based application stored on the mobile device receives the user input login information via a mobile device display of the mobile device, wherein the non-browser based application is a mobile operating system platform based application with a graphical user interface that is downloaded and installed on the mobile device, wherein the graphical user interface includes a graphical icon; the mobile device including the mobile device display, a mobile device memory, a mobile device processor, a mobile device radio transceiver that supports voice and data interactions through a first wireless communication channel using at least one of GSM or CDMA, and a mobile device wireless fidelity (Wi-Fi) interface; upon receipt of the user input login information, authenticating at the server a user of the mobile device associated with the user input login information prior to conducting the mobile banking transaction; receiving at the server user input from the non-browser based application to initiate a mobile banking transaction request including an identification code associated with the user, wherein the non-browser based application stored on the mobile device receives user input via the mobile device display of the mobile device; after receiving the mobile banking transaction request including the identification code associated with the user, processing at the server the mobile banking transaction using the payment method that corresponds to the identification code associated with the user; and after the mobile banking transaction has been processed, sending, from the server, a digital artifact to the non-browser based application.

2. The method of claim 1, wherein the mobile banking transaction comprises a bill payment.

3. The method of claim 1, wherein the mobile banking transaction comprises a funds transfer.

4. The method of claim 1, wherein the mobile banking transaction comprises loading funds.

5. The method of claim 1, wherein the digital artifact is a receipt, ticket, coupon, advertisement, or content.

6. The method of claim 1, wherein the user input login information includes biometric data or a personal identification number (PIN).

7. The method of claim 1, further wherein the digital artifact is cached on the mobile communication device and can be accessed by the non-browser based application when there is no network connection.

8. The method of claim 1, wherein upon the condition that the mobile device loses connection with a wireless network, the non-browser based application monitors for access to the wireless network and automatically reconnects to the wireless network when the wireless network is available.

9. The method of claim 1, further wherein no sensitive data is stored on the mobile device, wherein the sensitive data comprises at least one of information related to the payment method, information related to a PIN associated with the user input login information, and information related to an expiration dates associated with the payment method.

10. The method of claim 1, further wherein the non-browser based application shuts down due to a period of inactivity, wherein the period of inactivity means the non-browser based application has not received input at the non-browser based application.

11. The method of claim 1, further wherein the server is configured to store a single identification code associated with the user.

12. A system for conducting a mobile banking transaction using a server comprising: a mobile device including; a mobile device display; a mobile device processor; a mobile device memory that maintains a non-browser based application, wherein the non-browser based application is a mobile operating system platform based application with a graphical user interface that is downloaded and installed on the mobile device, wherein the graphical user interface includes a graphical icon; a mobile device radio transceiver that supports voice and data interactions through a first wireless communication channel using at least one of GSM or CDMA; and a mobile device wireless fidelity (Wi-Fi) interface. the server including: a server memory that maintains a payment method; a server transceiver that receives user input login information from a the non-browser based application stored on a the mobile device, wherein the non-browser based application stored on the mobile device receives the user input login information via the mobile device display of the mobile device; and receives user input into from the non-browser based application to initiate a mobile banking transaction request including an identification code associated with the user, wherein the non-browser based application stored on the mobile device receives the user input via the mobile device display of the mobile device; and after the mobile banking transaction has been processed, sends a digital artifact to the non-browser based application; a server processor that upon receipt of the user input login information, authenticates a user of the mobile device associated with the user input login information prior to conducting the mobile banking transaction; and after receiving the mobile banking transaction request including the identification code associated with the user, processes the mobile banking transaction using the payment method that corresponds to the identification code associated with the user.

13. The system of claim 12, wherein the mobile banking transaction comprises a bill payment.

14. The system of claim 12, wherein the mobile banking transaction comprises a funds transfer.

15. The system of claim 12, wherein the mobile banking transaction comprises loading funds.

16. The system of claim 12, wherein the digital artifact is a receipt, ticket, coupon, advertisement, or content.

17. The system of claim 12, wherein the user input login information includes biometric data or a personal identification number (PIN).

18. The system of claim 12, further wherein the digital artifact is cached on the mobile communication device and can be accessed by the non-browser based application when there is no network connection.

19. The system of claim 12, wherein upon the condition that the mobile device loses connection with a wireless network, the non-browser based application monitors for access to the wireless network and automatically reconnects to the wireless network when the wireless network is available.

20. The system of claim 12, further wherein no sensitive data is stored on the mobile device, wherein the sensitive data comprises at least one of information related to the payment method, information related to a PIN associated with the user input login information, and information related to an expiration dates associated with the payment method.

21. The system of claim 12, further wherein the non-browser based application shuts down due to a period of inactivity, wherein the period of inactivity means the non-browser based application has not received input at the non-browser based application.

22. The system of claim 12, further wherein the server is configured to store a single identification code associated with the user.

23. A non-transitory computer readable medium for conducting a mobile banking transaction using a server, comprising: computer code for maintaining, at the server, a payment method; computer code for receiving, at the server, user input login information from a non-browser based application stored on a mobile device, wherein the non-browser based application stored on the mobile device receives the user input login information via a mobile device display of the mobile device; ,wherein the non-browser based application is a mobile operating system platform based application with a graphical user interface that is downloaded and installed on the mobile device, wherein the graphical user interface includes a graphical icon, the mobile device including the mobile device display, a mobile device memory, a mobile device processor, a mobile device radio transceiver that supports voice and data interactions through a first wireless communication channel using at least one of GSM or CDMA, and a mobile device wireless fidelity (Wi-Fi) interface; computer code for upon receipt of the user input login information, authenticating at the server, a user of the mobile device associated with the user input login information prior to conducting the mobile banking transaction; computer code for receiving at the server, user input from non-browser based application to initiate a mobile banking transaction request including an identification code associated with the user, wherein the non-browser based application stored on the mobile device receives the user input via a mobile device display of the mobile device; computer code for after receiving the mobile banking transaction request including the identification code associated with the user, processing at the server the mobile banking transaction using the payment method that corresponds to the identification code associated with the user; and computer code for after the mobile banking transaction has been processed, sending, from the server, a digital artifact to the non-browser based application.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 illustrates one implementation of a block diagram of a communication system including a wireless mobile communication device.

(2) FIG. 2 illustrates one implementation of the wireless mobile communication device of FIG. 1.

(3) FIG. 3 illustrates one implementation of a method for authenticating a user.

(4) FIG. 4 illustrates one implementation of a method for remotely locking use of a mobile application on a mobile communication device.

(5) Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION OF THE INVENTION

(6) FIG. 1 illustrates one implementation of a communication system 100. The communication system 100 includes a hand-held, wireless mobile communication device 102 a point-of-sale device 104 and a remote server 106. In one implementation, the mobile communication device 102 includes a mobile application (discussed in greater detail below) that permits a user of the mobile communication device 102 to conduct payment transactions. Payment transactions can include, for example, using contactless payment technology at a retail merchant point of sale (e.g., through point of sale device 104), using mobile/internet commerce (e.g., purchase tickets and products, etc.), storage of payment information and other digital artifacts (receipts, tickets, coupons, etc), storage of banking information (payment account numbers, security codes, PIN's, etc.), and accessing banking service (account balance, payment history, bill pay, fund transfer, etc.), and so on.

(7) In one implementation, the mobile application running on the mobile communication device 102 implements one or more of the following tools to secure data that may be stored and presented on the mobile communication device 102 as a result of a payment transaction. The mobile application can implemented one the mobile communication device 102 through a management server which hosts and operates (either independently or through a third-party) the application for use by its customers over the Internet, or other wireless network (e.g., a private network), or a wired network. In one implementation, customers do not pay for owning the software itself but rather for using the software. In one implementation, the mobile application is accessible through an API accessible over the Web (or other network). The mobile application can include a multi-factored PIN-based login and authentication, and include session keys and have command-level authentication. In one implementation, the mobile application running on the mobile communication device 102 can be remotely locked through a remote server (e.g., remote server 106). In one implementation, a PIN request can be implemented to limit the amount of purchases that can be made. Further, security codes for different payment methods can be implemented to protect a user. Each of these tools is discussed in greater detail below.

(8) FIG. 2 illustrates one implementation of the mobile communication device 102. The mobile communication device 102 includes a mobile application 200 that (in one implementation) is provided to the mobile communication device 102 through a remote server (e.g., remote server 106). In one implementation, the mobile application is a Mobile Wallet application available from Mobile Candy Dish, Inc., of Berkeley, Calif. Providing the mobile application as a hosted service enables central monitoring and management of all security aspects of the service at the remote server. In addition, data (corresponding to a payment transaction) can be stored on the remote server (e.g., remote server 106 (FIG. 1)) in a secure manner. In one implementation, the remote server is a management server that is can be maintained by Mobile Candy Dish or a trusted third party, as described in U.S. patent application Ser. No. 11/933,351. For example, the data can be securely stored on the remote server using conventional PCI guidelines. Hence, in the event the mobile communication device 102 is lost (or stolen), no confidential data can be recovered as no data is stored on the mobile communication device 102. In addition, an added benefit is that a user can recover seamlessly by syncing new mobile communication device (via new installation of the mobile application) with the service. Thus, in one implementation, sensitive information (e.g., banking account numbers, credit card account numbers, expiry dates, and so on) are never stored on the mobile communication device. This reduces risk and exposure of the user's private information and data.

(9) Client Login and Authentication

(10) In general, while effort is made to minimize storage of sensitive user information and data in a memory of a mobile communication device, in one implementation, some data is stored in the memory of a mobile communication device due to reasons of performance, usability and user experience. For example, data may need to be stored on a mobile communication device in the following circumstances. Payment credentials, coupons, tickets, and so on may have to be stored on the secure element of an NFC phone. Account balance, banking payment history, etc., may be locally cached on a mobile communication device. In one implementation, a user can opt-in to save payment method security codes in the client (or mobile application) for convenience. Tickets and/or coupons may be locally cached so that a user can redeem the tickets and/or coupons in an offline mode. For example, a mobile communication device may be offline in a situation in which network connectivity inside a building is degraded, and storing a ticket and/or coupon in a local cache of the mobile communication device permits the user to access the ticket or coupon.

(11) In addition to data partitioning, in one implementation, users have an ability to subscribe to different services. For example, User A may subscribe to “Mobile Payments” and “Mobile Banking” services, while User B may only subscribe to “Mobile Banking” and “What's Nearby” services. Hence, in one implementation, the mobile application includes a mechanism to enable/disable different services on the Client based on particular services to which users are subscribed. Table 1 below illustrates example services that are enabled/disabled based on user subscriptions.

(12) TABLE-US-00001 TABLE 1 USER SERVICE SUBSCRIPTION STATUS User A Money Manager Disabled User B Money Manager Transaction Only User C Money Manager Transaction, Payment User D Money Manager Transaction, Payment, BillPay, FundTransfer
The above example control access to the Money Manager service and what privileges within the service a given user can perform. This will be used by the Client (mobile application) to enable/disable available features on the Client.

(13) In one implementation, when a user subscribes to a mobile wallet the user is assigned credentials that include a unique WalletID, SiteKey, a user-defined PIN, as well as tokens that specify access and privileges for the different services. FIG. 3 illustrates one implementation of a method 300 for authenticating a user. User input is received (through a mobile communication device) logging into the mobile application service (step 302). In one implementation, when a user attempts to login with the client, the user is prompted to enter login credentials (e.g., mobile phone number, 1-time activation code, Wallet PIN, etc.). A session key is generated (step 304). In one implementation, the session key is a unique server-generated session key that is valid only for the duration of a given session. In one implementation, the session key is used to ensure the server can identify the client and ensure that the client has been previously authenticated. Upon a successful login, the server will transfer credentials, service access and privileges (step 306), which are locally cached on the mobile communication device. The service access and privileges control the behavior of the client. In one implementation, to prevent command spoofing, the session key is passed in every API server call. The server will validate (every time) the session key is valid. If valid, the API server call is processed. Failure to validate the session key will cause a failure. In such a case, the client will flush the cached PIN and force the user to re-authenticate (or re-login).

(14) Remote Lock

(15) In one implementation, a mobile application running on a mobile communication device can be remotely locked (or disabled) by invalidating a session key. Users, via calling a Customer Care, a personal web portal, or some other mechanism, can implement changes (e.g., change PIN, etc.) that causes the server to invalidate the session key. In real-time, the next attempt by the client to issue an API server call, validation of the session key will fail, which (in one implementation) causes the client to automatically flush the cached PIN and session key, and force the user to re-authenticate. In addition, the client can perform additional actions, in addition to flushing the cached PIN and session key. This includes, but is not limited to, one or more of the following: changing the secure element mode to effective temporarily or permanently disable the secure element—i.e., a user can remotely alter the state of the smart chip to lock it remotely; and deleting all cached data stored in the memory (or disk) of the mobile communication device.

(16) Session Time Out

(17) In one implementation, while a client is open, a user has access to transaction data. In such an implementation, users who may misplace a mobile communication device while the client is open may expose the user to risk of information theft. Therefore, in one implementation, mobile application (or client) shuts down after a period of inactivity. Additional tasks that can be associated with the shutdown procedure can include, but is not limited to, temporarily shutting down a secure element (of the mobile communication device) to prevent NFC payments, NFC coupon redemption, and NFC ticket redemption.

(18) Payment Limit PIN

(19) For payments (mobile commerce ticket purchase, etc.), in one implementation a user can prevent either fraudulent purchases or accidental purchases by forcing a PIN prompt when a purchase amount exceed a user-specified value. In one implementation, a user can control this behavior globally (e.g., across all users' payment methods) or on a per-payment-method basis. Thus, when a user purchases ticket and selects a payment method (to pay for purchase), if the transaction amount exceeds a specified payment method's limit, the client will trigger and prompt for the PIN. In order to proceed with purchase, the user has to enter the correct PIN. The user's input is validated against the cached PIN on the client. The payment transaction will proceed if validated. Otherwise, an appropriate response is generated to the user. Effectively, this is a mechanism for the user (not the Merchant or Issuing Bank) to throttle/control the dollar amount that can be authorized for various payments and transactions. In the event of a contactless purchase, the client controls the smart chip. In the event of an electronic purchase (ticketing, etc.), a server can manages the controls.

(20) Local Storage of Payment Security Codes

(21) As a convenience to users, a user can opt-in and have only the security codes (CVV, etc.) associated to each of their payment methods locally stores on the client. In one implementation, management tools are provided to add/delete/edit these security codes. In one implementation, the security codes are encrypted (Key Management of encryption key performed by a server) and then only stored in the client on the mobile communication device. In one implementation, security codes are not stored in any form on the server. The encryption key and security codes can be kept separately to prevent fraudulent usage.

(22) Although the present invention has been particularly described with reference to implementations discussed above, various changes, modifications and substitutes are can be made. Accordingly, it will be appreciated that in numerous instances some features of the invention can be employed without a corresponding use of other features. Further, variations can be made in the number and arrangement of components illustrated in the figures discussed above.