IP Library Granted Patent US 9,953,314
Granted Patent B2
US 9,953,314 · App. 13/649,704 · Granted Apr 24, 2018

System, method, and computer-readable storage medium for payment of online purchases via a portable computing device

Inventors: Abiel Jaquez (Plano, TX); Alexander Muse (Dallas, TX); John Boyd (Denton, TX); Matthew Weathers (Palo Alto, CA); Scott Gordon Roberts (Dallas, TX); Kevin Henry Clark (Denton, TX); Rylan Barnes (Plano, TX)
Assignee: SHOPSAVVY., INC.
G06Q20/36G06Q20/12G06F3/0482G06F3/04842G06F17/30893G06Q30/02G06Q30/0201G06Q30/0601G06Q30/0613G06Q30/0641
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 9,953,314
App. No.
13/649,704
Granted
Apr 24, 2018
Kind
B2
Abstract

A system, method, and computer-readable storage medium for enabling an individual to use a purchase-proxy mechanism to conduct a financial transaction from a computing device with an online merchant, whereby the individual is enabled to use stored personal data, such as financial account information and fulfillment information, without having to store the personal data with the online merchant. The system, method, and computer-readable storage medium furthermore enable an individual to change a payment and/or fulfillment option at the time of purchase with minimal inconvenience.

Claims (83)

1. A purchase-proxy computer for interacting with at least a first online merchant system associated with a first merchant and a second online merchant system associated with a second merchant, the purchase-proxy computer comprising:

a processor; and

a memory storing executable instructions that, in response to execution by the processor, cause the purchase-proxy computer to at least:

receive a product-purchase request from a client device, the product-purchase request indicating a product to be purchased;

in response to receiving the product-purchase request:

utilize first online merchant interface data to interact with the first online merchant system to obtain first purchase data, wherein:

the first online merchant interface data includes data corresponding to multiple interfaces for interacting with the first online merchant system, the multiple interfaces including one or more of an API, standard Web site, mobile Web site, mobile app, and non-public URL for interacting with the first online merchant system, the proxy-purchase computer interfacing with the first online merchant system based on selection from the multiple interfaces, the selection from the multiple interfaces based upon efficiency or reliability of interfacing with the first online merchant system;

the first purchase data includes one or more of first online merchant data, product information, fulfillment data and price data for the first online merchant system; and

utilize second online merchant interface data to interact with the second online merchant system to obtain second purchase data, the second online merchant interface data including information for interacting with the second online-merchant system, the second purchase data including one or more of second online merchant data, product information, fulfillment data and price data for the second online merchant system;

transmit the first and second purchase data to the client device;

receive purchase-selection data from the client device in response to the transmitted first and second purchase data, the purchase-selection data including selection of one of the first and second online merchant systems for purchase of the product; and

in response to receiving the purchase-selection data, utilize the merchant interface data corresponding to the selected online merchant system to provide the selected online-merchant system user-wallet data, or to utilize previously submitted user-wallet data, to effect purchase of the product from the selected online-merchant system on behalf of a user of the client device via at least one of an application programming interface and automated data entry based on the merchant interface data for the selected online merchant system.

2. The purchase-proxy computer of claim 1 , wherein the memory stores further executable instructions that, in response to execution by the processor, cause the purchase-proxy computer to:

select one of a plurality of different types of interfaces for communication of the user-wallet data to the selected online merchant system, the different types of interfaces including a user interface, a mobile user interface or an application programming interface, the selection of the one of the plurality of interfaces based upon efficiency or reliability of interfacing with the selected online merchant system; and

cause communication of the user-wallet data to the selected online merchant system via the selected type of interface.

3. The purchase-proxy computer of claim 1 , wherein the user-wallet data includes one or more of credential information, contact information, demographic data, reward card data, financial account data, or a user preference.

4. The purchase-proxy computer of claim 1 , wherein the memory stores further executable instructions that, in response to execution by the processor, cause the purchase-proxy computer to receive at least a portion of the user-wallet data from the client device in connection with receiving the product-purchase request.

5. The purchase-proxy computer of claim 1 , wherein the memory stores further executable instructions that, in response to execution by the processor, cause the purchase-proxy computer to receive incentive data relevant to the product from one or more incentive systems, the instruction communicated to the selected online merchant being to conduct the purchase of the product according to the incentive data.

6. The purchase-proxy computer of claim 1 , wherein obtaining the first merchant purchase data comprises:

utilizing the first online merchant interface data to interact with the first online merchant system to provide the user-wallet data and an indicator of the product to be purchased to the first online merchant system; and

in response to providing the user-wallet data and the indicator, receiving the first merchant purchase data.

7. The purchase-proxy computer of claim 1 , wherein:

in response to receiving the product-purchase request, the processor is further caused to interface with the first online merchant system via multiple interfaces simultaneously.

8. The purchase-proxy computer of claim 1 , wherein the second online merchant interface data includes data corresponding to an interface for interacting with the second online merchant system, the interface for the second online merchant system being different than an interface used for the first online merchant system.

9. A method to conduct a purchase with an online merchant system using a purchase-proxy computer, the method comprising:

receiving a product-purchase request at the purchase-proxy computer from a client device, the product-purchase request indicating a product to be purchased,

in response to receiving the product-purchase request, receiving, at the purchase-proxy computer, purchase data for the product from at least two online merchant systems, the purchase data including merchant data, price data, and fulfillment data for each of the at least two online merchant systems;

causing communication of the purchase data from the purchase-proxy computer to the client device;

receiving purchase-selection data at the purchase-proxy computer from the client device in response to the purchase data, the purchase-selection data including selection of a selected one of the at least two online merchant systems;

in response to receiving the purchase-selection data, interacting with the selected online merchant system to provide user-wallet data to the selected online merchant system, or to utilize previously submitted user-wallet data, to effect purchase of the product from the selected online-merchant system on behalf of a user of the client device via at least one of an application programming interface and automated data entry;

selecting one of a plurality of different types of interfaces for communication of the user-wallet data to the selected online merchant system, the different types of interfaces including a user interface, a mobile user interface or an application programming interface, the selection of the one of the plurality of interfaces based upon efficiency or reliability of interfacing with the selected online merchant system; and

causing communication the user-wallet data to the respective selected online merchant system via the selected type of interface.

10. The method of claim 9 , wherein the user-wallet data includes one or more of credential information, contact information, demographic data, reward card data, financial account data, or a user preference.

11. The method of claim 9 , further comprising receiving at least a portion of the user-wallet data from the client device in connection with receiving a product-purchase request.

12. The method of claim 9 , further comprising receiving incentive data relevant to the product from one or more incentive systems, the instruction communicated to the selected online merchant being to conduct the purchase of the product according to the incentive data.

13. The method of claim 9 , wherein receiving, at the purchase-proxy computer, the purchase data, comprises:

interacting with the first online merchant system to provide the user-wallet data and an indicator of the product to be purchased to the first online merchant system; and

in response to providing the user-wallet data and the indicator, receiving at least a portion of the purchase data from the first online merchant system.

14. A non-transitory computer-readable storage medium having computer-readable program code portions stored therein that, in response to execution by a processor, cause a purchase-proxy computer to at least:

receive a product-purchase request from a client device, the product-purchase request indicating a product to be purchased;

in response to receiving the product-purchase request:

utilize first online merchant interface data to interact with a first online merchant system associated with a first online merchant to obtain first merchant purchase data, the first online merchant interface data including information for interacting with the first online merchant system, the first merchant purchase data including one or more of first online merchant data, product information, fulfillment data and price data for the first online merchant system; and

utilize second online merchant interface data to interact with a second online merchant system associated with a second merchant to obtain second purchase data for the product from the second online merchant system, the second online merchant interface data including information for interacting with the second online-merchant system, the second purchase data including one or more of second online merchant data, product information, fulfillment data and price data for the second online merchant system;

transmit the first and second purchase data to the client device;

receive purchase-selection data from the client device in response to the transmitted first and second purchase data, the purchase-selection data including selection of one of the first and second online merchant systems; and

in response to receiving the purchase-selection data, utilize the merchant interface data corresponding to the selected online merchant system to provide the selected online merchant system user-wallet data, or to utilize previously submitted user-wallet data, to effect purchase of the product from the selected online-merchant system on behalf of a user of the client device via at least one of an application programming interface and automated data entry based on the merchant interface data for the selected online merchant system.

15. The computer-readable storage medium of claim 14 having further computer-readable program code portions stored therein that, in response to execution by the processor, cause the purchase-proxy computer to:

select one of a plurality of different types of interfaces for communication of the user-wallet data to the selected online merchant system, the different types of interfaces including a user interface, a mobile user interface or an application programming interface; and

cause communication of the user-wallet data to the selected online merchant system via the selected type of interface.

16. The computer-readable storage medium of claim 14 , wherein the user-wallet data includes one or more of credential information, contact information, demographic data, reward card data, financial account data, or a user preference.

17. The computer-readable storage medium of claim 14 having further computer-readable program code portions stored therein that, in response to execution by the processor, causes the purchase-proxy computer to receive at least a portion of the user-wallet data from the client device.

18. The computer-readable storage medium of claim 14 having further computer-readable program code portions stored therein that, in response to execution by the processor, causes the purchase-proxy computer to receive incentive data relevant to the product from one or more incentive systems, the instruction communicated to the selected online merchant being to conduct the purchase of the product according to the incentive data.

19. The computer-readable storage medium of claim 14 , wherein obtaining the first merchant purchase data comprises:

utilizing the first online merchant interface data to interact with the first online merchant system to provide the user-wallet data and an indicator of the product to be purchased to the first online merchant system; and

in response to providing the user-wallet data and the indicator, receiving the first merchant purchase data.

20. A purchase-proxy computer comprising:

a processor; and

a memory storing:

a first portion of user-wallet data associated with a user-wallet identifier; and

executable instructions that, in response to execution by the processor, cause the purchase-proxy computer to at least:

receive a product-purchase request from a client device, the product-purchase request indicating a product to be purchased, and including the user-wallet identifier;

receive a second portion of the user-wallet data from the client device;

assemble the user-wallet data using the first and second portions of the user-wallet data;

receive, at the purchase-proxy computer, purchase data from at least first and second online merchant systems respectively associated with first and second merchants, the purchase data including merchant data, price data, and fulfillment data for each of the first and second online merchant systems;

cause communication of the purchase data to the client device;

receive purchase-selection data from the client device in response to the purchase data, the purchase-selection data including selection of the first online merchant and a corresponding fulfillment option for a purchase of the product;

in response to receiving the purchase-selection data, automatically provide the first online merchant system the user-wallet data to effect purchase of the product from the first online-merchant system on behalf of a user of the client device in accordance with the fulfillment option via one or more interfaces selected from a plurality of potential interfaces based on efficiency or reliability.

21. The purchase-proxy computer of claim 20 , further comprising:

the purchase proxy computer interacting with the first online merchant system to obtain a portion of the purchase data from the first online merchant system; and

the purchase proxy computer storing the portion of the purchase data in a memory of the purchase proxy computer.

22. A method to conduct a purchase with an online merchant using a purchase-proxy computer, the method comprising:

(a) providing a purchase proxy computer comprising:

(i) stored first and second merchant conduits configured to respectively communicate with first and second online merchant systems, at least the first merchant conduit including data corresponding to multiple interfaces for interacting with the first online merchant system, the multiple interfaces including one or more of an API, standard Web site, mobile Web site, mobile app, and non-public URL selected based on efficiency and reliability of communicating with the first online merchant system;

(ii) stored user wallet information; and

(iii) purchase data for a product for each of the first and second online merchant systems;

(b) receiving a product-purchase request at the purchase-proxy computer from a client device, the product-purchase request indicating the product, and transmitting the purchase data to the client device in response thereto;

(d) receiving purchase-selection data at the purchase-proxy computer from the client device in response to the transmitting, said purchase-selection data indicating selection of the first merchant;

(e) assembling user wallet information; and

(f) causing communication to conduct purchase of the product to the first online merchant via the first merchant conduit and selection from the multiple interfaces, whereby user-wallet information is provided to the online-merchant system based on selection from the multiple interfaces of the first merchant conduit, via at least one of an application programming interface and automated data entry.

23. The method according to claim 22 wherein said providing further comprises monitoring interface changes to the first and second online merchant systems and correspondingly updating the first and second merchant conduits in the purchase proxy computer.

24. The method of claim 22 , further comprising:

the purchase proxy computer interacting with the first online merchant system to obtain a portion of the purchase data from the first online merchant system; and

the purchase proxy computer storing the portion of the purchase data in a memory of the purchase proxy computer.

Assignments (11)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 8, 2022
From: PURCH GROUP, LLC,
To: MONOLITH TECHNOLOGIES INC.
Reel/Frame 059201/0220 →
SECURITY INTEREST Recorded Oct 4, 2018
From: PURCH GROUP, LLC
To: HSBC UK BANK PLC
Reel/Frame 047068/0583 →
CHANGE OF NAME Recorded Sep 4, 2018
From: PURCH GROUP, INC.
To: PURCH GROUP, LLC
Reel/Frame 047012/0860 →
RELEASE OF SECURITY INTEREST Recorded Sep 4, 2018
From: COMERICA BANK
To: SHOPSAVVY, INC.
Reel/Frame 046783/0419 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 30, 2018
From: SHOPSAVVY, INC.
To: PURCH GROUP, INC.
Reel/Frame 046751/0835 →
SECURITY INTEREST Recorded Jun 1, 2016
From: SHOPSAVVY, INC.
To: COMERICA BANK
Reel/Frame 038769/0162 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 4, 2016
From: SHOPSAVVY INC.
To: SV ACQUISITION HOLDINGS, INC. (NOW KNOWN AS SHOPSAVVY, INC.)
Reel/Frame 037896/0060 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 10, 2014
From: MUSE, ALEXANDER
To: BIG IN JAPAN
Reel/Frame 032181/0740 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 10, 2014
From: WEATHERS, MATTHEW
To: SHOPSAVVY, INC.
Reel/Frame 032181/0850 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 10, 2014
From: JAQUEZ, ABEL; BOYD, JOHN; ROBERTS, SCOTT GORDON; CLARK, KEVIN HENRY; BARNES, RYLAN
To: SHOPSAVVY, INC.
Reel/Frame 032181/0916 →
CHANGE OF NAME Recorded Feb 10, 2014
From: BIG IN JAPAN
To: SHOPSAVVY, INC.
Reel/Frame 032193/0150 →
Continuity (3)
Provisional Application 61670827 · Jul 12, 2012
Provisional Application 61640906 · May 1, 2012
Related Publication 20130297390A1 · Nov 7, 2013