阅读说明：本技术 用于第三方购买的方法及系统 (Method and system for third party purchase ) 是由 可伦·胡默尔阿隆 于 2018-05-08 设计创作，主要内容包括：方法及系统提供支付项目,如商品及服务,由他人选择,通过支付卡的授权持有人进行,如交易的第三方,为第三方指定支付项目。因此,一个有效及授权的支付卡的购买,例如,直接地,在实际的信用卡持有者及卖方之间进行,以符合所述支付卡(支付卡发行者)的规则。(Methods and systems provide payment items, such as goods and services, selected by others, to be made by authorized holders of payment cards, such as third parties to transactions, to designate payment items for the third parties. Thus, the purchase of a valid and authorized payment card, for example, directly between the actual credit card holder and the seller, is made to comply with the rules of the payment card (payment card issuer).)

1. A computer method for paying for an item selected by a purchaser, comprising the steps of:

(a) receiving, by a host computer over a communications network, 1) an electronic data object comprising a list of one or more items, one or more of the electronic data objects selected by a buyer associated with a buyer computer from a supplier associated with a supplier computer; 2) selecting a payer for the item of the electronic data object from the buyer's computer;

(b) the host computer responding to receiving the electronic data object and the payer's selection by sending a copy of the electronic data object to a computer associated with the payer, the copy of the electronic data object mapping to the computer of each provider of each item and the host computer; and

(c) the host computer receives from each supplier computer, over the communications network, a payment indication of items paid by the payer, which is otherwise an indication that all items paid have been released to the payer buyer.

2. The method of claim 1, wherein: the method further comprises:

(d) for unpaid items, a subsequent electronic data object is created that includes the unpaid item, and the subsequent data object is presented to the buyer computer to receive a selection of a payer for the electronic data object.

3. The method of claim 2, wherein: the method further comprises:

(e) the host computer responds to receipt of a subsequent electronic data object and selection by the payer by transmitting a copy of the subsequent electronic data object to the computer associated with the payer, which copy of the electronic data object maps to the name of each provider for each item of the computer and is sent to the host computer.

4. The method of claim 3, wherein: the method further comprises:

(f) the host computer receives from each supplier computer, over the communications network, a payment indication of items paid by the payer, which is otherwise an indication that all items paid have been released to the payer buyer.

5. The method of claim 4, wherein: receiving the payer selection includes: receiving a selection of at least one of: a specific payer, or a request to the host computer to select a payer.

6. The method of claim 5, wherein: the particular payer includes a payer from a database of payers associated with the buyer or is not a payer from a database of payers associated with the buyer.

7. The method of claim 5, wherein: the request to the host computer to select the payer is based on rules and policies.

8. The method of claim 1, wherein: prior to step (a), an electronic data object comprising one or more lists of items is presented to the buyer via the buyer computer, and the buyer is prompted to select a payer for an item of the electronic data object via the buyer computer.

9. The method of claim 1, wherein: the method further comprises:

the host computer receives an indication of acceptance of an item of the electronic data object to be paid for by the payer, sent from the payer computer to the host computer.

10. The method of claim 1, wherein: the method further comprises:

the host computer receives an indication of acceptance for an item of the electronic data object, the item being paid by the payer in accordance with rules and policies.

11. The method of claim 9 or 10, wherein: if the acceptance indication of the item is not received and/or the payer fails to pay within a predetermined time, the first computer takes at least one action comprising:

creating a subsequent electronic data object including unacceptable items and/or unpaid items and sending the subsequent electronic data object to the buyer computer to select a payer;

terminating the electronic data object; or

An electronic data object is stored.

12. The method of claim 11, wherein: if the at least one action includes creating a subsequent electronic data object including the non-accepted item and/or the non-paid item, and sending the subsequent electronic data object to the buyer computer to select the payer, the host computer:

(a) receiving, from the buyer computer over the communications network, 1) a subsequent electronic data object comprising a list of unapproved and/or unpaid items; and 2) a payer who selects an item of the electronic data object;

(b) responding to receipt of the electronic data object and selection by the payer by transmitting a copy of the electronic data object to a computer associated with the payer, the copy of the electronic data object having been mapped to each of the suppliers' computer items and host computers; and

(c) a payment indication of the items paid by the payer is received from each supplier computer over the communications network for the purpose of delivering all items paid to the buyer.

13. The method of claims 1 and 11, wherein: the electronic data object includes at least one electronic shopping cart.

14. The method of claim 1, wherein: the subsequent electronic data object includes at least one electronic shopping cart.

15. The method of claim 1, wherein: the electronic data object is from a website or application.

16. A computer method for paying for an item purchased by a purchaser, comprising the steps of:

a first electronic data object is received from a computer associated with a purchaser of the computer, the first electronic data object including items associated with at least one vendor, and a selection of a payer of the items of the first electronic data object, via a payment system associated with the host computer. An item of a first electronic data object;

sending, by a payment system associated with a host computer, a second electronic data object based on the first electronic data object to a computer associated with a selected payer for the first electronic data object, the second electronic data object mapped to the computer associated with at least one vendor and the host computer;

receiving an acceptance indication, whether each item in the second electronic data object is accepted by a payer for payment, and whether a payment indication is received for the item for which the payer accepts payment and is paid;

for items of the second electronic data object that the payer does not accept payment and/or that the payer does not pay, the payment system of the host computer creates a third electronic data object for the non-accepted and/or non-paid item for presentation to the buyer by a computer associated with the buyer; and

for items of the second electronic data object that are accepted and paid by the payer of the payment system of the host computer, the payment indication also indicates that the items of the second electronic data object are paid for use by the buyer.

17. The method of claim 16, wherein: a payment system of the host computer receives the acceptance indication and the payment indication.

18. The method of claim 17, wherein: the payment instructions are received from a computer associated with the provider of each paid item.

19. The method of claim 18, wherein: if the payer does not pay for the payment within the predetermined time, each item of the second electronic data object for which the payer accepts the payment becomes unpaid.

20. The method of claim 19, wherein: a payment system associated with the host computer sends the third electronic data object to a computer associated with the buyer and causes the computer associated with the buyer to prompt the buyer to select a payer for the third electronic data object and its items.

21. The method of claim 20, wherein: the payment system associated with the host computer performs at least one process comprising:

transmitting the third electronic data object to a computer associated with the selected payer; storing the third electronic data object; or

The third electronic data object is terminated.

22. The method of claim 21, wherein: the second electronic data object is a copy of the first electronic data object.

23. The method of claim 22, wherein: the third electronic data object is created with the item from the second electronic data object.

24. The method of claim 23, wherein: the third electronic data object includes certain items of the second electronic data object.

25. The method of claim 23, wherein: the third electronic data object includes all of the items of the second electronic data object.

26. The method of claim 21, wherein: the third electronic data object is the second electronic data object.

27. The method of claims 22 to 26, wherein: the first electronic data object, the second electronic data object and the third electronic data object are electronic shopping carts.

28. The method of claim 27, wherein: the first electronic data object, the second electronic data object and the third electronic data object are from a web page or an application.

29. A computer system for paying for an item purchased by a purchaser, comprising:

a storage medium for storing a computer component; and

at least one processor for executing computer components, comprising:

a first computer component for receiving from a computer associated with a purchaser of a first electronic item a first electronic data object including an item associated with at least one supplier, and a selection data object for a payer of the item of the first electronic data object;

a second computer component for sending a second electronic data object based on the first electronic data object to a computer associated with the payer of the selected first electronic data object, the second electronic data object being mapped to at least one associated computer vendor and host computer;

a third computer component for receiving an acceptance indication, whether each item of the second electronic data object is accepted by a payer for payment, and whether a payment indication is received for the item accepted by the payer for payment and paid; and

a fourth computer component for:

creating a third electronic data object for the non-accepted and/or non-paid items of the second electronic data object for presentation to the purchaser via a computer associated with the purchaser; and

at least one indication of payment for an item of the second electronic data object accepted and paid by the payer is received, the at least one indication of payment further indicating payment for the item of the second electronic data object accessible to the purchaser.

30. The system of claim 29, wherein: the second electronic data object is a copy of the first electronic data object.

31. The system of claim 30, wherein: the third electronic data object is created with the item from the second electronic data object.

32. The system of claim 31, wherein: the third electronic data object includes some of the items of the second electronic data object.

33. The system of claim 31, wherein: the third electronic data object includes all of the items of the second electronic data object.

34. The system of claim 29, wherein: the third electronic data object is the second electronic data object.

35. The system of any of claims 30 to 34, wherein: the first electronic data object, the second electronic data object and the third electronic data object are electronic shopping carts.

36. A computer usable non-transitory storage medium on which a computer program for causing a suitable programmed system to pay for an item purchased by a purchaser is implemented when such program is executed on a computer, by performing the steps comprising:

receiving a first electronic data object from a computer associated with a purchaser of an item of the first electronic data object, the first electronic data object including an item associated with at least one vendor and a selection of a payer of the item of the first electronic data object;

sending a second electronic data object based on the first electronic data object to a computer associated with the payer selected for the first electronic data object, the second electronic data object being mapped to a computer associated with at least one of the vendor and the host computer;

receiving an acceptance indication, whether each item in the second electronic data object is accepted by a payer for payment, and whether a payment indication is received for the item for which the payer accepts payment and is paid;

for items of the second electronic data object for which the payer does not accept payment and/or for which the payer does not pay, creating a third electronic data object for the non-accepted item and/or the non-paid item for presentation to the purchaser via a computer associated with the purchaser; and

for items of the second electronic data object that are accepted and paid by the payer who received the payment instruction, the payment instruction also indicates payment of items of the second electronic data object that the purchaser may access.

37. The computer-usable non-transitory storage medium of claim 36, wherein: the steps further include: receiving the acceptance indication and the payment indication.

38. The computer-usable non-transitory storage medium of claim 37, wherein: receiving the indication of payment from a computer associated with each of the suppliers of paid money.

39. The computer-usable non-transitory storage medium of claim 38, wherein: if the payer does not pay for the payment within the predetermined time, each item of the second electronic data object accepted for payment by the payer becomes unpaid.

40. The computer-usable non-transitory storage medium of claim 39, wherein: the payment system associated with the host computer sends the third electronic data object to the computer associated with the buyer and causes the computer associated with the buyer to prompt the buyer for selection. A third electronic data object and a payer of an item thereof.

41. The computer-usable non-transitory storage medium of claim 40, wherein: the steps further include performing at least one process, the process comprising:

transmitting the third electronic data object to a computer associated with the selected payer;

storing the third electronic data object; and

the third electronic data object is terminated.

42. The computer-usable non-transitory storage medium of claim 41, wherein: the second electronic data object is a copy of the first electronic data object.

43. The computer-usable non-transitory storage medium of claim 42, wherein: the third electronic data object is created with the item from the second electronic data object.

44. The computer-usable non-transitory storage medium of claim 43, wherein: the third electronic data object includes certain items of the second electronic data object.

45. The computer-usable non-transitory storage medium of claim 43, wherein: the third electronic data object includes all of the items of the second electronic data object.

46. The computer-usable non-transitory storage medium of claim 41, wherein: the third electronic data object is the second electronic data object.

47. A computer-usable non-transitory storage medium as recited in claims 42-46, wherein: the first electronic data object, the second electronic data object and the third electronic data object are electronic shopping carts.

Technical Field

The invention relates to a method and a system for payment.

Background

Today's economy relies heavily on credit and debit cards, collectively "payment cards. For example, an authorized payment card holder may hand his payment card to another person for purchase. Purchase transactions conducted in this manner are technically inefficient as defined by the payment card. Thus, the seller should not accept the debit card because the actual debit card holder will not give him.

In addition, the relationship between the payment card holder and the person who purchased the payment card from the seller is based solely on trust. The purchaser may purchase other items or services that are not authorized by the cardholder. In this case, the payment card holder lacks protection and recourse rights for the payment card company for these unauthorized goods or services purchased with the person whose payment card is being used.

Even if one were to do so using the aforementioned other's payment card, the seller may have to call or otherwise contact the payment card holder, which may take time. Sales are lost if the payment card holder cannot be contacted, or if no response is made within a certain time.

In addition, many people, even those who own credit cards, may not wish to know their identity nor the goods or services or points of sale listed on the receipt and monthly payment card statement. These people also want to use third party payers. Finally, some people without a payment card need to make credit card payments, for example, when the seller is remote and/or the seller only accepts payment cards.

Disclosure of Invention

The present invention provides methods and systems for allowing payment of items, such as goods and services, selected by others for which a payment object of an authorized holder of the payment card (e.g., a third party to a transaction) is authorized. As a result, for example, valid and authorized payment card purchases are made directly between the actual credit card holder and the seller, and thus within the rules of the payment card (payment card issuer). In addition, the payer may see exactly which items and services the payer has selected for purchase, and the payer may decide on the particular item or items to be paid for. In addition, because the above-described systems and methods are computerized, goods and/or services are selected, then paid for by the payer, and the goods and/or services are issued to the party who selected the goods, e.g., the goods and/or services. The services accessible to the participant who selected the project can now be done in real time.

Embodiments of the present invention relate to a computerized method for paying for an item selected by a buyer, for example, who is not a payer. The method comprises the following steps: receiving, by a host computer over a communication network: 1) an electronic data object including a list of one or more items, each of the one or more items of the electronic data object being selected by a buyer associated with the buyer. A computer from a supplier associated with a supplier computer; 2) selecting a payer for the item of the electronic data object from the buyer's computer; the host computer responding to receiving the electronic data object and selecting the payer by sending a copy of the electronic data object to a computer associated with the payer, the copy of the electronic data object mapping to each of the vendor's computer items and the host computer; and, the host computer receives from each supplier computer, through the communication network, a payment indication of the items that have been paid by the payer, the payment indication additionally being an indicator indicating that all the paid items are released to the buyer.

Optionally, the method further comprises: for unpaid items, a subsequent electronic data object is created that includes the unpaid item, and the subsequent data object is presented to the buyer computer to receive a selection of the payer. An electronic data object.

Optionally, the method further comprises: the host computer responds to receipt of the subsequent electronic data object and selection of the payer by sending a copy of the subsequent electronic data object to a computer associated with the payer. A computer for each vendor mapping to each project and a host computer.

Optionally, the method additionally comprises: the host computer receives from each supplier computer, via the communications network, a payment indication for the items that the payer has paid for, the payment indication otherwise being that an indicator of all paid items is released to the buyer.

Optionally, receiving the payer selection comprises: receiving a selection of at least one of: a specific payer, or a request to the host computer to select a payer.

Optionally, the particular payer includes a payer from a database of payers associated with the buyer, or a payer from a database of payers not associated with the buyer.

Optionally, the request to the host computer to select the payer is based on rules and policies.

Optionally, prior to initially receiving the electronic data object, the electronic data object includes a listing of one or more items, the listing being presented to the buyer via the buyer computer, and the buyer is prompted to select an item of the payer electronic data object via the buyer computer.

Optionally, the method further comprises: the host computer receives an acceptance indication of an item of the electronic data object to be paid by the payer, the acceptance indication being sent from the payer computer to the host computer.

Optionally, the method additionally includes the host computer receiving an acceptance indication for an item of the electronic data object that the payer is to pay for in accordance with the rules and policies.

Optionally, the method is such that, if an indication of acceptance of the item is not received within a predetermined time and/or the payer fails to pay for the item within the predetermined time, the first computer takes at least one action comprising: 1) a subsequent electronic device is created. A data object including unacceptable items and/or unpaid items, and sending a subsequent electronic data object to the buyer computer to select a payer; 2) terminating the electronic data object; alternatively, 3) storing the electronic data object.

Optionally, the method is such that, if the at least one action comprises creating a subsequent electronic data object comprising the non-accepted item and/or the non-paid item, and sending the subsequent electronic data object to the buyer computer to select the payer, the host:

(a) receiving, from the buyer computer over the communications network: 1) subsequent electronic data objects, including lists of non-accepted and/or non-paid items; 2) a payer who selects an electronic data object item;

(b) responding to receipt of the electronic data object and selection by the payer by transmitting a copy of the electronic data object to a computer associated with the payer, the copy of the electronic data object having been mapped to each of the suppliers' computer items and host computers; and

(c) an indication of payment for the items paid by the payer is received from each of the supplier computers over the communications network, the indication of payment being additionally an indication that all of the items paid are released to the buyer and accessible to the buyer.

Optionally, the electronic data object includes at least one electronic shopping cart.

Optionally, the subsequent electronic data object includes at least one electronic shopping cart. Alternatively, the electronic data object is from a website or an application.

Embodiments of the present invention relate to a method for paying for items purchased by a purchaser, e.g., who is not a payer. The method comprises the following steps: a first electronic data object is received from a computer associated with a host computer through a payment system associated with the host computer, the first electronic data object including an item associated with at least one vendor and a selection of a payer for the item of the first electronic data object. A purchaser of an item of the first electronic data object; sending, by a payment system associated with a host computer, a second electronic data object based on the first electronic data object to a computer associated with a selected payer for the first electronic data object, the second electronic data object mapped to the computer associated with at least one vendor and the host computer; receiving an acceptance indication, whether each item in the second electronic data object is accepted by a payer for payment, and whether a payment indication is received for the item for which the payer accepts payment and is paid; for items of the second electronic data object that are not accepted and/or not paid by the payer, the payment system of the host computer creates a third electronic data object for the items and/or payers that are not accepted. An unpaid amount provided to the buyer via a computer associated with the buyer; for the item of the second electronic data object accepted and paid by the payer for whom the payment indication was received by the payment system of the host computer, the payment indication also indicates that the item of the second electronic data is accessible to the buyer for which the data object was paid.

Optionally, the payment system of the host computer receives an acceptance indication and a payment indication.

Optionally, the payment instructions are received from a computer associated with the provider of each paid item.

Alternatively, if the payer does not pay for the payment within a predetermined time, each item of the second electronic data object for which the payer accepts payment becomes unpaid.

Optionally, a payment system associated with the host computer sends the third electronic data object to a computer associated with the buyer and causes the computer associated with the buyer to prompt the buyer to select a payer of the third electronic data object and its items.

Optionally, a payment system associated with the host computer performs at least one process comprising: sending the third electronic data object to the computer associated with the selected payer; and storing the third electronic data object; alternatively, the third electronic data object is terminated.

Optionally, the second electronic data object is a copy of the first electronic data object.

Optionally, a third electronic data object is created using the item from the second electronic data object.

Optionally, the third electronic data object includes some items of the second electronic data object.

Optionally, the third electronic data object includes all of the items of the second electronic data object.

Optionally, the third electronic data object is the second electronic data object.

Optionally, the first electronic data object, the second electronic data object, and the third electronic data object are electronic shopping carts.

Optionally, the first electronic data object, the second electronic data object, and the third electronic data object are from a web page or an application.

Embodiments of the present invention are also directed to a computer system for paying for an item purchased by a purchaser (e.g., not a payer). The system comprises: a storage medium for storing a computer component; and at least one processor for executing the computer components. The computer assembly includes: a first computer component for receiving a first electronic data object comprising an item associated with at least one supplier from a computer associated with a purchaser, and selecting a payer for the item of the first electronic data object. An item of a first electronic data object; a second computer component for sending a second electronic data object based on the first electronic data object to a computer associated with the payer of the selected first electronic data object, the second electronic data object being mapped to at least one associated computer vendor and host computer; a third computer component for receiving an acceptance indication indicating whether the payer accepts each of the second electronic data objects for payment, the payment indication being received for an item for which the payer accepts payment and pays; a fourth computer component for: creating a third electronic data object for the non-accepted and/or non-paid items of the second electronic data object for presentation to the purchaser via a computer associated with the purchaser; at least one payment instruction is received for an item of the second electronic data object accepted and paid by the payer, the at least one payment instruction additionally indicating payment for an item of the second electronic data object accessible to the purchaser.

Optionally, the second electronic data object is a copy of the first electronic data object.

Optionally, a third electronic data object is created using the item from the second electronic data object.

Optionally, the third electronic data object includes some items of the second electronic data object.

Optionally, the third electronic data object includes all of the items of the second electronic data object.

Optionally, the third electronic data object is the second electronic data object.

Optionally, the first electronic data object, the second electronic data object, and the third electronic data object are electronic shopping carts.

Embodiments of the present invention relate to a computer usable non-transitory storage medium having a computer program embodied thereon that, when such program is executed on a system, causes the appropriate programmed system to pay for an item purchased by a purchaser by performing the following steps. These steps include: a first electronic data object is received from a computer associated with a purchaser of an item of the first electronic data object, the first electronic data object including an item associated with at least one vendor and a selection of a payer of the item of the first electronic data object. (ii) a Sending a second electronic data object based on the first electronic data object to a computer associated with the payer selected for the first electronic data object, the second electronic data object being mapped to a computer associated with at least one of the vendor and the host computer; receiving an acceptance indication, whether each item in the second electronic data object is accepted by a payer for payment, and whether a payment indication is received for the item for which the payer accepts payment and is paid; for items of the second electronic data object that are either not accepted for payment by the payer and/or not paid for by the payer, creating a third electronic data object for the items that are not accepted and/or not paid for presentation to the buyer via a computer associated with the buyer; and, for an item of the second electronic data object accepted and paid by the payer who received the payment instruction, the payment instruction also indicates payment of the item of the second electronic data object accessible to the purchaser.

Optionally, the computer-usable non-transitory storage medium has the steps further comprising: an acceptance indication and a payment indication are received.

Optionally, the computer-usable non-transitory storage medium is such that the payment instructions are received from a computer associated with each of the paid items' suppliers.

Optionally, the computer-usable non-transitory storage medium is such that: each item of the second electronic data object accepted by the payer becomes unpaid if the payer does not pay for the payment within a predetermined time.

Optionally, the computer-usable non-transitory storage medium is such that: a payment system associated with the host computer sends the third electronic data object to a computer associated with the buyer and causes the computer associated with the buyer to prompt the buyer to select one. A third electronic data object and a payer of an item thereof.

Optionally, the computer-usable non-transitory storage medium is such that the steps further comprise performing at least one process comprising: transmitting the third electronic data object to a computer associated with the selected payer; storing the third electronic data object; alternatively, the third electronic data object is terminated.

Optionally, the computer-usable non-transitory storage medium is such that the second electronic data object is a copy of the first electronic data object.

Optionally, the computer-usable non-transitory storage medium is such that: a third electronic data object is created with the items from the second electronic data object.

Optionally, the computer-usable non-transitory storage medium causes a third electronic data object to include some items of the second electronic data object.

Optionally, the computer-usable non-transitory storage medium is such that the third electronic data object includes all of the items of the second electronic data object.

Optionally, the computer-usable non-transitory storage medium is such that the third electronic data object is the second electronic data object.

Optionally, the computer-usable non-transitory storage medium is such that the first electronic data object, the second electronic data object, and the third electronic data object are electronic shopping carts.

This document refers to terms used consistently or interchangeably herein. These terms, including variants thereof, are as follows.

Throughout this document, a "website" is a relevant collection of World Wide Web (WWW) files, including a beginning file called the home page or "web page", and typically also other files or "web pages". The term "website" is collectively referred to as "website" and "web page".

A Uniform Resource Locator (URL) is a unique address for a file, such as a web site or web page, that is accessible over a network, including the Internet.

In the following description and drawings, "n" and "nth" represent a series of members or the last member of a series of members, such as an element, computer, server, database, cache, component, list, link, data file, etc.

"computer" includes machines, computers and computing or computer systems (e.g., physically separate locations or devices), servers, computer and computerized devices, processors, processing systems, computing cores (e.g., shared devices), and similar systems, workstations, modules, and combinations thereof. The aforementioned "computers" can be of various types, such as personal computers (e.g., laptop computers, desktop computers, tablet computers) or any type of computing device, including devices that can be easily transported from one location to another (e.g., smart phones, Personal Digital Assistants (PDAs), mobile phones, or cellular phones).

"computer", "server" in accordance with the above definition is typically a remote computer or remote computer system or computer program therein, accessible over a communications medium such as a communications network or other computer network, including the Internet. . A "server" serves or performs the functions of other computer programs (and users thereof) in the same or other computers. The server may also include a virtual machine, a software-based emulation of a computer.

An "application" comprises executable software and optionally any Graphical User Interface (GUI) through which certain functions may be implemented.

A "client" is an application program that runs on a computer, workstation, etc. and relies on a server to perform some of its operations or functions.

Unless defined otherwise herein, all technical and/or scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Although methods and materials similar or equivalent to those described herein can be used in the practice or testing of embodiments of the present invention, the exemplary methods and/or materials are described below. In case of conflict, the patent specification, including definitions, will control. In addition, the materials, methods, and examples are illustrative only and not intended to be necessarily limiting.

Drawings

Some embodiments of the invention are described herein, by way of example only, with reference to the accompanying drawings. With specific reference to the drawings in detail, it is stressed that the particulars shown are by way of example and for purposes of illustrative discussion of the embodiments of the present invention. In this regard, it will be apparent to those skilled in the art from this description, taken in conjunction with the accompanying drawings, how embodiments of the present invention may be practiced.

Attention is now directed to the drawings, wherein like reference numerals or characters designate corresponding or identical components. In the drawings:

FIG. 1 is a schematic diagram of an exemplary environment in which a system of embodiments of the disclosed subject matter is implemented.

Fig. 2A is a block diagram of an architecture of the home server of fig. 1 and a system thereof.

Fig. 2B is a diagram of the payer database of fig. 2A.

Fig. 3 is a flow chart of an example process for a single cart from a single supplier according to an embodiment of the invention.

Fig. 4 is a flow chart of an example process for a single cart from multiple suppliers, according to an embodiment of the invention.

Fig. 5 is a flow chart of an example process for multiple carts corresponding to each of a plurality of suppliers according to an embodiment of the present invention.

Fig. 6A-6H are screen diagrams of a display appearing on a computer or computer monitor of a computer associated with the process of the embodiment of the invention of the flow chart of fig. 3.

Figures 7A-7K are screen views of a display appearing on a computer or computer monitor of a computer associated with the process of the embodiment of the invention of the flow chart of figure 4.

Detailed Description

Before explaining at least one embodiment of the invention in detail, it is to be understood that the invention is not necessarily limited in its application to the details of construction and to the arrangements of the components and/or methods set forth in the following description and/or illustrated in the drawings. Or illustrated in, the accompanying drawings. The invention is capable of other embodiments or of being practiced or carried out in various ways.

As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," module "or" system. Furthermore, aspects of the present invention may take the form of a computer program product embodied on one or more non-transitory computer-readable (storage) media having computer-readable program code embodied thereon.

Throughout this document, numerous textual and graphical references are made to trademarks. These trademarks are the property of their respective owners and are referred to herein for explanatory purposes only.

Reference is now made to fig. 1. The detailed description shows an exemplary operating environment including a network 50 (hereinafter "network"), a Home Server (HS)100 (also referred to as a home computer, host server or host computer) linked to the network 50 as that term is used interchangeably herein. The home server 100 also supports the system 100', alone or in combination with other computers, including servers, components and applications (e.g., client applications) associated with the home server 100, as described below. The network 50 is, for example, a communication network such as a Local Area Network (LAN) or a Wide Area Network (WAN), including a public network such as the internet. As shown in fig. 1, the network 50 is, for example, the internet. Network 50, although shown as a single network, may be a combination of networks and/or networks, including for example, in addition to the internet, one or more cellular networks, Wide Area Networks (WANs), and the like. As used herein, "link" includes a direct or indirect wired or wireless link and places computers, including servers, components, etc., in electronic and/or data communication with each other.

The home server 100 and the system 100' perform various processes according to the present invention, as described below. The home server 100 is caused to receive data objects, such as electronic carts, duplicate electronic carts, augment electronic carts, or create new electronic carts, electronic carts within the processing system 100', transmit electronic carts over the network 50 to the various entities 108, 110a-110n, 115a-115n linked to the network 50. The system 100 'also uses the system 100' and creates a mapping of the electronic carts described above between one or more of a plurality of entities, including a home of the system. The server/system 100/100' itself, the suppliers represented by computers 110a-110n, the payers represented by computers 115a-115n, and the buyers 109 represented by computer 108.

The Home Server (HS)100 has an architecture comprising one or more components, engines, modules, etc. for providing many other server functions and operations. The Home Server (HS)100 may be associated with additional storage, memory, cache and databases, both internal and external. For illustrative purposes, the Home Server (HS)100 may have a Uniform Resource Locator (URL) such as www.hs.com. Although a single Home Server (HS)100 is shown, the Home Server (HS)100 may be formed of multiple servers and/or components.

The application server 102 includes one or more Applications (APP)102 a. From the application server 102, suppliers (e.g., supplier 1 through supplier n) may access, e.g., by downloading, their respective application programs 102a to use the system 100 'via their computers (e.g., servers 110a-110n) and users (buyers/shoppers) 108 (via the smartphone representative's computer 109).

The Application (APP)102a includes code segments of the system 100 'that map to the home server 100 for allowing the provider computers 110a-110 and the user computer 108 to interact with the system 100'. There are also code segments, including self-executing instructions, for performing functions such as setting up an electronic cart (electronic data object) (also referred to herein as a "cart"), adding/subtracting items from the electronic cart, providing the electronic cart. A list of payers with shopping carts (e.g., in the form of a menu), sends the shopping carts to the system 100', and links the shopping carts to various entities, such as suppliers 110a-110n, and payers (computers 115 a-115115 n).

These computers 110a-11on of vendors 1 through n are linked to the network 50 and represent computers associated with vendors of numerous products and services. For example, for purposes of illustration, the vendor 1110a is a large online retailer (URL www.shopnile.com) that sells multiple items (e.g., products and services) from multiple vendors and bundles the items selected by the user (buyer/shopper 108) into a single electronic shopping cart (also referred to as an electronic data object) on its website, and the user 108 shops by selecting items displayed by the website. Also, for example, for illustration purposes, suppliers 2, 3 and 4110 b, 110c, 110d sell special items and use the APP 102 a's electronic data object or shopping cart.

Computers 115a, 115b (these element numbers are also used to indicate payers associated therewith), such as mobile devices, laptop computers, tablet computers (e.g., from cupertino, california, usa)

Manufactured iPads) and server, the computers 115a, 115b are associated with a payer, such as payer 1115a of system 100And payers 2, 115b, which represent all payers of the system (via payers 115n associated with the computer).

Although the servers 100, 102, 110a-110n, and 115a-115n shown in FIG. 1 are structural elements of the servers 100, 102, 110a-110n, and 115a-115n, it is contemplated that FIG. 1 and those described herein are most closely related to the disclosure of the invention herein, as well as other server computers or the like directly or indirectly linked to the network 50.

User computer 108, shown as a smart phone, is linked to the network through a cell tower 120 or the like. User computer 108 is associated with telephone numbers 847-. Although user computer 108 is shown as a smartphone or mobile computer, user computer 108 may be a standard desktop computer, workstation, etc., a laptop computer, a tablet computer (e.g., Apple's iPad). User computer 108, for example, runs a program such as

Such as a Web browsing application (for accessing Web sites and Web pages and URLs), and may use a Web browser application such as Siri^TMSuch as a voice activated browsing application. . User computer 108 may also be a voice operated device, such as Amazon Echo (TM) linked to network 50.

Referring to fig. 2A, the architecture of the system 100' in, for example, a home server 100 is shown. For example, the architecture of the system 100', such as shown in the home server 100, includes a Central Processing Unit (CPU)202 comprised of one or more processors. The CPU 202 is electrically connected to the storage/memory 204, registration and management module 206, request processing/communication/transmission module 206, shopping cart creation module 210, and payor assignment to shopping carts module 212, shopping cart replication module 214, shopping cart payment confirmation module 216, database 218, and system selection module 228 although the components 204, 206, 208, 210, 212, 214, 216, 218, and 228 are shown in the home server 100, any one or more of these components 204, 206, 208, 210, 212, 214, 216, 218, and 228 may be external to the home server 100 and linked to the home server 100 from its external location.

The Central Processing Unit (CPU)202 is formed by one or more processors (including microprocessors) for performing the functions and operations detailed herein of the home server 100, including controlling the components 204, 206, 208, 210, 212, 214, 216, 218, and 228, and executing instructions provided and/or obtained thereby. The Central Processing Unit (CPU)202 processor is, for example, a conventional processor, such as those used in servers, computers and other computerized devices, including data processors, for performing the functions of the home server 100 and system 100' and the operations detailed herein. For example, the processors may include the x86 processor from AMD and Intel, the x86 processor from Intel

And

a processor, and any combination thereof.

The storage/memory 204 associated with the CPU 202 is any conventional storage medium. The storage/memory 204 also includes machine executable instructions related to the operation of the CPU 202 and the components 204, 206, 208, 210, 212, 214, 216, 218, and 228, as well as the processes and sub-processes illustrated in fig. 1 and 2. Reference is made to fig. 3-5, which are described in detail herein. The memory/storage 204 also stores, for example, rules and policies for the system 100' and the home server 100. Although the CPU 202 and the processor of the memory/storage 204 are shown as a single component for representative purposes, they may be the processor 202 and the storage 204. A plurality of components, and may be external to the home server 100 and/or system 100' and linked to the network 50.

The registration/management module 206 handles the registration of all users (buyers/shoppers), payers and suppliers using or associated with the system 100'. This module 206 also handles the management of the system 100', i.e. normal daily operation.

The request processing/communication/transmission module 208 processes requests from the user (buyer/shopper) 109, suppliers 110a-111 and payers 115a-115n to enter the system, as well as transmissions from the user (buyer/shopper)'s electronic shopping cart and related communications. (109) Suppliers 110a-HOn and payers 115a-115 n.

The cart creation module 210 creates an electronic data object, such as an electronic cart, which is used by the system 100', as detailed herein. Module 210 retrieves all items selected by the shopper/purchaser with their associated computer electrically connected to system 100', returned (not selected for payment) and/or unpaid items in a previous electronic shopping cart to create a new or subsequent electronic shopping cart. The electronic cart is configured to accept and allow removal of items placed in the cart, which have been selected by a user (buyer/shopper) 109 via their mobile computer (e.g., smartphone 108). Items may also be placed in the electronic cart by electronic selection/movement into/out of the cart by the user 109, for example, by Quick Response (QR), Radio Frequency (RF), photography (imaging/image processing), bar code scanning, and Near Field Communication (NFC), for example, by the user 109 touching, sliding, or "clicking" off of the cart on the indicated device display screen (the functions described above are typically on a smartphone 108). The cart creation module also provides the list of payers to the electronic cart, for example, as menu 604 (fig. 6A), one of the payers (including having system 100' select the payer) is selected by the user. As shown in fig. 109, when electronically presented on the display screen of computer 108, for example, with an electronic shopping cart, the display of a menu for selecting payers appearing on the screen display of computer 108 and the listed items also serve to prompt user (buyer/shopper) 109 to select payers. In the event that the user selects "system select" to select a payer, the task is passed to the payer assignment module 212.

Payer assignment module 212 performs two primary functions. It checks the user-selected payers or result payers (other user-designated payers or system-selected payers) in the payer database 221 to see if they are already registered in the system 100'. Additionally, when the user (buyer/shopper) 109 has selected the system 100' to select a payer, for example, clicking in the menu 604 (FIG. 6A) contacts or swipes "system selection", which is a request to the system. To select the payers, module 212 selects the payers by applying rules and policies through system selection rules and policies module 228, as described below. As shown in menu 604, dad, mom, joe, rice card has previously been registered in system 100' as a payer for user (buyer/shopper) 109, who was given e-mail: com and phone numbers 847-. 2B, and is described in detail below.

The shopping cart replication module 214 is for replicating a shopping cart to be sent to a payer and/or a provider as appropriate, the replicated shopping cart is, for example, a shopping cart created by the shopping cart creation module 210. the replicated shopping cart is configured to map to the provider computers 110a-l for (sending) to the computers of the selected payers 115a-115 n. for the provider of the items in the replicated shopping cart, and for the system 100 'of the home server 100, then 110 n. thus, the replicated shopping cart at the selected payer computer 115a-115n is mapped to the provider computer 110 a-for the provider of the items in the replicated shopping cart and sends them to the system 100' of the home server 100, then 110 η. through this mapping, the system 100 'receives an acceptance indication, i.e., the payer has accepted the payment to pay the replicated shopping cart, and a payment indication, that the payer has accepted the payment for the item in the shopping cart by the selected payer, and similarly, the replicated shopping cart at the system 100 a, the selected payer computer 110 a-115 a can be mapped to the selected payer computer 100 a-115 a-1-n-c, and thus mapped to the selected payer computer 100 a-115n, and the system 100' of the home server 100, and the replication system 100, 1110 is configured to send the selected payer computer 100 a, if necessary.

Shopping cart payment confirmation module 216 typically receives data, such as an acceptance indication (or indications of acceptance, which terms are used interchangeably herein), from payer computers 115a-115n via a mapping of shopping carts (e.g., replicated shopping carts to system 100'). And also obtain payment instructions from the provider computers 110a-110n through the mapping. The received data also includes data indicating whether the items in the shopping cart are paid or unpaid by the payer, such as within a predetermined time period. The predetermined period of time may be a preset time until a "timeout" occurs and no payment is made. This results in the unpaid items in the cart being returned to the system for placement in a new cart, or simply stored (e.g., in the stored cart database 224) and/or terminated. Data associated with the cart storage and the cart itself is stored, for example, in the event database 225. Payment for the items in the cart has been made when payment instructions are received in module 216 of system 100', for example, as an indication and/or confirmation that payment for the items in the cart has been issued by the supplier to the buyer, and/or that the buyer can use the paid items (buyer). The acceptance metrics, payment metrics, and other data received by the shopping cart payment module 216 are typically passed to an event database 225 (described in detail below) for storage and analysis.

The databases 218 include databases for users (buyers/shoppers) 220 (registered in the system 100'), payers 221 (registered in the system 100'), suppliers 222 (registered in the system 100'), shopping carts with their merchandise, payers' databases, payments 223, stored shopping carts 224, and events 225. The events stored in the event database 225 include, for example, a shopping cart provided to the payer and the items initially displayed in the shopping cart, the actual payer and the actual items in the shopping cart. The shopping cart that they use to pay is a payment manual or rules and policies, and items that the payer does not accept (select) and items that are accepted that are not ultimately paid for (e.g., timeout) are returned to the system 100'). The database 225 is used in conjunction with a system selection rules and policy module 228. Other databases may also be used depending on the system 100'.

Referring to FIG. 2B, a portion of payer database 221 is shown, for exampleE.g., and by phone number 847-: com. the registered payer @ abc associated with the user (buyer/shopper) (e.g., user (buyer/shopper) 109) identified by the user. If the payer does not manually select an item in the shopping cart within a predetermined time (e.g., set by an administrator of system 100'), then a listing of the payer and their Identifier (ID) and the rules for each payer is being paid. For example, payer "Dad" is given by telephone number 913-: com and Dad @ xyzHandle: @ dad denotes. Dad has 3 rules as payers for user 109. The rules are that he will pay for items in a shopping cart, with a maximum payment amount of $ 60 per item and $ 200 for that cart. The final rule is that as the payer of user 109, he only needs to pay for three shopping carts per month.

When the user 109 selects the menu option "system select," as shown in FIG. 2, the system selection rules and policies module 228 selects the payer in response to receiving the payer's selection. The menu shown in fig. 6A (on menu 604). The module 228 selects, for example, the best payer by applying rules and policies based on the received shopping cart and its items, for example, based on data from the event database 225. Referring to fig. 3-5, flow charts detailing computer-implemented processes according to embodiments of the disclosed subject matter are shown. Reference is also made to the figures. 1. 2A and 2B.

The processes and sub-processes of fig. 3-5 may be divided into two steps. Is a computerized process performed by the system 100', and in some cases, the application 102a is deployed on the user computer 108, while the vendors 2, 3, and 4 are deployed on the user computer 108. The foregoing processes and sub-processes may be performed, for example, manually, automatically, or a combination thereof and, for example, in real-time. Reference is also made to the diagrams and screenshots of fig. 6A-6H. Information for the user's 109 computer (mobile computer, e.g., smartphone 108), providers 110a-HOn, and payers 115a-115n appearing on screen 109 when describing the process of FIG. 3. Details are as follows. Referring also to the diagrams and screen shots of FIGS. 7A-7K, when describing the process of FIG. 4, shown in FIG. 11b, appears on the screen displays of the user's 109 computer (mobile computer, e.g., smartphone 108), suppliers 110a-110n, and payers 115a-15n, as detailed below. Referring to FIGS. 3-5, before beginning blocks 300, 400, 500 of the detailed process, step 300 is first performed, and Application (APP)102a may be installed on user computer 108, vendor computers 110b-11n, and payers 115a-115 n.

Referring to FIG. 3, after START 300, the process moves to block 302, where an electronic data object, i.e., an electronic cart, is created by the website for holding the goods (e.g., products and services) selected by the user (buyer/shopper). An application (e.g., APP 102 a). A payer of the shopping cart is selected and the shopping cart is then provided to the selected payer for payment. Once payment is confirmed or otherwise verified (e.g., by receiving payment instructions or payment instructions), the terms may be used interchangeably herein, e.g., from the computer of each supplier associated with the now-paid goods, the paid goods are released to the user (buyer/shopper).

Processing proceeds to block 304 where the system 100' receives data for the shopping cart or a representation thereof, e.g., graphically presents the shopping cart to the user computer 108 as a screen display 602 (e.g., a web page). Payers with a list of payer selections, such as a payer options menu 604 as shown in fig. 6. 6A. The display 602 of fig. 6 includes: FIG. 6A is a shopping cart created by a website and presented on the website of a vendor (e.g., vendor 1110a), for example, as part of a "shopping cart" web page. Payers listed by name as on menu 604 are payers registered in system 100', for example in payer database 221. In this screen display 602, the shopping cart includes four items to be purchased (1 pan, 2 hats and 1 shoe). Menu 604 prompts user 109 to enter the payer for the shopping cart and upon selection of the payer, "dad" associated with telephone number 913-. As shown in fig. 6, a "send" button 608 is sent. Thus, as shown in fig. 6B, a selection has been made for system 100' to make dad the payer.

Processing proceeds to block 306 where a determination is made as to whether the system 100 'received the payer's selection within a predetermined time at block 306. If not, the process passes to block 322, where the shopping cart is stored, for example, in database 224 or terminated, and then the process passes to block 324, where it ends. If so, at block 306, the process passes to block 308, where the shopping cart is copied and sent (sent) to the designated payer, e.g., Dad (represented by payer 1's computer 115 a) via network 50. The shopping cart displayed to dad is represented by screen display 610 of the screen diagram of fig. 6C.

Processing moves to block 310 where the payer may accept the items in the shopping cart for payment or make a payment for a particular payer in the payer database 221 according to rules and policies in the system 100'. In fig. 6D, payer dad has accepted payment for all items, as indicated by an "X" in acceptance box 612 of screen display 610. Once dad activates the "send" button 614, the process passes to block 312 (where acceptance indicates that a transmission from dad's payer computer 115a to system 100' and/or the provider. dad should not manually accept all items, as shown in fig. 2. in fig. 6E, or according to rules and policies, for accepted items, i.e., "griddle," 616, the process passes to block 312 and for items that do not accept, i.e., hat 618 and shoe 619, the process moves to block 316.

At block 312, for the accepted item, it is determined whether payment was made before a time out (a predetermined time at which the system 100' no longer accepts payment). If so, the process passes to block 314, where if only certain items in the initial shopping cart (the cart initially presented to the payer) are accepted and paid, or if all of the items in the initial items are copied, the shopping cart accepted and paid for by the creation or copying of the cart, and the paid cart is then sent to the supplier 110a and/or buyer 109, represented by their computer 108. The module 216 confirms that (received) (e.g., payment instructions for payment instructions obtained from the supplier's computer) were released and allows the purchaser 109 to electronically access the information, electronically transmit it, or deliver it to an actual location associated with the purchaser 109, or for pickup. Represented by the purchaser 109 or its designation. The process moves to block 324 where it ends because the paid shopping cart is no longer circulating in the system 100' but may be stored in one or more of the databases 223, 224, 225, for example. If no in block 312. Accepted items have not been paid for before the timeout and are returned to the system 100' at block 316.

Items that are not accepted and/or returned (for non-payment) are returned to the system 100' at block 316 to the shopping cart creation module 210 at block 316.

From block 316, the process moves to block 318, where the system 100' has the unapproved and/or returned (for non-payment) items, e.g., presenting the items to the buyer in the form of a new shopping cart, and prompting the buyer to select a payer from a menu, in block 318. For example, assuming a payment for "pan" is accepted at block 310, a payment is timely made at block 312 and released to the purchaser at block 314, and the new shopping cart is shown in screen display 622 of FIG. 6. As shown in fig. 6F, including a hat 618 and a shoe 619, and a payer selection box 624, as presented to the buyer. Payer selection box 624 has changed to no longer contain dad because dad has operated on certain items in the shopping cart.

For example, the processes of blocks 310, 312, and 316 may be simultaneous in time. Thus, for example, depending on the time of the block, at block 316, the items returned from blocks 310 and 312 to system 100' may be combined and presented as a single new cart at block 318, or as a single block. The article arrives at system 100 'after being returned to system 100'. The process then moves from block 318 to block 320 and proceeds as described below for each cart.

From block 318, processing moves to block 320, where it is determined whether the system 100' received a payer selection from the user (shopper/buyer) 109 within a predetermined time, at block 320. If so, the user (shopper/purchaser) 109 has entered the selected payer, e.g., "mom," associated with telephone number 913-. As shown in fig. 6G, and activates the "send" button 630 to send the shopping cart (as shown in screen display 628) back to the system 100'. Processing proceeds to block 308 where module 214 copies the shopping cart (of screen display 628) and sends it to the mom's computer, e.g., payer 2115 b, in block 308. The copied shopping cart is shown as screen display 634 of FIG. 6, as displayed to mother on her computer 115 b. 6 hours the process resumes (repeats) from block 308 as described above.

Returning to block 320, if the payer selection is not received within the predetermined time period, the process proceeds to block 322, where the cart is stored, for example, in the database 224 or terminated. The process then moves to block 324, where it ends.

Turning to FIG. 4, after start 400, the process moves to block 402, where an electronic data object, i.e., an electronic cart, is created via a website and/or application for holding items (e.g., products and services) selected by a user (buyer/shopper). (e.g., APP 102a) to select a payer for a shopping cart. The shopping cart will be displayed and the shopping cart will be displayed to the selected payer for payment. Upon confirming payment or otherwise verifying payment, for example, by receiving payment instructions from, for example, the computer of each supplier associated with the now-paid goods, the paid goods are issued to the user (buyer/shopper).

The process proceeds to block 404, where the system 100' receives the carts, or data representative thereof, and merges the carts into a single cart at block 404. The single shopping cart is presented to user computer 108 graphically as screen display 702, and is now associated with a payer selection list, e.g., payer option (menu) menu 704, as shown in FIG. 7A. Payers, as listed by name in menu 704, are payers registered in system 100', for example, in payers database 221. In this screen display 702, the shopping cart includes six items to be purchased (3 chili sauce, 1 storage container, 1 shoe and 1 gift card). Menu 704 prompts user 109 to enter the payer for the shopping cart, and upon selection of the payer, "dad" associated with telephone number 913-. As shown in fig. 7B, button 708.

Processing proceeds to block 406 where a determination is made as to whether the system 100 'received the payer's selection within a predetermined time, block 406. If not, processing proceeds to block 422, where the shopping cart is stored, for example, in database 224 or terminated, and processing proceeds to block 324, where it ends. If so, at block 406, the process passes to block 408, where the shopping cart is copied and sent (sent) to the designated payer, e.g., Dad (represented by payer 1's computer 115 a) via network 50. The shopping cart displayed to dad is represented by screen display 710 of the screen diagram of fig. 7C.

Processing proceeds to block 410 where the payer may accept the item for payment in the shopping cart or make a payment for a particular payer in the payer database 221, according to rules and policies in the system 100'. Refer to the figure. In FIG. 7D, payer Dad is contacted, but manual payment is not accepted (by entering an acceptance as input into his computer 108, the computer 108 is sent to the system 100' and/or the vendor). Since the rules and policies are for the father, in payer database 221 (FIGS. 2A and 2B), the rules and policies have been applied to the shopping cart, and therefore, the father has accepted payment for all items, as indicated by an "X" in acceptance box 712 of screen display 710, rather than in the shoes. In the case of activating rules and policies, the "send" button 714 is activated and processing proceeds to block 412. Since the father does not receive all the items, as shown in fig. 3, i.e. shoes. Referring to fig. 7D, according to rules and policies, processing proceeds to block 412 to obtain accepted items, i.e., chili sauce, storage containers and gift cards (where an acceptance indication is transmitted from the system 100' to the vendor), and to block 416 for unacceptable items, i.e., shoes.

At block 412, for the accepted item, it is determined whether payment was made before a timeout (a predetermined time at which the system 100' no longer accepts payment). If so, the process passes to block 414. At block 414, a separate shopping cart is created for each supplier, each shopping cart including an indication of the amount paid from the supplier. For example from the shopping cart of figure 2. In FIG. 7D, a shopping cart was created for vendor 2 that included the sauce and storage container, and another shopping cart was created for vendor 4 that included the gift card. The carts now paid for by a cart from supplier 2 are sent to a single supplier (e.g., supplier 2110 b and supplier 4110 d) and/or buyer, respectively. The now-paid items, as confirmed by block 216 (payment instructions for each payment item have been received from the requisite supplier (e.g., supplier computer), are released and the buyer (e.g., obtained from the paid supplier) is enabled to make the items available). The process moves to block 424 where it ends because the paid shopping cart is no longer circulating in system 100' but may be stored in one or more of databases 223, 224, 225, for example.

Returning to block 410, at block 416, unacceptable items, such as shoes, are returned to the system 100' (from the screen display 710 of FIG. 7D) to the shopping cart creation module 210. Similarly, if accepted items have not been paid for before a timeout at block 412, then these items are also returned to the system 100', at block 416.

From block 416, the process moves to block 418. At block 418, the system 100' with the unapproved and/or returned (for non-payment) items presents the items to the buyer, for example, in a new shopping cart, and prompts the buyer to select a payer from a menu. For example, assume that payment for the sauce, storage container and gift card is accepted at block 410, and timely payment is made at block 412, and a new shopping cart is issued to the purchaser at block 414, as shown in the on-screen display. Fig. 722. As shown in fig. 7E, the shoe includes a shoe and payer selection box 724, as presented to the purchaser. Payer selection box 624 has changed to no longer contain dad because dad has operated on certain items in the shopping cart.

For example, the processes of blocks 410, 412, and 416 may be simultaneous in time. Thus, for example, depending on the time of the block, the items returned from blocks 410 and 412 to system 100' may be combined and presented as a single new cart at block 418, or shown as separate carts at block 418, at block 416. The article arrives at system 100 'after being returned to system 100'. The process then moves from block 418 to block 420 and proceeds as described below for each cart.

From block 418, the process moves to block 420, where it is determined whether the system 100' received a payer selection from the user (shopper/buyer) 109 within a predetermined time in block 420. If so, the user (shopper/buyer) 109 has entered the selected payer, such as "Others" associated with "Tom" in telephone numbers 617 and 925 and 1212, into payer box 726 of screen display 728 of FIG. 7. As shown in fig. 7F, and activates the "send" button 730 to send the shopping cart (as shown in the screen display 628) back to the system 100'. The system 100' sends an electronic communication, such as text, email, social network communication, phone, via the module 208, to contact Tom so that he can register in the system 100 via the registration module 206, so that his Tom at 617 and 925 and 1212 are payers in the payer database 221. For example, here, in connection with tom, he registers in the system 100' and becomes a payer in the database 221 (juxtaposed in the payer, therefore, the database 221 associated with the user 109).

From block 420, the process moves to block 408, where in block 408, the shopping cart (of screen display 728) is copied by module 214 and sent to a computer such as Tom's Tom. Payer n 115 n. The copied shopping cart is shown as screen display 734 of FIG. 7G. Tom's computer 115 n.

Returning to block 420, if the payer selection is not received within the predetermined time period, the process proceeds to block 422, where the cart is stored, for example, in the database 224 or terminated. The process then moves to block 424 where it ends.

Returning to block 408 and screen display 734 of fig. 7. In fig. 7G, tom does not receive payment for shoes as per block 410. Instead, tom leaves the accept box blank and activates the send button 736, moving the process to block 416, where the shoe is returned to the system 100'. The process then proceeds to block 418 where the new shopping cart is presented to the purchaser to select (enter) the payer at block 418. This is illustrated, for example, by the cart of screen display 740 of fig. 7. Referring to FIG. 7H, the shopping cart including menu box 742 is shown to the user 109. The process proceeds to block 420 where the payer is selected, e.g., has been selected as "system select" in block 744, and sent to the system 100 'for operation on the system 100' by activating the "send" button 746 of the screen display 740 of fig. 7I, in block 420.

Processing proceeds to block 408 where the shopping cart is copied and sent to the payer Mika selected by the system in block 408. The cart appears as screen display 750 of fig. 7. 7J. Mika is the system selection payer selected by the system selection module 228, applying rules and policies. For example, a rule or policy may be "who is the last payer to pay for items similar to those in the shopping cart," such as shoes. The event database 225 is checked and the last payer of the shoe is a rice card for the buyer 109. Thus, based on the application of the rules and policies module 228, the system 100' selects Mika as the payer for the shopping cart.

Processing proceeds to 410 where Mika accepts payment for the shoe ("X" in accept block 752), and activates the "send" button 754 of screen display 750 of fig. 7. 7K. Here, Mika has paid in time when the process moves to block 412. Thus, the process moves from block 412 to block 414, as detailed above (where the user 109 (via his mobile computer 108, can access his shoes as paid for by Mika)) accesses the shoes, and then to block 424, where the process ends.

Turning now to the figures. Referring to FIG. 5, after START 500, the process moves to block 502, where an electronic data object (i.e., an electronic shopping cart) (e.g., APP 102a) for holding items (e.g., products and services) selected by a user (buyer/shopper) is created by a website or application. A payer is selected for each shopping cart, the shopping carts are presented to the selected payer for payment, and once payment is confirmed or otherwise verified, the paid money is released and made available to the user (buyer/shopper).

The process moves to block 504a where the system 100' receives data for each shopping cart, or a representative thereof, each shopping cart corresponding to a supplier or group of suppliers of the items. Each shopping cart will now be handled individually. Thus, the system can process multiple carts simultaneously (including simultaneously).

Moving from block 504a to block 504b, each shopping cart is associated with a payer selection, as described above, for example, graphically on a display screen with a menu of payer selections. Each shopping cart having a payer selection menu is presented, for example, graphically (via a display) to user computer 108, and the user is prompted to select a payer from the menu. Payers, as listed by name, are registered payers in the system 100', for example in the payer database 221.

Processing proceeds to block 506 where a determination is made at block 506 whether the system 100 'received the payer's selection within a predetermined time. If not, processing proceeds to block 522, where the shopping cart is either stored, for example, in database 224, or terminated, and processing proceeds to block 524, where it ends. If so, at block 506, the process moves to block 508, where the shopping cart is copied and sent (sent) to the designated payor via the network 50.

From block 508, the process proceeds to block 510, where the payer may accept the items in the shopping cart for payment, or make payment according to rules and policies in the system 100' of the particular payer in the payer database. 221. For the payer's acceptance item, the process moves to block 512. For the non-accepted items of the payer, the process moves to block 516.

At block 512, for items that are accepted (e.g., one or more acceptance indications have been sent from the payer computer to the system 100', such as block 216), it is determined whether payment has been made before a timeout when the system 100' is no longer accepting payment for a predetermined time. If so, the process passes to block 514, where a shopping cart is created if only a portion of the items in the initial shopping cart (the shopping cart initially presented to the payer) are accepted and paid for, or if all of the items in the initial items are copied. The created and repeated shopping cart is accepted and paid for, and the paid shopping cart is then sent to the supplier and/or buyer. The now paid merchandise, as confirmed by block 216 (payment instructions having received payment instructions from the supplier's computer), is released and made available to the purchaser from the supplier of the paid merchandise. The process moves to block 524 and ends at block 524 because the paid-for carts are no longer circulated in the system 100' but may be stored in one or more of the databases 223, 224, 225, for example.

Returning to block 510, at block 516, the unacceptable items are returned to the system 100' and then to the shopping cart creation module 210. Similarly, at block 512, if accepted items have not been paid before the timeout, these items will also return to at block 516, and the system 100' moves processing to block 518. At block 518, the system 100' has items that are not accepted and/or returned (for non-payment), e.g., the items are presented in a new shopping cart. Paying the buyer and prompting the buyer to select a payer from the menu.

From block 518, the process moves to block 520, where it is determined whether the system 100' received a payer selection from the user (shopper/buyer) 109 within a predetermined time in block 520. If so, the user (shopper/purchaser) 109 has entered the selected payer into the shopping cart (e.g., a payer selection menu associated with the shopping cart), and the process returns to block 508, from which it recovers, as described above.

Returning to block 520, if the payer selection is not received within the predetermined time period, the process proceeds to block 522, where the cart is stored, for example, in the database 224 or terminated, in block 522. The process then moves to block 524 where it ends.

Implementation of the method and/or system of embodiments of the present invention may include performing or completing selected tasks manually, automatically, or a combination thereof. Furthermore, according to actual instrumentation and equipment of embodiments of the method and/or system of the present invention, several selected tasks could be implemented by hardware, software, firmware or a combination thereof using an operating system. For example, hardware for performing selected tasks according to embodiments of the invention could be implemented as a chip or a circuit. As software, selected tasks according to embodiments of the invention could be implemented as a plurality of software instructions being executed by a computer using any suitable operating system. In an exemplary embodiment of the invention, one or more tasks according to exemplary embodiments of the methods and/or systems described herein are performed by a data processor, such as a computing platform for executing a plurality of instructions.

Optionally, the data processor includes volatile memory and/or non-volatile memory for storing instructions and/or data, e.g., a non-volatile storage medium, such as a magnetic hard disk and/or removable medium, for storing instructions and/or data. And/or data. Optionally, a network connection is also provided. A display and/or a user input device, such as a keyboard or mouse, are also optionally provided.

For example, any combination of one or more non-transitory computer-readable (storage) media may be utilized in accordance with the above-listed embodiments of the present invention. The non-transitory computer-readable (storage) medium may be a computer-readable signal medium or a computer-readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a memory only (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any other suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

As will be understood from the reference paragraphs provided above and with reference to the accompanying drawings, various embodiments of computer-implemented methods are provided herein, some of which may be performed by various embodiments of the apparatus and systems described herein, and some of which may be performed. According to instructions stored in a non-transitory computer readable storage medium as described herein. Additionally, it will be apparent to those skilled in the art that some embodiments of the computer-implemented methods provided herein may be performed by other devices or systems and according to instructions stored in computer-readable storage media different from those described herein. Reference is made to the embodiments described herein. Any reference to systems and computer-readable storage media for the following computer-implemented methods is provided for illustrative purposes and is not intended to limit any such systems and any such non-transitory computer-readable storage media in terms of: the above-described embodiments of a computer-implemented method. Also, any reference to the following computer-implemented methods is provided for illustrative purposes with respect to systems and computer-readable storage media and is not intended to limit any such computer-implemented methods disclosed herein.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The description of various embodiments of the present invention has been presented for purposes of illustration but is not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles of the embodiments, the practical application or technical improvements to the technology found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

It is appreciated that certain features of the invention, which are, for clarity, described in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features of the invention which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable subcombination or as suitable in any other described embodiment of the invention. Certain features described in the context of various embodiments should not be considered essential features of those embodiments unless the embodiment is inoperable without those elements.

The above-described processes including portions thereof may be performed by software, hardware, and combinations thereof. These processes and portions thereof may be performed by computers, computer type devices, workstations, processors, microprocessors, other electronic search tools and memory, and other non-transitory storage type devices associated therewith. The process and portions thereof may also be embodied in a programmable non-transitory storage medium such as a Compact Disc (CD) or other magnetic disk, including magnetic, optical, etc., readable by a machine or the like, or other computer usable storage medium including magnetic, optical, or semiconductor storage, or other source of electronic signals.

The processes (methods) and systems herein, including components thereof, have been described with exemplary reference to specific hardware and software. These processes (methods) have been described as exemplary, whereby one of ordinary skill in the art may omit and/or alter certain steps and their order to reduce these embodiments without undue experimentation. The processes (methods) and systems have been described in a manner sufficient to enable those of ordinary skill in the art to readily adapt other hardware and software that may be required to reduce any embodiment without undue experimentation and implementation using routine techniques.

While the present invention has been described in conjunction with specific embodiments thereof, it is evident that many alternatives, modifications, and variations will be apparent to those skilled in the art. Accordingly, it is intended to embrace all such alternatives, modifications and variations that fall within the spirit and broad scope of the appended claims.