IP Library Granted Patent US 11,599,865
Granted Patent B2
US 11,599,865 · App. 16/906,239 · Granted Mar 7, 2023

Method and system for remote transaction processing using a non-browser based application

Inventor: Michelle Fisher (Berkeley, CA)
Assignee: Michelle Fisher
G06Q20/20G06Q20/00G06Q20/108G06Q20/16G06Q20/202G06Q20/204G06Q20/206G06Q20/32G06Q20/322G06Q20/325G06Q20/326G06Q20/3223G06Q20/3226G06Q20/3227G06Q20/3255G06Q20/3278G06Q20/3674G06Q20/382G06Q20/3821G06Q20/40G06Q20/409G06Q20/4012G06Q20/4014G06Q30/02G06Q30/0222G06Q30/0238G06Q30/0251G06Q30/0253G06Q30/0255G06Q30/0267G06Q30/0268G06Q30/06G06Q30/0613G06Q30/0635G06Q40/10G06Q40/12H04B5/0025H04M1/72445H04W4/18H04W4/21H04W8/205G06Q20/10G06Q20/105G06Q40/00G07F7/1008H04N21/812H04W4/02H04W4/029H04W4/80H04W88/02
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,599,865
App. No.
16/906,239
Granted
Mar 7, 2023
Kind
B2
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 (68)

1. A method for processing a remote transaction received from a non-browser based application comprising:

receiving, at the non-browser based application, information related to a userID 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 information related to the userID and the information related to the password from the remote management server;

after user authentication, receiving a list of products from the remote management server at the non-browser based application for display using the non-browser based application;

receiving, at the non-browser based application an identification of one or more products selected from the list of products, wherein the non-browser based application receives the identification of one or more products selected from the list of products through the user input via the mobile device display of the mobile device;

transmitting from the non-browser based application to the remote management server the identification of one or more products selected from the list of products;

receiving, from the non-browser based application, a transaction purchase request, wherein the non-browser based application receives the transaction purchase request through the user input via the mobile device display of the mobile device;

transmitting, from the non-browser based application, the transaction purchase request to the remote management server;

after the remote transaction has been processed by a transaction server using a payment method, receiving at the non-browser based application, a digital artifact from the remote management server; and

displaying the digital artifact within the non-browser based application.

2. The method of claim 1 , wherein the payment method is a credit card, debit card, or prepaid card.

3. The method of claim 1 , wherein the digital artifact comprises an advertisement, receipt, ticket, coupon, media, metadata, and/or content.

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

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

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

7. The method of claim 1 , wherein no sensitive information is stored on the mobile device.

8. The method of claim 7 , wherein the sensitive information comprises at least one of information related to the payment method.

9. The method of claim 1 , further wherein the non-browser based application generates an alert if it has not received the digital artifact from the remote management server within a certain period of time.

10. The method of claim 1 , further wherein the non-browser based application displays the digital artifact while the mobile device maintains a connection to a wireless network; and

further comprises:

losing the connection of the mobile device to the wireless network while the non-browser based application displays the digital artifact; and

in an offline mode, after losing the connection, continuing to display the digital artifact within the non-browser based application.

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

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

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

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

15. A mobile device for processing a remote transaction received from a non-browser based application compromising

a mobile device input interface configured to:

receive, at the 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 a list of products from the remote management server at the non-browser based application for display using the non-browser based application;

receive, at the non-browser based application an identification of one or more products selected from the list of products, wherein the non-browser based application receives the identification of one or more products selected from the list of products through the user input via the mobile device display of the mobile device;

receive, at the non-browser based application, a transaction purchase request, wherein the non-browser based application receives the transaction purchase request through the user input via the mobile device display of the mobile device;

after the remote transaction has been processed by a transaction server using a payment method, receiving at the non-browser based application, a digital artifact from the remote management server;

a mobile device output interface 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;

transmit from the non-browser based application to the remote management server the identification of one or more products selected from the list of products;

transmit, from the non-browser based application, the transaction purchase request to the remote management server;

a mobile device display configured to display the digital artifact within the non-browser based application.

16. The mobile device of claim 15 , wherein the payment method is a credit card, debit card, or prepaid card.

17. The mobile device of claim 15 , wherein the digital artifact comprises an advertisement, receipt, ticket, coupon, media, metadata, and/or content.

18. The mobile device of claim 15 , further wherein data stored on the mobile device is encrypted using a mobile operating system native to the mobile device.

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

20. The mobile device of claim 15 , wherein the information related to the password, is information related to biometric data.

21. The mobile device of claim 15 , wherein no sensitive information is stored on the mobile device.

22. The mobile device of claim 21 , wherein the sensitive information comprises at least one of information related to the payment method.

23. The mobile device of claim 15 , further wherein the non-browser based application generates an alert if it has not received the digital artifact from the remote management server within a certain period of time.

24. The mobile device of claim 15 , further wherein the non-browser based application displays the digital artifact while the mobile device maintains a connection to a wireless network; and

further comprises:

losing the connection of the mobile device to the wireless network while the non-browser based application displays the digital artifact; and

in an offline mode, after losing the connection, continuing to display the digital artifact within the non-browser based application.

25. The mobile device of claim 15 , 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.

26. The mobile device of claim 15 , further wherein the non-browser based application sends a request to the remote management server for retransmission of the digital artifact if it has not received the digital artifact from the remote management server within a certain period of time.

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

28. The mobile device of claim 15 , 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.

29. The method of claim 1 , further wherein the remote management server is configured to store the user ID for a plurality of the user's mobile devices and further wherein the configuration means that the remote management server scales.

30. The method of claim 1 , further wherein the digital artifact is stored in the mobile device memory due to reasons of performance, usability, user experience, and user convenience.

31. The method of claim 1 , further wherein maintaining the payment method at the remote management server results in a more secure system.

32. The method of claim 1 , further wherein the transaction does not use a Point-Of-Sale terminal.

33. The method of claim 1 , further wherein the non-browser based application is stored in a local mobile device memory during execution of the non-browser based application, a bulk storage mobile device memory when the non-browser based application is not being executed, and a cache mobile device memory to provide temporary storage of at least some of the non-browser based application in order to reduce the number of times the non-browser based application must be retrieved from the bulk storage mobile device memory during the execution.

34. The method of claim 1 , wherein the non-browser based application is not Short Messaging Service (SMS).

35. The mobile device of claim 15 , further wherein the remote management server is configured to store the user ID for a plurality of the user's mobile devices and further wherein the configuration means that the remote management server scales.

36. The mobile device of claim 15 , further wherein the digital artifact is stored in the mobile device memory due to reasons of performance, usability, user experience, and user convenience.

37. The mobile device of claim 15 , further wherein maintaining the payment method at the remote management server results in a more secure system.

38. The mobile device of claim 15 , further wherein the transaction does not use a Point-Of-Sale terminal.

39. The mobile device of claim 15 , further wherein the non-browser based application is stored in a local mobile device memory during execution of the non-browser based application, a bulk storage mobile device memory when the non-browser based application is not being executed, and a cache mobile device memory to provide temporary storage of at least some of the non-browser based application in order to reduce the number of times the non-browser based application must be retrieved from the bulk storage mobile device memory during the execution.

40. The mobile device of claim 15 , wherein the non-browser based application is not Short Messaging Service (SMS).

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 26, 2023
From: FISHER, MICHELLE
To: BLAZE MOBILE, INC
Reel/Frame 065955/0144 →
Continuity (5)
Continuation 15822131 · Nov 25, 2017
Continuation 14686695 · Apr 14, 2015
Continuation 13710646 · Dec 11, 2012
Continuation 11948903 · Nov 30, 2007
Related Publication 20210035079A1 · Feb 4, 2021