Remote transaction processing of at a transaction server

• US 10,825,007 B2
• Filed: 04/15/2014
• Issued: 11/03/2020
• Est. Priority Date: 11/30/2007
• Status: Active Grant

• Current Assignee: Michelle T. Fisher
• Original Assignee: Michelle Fisher
• Inventors: Fisher, Michelle
• Primary Examiner(s): Goyea, Olusegun
• Application Number:
  US14/253,648
• Publication Number:
  US 20140324635A1
• Time in Patent Office: 2,394 Days
• Field of Search: 705 7, 705 16, 705 18, 705 261, 705 30- 34, 705 39- 44, 705 70, 705 11, 705 1467, 705 1472, 705 24, 705 28, 705 35, 705 2662, 705 65, 705 1423, 705 268, 705 271, 705 2681, 705 51, 705 46, 455406, 455407, 4554141, 455411, 707737, 707754, 707621, 707622, 707999103, 707999107, 23546246, 380201, 348 1403, 713153
• 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 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

1. A method for processing a transaction, comprising:

receiving, at a transaction server, a payment method that corresponds to an identification code associated with a user from a remote management server, wherein

prior to receiving the payment method that corresponds to the identification code associated with the user from the remote management server, the remote management server

sends a list of products to a non-browser based application generated screen generated by a non-browser based application with a graphical user interface that is downloaded and installed on a mobile device for display with a mobile device display of the mobile device, wherein the non-browser based application only generates a non-browser based application generated screen, the non-browser based application generated screen corresponding to a specific screen or area of the non-browser based application, the mobile device including the mobile device display, a mobile device processor, a mobile device wireless radio transceiver configured to support voice and data interactions through a first wireless communication channel, and a mobile device wireless fidelity (Wi-Fi) transceiver,

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

receives a transaction purchase request from a user from the non-browser based application generated screen, wherein the non-browser based application generated screen receives the transaction purchase request via the mobile device display of the mobile device

receives user input login information including an identification code associated with the user from the non-browser based application generated screen, wherein the non-browser based application generated screen stored on the mobile device receives the user input login information via a mobile device display of the mobile device;

upon receipt of the user input login information, authenticating, at the remote management server, the user associated with the user input login information; and

transmits the payment method that corresponds to the identification code associated with the user to the transaction server;

processing, at the transaction server, the transaction using the payment method; and

sending, from the transaction server, a transaction verification to the remote management server, wherein the transaction verification indicates that the transaction has processed and further wherein after receiving the transaction verification, the remote management server downloads the one or more products to the mobile device.

4. The method of claim 1, wherein the payment method is a default payment method.

5. The method of claim 1, wherein the payment method is a user selected payment method.

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

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

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

13. The method of claim 12, wherein the sensitive data comprises at least one of information related to the payment method, information related to the user input login information , information related to identification information, and information related to an expiration dates associated with the payment method.

18. The method of claim 1, further wherein after the transaction has processed, the remote management server sends a digital artifact to the mobile device.

19. The method of claim 18, further wherein the digital artifact is cached on the mobile device and accessible by the non-browser based application when there is no network connection.

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

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

22. The method of claim 1, further wherein the non-browser based application generated screen receives input to zoom into an image associated with a product to be purchased which results in an updated image of the product to be purchased being displayed, wherein the non-browser based application receives the input to zoom into the image associated with the product to be purchased via the mobile device display of the mobile device.

23. The method of claim 1, further wherein the graphical user interface enables the interaction between the non-browser based application and the mobile device through a graphical icon, wherein the non-browser based application receives the interaction via the mobile device display of the mobile device.

24. The method of claim 18, 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 a digital artifact in an organized and easily retrievable fashion.

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

33. The method of claim 32, wherein the advertisement or coupon is based on one or more targeting parameters.

34. The method of claim 33, wherein the one or more targeting parameters comprise personal information and transaction related information.

2. A transaction server for processing a transaction, comprising:

a transaction server interface configured to;

receive a payment method that corresponds to an identification code associated with a user from a remote management server, wherein

prior to receiving the payment method that corresponds to the identification code associated with the user from the remote management server, the remote management server

sends a list of products to a non-browser based application generated screen generated by a non-browser based application with a graphical user interface that is downloaded and installed on a mobile device for display with a mobile device display of the mobile device, wherein the non-browser based application only generates a non-browser based application generated screen, the non-browser based application generated screen corresponding to a specific screen or area of the non-browser based application, the mobile device including the mobile device display, a mobile device processor, a mobile device wireless radio transceiver configured to support voice and data interactions through a first wireless communication channel, and a mobile device wireless fidelity (Wi-Fi) transceiver;

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

receives a transaction purchase request including information relating to the identification of the one or more products from the non-browser based application generated screen, wherein the non-browser based application generated screen receives the transaction purchase request from the user via the mobile device display of the mobile device;

receives user input login information including an identification code associated with a user from the non-browser based application generated screen, wherein the non-browser based application generated screen receives the user input login information via a mobile device display of the mobile device;

upon receipt of the user input login information, authenticating, at the remote management server, a user associated with the user input login information;

transmits the payment method that corresponds to the identification code associated with the user to the transaction server; and

send a transaction verification to the remote management server, wherein the transaction verification indicates that the transaction has processed and further wherein after receiving the transaction verification, the remote management server downloads the one or more products to the mobile device;

a transaction server processor that processes the transaction using the payment method.

6. The transaction server of claim 2, where the payment method includes credit card information.

7. The transaction server of claim 2, wherein the payment method is a default payment method.

8. The transaction server of claim 2, wherein the payment method is a user selected payment method.

9. The transaction server of claim 2, where the payment method includes credit card information.

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

15. The transaction server of claim 14, 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.

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

17. The transaction server of claim 16, wherein the sensitive data comprises at least one of information related to the payment method information related to the user input login information, information related to identification information, and information related to an expiration dates associated with the payment method.

25. The transaction server of claim 2, further wherein after the transaction has processed, the remote management server sends a digital artifact to the mobile device.

26. The transaction server of claim 25, further wherein the digital artifact is cached on the mobile device and accessible by the non-browser based application when there is no network connection.

27. The transaction server of claim 25, 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.

28. The transaction server of claim 25, wherein the remote management server sends the digital artifact to the non-browser based application generated screen based on the geographical location of the mobile device.

29. The transaction server of claim 2, further wherein the non-browser based application generated screen receives input to zoom into an image associated with a product to be purchased which results in an updated image of the product to be purchased being displayed, wherein the non-browser based application receives the input to zoom into the image associated with the product to be purchased via the mobile device display of the mobile device.

30. The transaction server of claim 2, further wherein the graphical user interface enables the interaction between the non-browser based application and the mobile device through a graphical icon, wherein the non-browser based application receives the interaction via the mobile device display of the mobile device.

31. The transaction server of claim 25, 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 a digital artifact in an organized and easily retrievable fashion.

35. The transaction server of claim 25, wherein the digital artifact is media, content, ticket, a receipt, an advertisement or coupon.

36. The transaction server of claim 35, wherein the advertisement or coupon is based on one or more targeting parameters.

3. A non-transitory computer readable medium for processing a transaction, comprising:

computer code for receiving, at a transaction server, a payment method that corresponds to an identification code associated with a user from a remote management server from a remote management server, wherein

prior to receiving the payment method that corresponds to the identification code associated with the user from the remote management server, the remote management server

sends a list of products to a non-browser based application generated screen generated by a non-browser based application with a graphical user interface that is downloaded and installed on a mobile device for display with a mobile device display of the mobile device, wherein the non-browser based application only generates a non-browser based application generated screen, the non-browser based application generated screen corresponding to a specific screen or area of the non-browser based application, the mobile device including the mobile device display, a mobile device processor, a mobile device wireless radio transceiver configured to support voice and data interactions through a first wireless communication channel, and a mobile device wireless fidelity (Wi-Fi) transceiver,

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

receives a transaction purchase request including information relating to the identification of the one or more products from the non-browser based application generated screen, wherein the non-browser based application generated screen receives the transaction purchase request from a the user via the mobile device display of the mobile device;

receives user input login information including an identification code associated with the user from the non-browser based application generated screen, wherein the non-browser based application generated screen stored on the mobile device receives the user input login information via a mobile device display of the mobile device;

upon receipt of the user input login information, authenticating, at the remote management server, a user associated with the user input login information; and

transmits the payment method that corresponds to the identification code associated with the user to the transaction server;

computer code for processing, at the transaction server, the transaction using the payment method; and

computer code for sending, from the transaction server, a transaction verification to the remote management server, wherein the transaction verification indicates that the transaction has processed and further wherein after receiving the transaction verification, the remote management server downloads the one or more products to the mobile device.