# US 2024/0005293 A1 · Blaze in app purchase with authentication using a remote management server

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0005293 A1
- Document ID: US20240005293A1
- Status: Published application
- Kind: A1
- Application number: 18/369,463
- Filed: 2023-09-18
- Published: 2024-01-04
- Earliest claimed: 2007-11-30
- Assignees: Michelle Fisher
- Inventors: Michelle Fisher
- Web page: https://patentgrep.com/patent/US20240005293A1

## CPC

- G06Q 20/20: Point-of-sale [POS] network systems
- G06Q 10/10: Office automation; Time management
- G06Q 20/00: Payment architectures, schemes or protocols (apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12)
- G06Q 20/108: {Remote banking, e.g. home banking}
- G06Q 20/16: Payments settled via telecommunication systems
- 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}
- G06Q 20/204: {comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit}
- G06Q 20/206: {comprising security or operator identification provisions, e.g. password entry}
- G06Q 20/32: using wireless devices
- G06Q 20/322: {Aspects of commerce using mobile devices [M-devices]}
- G06Q 20/3223: {Realising banking transactions through M-devices}
- G06Q 20/3226: {Use of secure elements separate from M-devices}
- G06Q 20/3227: {using secure elements embedded in M-devices}
- G06Q 20/325: {using wireless networks}
- G06Q 20/3255: {using mobile network messaging services for payment, e.g. SMS}
- G06Q 20/326: {Payment applications installed on the mobile devices}
- G06Q 20/3278: {RFID or NFC payments by means of M-devices}
- G06Q 20/3674: {involving authentication}
- G06Q 20/382: {insuring higher security of transaction}
- G06Q 20/3821: {Electronic credentials}
- 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
- G06Q 20/4012: {Verifying personal identification numbers [PIN]}
- G06Q 20/4014: {Identity check for transactions}
- G06Q 20/4016: {involving fraud or risk level assessment in transaction processing}
- G06Q 20/409: {Device specific authentication in transaction processing}
- G06Q 30/02: Marketing; Price estimation or determination; Fundraising
- G06Q 30/0222: {During e-commerce, i.e. online transactions}
- G06Q 30/0238: at point-of-sale [POS]
- G06Q 30/0251: Targeted advertisements
- G06Q 30/0253: {During e-commerce, i.e. online transactions}
- G06Q 30/0255: {based on user history}
- G06Q 30/0267: {Wireless devices}
- G06Q 30/0268: {at point-of-sale [POS]}
- G06Q 30/06: Buying, selling or leasing transactions
- G06Q 30/0613: {using intermediate agents}
- G06Q 30/0633: {Managing shopping lists, e.g. compiling or processing purchase lists (shipping orders G06Q10/083; order filling G06Q10/087)}
- G06Q 30/0635: {replenishment orders; recurring orders}
- G06Q 40/10: Tax strategies
- G06Q 40/12: Accounting
- H04B 5/70: specially adapted for specific purposes
- H04M 1/72445: for supporting Internet browser applications
- 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
- H04W 4/21: for social networking applications
- H04W 8/205: {Transfer to or from user equipment or user record carrier}
- G06Q 20/10: specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q 20/105: {involving programming of a portable memory device, e.g. IC cards, "electronic purses"}
- G06Q 40/00: Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G07F 7/1008: {Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system}
- H04N 21/812: {involving advertisement data (advertising per se G06Q30/02)}
- H04W 4/02: Services making use of location information
- H04W 4/029: Location-based management or tracking services
- H04W 4/80: Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
- H04W 88/02: Terminal devices
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04B: TRANSMISSION
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- G07F: COIN-FREED OR LIKE APPARATUS (coin sorting G07D3/00; coin testing G07D5/00; {handling coins or paper currencies apart from payment activated apparatus G07D; payment architectures, schemes or protocols G06Q20/00})
- H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION

## Abstract

A method and system for receiving digital artifacts from a management server. The method includes sending a request for a digital artifact from a mobile application to the management server for display within a specific mobile application generated screen, receiving the digital artifact from the management server, and displaying the digital artifact with the specific mobile application generated screen.

## Claims

### Claim 1

A method for purchasing a product, comprising:
maintaining, at a remote management server, a payment method;
receiving, at the remote management server, user input login information including a userID and information related to a password from a non-browser based application, wherein the non-browser based application is a mobile operating system platform non-browser based mobile application with a graphical user interface which includes a graphical icon that is preinstalled or downloaded and installed on a mobile device, wherein the non-browser based application stored on the mobile device receives the user input login information including the userID and the information related to the password through user input via a mobile device display of the mobile device, the mobile device including the mobile device display, a mobile device processor, a mobile device wireless transceiver configured to support voice and data interactions through a first wireless communication channel, and a mobile device wireless fidelity (Wi-Fi) transceiver,
upon receipt of the user input login information including the userID and the information related to the password, authenticating, at the remote management server, a user associated with the user input login information;
after the user authentication, sending a list of products from the remote management server to the non-browser based application for display using the non-browser based application;
receiving, at the remote management server an identification of one or more products selected from the list of products, from the non-browser based application, 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;
receiving, at the remote management server a transaction purchase request for the one or more products from the non-browser based application, 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 receiving the transaction purchase request, transmitting, from the remote management server the payment method to a transaction server which processes a transaction for the one or more products using the payment method that corresponds to the userID;
receiving, at the remote management server, a transaction verification from the transaction server, wherein the transaction verification indicates that the transaction for the one or more products has been processed; and
after the transaction for the one or more products has been processed, sending, from the remote management server to the non-browser based application, a digital artifact for display within the non-browser based application using the mobile device display.

### Claim 2 (depends on 1)

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

### Claim 3 (depends on 1)

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

### Claim 4 (depends on 1)

The method of claim 1, further wherein the digital artifact can be used by the non-browser based application when there is not a network connection.

### Claim 5 (depends on 1)

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.

### Claim 6 (depends on 1)

The method of claim 1, further wherein the non-browser based application displays the digital artifact while the mobile device maintains a wireless connection to a wireless network; and
further comprises:
losing the wireless 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 wireless connection, continuing to display the digital artifact within the non-browser based application.

### Claim 7 (depends on 1)

The method of claim 1, wherein the password is a PIN or biometric data.

### Claim 8 (depends on 1)

The method of claim 1, 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.

### Claim 9 (depends on 1)

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

### Claim 10 (depends on 9)

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

### Claim 11 (depends on 1)

The method of claim 1, further wherein the remote management server is configured to store a single userID for plurality of mobile devices, and further wherein the configuration means the remote management server scales.

### Claim 12 (depends on 1)

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.

### Claim 13 (depends on 1)

The method of claim 1, further wherein the non-browser based application is stored in a local mobile device memory during an execution of the non-browser based application, a bulk storage mobile device memory for 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.

### Claim 14 (depends on 1)

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

### Claim 15 (depends on 9)

The method of claim 9, further wherein sensitive data is only sent from the mobile device directly to the remote management server which reduces the potential for identity theft and/or fraudulent purchases made through a mobile device.

### Claim 16

A remote management server for purchasing a product comprising:
a remote management server memory that maintains a payment method,
a remote management server transceiver that:
receives user input login information including a userID and information related to a password from a non-browser based application, wherein the non-browser based application is a mobile operating system platform non-browser based mobile application with a graphical user interface which includes a graphical icon that is preinstalled or downloaded and installed on a mobile device, wherein the non-browser based application stored on the mobile device receives the user input login information including the userID and the information related to the password through user input via a mobile device display of the mobile device, the mobile device including the mobile device display, a mobile device processor, a mobile device wireless transceiver configured to support voice and data interactions through a first wireless communication channel, and a mobile device wireless fidelity (Wi-Fi) transceiver;
after user authentication, sends a list of products to the non-browser based application for display using the non-browser based application;
receives an identification of one or more products selected from the list of products, from the non-browser based application, 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;
receives a transaction purchase request for the one or more products from the non-browser based application, 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 receiving the transaction purchase request for the one or more products, transmits the payment method to a transaction server which processes a transaction for the one or more products using the payment method that corresponds to the userID;
receives a transaction verification from a transaction server, wherein the transaction verification indicates that the transaction for the one or more products has been processed; and
after the transaction for the one or more products has been processed, sends a digital artifact to the non-browser based application for display within the non-browser based application generated screen using the mobile device display; and
a remote management server processor that
upon receipt of the user input login information including the userID and information related to a password, authenticates the user associated with the user input login information.

### Claim 17 (depends on 16)

The remote management server of claim 16, wherein the payment method is a credit card, a debit card, or a prepaid card.

### Claim 18 (depends on 16)

The remote management server of claim 16, wherein the digital artifact is a receipt, ticket, media, content, advertisement, or coupon.

### Claim 19 (depends on 16)

The remote management server of claim 16, further wherein the digital artifact can be used by the non-browser based application when there is not a network connection.

### Claim 20 (depends on 16)

The remote management server of claim 16, further wherein the non-browser based application can be used when the mobile device is not connected to a wireless network.

### Claim 21 (depends on 16)

The remote management server of claim 16, further wherein the non-browser based application displays the digital artifact while the mobile device maintains a wireless connection to a wireless network; and
further comprises:
losing the wireless 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 wireless connection, continuing to display the digital artifact within the non-browser based application.

### Claim 22 (depends on 16)

The remote management server of claim 16, wherein the password is a PIN or biometric data.

### Claim 23 (depends on 16)

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

### Claim 24 (depends on 16)

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

### Claim 25 (depends on 24)

The remote management server of claim 24, wherein the sensitive data comprises at least one of information related to the payment method and information related to expiration dates associated with the payment method.

### Claim 26 (depends on 16)

The remote management server of claim 16, further wherein the remote management server is configured to store a single userID for plurality of mobile devices, and further wherein the configuration means the remote management server scales.

### Claim 27 (depends on 16)

The remote management server of claim 16, further wherein the non-browser based application can be used when the mobile device is not connected to a wireless network.

### Claim 28 (depends on 16)

The remote management server of claim 16, further wherein the non-browser based application is stored in a local mobile device memory during an execution of the non-browser based application, a bulk storage mobile device memory for 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.

### Claim 29 (depends on 16)

The remote management server of claim 16, further wherein the non-browser based application is not Short Messaging Service (SMS).

### Claim 30 (depends on 24)

The remote management server of claim 24, further wherein sensitive data is only sent from the mobile device directly to the remote management server which reduces the potential for identity theft and/or fraudulent purchases made through a mobile device
