IP Library Granted Patent US 11,164,207
Granted Patent B2
US 11,164,207 · App. 17/009,356 · Granted Nov 2, 2021

Processing a mobile banking transactions using a non-browser based application

Inventor: Michelle Fisher (Berkeley, CA)
Assignee: Michelle Fisher
G06Q30/0239G06F3/0484G06Q20/322G06Q30/0267G06Q30/0277G06Q40/02H04L63/0428H04L67/34H04W4/02H04W4/024H04W4/60H04W4/80H04L67/306H04M1/72406H04M1/72427H04W8/18
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,164,207
App. No.
17/009,356
Granted
Nov 2, 2021
Kind
B2
Abstract

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.

Claims (44)

1. A method for processing a mobile banking transaction, 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 a 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, from the non-browser based application the information related to the userID and the information related to the password to a remote management server; receiving, at the mobile device, information authenticating the user associated with the userID and the information related to the password from the remote management server; after user authentication, receiving, 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 receiving the request for the mobile banking transaction, transmitting the request for the mobile banking transaction from the non-browser based application to the remote management server which transmits it to a transaction server for processing the request for the mobile banking transaction using a payment method; after the request for the mobile banking transaction has been processed, receiving a digital artifact from the remote management server at the non-browser based application; 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 bill pay.

3. The method of claim 1 , wherein the request for the mobile banking transaction comprises transferring funds.

4. The method of claim 1 , wherein the request for the mobile banking transaction comprises viewing transaction history.

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

6. The method of claim 1 , wherein the request for the mobile banking transaction comprises viewing reward points.

7. The method of claim 1 , wherein the request for the mobile banking transaction comprises depositing a check.

8. The method of claim 1 , wherein the request for the mobile banking transaction comprises withdrawing cash from an ATM machine.

9. The method of claim 1 , wherein the digital artifact comprises one of a receipt, advertisement, coupon, ticket, media, or content.

10. The method of claim 1 , where the payment method is a bank account, credit card, debit card, or prepaid card.

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

12. The method of claim 1 , further wherein the digital artifact is cached on the mobile device and accessible by the non-browser based application when the mobile device is not connected to a wireless network.

13. The method of claim 1 , further wherein the digital artifact can be viewed in the non-browser based application when the mobile device is not connected to a wireless network.

14. The method of claim 1 , further 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 re-connects to the wireless network when the wireless network is available.

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

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

17. The method of claim 16 , wherein the sensitive data is information related to the payment method.

18. The method of claim 1 , further wherein the non-browser based application automatically displays the digital artifact in an easily retrievable format.

19. The method of claim 1 , further wherein the non-browser based application is configured to use a structured format, wherein the structured format means the non-browser based application can store and display the digital artifact in an organized manner.

20. 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 plurality of mobile devices, and further wherein the configuration means the remote management server scales.

21. The method of claim 1 , further wherein the information related to the password is information related to a personal identification number (PIN).

22. The method of claim 1 , further, wherein the information related to the password is information related to biometric data.

23. 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; receive information authenticating the user associated with the information related to the userID and the information related to the password from the remote management server; after user authentication, receive, at the non-browser based application, the 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, receive a digital artifact from the remote management server at the non-browser based application; a mobile device output interface, wherein at least one of the mobile device radio transceiver or the mobile device Wi-Fi transceiver is configured to: transmit, from the non-browser based application the information related to the userID and information related to the password to the remote management server; after receiving the request for the mobile banking transaction, transmit the request for the mobile banking transaction from the non-browser based application to the remote management server which transmits it to a transaction server for processing the request for the mobile banking transaction using a payment method; and a mobile device display configured to display the digital artifact within the non-browser based application.

24. The mobile device of claim 23 , wherein the request for the mobile banking transaction comprises bill pay.

25. The mobile device of claim 23 , wherein the request for the mobile banking transaction comprises transferring funds.

26. The mobile device of claim 23 , wherein the request for the mobile banking transaction comprises viewing transaction history.

27. The mobile device of claim 23 , wherein the request for the mobile banking transaction comprises viewing account balance.

28. The mobile device of claim 23 , wherein the request for the mobile banking transaction comprises depositing a check.

29. The mobile device of claim 23 , wherein the request for the mobile banking transaction comprises withdrawing cash from an ATM machine.

30. The mobile device of claim 23 , wherein the digital artifact comprises one of a receipt, advertisement, coupon, ticket, media, or content.

31. The mobile device of claim 23 , wherein the digital artifact comprises one of a receipt, advertisement, coupon, ticket, media, or content.

32. The mobile device of claim 23 , where the payment method is a bank account, credit card, debit card, or prepaid card.

33. The mobile device of claim 23 , further wherein the non-browser based application is operative when the mobile device is not connected to a wireless network.

34. The mobile device of claim 23 , further wherein the digital artifact is cached on the mobile device and accessible by the non-browser based application when the mobile device is not connected to a wireless network.

35. The mobile device of claim 23 , further wherein the digital artifact can be viewed in the non-browser based application when the mobile device is not connected to a wireless network.

36. The mobile device of claim 23 , 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.

37. The mobile device of claim 23 , 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.

38. The mobile device of claim 23 , further wherein no sensitive data is stored on the mobile device.

39. The mobile device of claim 38 , wherein the sensitive data is information related to the payment method.

40. The mobile device of claim 23 , further wherein the non-browser based application automatically displays the digital artifact in an easily retrievable format.

41. The mobile device of claim 23 , further wherein the non-browser based application is configured to use a structured format, wherein the structured format means the non-browser based application can store and display the digital artifact in an organized manner.

42. The mobile device of claim 23 , further wherein the remote management server is configured to store a single identification code associated with a user for a plurality of mobile devices, and further wherein the configuration means the remote management server scales.

43. The mobile device of claim 23 , further wherein the information related to the password is information related to a personal identification number (PIN).

44. The mobile device of claim 23 , further, wherein the information related to the password is information related to biometric data.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 29, 2025
From: MICHELLE FISHER
To: BLAZE MOBILE TECHNOLOGIES, LLC
Reel/Frame 072723/0869 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 12, 2024
From: BLAZE MOBILE, INC.
To: BLAZE MOBILE TECHNOLOGIES, LLC
Reel/Frame 066723/0784 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 23, 2021
From: FISHER, MICHELLE
To: BLAZE MOBILE, INC
Reel/Frame 058191/0329 →
Continuity (7)
Continuation 16796892 · Feb 20, 2020
Continuation 16457874 · Jun 28, 2019
Continuation 15980735 · May 15, 2018
Continuation 15134101 · Apr 20, 2016
Continuation 14180562 · Feb 14, 2014
Continuation 11956261 · Dec 13, 2007
Related Publication 20210035149A1 · Feb 4, 2021