Mobile banking transactions at a server with authentication

• US 10,235,664 B2
• Filed: 03/19/2014
• Issued: 03/19/2019
• Est. Priority Date: 11/30/2007
• Status: Active Grant

• Current Assignee: Blaze Mobile Technologies LLC
• Original Assignee: Michelle Fisher
• Inventors: Fisher, Michelle
• Primary Examiner(s): Goyea, Olusegun
• Application Number:
  US14/219,223
• Publication Number:
  US 20140304082A1
• Time in Patent Office: 1,826 Days
• Field of Search: 705 141- 1464, 705 16- 18, 705 261- 2635, 705 30- 34, 705 40, 705 44, 705 1466, 705 26, 705 56, 705 64, 455 411, 455405-410, 4554141, 455443, 455445, 455550-558, 455411, 455 412, 235375-385, 235451, 713183-186, 84609, 715727
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 20/00 Payment architectures, schemes or protocols apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/105 involving programming of a portable memory device, e.g. IC cards, "electronic purses"
• CPC Class Codes: G06Q 20/108 Remote banking, e.g. home banking
• CPC Class Codes: G06Q 20/16 Payments settled via telecommunication systems
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/202 Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
• CPC Class Codes: G06Q 20/204 comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
• CPC Class Codes: G06Q 20/206 comprising security or operator identification provisions, e.g. password entry
• CPC Class Codes: G06Q 20/32 using wireless devices
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/3226 Use of secure elements separate from M-devices
• CPC Class Codes: G06Q 20/3227 using secure elements embedded in M-devices
• CPC Class Codes: G06Q 20/325 using wireless networks
• CPC Class Codes: G06Q 20/3255 using mobile network messaging services for payment, e.g. SMS
• CPC Class Codes: G06Q 20/326 Payment applications installed on the mobile devices
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/382 : insuring higher security of transaction
• CPC Class Codes: G06Q 20/3821 : Electronic credentials
• CPC Class Codes: G06Q 20/40 : Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/4012 : Verifying personal identification numbers [PIN]
• CPC Class Codes: G06Q 20/4014 : Identity check for transactions
• CPC Class Codes: G06Q 20/409 : Device specific authentication in transaction processing
• CPC Class Codes: G06Q 30/02 : Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0222 : During e-commerce, i.e. online transactions
• CPC Class Codes: G06Q 30/0238 : at point-of-sale [POS]
• CPC Class Codes: G06Q 30/0251 : Targeted advertisements
• CPC Class Codes: G06Q 30/0253 : During e-commerce, i.e. online transactions
• CPC Class Codes: G06Q 30/0255 : based on user history
• CPC Class Codes: G06Q 30/0267 : Wireless devices
• CPC Class Codes: G06Q 30/0268 : at point-of-sale [POS]
• CPC Class Codes: G06Q 30/06 : Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0613 : Third-party assisted
• CPC Class Codes: G06Q 30/0635 : Processing of requisition or of purchase orders
• CPC Class Codes: G06Q 40/00 : Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/10 : Tax strategies
• CPC Class Codes: G06Q 40/12 : Accounting
• CPC Class Codes: G07F 7/1008 : Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
• CPC Class Codes: H04B 5/70 : specially adapted for specific purposes
• CPC Class Codes: H04M 1/72445 : for supporting Internet browser applications
• CPC Class Codes: H04N 21/812 : involving advertisement data advertising per se G06Q30/02
• CPC Class Codes: H04W 4/02 : Services making use of location information
• CPC Class Codes: H04W 4/029 : Location-based management or tracking services
• CPC Class Codes: H04W 4/18 : Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
• CPC Class Codes: H04W 4/21 : for social networking applications
• CPC Class Codes: H04W 4/80 : Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 8/205 : Transfer to or from user equipment or user record carrier
• CPC Class Codes: H04W 88/02 : Terminal devices

Abstract

A method and system for conducting an online payment transaction through a point of sale device. The method includes receiving input from a user selecting an item for purchase through the point of sale device; calculating a total purchase amount for the item in response to a request from the user to purchase the item; and sending payment authorization for the total purchase amount from the point of sale device to a payment entity, in which the payment authorization is sent to the payment entity via a mobile communication device of the user. The method further includes receiving a result of the payment authorization from the payment entity through the mobile communication device; and completing the payment transaction based on the result of the payment authorization.

Claims

1. A method for processing a mobile banking transaction,

maintaining, at a remote management server, a payment method;

receiving, at the remote management server, an identification code associated with a user and information related to a PIN from a non-browser based application stored on a mobile device, wherein the non-browser based application stored on the mobile device receives the identification code associated with the user and the information related to the PIN 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 processor, a mobile device memory that maintains the non-browser based application, a mobile device wireless 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 identification code associated with the user and the information related to the PIN, authenticating at the remote management server a user of the mobile device prior to conducting the mobile banking transaction;

after authenticating the user, receiving, at the remote management server, user input from the non-browser based application to initiate a mobile banking transaction request, wherein the non-browser based application stored on the mobile device receives the mobile banking transaction request through user input via the mobile device display of the mobile device;

after receiving the mobile banking transaction request, processing at the remote management server the mobile banking transaction using the payment method; and

after the mobile banking transaction has been processed, sending, from the remote management server, a digital artifact to the non-browser based application for display within a non-browser based application generated screen, the non-browser based generated screen corresponding to a specific screen or area of the non-browser based application.

4. The method of claim 1, wherein the mobile banking transaction comprises bill pay.

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

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

7. The method of claim 1, wherein the mobile banking transaction comprises viewing, the account balance.

8. The method of claim 1, wherein the mobile banking transaction comprises viewing transaction history.

9. The method of claim 1, wherein the digital artifact is a receipt.

10. The method of claim 1, wherein the digital artifact is an advertisement, coupon, ticket, media, or content.

11. The method of claim 1, further wherein data stored on the mobile device is encrypted using software tools native to the mobile operating system.

18. The method of claim 1, further wherein the non-browser based application can be used when the mobile device is not connected to a wireless network.

19. The method of claim 18, further wherein 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 method of claim 1, further wherein the digital artifact can be viewed in the non-browser based application when there is no network connection.

21. The method of claim 1, further wherein no sensitive data is stored on the mobile device.

22. The method of claim 21, wherein the sensitive data comprises at least one of information related to the payment method, information related to the PIN, and information related to an expiration dates associated with the payment method.

23. The method of claim 10, further wherein the digital artifact is based on targeting parameters that includes one or more of personal information and transaction related information.

24. The method of claim 23, wherein personal information comprises one or more of location, gender, age, interest, affiliation, userid, pageid, zip code, area code, and occupation.

25. The method of claim 23, wherein transaction related information comprises one or more of information related to historical payment transaction, information related to real-time payment transaction, information related to contactless transactions made using the mobile device, information related to interne commerce, information related to bill pay, information related to top spend categories, information related to merchants, information related to storage of banking information, information related to accessing account balance, information related to accessing payment history, information related to accessing funds transfer , information related to storing tickets, information related to storing receipts, information related to storing coupons, information related to transactions made by the user but not through the mobile device, and information related to raw data downloaded from banks.

27. The system of claim 23, further wherein 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.

36. The method of claim 1, further wherein the non-browser based application sends a request to the remote management server to retransmit the digital artifact if it has not received the digital artifact from the remote management server within a certain period of time.

37. The method of claim 1, wherein the remote management server sends the digital artifact to the non-browser based application based on the geographical location of the mobile device.

38. The method of claim 1, further wherein the non-browser based application is configured to use a structured format and further wherein the structured format means the non-browser based application can store and display the digital artifact on the mobile device in an organized and easily retrievable fashion.

39. The method of claim 1, further wherein the remote management server is configured to store a single identification code associated with a user for a variety of mobile devices, and further wherein the configuration means the remote management server scales.

44. 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.

2. A system for processing a mobile banking transaction, 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 wireless 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;

a remote management server including;

a remote management server memory that maintains a payment method;

a remote management server transceiver that

receives an identification code associated with a user and information related to a PIN from the non-browser based application stored on the mobile device, wherein the non-browser based application stored on the mobile device receives the identification code associated with the user and information related to the PIN via the mobile device display of the mobile device; and

after authenticating the user, receives user input from the non-browser based application to initiate a mobile banking transaction request, wherein the non-browser based application stored on the mobile device receives the mobile banking transaction request through 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 for display within a non-browser based application generated screen, the non-browser based generated screen corresponding to a specific screen or area of the non-browser based application;

a remote management server processor that

upon receipt of the identification code associated with the user and the information related to the PIN, authenticates a user of the mobile device; and

after receiving the mobile banking transaction request, processes the mobile banking transaction using the payment method.

12. The system of claim 2, wherein the mobile banking transaction comprises bill pay.

13. The system of claim 2, wherein the mobile banking transaction comprises funds transfer.

14. The system of claim 2, wherein the mobile banking transaction comprises loading funds.

15. The system of claim 2, wherein, the mobile banking transaction comprises, viewing account balance.

16. The system of claim 2, wherein the mobile banking transaction comprises, viewing transaction history.

17. The system of claim 2, wherein data stored on the mobile device is encrypted using software tools native to the mobile operating system.

26. The system of claim 2, further wherein the non-browser based application can be used when the mobile device is not connected to a wireless network.

28. The system of claim 2, further wherein the digital artifact can be viewed in the non-browser based application when there is no network connection.

29. The system of claim 2, further wherein no sensitive data is stored on the mobile device.

30. The system of claim 29, wherein the sensitive data comprises at least one of information related to the payment method, information related to the PIN, and information related to an expiration dates associated with the payment method.

31. The system of claim 2, wherein the digital artifact is a receipt.

32. The system of claim 2, wherein the digital artifact is an advertisement, coupon, ticket, media, or content.

33. The system of claim 32, further wherein the digital artifact is based on targeting parameters that includes one or more of personal information and transaction related information.

34. The system of claim 33, wherein personal information comprises one or more of location, gender, age, interest, affiliation, userid, pageid, zip code, area code, and occupation.

35. The system of claim 33, wherein transaction related information comprises one or more of information related to historical payment transaction, information related to real-time payment transaction, information related to contactless transactions made using the mobile device, information related to interne commerce, information related to bill pay, information related to top spend categories, information related to merchants, information related to storage of banking information, information related to accessing account balance, information related to accessing payment history, information related to accessing funds transfer , information related to storing tickets, information related to storing receipts, information related to storing coupons, information related to transactions made by the user but not through the mobile device, and information related to raw data downloaded from banks.

40. The system of claim 2, further wherein the, non-browser based application sends a request to the remote management server to retransmit the digital artifact if it has not received the digital artifact from the remote management server within a certain period of time.

41. The system of claim 2, wherein the remote management server sends the digital artifact to the non-browser based application based on the geographical location of the mobile device.

42. The system of claim 2, further wherein the non-browser based application is configured to use a structured format and further wherein the structured format means the non-browser based application can store and display the digital artifact on the mobile device in an organized and easily retrievable fashion.

43. The system of claim 2, further wherein the remote management server is configured to store a single identification code associated with a user for a variety of mobile devices and further wherein the configuration means the remote management server scales.

45. The system of claim 2, 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.

3. A remote management server for processing a mobile banking transaction comprising

a remote management server memory that maintains a payment method;

a remote management server transceiver that

receives an identification code associated with a user and information related to a PIN from a non-browser based application stored on a mobile device, wherein the non-browser based application stored on the mobile device receives the identification code associated with the user and information related to the PIN 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 processor, a mobile device memory that maintains the non-browser based application, 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; and

after authenticating the user, receives user input into the non-browser based application to initiate a mobile banking transaction request, 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 for display within a non-browser based application generated screen, the non-browser based generated screen corresponding to a specific screen or area of the non-browser based application

a remote management server processor that

upon receipt of the identification code associated with the user and information related to the PIN, authenticates a user of the mobile device; and

after receiving the mobile banking transaction request, processes the mobile banking transaction using the payment method.