IP Library Granted Patent US 11,669,856
Granted Patent B2
US 11,669,856 · App. 17/512,932 · Granted Jun 6, 2023

Processing mobile banking transactions using a remote management server

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,669,856
App. No.
17/512,932
Granted
Jun 6, 2023
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 (61)

1. A method for processing a mobile banking transaction, comprising:

receiving, at remote management server, information related to an identification code associated with a user and information related to a password from a non-browser based application, 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 wireless communication channel, and a mobile device wireless fidelity (Wi-Fi) transceiver;

authenticating a user associated with the identification code associated with the user and the information related to the password;

after user authentication, receiving, a request for the mobile banking transaction from the non-browser based application, 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 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, transmitting a digital artifact from the remote management server to the non-browser based application which displays 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 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.

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

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

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

15. The method of claim 14 , wherein the sensitive data is information related to the payment method.

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

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

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

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

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

21. A remote management server for processing a mobile banking transaction, the mobile device comprising:

a remote management server input interface configured to:

receive information related to an identification code associated with a user and information related to a password from a non-browser based application, 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 a request for the mobile banking transaction from the non-browser based application, wherein the non-browser based application receives the request for the mobile banking transaction through user input via the mobile device display;

a mobile device processor configured to:

authenticate the user associated with the information related to the identification code associated with the user and the information related to the password;

a mobile device output interface configured to:

after receiving the request for the mobile banking transaction, transmit the request for the mobile banking transaction from the remote management server to a transaction server for processing the request for the mobile banking transaction using a payment method; and

after the request for the mobile banking transaction has been processed, transmit a digital artifact from the remote management server to the non-browser based application which displays the digital artifact within the non-browser based application.

22. The remote management server of claim 21 , wherein the request for the mobile banking transaction comprises bill pay.

23. The remote management server of claim 21 , wherein the request for the mobile banking transaction comprises transferring funds.

24. The remote management server of claim 21 , wherein the request for the mobile banking transaction comprises viewing transaction history.

25. The remote management server of claim 21 , wherein the request for the mobile banking transaction comprises viewing account balance.

26. The remote management server of claim 21 , wherein the request for the mobile banking transaction comprises depositing a check.

27. The remote management server of claim 21 , wherein the request for the mobile banking transaction comprises withdrawing cash from an ATM machine.

28. The remote management server of claim 21 , wherein the digital artifact comprises one of a receipt, advertisement, coupon, ticket, media, or content.

29. The remote management server of claim 21 , wherein the digital artifact comprises one of a receipt, advertisement, coupon, ticket, media, or content.

30. The remote management server of claim 21 , where the payment method is a bank account, credit card, debit card, or prepaid card.

31. The remote management server of claim 21 , further 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.

32. The remote management server of claim 21 , 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.

33. The remote management server of claim 21 , 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.

34. The remote management server of claim 21 , further wherein no sensitive data is stored on the mobile device.

35. The remote management server of claim 34 , wherein the sensitive data is information related to the payment method.

36. The remote management server of claim 21 , further wherein the non-browser based application automatically displays the digital artifact in an easily retrievable format.

37. The remote management server of claim 21 , 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.

38. The remote management server of claim 21 , 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.

39. The remote management server of claim 21 , further wherein the information related to the password is information related to a personal identification number (PIN).

40. The remote management server of claim 21 , 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 Dec 26, 2023
From: FISHER, MICHELLE
To: BLAZE MOBILE, INC
Reel/Frame 065955/0144 →
Continuity (8)
Continuation 17009356 · Sep 1, 2020
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 20220084060A1 · Mar 17, 2022