US20110047022A1 - Method and apparatus for providing cross-benefits based on a customer activity - Google Patents

Method and apparatus for providing cross-benefits based on a customer activity Download PDF

Info

Publication number
US20110047022A1
US20110047022A1 US12/938,046 US93804610A US2011047022A1 US 20110047022 A1 US20110047022 A1 US 20110047022A1 US 93804610 A US93804610 A US 93804610A US 2011047022 A1 US2011047022 A1 US 2011047022A1
Authority
US
United States
Prior art keywords
customer
vendor
offer
obligation
service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US12/938,046
Other versions
US8700456B2 (en
Inventor
Jay S. Walker
Daniel E. Tedesco
Stephen C. Tulley
John M. Packes, Jr.
Deirdre O'Shea
Keith Bemer
James A. Jorasch
Dean P. Alderucci
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
PayPal Inc
Original Assignee
Walker Digital LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US09/219,267 external-priority patent/US7831470B1/en
Priority claimed from US09/274,281 external-priority patent/US7818284B1/en
Priority to US12/938,046 priority Critical patent/US8700456B2/en
Application filed by Walker Digital LLC filed Critical Walker Digital LLC
Publication of US20110047022A1 publication Critical patent/US20110047022A1/en
Assigned to INVENTOR HOLDINGS, LLC reassignment INVENTOR HOLDINGS, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: WALKER DIGITAL, LLC
Priority to US14/251,746 priority patent/US9697553B2/en
Publication of US8700456B2 publication Critical patent/US8700456B2/en
Application granted granted Critical
Assigned to WALKER DIGITAL CORPORATION reassignment WALKER DIGITAL CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ALDERUCCI, DEAN, BEMER, KEITH, JORASCH, JAMES A., O'SHEA, DEIRDRE, PACKES, JOHN M., JR., TEDESCO, DANIEL E., TULLEY, STEPHEN C., WALKER, JAY S.
Assigned to WALKER DIGITAL, LLC reassignment WALKER DIGITAL, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: WALKER DIGITAL CORPORATION
Assigned to PAYPAL, INC. reassignment PAYPAL, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: INVENTOR HOLDINGS, LLC
Adjusted expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]
    • G06Q30/0611Request for offers or quotes
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/101Collaborative creation, e.g. joint development of products or services
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207Discounts or incentives, e.g. coupons or rebates
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207Discounts or incentives, e.g. coupons or rebates
    • G06Q30/0208Trade or exchange of goods or services in exchange for incentives or rewards
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207Discounts or incentives, e.g. coupons or rebates
    • G06Q30/0226Incentive systems for frequent usage, e.g. frequent flyer miles programs or point systems
    • G06Q30/0233Method of redeeming a frequent usage reward
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207Discounts or incentives, e.g. coupons or rebates
    • G06Q30/0234Rebates after completed purchase
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207Discounts or incentives, e.g. coupons or rebates
    • G06Q30/0235Discounts or incentives, e.g. coupons or rebates constrained by time limit or expiration date
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207Discounts or incentives, e.g. coupons or rebates
    • G06Q30/0236Incentive or reward received by requiring registration or ID from user
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207Discounts or incentives, e.g. coupons or rebates
    • G06Q30/0238Discounts or incentives, e.g. coupons or rebates at point-of-sale [POS]

Definitions

  • U.S. patent application Ser. No. 09/282,747 is a continuation-in-part of U.S. patent application Ser. No. 09/219,267 entitled “METHOD AND APPARATUS FOR FACILITATING ELECTRONIC COMMERCE THROUGH PROVIDING CROSS-BENEFITS DURING A TRANSACTION”, filed on Dec. 23, 1998; and is a continuation-in-part of U.S. patent application Ser. No. 09/274,281 entitled “METHOD AND APPARATUS FOR PROVIDING CROSS-BENEFITS VIA A CENTRAL AUTHORITY”, filed Mar. 22, 1999 and issued as U.S. Pat. No. 7,818,284 on Oct.
  • the present invention relates to methods and apparatus for facilitating commerce.
  • a vendor may also offer promotions to provide an incentive for customers to make purchases. For example, a vendor may offer a “buy one get one free” promotion whereby a purchase of an item yields the benefit of an additional item at no cost. Similarly, a vendor may provide a discount on a purchase in exchange for signing up for a credit card account provided by the vendor.
  • Promotions may also be provided among two or more vendors. For example, a first vendor may advertise that if a particular product is purchased, another product may be purchased from or given away by a second vendor.
  • a benefit e.g. a credit for the price of the items
  • a controller receives information relating to customer activity with a first vendor, typically via a Web page that a customer accesses.
  • the controller further receives an indication of items (goods and/or services) the customer desires to purchase, the items having an associated total price.
  • the controller determines, based on any of various criteria, whether to provide an offer for a subsidy based on the information relating to customer activity. For example, a customer who places certain items in his virtual “shopping cart” may receive such an offer.
  • the offer for a subsidy is from a second vendor (a subsidizing vendor), and may define, for example, a reduction in the price charged for the item and an obligation for the customer to fulfill in exchange for the subsidy.
  • the customer may be obliged to sign up for a credit card or telephone service provided by the subsidizing vendor.
  • An indication of the offer for the subsidy is provided to the customer, e.g., via a text or graphical display on the Web page.
  • the customer responds via known user interface techniques and, if he accepts the offer, he is charged a second price for the items.
  • the second price is less than the total price, and may even be zero. Thus the customer may get his desired items for free in exchange for fulfilling the obligation with the subsidizing vendor.
  • FIG. 1A is a schematic illustration of an embodiment of an apparatus for facilitating commerce in accordance with the present invention.
  • FIG. 1B is a schematic illustration of another embodiment of an apparatus for facilitating commerce in accordance with the present invention.
  • FIG. 2 is a schematic illustration of a controller of the apparatus of FIG. 1 .
  • FIG. 3 is a schematic illustration of a vendor server of the apparatus of FIG. 1 .
  • FIG. 4 is a representation of a customer database of the controller of FIG. 2 .
  • FIG. 5 is a representation of a vendor database of the controller of FIG. 2 .
  • FIG. 6 is a representation of a transaction database of the controller of FIG. 2 .
  • FIG. 7 is a representation of a subsidizer database of the controller of FIG. 2 .
  • FIG. 8 is a representation of an offer rules database of the controller of FIG. 2 .
  • FIG. 9 is a representation of an offers database of the controller of FIG. 2 .
  • FIG. 10 is a representation of a record of an offer summary database of the controller of FIG. 2 .
  • FIG. 11 is a representation of a record of another embodiment of the offer summary database.
  • FIG. 12 is a schematic illustration of an item database of the vendor server of FIG. 3 .
  • FIG. 13 is a flow chart illustrating an embodiment of a method for providing an offer for a benefit.
  • FIG. 14 is a flow chart illustrating an embodiment of a method for providing an offer for a benefit using offer rules.
  • FIGS. 15A and 15B are a flow chart illustrating an embodiment of a method for providing an offer which may be accepted by fulfilling an obligation associated with the offer.
  • FIG. 16 is a flow chart illustrating an embodiment of a method for determining whether customers have fulfilled their obligations associated with an offer for a benefit.
  • FIG. 17 is a flow chart illustrating an embodiment of a method for providing an offer for a benefit after a customer has made a purchase from a vendor.
  • a customer that purchases items from a first vendor may be paid, directly or indirectly, by a second vendor, so that the customer pays a reduced price, perhaps nothing at all, for his desired items.
  • the customer participates or agrees to participate in a transaction with the second vendor.
  • the customer may be required to sign up for a service that is provided by the second vendor. Since many service providers are willing to pay significant amounts of money (e.g. often $50 to $200) to acquire a new customer, the ability to acquire a customer by essentially “intervening” in a sale between others can benefit all parties involved.
  • the second vendor provides a subsidy to the customer. The customer is benefited by the reduced price of his items, the first vendor is benefited by the increased sales and customer satisfaction that such an arrangement would bring, and the second vendor is benefited by the additional transaction, particularly the acquisition of a new customer in one embodiment.
  • ⁇ activities may be used to indicate, among other things, whether the customer is likely to accept an offer for a benefit from a subsidizing vendor. For example, when a customer begins to interact with a first vendor (e.g. via the first vendor's Web site), various types of customer activity may be used to indicate whether the customer is willing to transact with the first vendor. Similarly, various types of customer activity may be used to indicate whether the customer is willing to transact with a subsidizing vendor. Detection of such customer activity can assist is identifying, e.g., which customers should be given offers for subsidies, and when.
  • an apparatus 100 includes a controller 110 that is in communication with a vendor server 120 .
  • the controller 110 and the vendor server 120 may comprise computers, such as those based on an Intel® Pentium® microprocessor, that are adapted to communicate via the Internet (e.g. via a modem) or other medium. Any number of vendor servers may be in communication with the controller 110 .
  • devices in communication with each other need not be continually transmitting to each other. On the contrary, such devices need only transmit to each other as necessary, and may actually refrain from exchanging data most of the time. For example, a device in communication with another device via the Internet may not transmit data to the other device for weeks at a time.
  • the vendor server 120 may be a “Web server” of a vendor (e.g. a retail seller).
  • a vendor server could then generate Web pages (documents on the World Wide Web that typically include an HTML file and associated graphics and script files) that may be accessed via the World Wide Web and allow purchases from the vendor to be made in a manner known in the art.
  • a Web site consists of several such Web pages and associated databases served up by an HTTP server (e.g. the vendor server 120 ) on the World Wide Web.
  • the vendor server 120 may be a computer involved in operating a physical store. Such a computer, for example a point of sale (POS) server, would perform such tasks as inventory management and transaction processing for the store.
  • POS point of sale
  • the controller 110 is also in communication with a subsidizing vendor server 140 .
  • the subsidizing vendor server 140 may comprise a computer, such as those based on an Intel® Pentium® microprocessor, that is adapted to communicate via the Internet (e.g. via a modem) or other medium. Any number of subsidizing vendor servers may be in communication with the controller 110 .
  • the subsidizing vendor server 140 may be a “Web server” of a vendor.
  • the subsidizing vendor server 140 could then generate a Web page that may be accessed via the World Wide Web and allow transactions with the subsidizing vendor in a manner known in the art.
  • the subsidizing vendor server 140 may be a computer involved in operating a physical store. Such a computer would perform such tasks as inventory management and transaction processing.
  • the vendor server 120 may be in communication with a customer terminal 130 that transmits data regarding a customer transaction (e.g. a purchase). Any number of customer terminals may be in communication with the vendor server 120 .
  • the customer terminal 130 may be a point of sale (POS) terminal, such as the NCR 7 454 manufactured by NCR Corporation or the IBM 4683 manufactured by International Business Machines.
  • POS terminals perform such processes as calculating the total price of a purchase (goods or services) and calculating the amount of change due to a customer.
  • POS terminals may furthermore track purchases made and adjust databases of inventory accordingly.
  • the customer terminal 130 may be a computer, such as those based on an Intel® Pentium® microprocessor, that are adapted to communicate via the Internet (e.g. via a modem) or other medium. Such computers are able to appropriately access a Web page to communicate with a vendor server in a manner that is known to those skilled in the art.
  • a computer such as those based on an Intel® Pentium® microprocessor, that are adapted to communicate via the Internet (e.g. via a modem) or other medium.
  • Such computers are able to appropriately access a Web page to communicate with a vendor server in a manner that is known to those skilled in the art.
  • the customer terminal 130 may be a telephone, an automated teller machine (ATM), slot machine, a vending machine or other device that receives payment from customers in exchange for providing goods or services.
  • the vendor server in such an embodiment could include an IVRU (Interactive Voice Response Unit), such as the Vision 2001 or the Insight IVR/Web, both from Interactive Voice Technologies, Corp., or the OmniVox for Windows NT from APEX Voice Communications.
  • An IVRU allows a user of a DTMF (Dual Tone Multi-Frequency) signal generating telephone to communicate with a computer.
  • the DTMF signals received from the user's telephone are interpreted by the vendor server, and the vendor server may also communicate with the user by generating and transmitting voice or other audio signals, such as a list of IVRU menu options.
  • controller 110 is especially advantageous in an embodiment where a plurality of subsidizing vendors and/or a plurality of vendor servers serving customers participate in the described invention.
  • an apparatus 150 represents another embodiment of an apparatus for facilitating commerce in accordance with the present invention.
  • a vendor server 160 communicates with a customer terminal 170 and with a subsidizing vendor server 180 without the intervening controller 110 . Accordingly, the embodiment illustrated by FIG. 1B is appropriate for a direct relationship between the vendor servicing customers and the subsidizing vendor.
  • reference numeral 200 indicates a device that may be the controller 110 ( FIG. 1A ).
  • the functionality of the device 200 may be performed by another device, such as the vendor server 160 ( FIG. 1B ), which operates to provide a customer with an offer for a subsidy from a second vendor.
  • the device 200 comprises a processor 202 , such as an Intel® Pentium® microprocessor.
  • the processor 202 is in communication with a data storage device 210 , such as an appropriate combination of magnetic, optical and/or semiconductor memory.
  • the data storage device 210 may comprise one or more of a ROM, RAM and hard disk.
  • the processor 202 and the data storage device 210 may each be (i) located entirely within a single computer or other computing device; (ii) connected to each other by a remote communication medium, such as a serial port cable, telephone line or radio frequency transceiver; or (iii) a combination thereof.
  • the controller 110 may comprise one or more computers that are connected to a remote server computer for maintaining databases.
  • the data storage device 210 stores a program 220 for controlling the processor 202 .
  • the processor 202 performs instructions of the program 220 , and thereby operates in accordance with the present invention, and particularly in accordance with the methods described in detail herein.
  • the program 220 furthermore includes program elements that may be necessary, such as an operating system and “device drivers” for allowing the processor 202 to interface with computer peripheral devices. Appropriate device drivers and other necessary program elements are known to those skilled in the art, and need not be described in detail herein.
  • the storage device 210 also stores (i) a customer database 230 , (ii) a vendor database 240 , (iii) a transaction database 250 , (iv) a subsidizer database 260 , (v) an offer rules database 270 , (vi) an offers database 280 and (vii) an offer summary database 290 .
  • the databases 230 , 240 , 250 , 260 , 270 , 280 and 290 are described in detail below and depicted with exemplary entries in the accompanying figures.
  • the schematic illustrations and accompanying descriptions of the databases presented herein are exemplary arrangements for stored representations of information. A number of other arrangements may be employed besides those suggested by the tables shown.
  • the illustrated entries of the databases represent exemplary information, and those skilled in the art will understand that the number and content of the entries can be different from those illustrated herein.
  • FIG. 3 illustrates the vendor server 120 of FIG. 1A .
  • the vendor server may communicate with a subsidizing vendor server 180 without the intervening controller 110 .
  • the description of the vendor server 120 is applicable to the vendor server 160 of FIG. 1B .
  • the databases stored by the data storage device of the vendor server could include the databases depicted in FIGS. 2 and 3 .
  • the vendor server 120 comprises a processor 302 , such as an Intel® Pentium® microprocessor, which is in communication with a customer terminal 315 and the controller 110 .
  • the processor 302 is also in communication with a data storage device 310 , such as an appropriate combination of magnetic, optical and/or semiconductor memory.
  • the data storage device 310 may comprise one or more of a ROM, RAM and hard disk.
  • the processor 302 and the data storage device 310 may each be (i) located entirely within a single computer or other computing device; (ii) connected to each other by a remote communication medium, such as a serial port cable, telephone line or radio frequency transceiver; or (iii) a combination thereof.
  • the vendor server 120 may comprise one or more computers that are connected to a remote server computer for maintaining databases.
  • the data storage device 310 stores a program 320 for controlling the processor 302 .
  • the processor 302 performs instructions of the program 320 , and thereby operates in accordance with the present invention, and particularly in accordance with the methods described in detail herein.
  • the program 320 furthermore includes program elements that may be necessary, such as an operating system and “device drivers” for allowing the processor 302 to interface with computer peripheral devices. Appropriate device drivers and other necessary program elements are known to those skilled in the art, and need not be described in detail herein.
  • the storage device 310 also stores (i) a customer database 330 , (ii) an item database 340 , and (iii) a transaction database 350 .
  • the customer database 330 and the transaction database 350 of the vendor server 120 may be similar or identical to the customer database 230 and transaction database 250 of the controller 110 .
  • the controller 110 may store data that is derived from the vendor server 120 , and vice versa. If each vendor server stores data on its own customers and its own transactions, the controller 110 could aggregate this data from each vendor server.
  • the databases 330 , 340 and 350 are described in detail below and depicted with exemplary entries in the accompanying figures.
  • the schematic illustrations and accompanying descriptions of the databases presented herein are exemplary arrangements for stored representations of information. A number of other arrangements may be employed besides those suggested by the tables shown.
  • the illustrated entries of the databases represent exemplary information, and those skilled in the art will understand that the number and content of the entries can be different from those illustrated herein.
  • a table 400 represents an embodiment of the customer database 230 ( FIG. 2 ) and/or the customer database 330 ( FIG. 3 ).
  • the table 400 includes entries 402 , 404 , 406 and 408 , each defining a customer that may purchase items from a vendor. Such information may be determined, for example, when a customer registers for a frequent shopper card. Those skilled in the art will understand that the table 400 may include any number of entries.
  • the table 400 also defines fields for each of the entries 402 , 404 , 406 and 408 .
  • the fields specify (i) a customer identifier 420 that uniquely identifies the customer, (ii) a name 422 of the customer, (iii) a billing address 424 of the customer, (iv) credit card information 426 which may be used to render payment in purchasing the items, and (v) an electronic mail (“e-mail”) address 428 for communication with the customer.
  • the data specified by fields 422 , 424 , 426 and 428 may be received from the corresponding customer (e.g. via the corresponding customer terminal and/or vendor server that interacts with the customer).
  • the data may be provided when the customer makes a purchase from a vendor's Web site by requiring the customer to enter information into an HTML form provided on a Web page.
  • the controller 110 in the embodiment of FIG. 1A , or the vendor server 160 in the embodiment of FIG. 1B would generate a unique customer identifier to store in the field 420 of the entry corresponding to the new customer. Once such information is stored for a customer, it may be retrieved upon reference to the appropriate customer identifier.
  • a table 500 represents an embodiment of the vendor database 240 ( FIG. 2 ).
  • the table 500 includes entries 502 , 504 , 506 and 508 , each defining a vendor that services customers and may have those customers receive offers for subsidies. Such information may be determined when a vendor registers for participation in the subsidizing program described herein. Those skilled in the art will understand that the table 500 may include any number of entries.
  • the table 500 also defines fields for each of the entries 502 , 504 , 506 and 508 .
  • the fields specify (i) a vendor identifier 520 that uniquely identifies the vendor, (ii) a vendor name 522 , (iii) a vendor e-mail address 524 for communication with the vendor, and (iv) an amount owed 526 to the vendor (e.g. promised but unpaid subsidy amounts).
  • the data specified by fields 522 and 524 may be received from the corresponding vendor (e.g. via the corresponding vendor server).
  • the data may be provided when the vendor registers with the controller 110 in the embodiment of FIG. 1A .
  • the controller 110 in the embodiment of FIG. 1A or the vendor server 160 in the embodiment of FIG. 1B , would generate a unique vendor identifier to store in the field 520 of the entry corresponding to the new vendor. Once such information is stored for a vendor, it may be retrieved upon reference to the appropriate vendor identifier.
  • a table 600 represents an embodiment of the transaction database 250 ( FIG. 2 ) and/or the transaction database 350 ( FIG. 3 ).
  • the table 600 includes entries 602 , 604 and 606 , each defining a transaction with a vendor server. Typically, the transaction includes a purchase of items by a customer. Those skilled in the art will understand that the table 600 may include any number of entries.
  • the table 600 also defines fields for each of the entries 602 , 604 and 606 .
  • the fields specify (i) a transaction identifier 620 that uniquely identifies the transaction, (ii) a time 622 of the transaction, (iii) the items ordered 624 , (iv) credit card information 626 that may define a credit card account that was charged to pay for the items purchased, (v) an amount charged 628 for the items, (vi) a delivery address 630 for the items, and (vii) a customer identifier 632 (if any) that identifies the customer that made the purchase.
  • the data specified by fields 624 , 626 , 628 , 630 and 632 may be received via the corresponding customer terminal.
  • the items ordered may be identified by being scanned by a bar code scanner that transmits a representative signal to a POS terminal.
  • the items ordered may have been selected by a customer via a Web page displayed by his personal computer.
  • the credit card information may be read by a credit card reader that transmits a representative signal to a POS terminal.
  • the credit card information may be entered by a customer into a form on a Web page displayed by his personal computer.
  • the data may be transmitted from the customer device to the controller 110 in the embodiment of FIG. 1A , or to the vendor server 160 in the embodiment of FIG. 1B .
  • a unique transaction identifier may be generated and the time of the transaction may be recorded (e.g. with reference to a clock signal generated by the customer terminal, vendor server, controller or other device).
  • the transaction identifier and the time are stored in the fields 620 and 622 respectively of the entry corresponding to the new transaction. Once such information is stored for a transaction, it may be retrieved upon reference to the appropriate transaction identifier.
  • a table 700 represents an embodiment of the subsidizer database 260 ( FIG. 2 ).
  • the table 700 includes entries 702 , 704 and 706 , each defining a subsidizing vendor that may subsidize purchases. Such information may be determined when a subsidizing vendor registers for participation in the subsidizing program described herein. Those skilled in the art will understand that the table 700 may include any number of entries.
  • the table 700 also defines fields for each of the entries 702 , 704 and 706 .
  • the fields specify (i) a subsidizing vendor identifier 720 that uniquely identifies the subsidizing vendor, (ii) a name 722 of the subsidizing vendor, (iii) an account 724 used to pay for the subsidies, (iv) an amount owed 726 by the subsidizing vendor, and (v) a rank 728 used to prioritize subsidizing vendors and/or subsidies from those subsidizing vendors.
  • the ranks may be established periodically (e.g. once per year) based on various criteria. For example, the ranks may be adjusted dynamically based on the acceptance rates of offers from the subsidizing vendors and/or amount of funds the subsidizing vendors have provided in connection with their offers.
  • the data specified by fields 722 and 724 may be received from the corresponding subsidizing vendor (e.g. via the corresponding vendor server).
  • the data may be provided when the subsidizing vendor registers with the controller 110 in the embodiment of FIG. 1A , or with the vendor server 160 in the embodiment of FIG. 1B .
  • the controller 110 in the embodiment of FIG. 1A , or the vendor server 160 in the embodiment of FIG. 1B would generate a unique subsidizing vendor identifier to store in the field 720 of the entry corresponding to the new subsidizing vendor.
  • the amount owed is calculated and updated for each subsidizing vendor.
  • the amount owed is updated when an offer from a particular subsidizing vendor is accepted by a customer.
  • the rank of each subsidizing vendor is updated according to a ranking scheme. For example, subsidizing vendors may pay for a preferential rank, and/or rank may be determined by the number (or percentage) of corresponding offers that are accepted. Once such information is stored for a subsidizing vendor, it may be retrieved upon reference to the appropriate subsidizing vendor identifier.
  • a table 800 represents an embodiment of the offer rules database 270 ( FIG. 2 ).
  • the table 800 includes entries 802 , 804 , 806 , 808 and 810 , each defining, among other things, an offer rule.
  • the vendor provides an offer for a specified benefit, such as a subsidy.
  • a subsidy Such information may be determined when a subsidizing vendor registers for participation in the subsidizing program described herein.
  • the table 800 may include any number of entries.
  • the table 800 also defines fields for each of the entries 802 , 804 , 806 , 808 and 810 .
  • the fields specify (i) an offer rule identifier 820 that uniquely identifies the offer rule, (ii) a subsidizing vendor identifier 822 that uniquely identifies the subsidizing vendor, (iii) customer activity 824 that is required in order for an offer to be provided, (iv) a subsidy amount 826 , (v) when the offer rule is effective 828 (i.e. other requirements in order to satisfy the offer rule), and (vi) an additional transaction 830 that is required of the customer in exchange for the subsidy. As described below, several types of transactions, such as additional purchases or initiating service agreements, may be required of the customer.
  • Some types of customer activity in a Web embodiment include a mouse click on a predetermined portion of a Web page, on a predetermined banner advertisement, and on an indication of an item.
  • a mouse-over indication of cursor location and/or movement
  • Such customer activity can indicate, for example, that the customer is evaluating particular products on the Web site by clicking on particular links or placing the cursor over the links.
  • Some other types of customer activity in a Web embodiment include performing a search for a predetermined item, opening or accessing an electronic cash account (e.g. an e-cash “wallet”), accessing predetermined Web pages, a predetermined number of predetermined Web pages, predetermined Web pages in a predetermined sequence, or
  • predetermined Web pages during a predetermined time period; a duration that the Web site is open; and previous access to a predetermined Web site at least a predetermined number of times.
  • customer activity include a predetermined number of items that a customer is ready to purchase from a vendor (indicated, for example, by the content of the customer's virtual shopping cart), one or more predetermined items that the customer is ready to purchase from a vendor, a duration that an item is selected for purchase, requesting a coupon for a predetermined item, an item having at least a predetermined price that the customer is ready to purchase from the first vendor, at least a predetermined number of previous purchases from the first vendor, and frequent shopper status of the customer.
  • the data specified by fields 824 , 826 , 828 and 830 may be received from the corresponding subsidizing vendor (e.g. via the corresponding subsidizing vendor server) for each offer rule the subsidizing vendor establishes.
  • the data may be provided when the subsidizing vendor registers with the controller 110 in the embodiment of FIG. 1A , or with the vendor server 160 in the embodiment of FIG. 1B .
  • the controller 110 in the embodiment of FIG. 1A , or the vendor server 160 in the embodiment of FIG. 1B would generate a unique offer rule identifier to store in the field 820 of the entry corresponding to the new offer rule.
  • the corresponding subsidizing vendor identifier would also be stored in the field 822 . Once such information is stored for an offer rule, it may be retrieved upon reference to the appropriate offer rule identifier.
  • the customer activity that is required in order for an offer to be provided may be set by the subsidizing vendor.
  • the required customer activity may be set by the controller 110 for each subsidizing vendor.
  • the subsidizing vendor may be unable to decide which type of customer activity should be required.
  • the required customer activity may be set and thereafter dynamically adjusted based on acceptance rates of provided offers.
  • a table 900 represents an embodiment of the offers database 280 ( FIG. 2 ).
  • the table 900 includes entries 902 , 904 , 906 , 908 and 910 , each defining an offer for a subsidy. The offer was provided to a customer during a transaction of the customer with the vendor.
  • the table 900 may include any number of entries.
  • the table 900 also defines fields for each of the entries 902 , 904 , 906 , 908 and 910 .
  • the fields specify (i) an offer identifier 920 that uniquely identifies the offer, (ii) a transaction identifier 922 that uniquely identifies the transaction during which the offer was provided, (iii) a subsidizing vendor identifier 924 that uniquely identifies the subsidizing vendor, (iv) an identifier of an offer rule 926 that was applied during the transaction, (v) when the offer was provided 928 , (vi) an expiration date 930 (if any) for the offer, (vii) a subsidy amount 932 , (viii) a total price 934 that the customer would have to pay without the subsidy, (ix) a total price 936 that the customer would have to pay with the subsidy, and (x) when the offer was accepted 938 (if it was accepted).
  • offer rules define specific subsidies.
  • the identifier of an offer rule stored in field 926 may be used to determine a corresponding subsidy amount.
  • the subsidy amount may be a fixed amount, such as $50.
  • the subsidy amount may further be dependent on various criteria such as the purchase total. For example, the subsidy amount could be for the lesser of the purchase total and $50. Similarly, the subsidy amount could be for the lesser of a portion of the purchase total and $50. For example, the subsidy amount could be for the lesser of $50 and half the purchase total.
  • the data specified by fields 928 , 934 , 936 and 938 may be received from the corresponding customer terminal for each offer that has been provided. For example, when the offer is provided a new entry of the table 900 may be created. At that time, the date and time that the offer was provided may be recorded (e.g. with reference to a clock signal generated by the customer terminal, vendor server, controller or other device), and the total price and the total price with the subsidy amount may be received, e.g., from the POS terminal.
  • the field 938 of the new entry would initially be set to “open” to indicate that the offer is open (not yet accepted or rejected). Field 922 , 924 and 926 of the new entry would be set to the appropriate identifiers.
  • Field 930 could be calculated from the field 928 (e.g. a predetermined time after the time in field 928 or “none” if there is no desired expiration date).
  • Field 932 is determined from the corresponding offer rule applied, as described above with respect to field 826 .
  • the field 938 may be updated when an offer is rejected or accepted.
  • a table 1000 represents a record of an embodiment of the offer summary database 290 ( FIG. 2 ).
  • the offer summary database 290 typically includes a plurality of records, each defining a summary of offers for subsidies that have been provided on behalf of a particular subsidizing vendor.
  • the table 1000 includes a subsidizing vendor identifier 1002 that uniquely identifies the subsidizing vendor, a total number of offers provided 1004 on behalf of the subsidizing vendor, a total number of those offers that were accepted 1006 , and a total amount 1008 of the subsidies due in connection with accepted offers.
  • the table 1000 also includes entries 1010 and 1012 , each defining offers provided due to satisfaction of an offer rule of the subsidizing vendor. Those skilled in the art will understand that the table 1000 may include any number of entries.
  • the table 1000 also defines fields for each of the entries 1010 and 1012 . The fields specify (i) an offer rule identifier 1020 that uniquely identifies the offer rule, (ii) a number 1022 of offers provided due to the offer rule, (iii) a number 1024 of these offers that were accepted, and (iv) an amount 1026 of the subsidies due in connection with these accepted offers.
  • the information stored in the offer summary database 290 may be organized by the vendor through which the offer was provided. Such an embodiment would allow a comparison of the acceptance rate of offers at different vendors.
  • the controller 110 in the embodiment of FIG. 1A or the vendor server 160 in the embodiment of FIG. 1B , would create a record such as the record 1000 and store the subsidizing vendor identifier 1002 .
  • a corresponding entry is created and the offer rule identifier is stored in field 1020 .
  • the data specified by fields 1022 , 1024 and 1026 may be adjusted as offers are provided and acceptances of the offers are received. For example, when an offer is provided, the corresponding offer rule is identified and thus the corresponding entry is identified. The field 1022 of that entry is increased by one to reflect the newly-provided offer. Similarly, when an offer is accepted, field 1024 of that entry is increased by one to reflect the new acceptance and the amount of the subsidy associated with the accepted offer is added to the field 1026 of the entry.
  • the sum of the number of offers indicated by the field 1022 for all entries is stored as the total number of offers 1004 for the corresponding record.
  • the number of offers accepted indicated by the field 1024 for all entries is stored as the total number of offers accepted 1006 for the corresponding record
  • the sum of the amounts indicated by the field 1026 for all entries is stored as the total amount 1008 for the corresponding record.
  • a table 1100 represents a record of another embodiment of the offer summary database 290 ( FIG. 2 ).
  • information is organized by offer rule.
  • For each offer rule various types of customer activity may have been required. The results of each type of customer activity are summarized in the record.
  • Various types of customer activity may be required for an offer rule in order to test which customer activities are relatively successful in soliciting an acceptance of an offer. For example, every hour a different customer activity may be required in order for an offer to be provided in accordance with the offer rule. In such an embodiment, each hour the controller 110 ( FIG. 1A ) may update the customer activity field 824 of an entry of the offer rules database 270 to reflect the new customer activity that is required. The most successful customer activity requirement may then be used in the future.
  • the offer summary database 290 can include a plurality of records, each defining a summary of offers for subsidies that have been provided in response to a customer activity in accordance with the offer rule.
  • the table 1100 includes an offer rule identifier 1102 that uniquely identifies the offer rule.
  • the table 1100 also includes entries 1104 , 1106 and 1108 . Each entry defines offers provided in accordance with the offer rule and upon certain customer activity. Those skilled in the art will understand that the table 1100 may include any number of entries.
  • the table 1100 also defines fields for each of the entries 1104 , 1106 and 1108 .
  • the fields specify (i) customer activity 1120 required for the offer, (ii) a number 1122 of offers provided due to the particular customer activity for the offer rule, (iii) a number 1124 of these offers that were accepted, and (iv) an acceptance rate 1126 (the ratio of offers accepted to number of offers provided).
  • customer activity 1120 required for the offer (ii) a number 1122 of offers provided due to the particular customer activity for the offer rule, (iii) a number 1124 of these offers that were accepted, and (iv) an acceptance rate 1126 (the ratio of offers accepted to number of offers provided).
  • the information stored in the offer summary database 290 may be organized according to other information.
  • the controller 110 in the embodiment of FIG. 1A or the vendor server 160 in the embodiment of FIG. 1B , would create a record such as the record 1100 and store the offer rule identifier 1102 .
  • a corresponding entry is created and an indication of the customer activity is stored in field 1120 .
  • the data specified by fields 1122 , 1124 and 1126 may be adjusted as offers are provided and acceptances of the offers are received. For example, when an offer is provided in response to a particular customer activity, the corresponding entry is identified. The field 1122 of that entry is increased by one to reflect the newly-provided offer.
  • field 1124 of that entry is increased by one to reflect the new acceptance and the acceptance rate is calculated and stored in the field 1126 of the entry.
  • a table 1200 represents an embodiment of the item database 340 ( FIG. 3 ).
  • the table 1200 includes entries 1202 and 1204 , each defining an item sold via a vendor server. Those skilled in the art will understand that the table 1200 may include any number of entries.
  • the table 1200 also defines fields for each of the entries 1202 and 1204 . The fields specify (i) a item identifier 1220 that uniquely identifies the item, (ii) an item description 1222 , (iii) an item price 1224 for which the item is typically sold, and (iv) an availability 1226 of the item which may be based on an inventory level of the item.
  • the data specified by fields 1222 , 1224 and 1226 may be received from the corresponding vendor.
  • the data may be provided when a vendor prepares to sell the item.
  • the vendor server Upon the entering of a new item, the vendor server would generate a unique customer identifier to store in the field 1220 of the entry corresponding to the new item. Once such information is stored for an item, it may be retrieved upon reference to the appropriate item identifier.
  • a flow chart 1300 illustrates an embodiment of a method for providing an offer for a benefit (e.g. a reduced price) to a customer that is to purchase items from a vendor.
  • a benefit e.g. a reduced price
  • the illustrated method is described below as being performed by the controller 110 in the embodiment of FIG. 1A , the illustrated method may alternatively be performed by the vendor server 160 in the embodiment of FIG. 1B .
  • Information relating to customer activity of a customer with a first vendor is received (step 1302 ). Such information may be received via a Web server, for example, in an embodiment where a vendor sells via the Internet.
  • the Web server which may be the vendor server, may receive data from the customer terminal that indicates, for example, hyperlinks that the customer clicks on, buttons that the customer actuates, or mouse movements of the customer terminal.
  • the information may be received from a “cookie” stored on the customer terminal (e.g. on a personal computer of the customer).
  • a cookie is a block of data that a Web server (e.g. the vendor server) stores on a client system (e.g. a customer terminal).
  • client system e.g. a customer terminal
  • Cookies may be used to identify users of the customer terminal, to instruct the Web server to send a customized version of a Web page, to submit account information for the user, and for other administrative purposes.
  • the information may be received via a telephone, for example, in an embodiment where a vendor sells via an IVRU.
  • the information may also be received via a POS terminal, for example, in an embodiment where a vendor sells at a retail store.
  • the POS terminal receives data such as UPC codes that identify items scanned with a bar code scanner, prices of those items, and information received from a customer's frequent shopper card.
  • the information may be received via a device, such as a PDA (Personal Digital Assistant) or a scanner mounted on a shopping cart, that the customer uses to indicate the items he has selected for purchase or the items in which he his otherwise interested.
  • PDA Personal Digital Assistant
  • the information may also be received via a sensor that senses the presence or location of a customer.
  • a sensor that senses the presence or location of a customer.
  • infrared or pressure sensors may be disposed in a store and operable to sense when a customer is near particular products or areas.
  • the information may also be received via a device that scans items with a bar code scanner and provides the prices of those items that are scanned.
  • a device that scans items with a bar code scanner and provides the prices of those items that are scanned.
  • Such devices are known and are frequently disposed in supermarkets to allow customers to determine the prices of items, especially items that are on sale or otherwise subject to special pricing.
  • the information relating to customer activity dictates whether the offer is provided. For example, as described in detail below there may be one or more rules specifying customer activity that is required. If an offer should not be provided, then the controller 110 interacts with the customer conventionally (step 1306 ).
  • an offer for a subsidy from a second vendor is determined (step 1308 ). For example, in an embodiment where one or more rules are included, if a rule is satisfied a corresponding offer for a subsidy is provided.
  • An indication of the offer (or offers) is provided to the customer (step 1310 ). For example, text and/or images may be displayed on a Web page that is displayed on the customer terminal, text may be displayed on a monitor of a POS terminal, or an audio signal may be transmitted via an IVRU to a telephone.
  • the indication of the offer may be provided via a device, such as a PDA (Personal Digital Assistant) or a display mounted on a shopping cart of the customer, that accompanies the customer as he browses a store.
  • a display disposed in a particular location in the store e.g. below a product display
  • the indication of the offer may be provided via a device that scans items with a bar code scanner and provides the prices of those items scanned.
  • a device that could display an offer upon scanning the bar code of an item.
  • the offer typically specifies a subsidy amount and an obligation to fulfill in exchange for the subsidy.
  • an additional transaction may be required of the customer.
  • the customer may be required to sign up for a service that is provided by the second vendor (e.g. initiate a service agreement with the second vendor).
  • the customer may be required to switch from a current service provider to the second vendor, so that the service will no longer be provided by the current service provider.
  • Examples of services include telephone service, Internet service, banking services, credit card account services, insurance service, securities trading service, utilities service, satellite television service, or cable television service.
  • Telephone service can include long distance service such as is provided by Sprint Communications Company, L.P or wireless service such as is provided by AT & T.
  • Signing up for banking services may include the requirement to transfer a particular minimum balance to a new bank account.
  • Signing up for credit card account services may similarly include the requirement to apply for a credit card account and/or transfer a particular minimum balance to a new or existing credit card account.
  • Signing up for securities trading services may include the requirement to open an account with a particular minimum balance amount.
  • the controller 110 receives an indication of items the customer desires to purchase (step 1312 ).
  • the items may have been scanned by a bar code scanner and thus identified by a POS terminal.
  • the items may have been selected by a customer via a Web page and put in a virtual “shopping cart”.
  • Other ways to indicate items the customer desires to purchase will be apparent to those skilled in the art.
  • the controller 110 also receives a response to the offer from the customer terminal (step 1314 ).
  • the customer may indicate his response by, for example, clicking a button on a Web page, actuating particular keys on a touch-tone telephone, actuating a button on a keypad in communication with a POS terminal, or verbally responding to a cashier that actuates buttons on the POS terminal.
  • the controller 110 interacts with the customer conventionally (step 1306 ). Otherwise, the offer is accepted and the customer is charged a lower price for the items than he otherwise would have been charged (step 1318 ). The customer may even get the items for free or receive a credit (e.g. money back or store credit).
  • the benefit to the customer may be different than a reduced price on the items he desires to purchase. For example, the customer may be given a product upgrade to another (higher value) item or the customer may be given an additional item at a discount or for free. The customer may also be provided with cash, store credit or other monetary award.
  • a flow chart 1400 illustrates an embodiment of a method for providing an offer for a benefit to a customer that is to purchase items from a vendor.
  • one or more rules determine which offers (if any) are provided to a customer.
  • the illustrated method is described below as being performed by the controller 110 in the embodiment of FIG. 1A , the illustrated method may alternatively be performed by the vendor server 160 in the embodiment of FIG. 1B .
  • the controller selects an offer rule to evaluate against the customer activity (step 1404 ).
  • the rule may be defined by and selected from the offer rules database 270 ( FIG. 2 ). For example, referring again to FIG. 8 , each entry of the table 800 defines an offer rule. Accordingly, the controller 110 may select an entry of the offer rules database 270 (e.g. starting with the first entry).
  • each offer rule includes customer activity that is required in order for an offer to be provided. Accordingly, the received information relating to customer activity may be compared with the customer activity that is required by the offer rule (step 1406 ). If the customer activity does not satisfy the offer rule, then it is determined whether there are more offer rules that have not yet been so compared to the received information (step 1408 ). If there are not any more offer rules, then the controller 110 interacts conventionally with the customer (step 1410 ).
  • step 1404 If there are more offer rules, then another offer rule is selected (step 1404 ). For example, the next entry in the offer rules database 270 may be selected. Those skilled in the art will realize that the offer rules need not be selected according to the sequence defined by the offer rules database 270 .
  • the controller 110 determines if the offer rule is otherwise effective (step 1412 ). For example, referring to FIG. 8 , each entry of the table 800 defines other requirements necessary in order to satisfy the offer rule (i.e. the field 828 ). If the rule is not otherwise effective (i.e. the other requirements are not satisfied), then it is determined whether there are more offer rules that have not yet been so compared to the received information (step 1408 ). If there are not any more offer rules, then the controller 110 interacts conventionally with the customer (step 1410 ). Otherwise, another offer rule is selected (step 1404 ).
  • the controller 110 If the offer rule is otherwise effective, then the controller 110 generates an offer (step 1414 ).
  • the offer indicates the subsidy amount (specified by the field 826 of the corresponding entry) and an additional transaction required (specified by the field 830 of the corresponding entry).
  • An indication of the offer is provided to the customer (step 1416 ), as described above. If there any more offer rules, then they are in turn selected and evaluated as described above.
  • the illustrated method allows one or more offers to be provided to a customer.
  • the customer may in turn accept an offer as described above.
  • the customer may be asked to select one (or more) of the plurality, and the selection would indicate an acceptance of the selected offer.
  • the sequence of the offers may be defined by, for example, the ranks of the corresponding subsidizing vendors.
  • a flow chart 1500 illustrates an embodiment of a method for providing an offer for a benefit to a customer that is to purchase items from a vendor.
  • a customer receives a subsidy subject to an obligation.
  • the customer may receive an immediate benefit in exchange for participating or agreeing to participate in a transaction with the second vendor.
  • the customer may be required to participate in a future transaction with the second vendor.
  • the illustrated method is described below as being performed by the controller 110 in the embodiment of FIG. 1A , the illustrated method may alternatively be performed by the vendor server 160 in the embodiment of FIG. 1B .
  • step 1502 Information relating to customer activity of a customer with a first vendor is received (step 1502 ). It is then determined whether an offer for a subsidy should be provided (step 1504 ). If an offer should not be provided, then the controller 110 interacts with the customer conventionally (step 1506 ). Otherwise, an offer for a subsidy from a second vendor is determined (step 1508 ). For example, the information relating to customer activity may satisfy a rule, and the rule in turn specifies an offer. The controller 110 provides an indication of the offer (including its associated obligation) to the customer (step 1510 ).
  • the controller 110 receives an indication of items the customer desires to purchase (step 1512 ).
  • the controller 110 also receives a credit card account identifier (step 1514 ), such as a credit card number.
  • the credit card account identifier may be received, for example, via a credit card authorization terminal that is in communication with a POS terminal, as is known to those skilled in the art.
  • the credit card account is charged a lower price for the items than otherwise would have been charged (step 1516 ).
  • the customer may even get the items for free.
  • the controller 110 determines whether the customer has fulfilled the obligation of the offer (step 1518 ).
  • the obligation could be a requirement to sign up for a service provided by the second vendor.
  • the second vendor may provide, for example, telephone service, Internet service, banking services, credit card account services, insurance service, securities trading service, satellite television service, or cable television service.
  • the obligation may further include a requirement that the service be maintained for a particular amount of time.
  • the customer may have been required to fulfill the obligation before his credit card account is charged.
  • the customer may have been required to fill out a credit card application before completing the purchase of his items.
  • the obligation may be need to be fulfilled at still other times.
  • the controller 110 can access a list of new or existing customers to determine whether the customer has fulfilled his obligation by signing up (and therefore becoming a new customer).
  • the controller 110 could access such a list periodically (e.g. every week) or upon demand (e.g. the controller receives the names of new customers as they become available).
  • the controller 110 could query the subsidizing vendor server, and in response receive a signal that indicates whether the customer had signed up for service from the second vendor.
  • the customer could be required to switch service providers from another service provider to the second vendor.
  • the controller 110 records the time and date the obligation was fulfilled (step 1520 ).
  • the time and date may be stored, for example, in the field 938 of the entry corresponding to the offer. In such an embodiment, fulfilling the obligation may be considered acceptance of the offer.
  • step 1522 it is determined whether the offer has expired.
  • the expiration date and time of an offer is indicated by the field 930 of the offers database 280 ( FIG. 2 ), and may be calculated based on the time the offer was provided. If the offer has expired without the obligation being fulfilled, the credit card account of the customer is charged for the difference between the item price and the lower price previously charged (step 1524 ). This step assesses a penalty against the customer by removing the benefit that was previously provided to the customer if the customer does not fulfill the obligation within the allotted time.
  • the credit card account is charged $95 in total ($80 and $15), which is the conventional price for the item.
  • An even larger amount may be charged (i.e. greater than $15 in the above example) if desired to deter customers from reneging on the obligation.
  • a flow chart 1600 illustrates an embodiment of a method for determining whether customers have fulfilled their obligations associated with an offer for a benefit. Although the illustrated method is described below as being performed by the controller 110 in the embodiment of
  • the illustrated method may alternatively be performed by the vendor server 160 in the embodiment of FIG. 1B .
  • the obligation is to become a new customer of a subsidizing vendor.
  • the customer may have been obliged to initiate a new service agreement so that a particular service is provided to the customer by the subsidizing vendor.
  • the controller 110 selects a customer from a list of new customers (step 1602 ) of the subsidizing vendor.
  • the list of new customers may be generated by the subsidizing vendor and transmitted to the controller 110 periodically (e.g. every week) or upon request.
  • Such a list may be compiled by the subsidizing vendor as customers sign up for service and/or complete prerequisites for becoming a customer. Customers may be selected from the list, for example, in the order that they signed up during a predetermined period of time.
  • the controller 110 determines if the selected customer has been offered a subsidy (step 1604 ).
  • the controller may determine whether the selected customer is represented in any entry of the offers database 280 .
  • each entry of the table 900 includes in field 922 an indication of the transaction during which the offer was provided.
  • the corresponding entry of the transaction database 250 in turn indicates a customer identifier (e.g. the field 632 of the table 600 ). If the selected customer has not been offered a subsidy, then the controller 110 determines whether there are more customers that have not yet been selected (step 1610 ). Another customer is selected (step 1602 ) as long as there are more customers in the list that have not been selected.
  • the controller 110 determines if the offer for the subsidy included an obligation to become a customer of the subsidizing vendor (step 1606 ). For example, referring again to FIG. 9 , each entry of the table 900 includes in field 926 an indication of the offer rule applied during the transaction. The corresponding entry of the offer rules database 270 in turn indicates an additional transaction required of the customer (e.g. in the field 830 of the table 800 ). Thus, the controller 110 determines whether the presence of the selected customer on the list of new customers indicates fulfillment of a previous obligation.
  • the controller 110 records that the selected customer has fulfilled his obligation (step 1608 ). For example, the time and date that the customer became a new customer of the subsidizing vendor may be recorded in the field 938 of the corresponding entry of the table 900 . Then additional customers, if any, are selected and processed similarly (e.g., steps 1610 and 1602 ). Customers that have not fulfilled their respective obligations may eventually be penalized in some manner, for example, by charging their credit card accounts a penalty fee amount.
  • the controller 100 could search a list of customers that have accepted offers, rather than a list of new customers, in order to determine whether those customers have become new customers of the specified vendor.
  • a flow chart 1700 illustrates an embodiment of a method for providing an offer for a benefit after a customer has made a purchase from a first vendor.
  • the illustrated method is described below as being performed by the controller 110 in the embodiment of FIG. 1A , the illustrated method may alternatively be performed by the vendor server 160 in the embodiment of FIG. 1B .
  • the controller 110 selects a customer from the list of customers that have purchased from the first vendor (step 1702 ).
  • the first vendor may record the name, address, telephone number and/or e-mail address of each customer that purchases items within a predetermined time period (e.g. each month).
  • the customer selected from the list may be, for example, the first customer that purchased items during a predetermined period of time.
  • the vendor server may determine if contact information of the customer is stored. For example, the vendor server may determine whether the customer is a member of a frequent shopper program (in which contact information is typically obtained upon registration). Alternatively, it may be determined whether the customer filled in a form on a Web page that requests contact information. If contact information of the customer is not stored, the vendor server can then request contact information of the customer, and wait for the customer to provide that contact information.
  • the controller determines whether the selected customer should be provided an offer for a subsidy (step 1704 ) from a second vendor, as described above. If the customer should not be provided with an offer for a subsidy, then the controller determines whether there are more customers on the list (step 1708 ). If so, then another customer is selected (step 1702 ).
  • the controller 110 provides an indication of the offer for a subsidy to the selected customer using contact information of the customer (step 1706 ).
  • the indication of an offer may be provided, for example, via e-mail, postal mail, and/or telephone.
  • the controller 110 may generate a textual message specifying the offer, and then transmit that message via e-mail to an e-mail address of the customer.
  • the controller 110 may also generate a textual message which is printed onto a sheet of paper, and a postal mail address which is printed onto a mailing label.
  • the mailing label is used in directing the sheet of paper to the customer via conventional postal mail.
  • the offer may be provided on a credit card billing statement of the customer.
  • the controller 110 may also generate an audio message which is transmitted via a telephone to the customer by connecting to the appropriate telephone number.

Abstract

In accordance with some embodiments of the present invention, a controller receives an indication of acceptance by a customer of an offer for a subsidy from a second vendor (e.g., a subsidizing vendor). The offer may define, for example, a reduction in the price charged for an item purchased from a first vendor and an obligation for the customer to fulfill in exchange for the subsidy. The customer is charged a second price for the items, which is less than the total price, and may even be zero.

Description

  • The present application is a continuation of U.S. patent application Ser. No. 09/282,747 entitled METHOD AND APPARATUS FOR PROVIDING CROSS-BENEFITS BASED ON A CUSTOMER ACTIVITY filed Mar. 31, 1999.
  • U.S. patent application Ser. No. 09/282,747 is a continuation-in-part of U.S. patent application Ser. No. 09/219,267 entitled “METHOD AND APPARATUS FOR FACILITATING ELECTRONIC COMMERCE THROUGH PROVIDING CROSS-BENEFITS DURING A TRANSACTION”, filed on Dec. 23, 1998; and is a continuation-in-part of U.S. patent application Ser. No. 09/274,281 entitled “METHOD AND APPARATUS FOR PROVIDING CROSS-BENEFITS VIA A CENTRAL AUTHORITY”, filed Mar. 22, 1999 and issued as U.S. Pat. No. 7,818,284 on Oct. 19, 2010; and is a continuation-in-part of U.S. patent application Ser. No. 09/116,367 entitled “METHOD AND APPARATUS FOR PROVIDING A DISCOUNT TO A CUSTOMER THAT PARTICIPATES IN TRANSACTIONS AT A PLURALITY OF MERCHANTS”, filed Oct. 5, 1998 and now abandoned.
  • U.S. patent application Ser. No. 09/274,281 is a continuation-in-part of U.S. patent application Ser. No. 09/219,267 entitled “METHOD AND APPARATUS FOR FACILITATING ELECTRONIC COMMERCE THROUGH PROVIDING CROSS-BENEFITS DURING A TRANSACTION”, filed Dec. 23, 1998.
  • The entirety of each of the applications identified above is incorporated by reference herein as part of the present disclosure.
  • FIELD OF THE INVENTION
  • The present invention relates to methods and apparatus for facilitating commerce.
  • BACKGROUND OF THE INVENTION
  • There is a great deal of competition among vendors to attract and retain customers. Even when a customer has browsed a vendor's inventory, he will not make a purchase if an item's price is greater than the amount the customer is willing to pay. One way to increase customer willingness to purchase is to provide discounts on items purchased. Unfortunately, vendors must use discounts sparingly, since reducing purchase prices likewise reduces margins and the reduced margins may not be offset by increased sales volume.
  • A vendor may also offer promotions to provide an incentive for customers to make purchases. For example, a vendor may offer a “buy one get one free” promotion whereby a purchase of an item yields the benefit of an additional item at no cost. Similarly, a vendor may provide a discount on a purchase in exchange for signing up for a credit card account provided by the vendor.
  • Promotions may also be provided among two or more vendors. For example, a first vendor may advertise that if a particular product is purchased, another product may be purchased from or given away by a second vendor.
  • A parent application of U.S. patent application Ser. No. 09/219,267 entitled “METHOD AND APPARATUS FOR FACILITATING ELECTRONIC COMMERCE THROUGH PROVIDING CROSS-BENEFITS DURING A TRANSACTION”, filed Dec. 23, 1998, discloses a method and apparatus that permits a customer that is purchasing items from a first vendor to receive a benefit (e.g. a credit for the price of the items) from a second vendor. The present application provides further embodiments of this novel and beneficial invention.
  • SUMMARY OF THE INVENTION
  • It is an object of the present invention to provide a method and apparatus for facilitating commerce.
  • In accordance with the present invention, a controller receives information relating to customer activity with a first vendor, typically via a Web page that a customer accesses. The controller further receives an indication of items (goods and/or services) the customer desires to purchase, the items having an associated total price. The controller determines, based on any of various criteria, whether to provide an offer for a subsidy based on the information relating to customer activity. For example, a customer who places certain items in his virtual “shopping cart” may receive such an offer. The offer for a subsidy is from a second vendor (a subsidizing vendor), and may define, for example, a reduction in the price charged for the item and an obligation for the customer to fulfill in exchange for the subsidy. For example, the customer may be obliged to sign up for a credit card or telephone service provided by the subsidizing vendor.
  • An indication of the offer for the subsidy is provided to the customer, e.g., via a text or graphical display on the Web page. The customer responds via known user interface techniques and, if he accepts the offer, he is charged a second price for the items. The second price is less than the total price, and may even be zero. Thus the customer may get his desired items for free in exchange for fulfilling the obligation with the subsidizing vendor.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1A is a schematic illustration of an embodiment of an apparatus for facilitating commerce in accordance with the present invention.
  • FIG. 1B is a schematic illustration of another embodiment of an apparatus for facilitating commerce in accordance with the present invention.
  • FIG. 2 is a schematic illustration of a controller of the apparatus of FIG. 1.
  • FIG. 3 is a schematic illustration of a vendor server of the apparatus of FIG. 1.
  • FIG. 4 is a representation of a customer database of the controller of FIG. 2.
  • FIG. 5 is a representation of a vendor database of the controller of FIG. 2.
  • FIG. 6 is a representation of a transaction database of the controller of FIG. 2.
  • FIG. 7 is a representation of a subsidizer database of the controller of FIG. 2.
  • FIG. 8 is a representation of an offer rules database of the controller of FIG. 2.
  • FIG. 9 is a representation of an offers database of the controller of FIG. 2.
  • FIG. 10 is a representation of a record of an offer summary database of the controller of FIG. 2.
  • FIG. 11 is a representation of a record of another embodiment of the offer summary database.
  • FIG. 12 is a schematic illustration of an item database of the vendor server of FIG. 3.
  • FIG. 13 is a flow chart illustrating an embodiment of a method for providing an offer for a benefit.
  • FIG. 14 is a flow chart illustrating an embodiment of a method for providing an offer for a benefit using offer rules.
  • FIGS. 15A and 15B are a flow chart illustrating an embodiment of a method for providing an offer which may be accepted by fulfilling an obligation associated with the offer.
  • FIG. 16 is a flow chart illustrating an embodiment of a method for determining whether customers have fulfilled their obligations associated with an offer for a benefit.
  • FIG. 17 is a flow chart illustrating an embodiment of a method for providing an offer for a benefit after a customer has made a purchase from a vendor.
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • Applicants have recognized that the acquisition budgets of various service providers may be advantageously used to facilitate commerce. A customer that purchases items from a first vendor may be paid, directly or indirectly, by a second vendor, so that the customer pays a reduced price, perhaps nothing at all, for his desired items. In exchange, the customer participates or agrees to participate in a transaction with the second vendor. For example, the customer may be required to sign up for a service that is provided by the second vendor. Since many service providers are willing to pay significant amounts of money (e.g. often $50 to $200) to acquire a new customer, the ability to acquire a customer by essentially “intervening” in a sale between others can benefit all parties involved. In short, the second vendor provides a subsidy to the customer. The customer is benefited by the reduced price of his items, the first vendor is benefited by the increased sales and customer satisfaction that such an arrangement would bring, and the second vendor is benefited by the additional transaction, particularly the acquisition of a new customer in one embodiment.
  • In addition, applicants have also recognized that various types of customer activities may be used to indicate, among other things, whether the customer is likely to accept an offer for a benefit from a subsidizing vendor. For example, when a customer begins to interact with a first vendor (e.g. via the first vendor's Web site), various types of customer activity may be used to indicate whether the customer is willing to transact with the first vendor. Similarly, various types of customer activity may be used to indicate whether the customer is willing to transact with a subsidizing vendor. Detection of such customer activity can assist is identifying, e.g., which customers should be given offers for subsidies, and when.
  • Referring to FIG. 1A, an apparatus 100 includes a controller 110 that is in communication with a vendor server 120. The controller 110 and the vendor server 120 may comprise computers, such as those based on an Intel® Pentium® microprocessor, that are adapted to communicate via the Internet (e.g. via a modem) or other medium. Any number of vendor servers may be in communication with the controller 110. Those skilled in the art will understand that devices in communication with each other need not be continually transmitting to each other. On the contrary, such devices need only transmit to each other as necessary, and may actually refrain from exchanging data most of the time. For example, a device in communication with another device via the Internet may not transmit data to the other device for weeks at a time.
  • The vendor server 120 may be a “Web server” of a vendor (e.g. a retail seller). A vendor server could then generate Web pages (documents on the World Wide Web that typically include an HTML file and associated graphics and script files) that may be accessed via the World Wide Web and allow purchases from the vendor to be made in a manner known in the art. A Web site consists of several such Web pages and associated databases served up by an HTTP server (e.g. the vendor server 120) on the World Wide Web. Alternatively, the vendor server 120 may be a computer involved in operating a physical store. Such a computer, for example a point of sale (POS) server, would perform such tasks as inventory management and transaction processing for the store.
  • The controller 110 is also in communication with a subsidizing vendor server 140. The subsidizing vendor server 140 may comprise a computer, such as those based on an Intel® Pentium® microprocessor, that is adapted to communicate via the Internet (e.g. via a modem) or other medium. Any number of subsidizing vendor servers may be in communication with the controller 110.
  • The subsidizing vendor server 140 may be a “Web server” of a vendor. The subsidizing vendor server 140 could then generate a Web page that may be accessed via the World Wide Web and allow transactions with the subsidizing vendor in a manner known in the art. Alternatively, the subsidizing vendor server 140 may be a computer involved in operating a physical store. Such a computer would perform such tasks as inventory management and transaction processing.
  • The vendor server 120 may be in communication with a customer terminal 130 that transmits data regarding a customer transaction (e.g. a purchase). Any number of customer terminals may be in communication with the vendor server 120. The customer terminal 130 may be a point of sale (POS) terminal, such as the NCR 7454 manufactured by NCR Corporation or the IBM 4683 manufactured by International Business Machines. As is known in the art, POS terminals perform such processes as calculating the total price of a purchase (goods or services) and calculating the amount of change due to a customer. POS terminals may furthermore track purchases made and adjust databases of inventory accordingly.
  • In another embodiment, the customer terminal 130 may be a computer, such as those based on an Intel® Pentium® microprocessor, that are adapted to communicate via the Internet (e.g. via a modem) or other medium. Such computers are able to appropriately access a Web page to communicate with a vendor server in a manner that is known to those skilled in the art.
  • In still other embodiments, the customer terminal 130 may be a telephone, an automated teller machine (ATM), slot machine, a vending machine or other device that receives payment from customers in exchange for providing goods or services. The vendor server in such an embodiment could include an IVRU (Interactive Voice Response Unit), such as the Vision 2001 or the Insight IVR/Web, both from Interactive Voice Technologies, Corp., or the OmniVox for Windows NT from APEX Voice Communications. An IVRU allows a user of a DTMF (Dual Tone Multi-Frequency) signal generating telephone to communicate with a computer. The DTMF signals received from the user's telephone are interpreted by the vendor server, and the vendor server may also communicate with the user by generating and transmitting voice or other audio signals, such as a list of IVRU menu options.
  • The use of the controller 110 is especially advantageous in an embodiment where a plurality of subsidizing vendors and/or a plurality of vendor servers serving customers participate in the described invention. A parent application, U.S. patent application Ser. No. 09/274,281 entitled “METHOD AND APPARATUS FOR PROVIDING CROSS-BENEFITS VIA A CENTRAL AUTHORITY”, filed Mar. 22, 1999 and issued as U.S. Pat. No. 7,818,284 on Oct. 19, 2010, the entirety of which is incorporated by reference herein as part of the present disclosure, discloses an invention utilizing such a controller.
  • Referring to FIG. 1B, an apparatus 150 represents another embodiment of an apparatus for facilitating commerce in accordance with the present invention.
  • Specifically, in the apparatus 150 a vendor server 160 communicates with a customer terminal 170 and with a subsidizing vendor server 180 without the intervening controller 110. Accordingly, the embodiment illustrated by FIG. 1B is appropriate for a direct relationship between the vendor servicing customers and the subsidizing vendor.
  • Referring to FIG. 2, reference numeral 200 indicates a device that may be the controller 110 (FIG. 1A). In another embodiment, the functionality of the device 200 may be performed by another device, such as the vendor server 160 (FIG. 1B), which operates to provide a customer with an offer for a subsidy from a second vendor.
  • The device 200 comprises a processor 202, such as an Intel® Pentium® microprocessor. The processor 202 is in communication with a data storage device 210, such as an appropriate combination of magnetic, optical and/or semiconductor memory. For example, the data storage device 210 may comprise one or more of a ROM, RAM and hard disk. The processor 202 and the data storage device 210 may each be (i) located entirely within a single computer or other computing device; (ii) connected to each other by a remote communication medium, such as a serial port cable, telephone line or radio frequency transceiver; or (iii) a combination thereof. In one embodiment, the controller 110 may comprise one or more computers that are connected to a remote server computer for maintaining databases.
  • The data storage device 210 stores a program 220 for controlling the processor 202. The processor 202 performs instructions of the program 220, and thereby operates in accordance with the present invention, and particularly in accordance with the methods described in detail herein. The program 220 furthermore includes program elements that may be necessary, such as an operating system and “device drivers” for allowing the processor 202 to interface with computer peripheral devices. Appropriate device drivers and other necessary program elements are known to those skilled in the art, and need not be described in detail herein.
  • The storage device 210 also stores (i) a customer database 230, (ii) a vendor database 240, (iii) a transaction database 250, (iv) a subsidizer database 260, (v) an offer rules database 270, (vi) an offers database 280 and (vii) an offer summary database 290. The databases 230, 240, 250, 260, 270, 280 and 290 are described in detail below and depicted with exemplary entries in the accompanying figures. As will be understood by those skilled in the art, the schematic illustrations and accompanying descriptions of the databases presented herein are exemplary arrangements for stored representations of information. A number of other arrangements may be employed besides those suggested by the tables shown. Similarly, the illustrated entries of the databases represent exemplary information, and those skilled in the art will understand that the number and content of the entries can be different from those illustrated herein.
  • FIG. 3 illustrates the vendor server 120 of FIG. 1A. As described above with reference to FIG. 1B, in one embodiment the vendor server may communicate with a subsidizing vendor server 180 without the intervening controller 110. Accordingly, the description of the vendor server 120 is applicable to the vendor server 160 of FIG. 1B. In such an embodiment, the databases stored by the data storage device of the vendor server could include the databases depicted in FIGS. 2 and 3.
  • The vendor server 120 comprises a processor 302, such as an Intel® Pentium® microprocessor, which is in communication with a customer terminal 315 and the controller 110. The processor 302 is also in communication with a data storage device 310, such as an appropriate combination of magnetic, optical and/or semiconductor memory. For example, the data storage device 310 may comprise one or more of a ROM, RAM and hard disk. The processor 302 and the data storage device 310 may each be (i) located entirely within a single computer or other computing device; (ii) connected to each other by a remote communication medium, such as a serial port cable, telephone line or radio frequency transceiver; or (iii) a combination thereof. In one embodiment, the vendor server 120 may comprise one or more computers that are connected to a remote server computer for maintaining databases.
  • The data storage device 310 stores a program 320 for controlling the processor 302. The processor 302 performs instructions of the program 320, and thereby operates in accordance with the present invention, and particularly in accordance with the methods described in detail herein. The program 320 furthermore includes program elements that may be necessary, such as an operating system and “device drivers” for allowing the processor 302 to interface with computer peripheral devices. Appropriate device drivers and other necessary program elements are known to those skilled in the art, and need not be described in detail herein.
  • The storage device 310 also stores (i) a customer database 330, (ii) an item database 340, and (iii) a transaction database 350. The customer database 330 and the transaction database 350 of the vendor server 120 may be similar or identical to the customer database 230 and transaction database 250 of the controller 110. For example, the controller 110 may store data that is derived from the vendor server 120, and vice versa. If each vendor server stores data on its own customers and its own transactions, the controller 110 could aggregate this data from each vendor server.
  • The databases 330, 340 and 350 are described in detail below and depicted with exemplary entries in the accompanying figures. As will be understood by those skilled in the art, the schematic illustrations and accompanying descriptions of the databases presented herein are exemplary arrangements for stored representations of information. A number of other arrangements may be employed besides those suggested by the tables shown. Similarly, the illustrated entries of the databases represent exemplary information, and those skilled in the art will understand that the number and content of the entries can be different from those illustrated herein.
  • Referring to FIG. 4, a table 400 represents an embodiment of the customer database 230 (FIG. 2) and/or the customer database 330 (FIG. 3). The table 400 includes entries 402, 404, 406 and 408, each defining a customer that may purchase items from a vendor. Such information may be determined, for example, when a customer registers for a frequent shopper card. Those skilled in the art will understand that the table 400 may include any number of entries. The table 400 also defines fields for each of the entries 402, 404, 406 and 408. The fields specify (i) a customer identifier 420 that uniquely identifies the customer, (ii) a name 422 of the customer, (iii) a billing address 424 of the customer, (iv) credit card information 426 which may be used to render payment in purchasing the items, and (v) an electronic mail (“e-mail”) address 428 for communication with the customer.
  • For each entry of the table 400, the data specified by fields 422, 424, 426 and 428 may be received from the corresponding customer (e.g. via the corresponding customer terminal and/or vendor server that interacts with the customer). For example, the data may be provided when the customer makes a purchase from a vendor's Web site by requiring the customer to enter information into an HTML form provided on a Web page. Upon registration of a new customer, the controller 110 in the embodiment of FIG. 1A, or the vendor server 160 in the embodiment of FIG. 1B, would generate a unique customer identifier to store in the field 420 of the entry corresponding to the new customer. Once such information is stored for a customer, it may be retrieved upon reference to the appropriate customer identifier.
  • Referring to FIG. 5, a table 500 represents an embodiment of the vendor database 240 (FIG. 2). The table 500 includes entries 502, 504, 506 and 508, each defining a vendor that services customers and may have those customers receive offers for subsidies. Such information may be determined when a vendor registers for participation in the subsidizing program described herein. Those skilled in the art will understand that the table 500 may include any number of entries. The table 500 also defines fields for each of the entries 502, 504, 506 and 508. The fields specify (i) a vendor identifier 520 that uniquely identifies the vendor, (ii) a vendor name 522, (iii) a vendor e-mail address 524 for communication with the vendor, and (iv) an amount owed 526 to the vendor (e.g. promised but unpaid subsidy amounts).
  • For each entry of the table 500, the data specified by fields 522 and 524 may be received from the corresponding vendor (e.g. via the corresponding vendor server). For example, the data may be provided when the vendor registers with the controller 110 in the embodiment of FIG. 1A. Upon registration of a new vendor, the controller 110 in the embodiment of FIG. 1A, or the vendor server 160 in the embodiment of FIG. 1B, would generate a unique vendor identifier to store in the field 520 of the entry corresponding to the new vendor. Once such information is stored for a vendor, it may be retrieved upon reference to the appropriate vendor identifier.
  • Referring to FIG. 6, a table 600 represents an embodiment of the transaction database 250 (FIG. 2) and/or the transaction database 350 (FIG. 3). The table 600 includes entries 602, 604 and 606, each defining a transaction with a vendor server. Typically, the transaction includes a purchase of items by a customer. Those skilled in the art will understand that the table 600 may include any number of entries. The table 600 also defines fields for each of the entries 602, 604 and 606. The fields specify (i) a transaction identifier 620 that uniquely identifies the transaction, (ii) a time 622 of the transaction, (iii) the items ordered 624, (iv) credit card information 626 that may define a credit card account that was charged to pay for the items purchased, (v) an amount charged 628 for the items, (vi) a delivery address 630 for the items, and (vii) a customer identifier 632 (if any) that identifies the customer that made the purchase.
  • For each entry of the table 600, the data specified by fields 624, 626, 628, 630 and 632 may be received via the corresponding customer terminal. For example, the items ordered may be identified by being scanned by a bar code scanner that transmits a representative signal to a POS terminal. Alternatively, the items ordered may have been selected by a customer via a Web page displayed by his personal computer. Other ways to indicate items the customer desires to purchase will be apparent to those skilled in the art. Similarly, the credit card information may be read by a credit card reader that transmits a representative signal to a POS terminal. Alternatively, the credit card information may be entered by a customer into a form on a Web page displayed by his personal computer. Those skilled in the art will understand that other payment identifiers besides credit card information may be employed, such as debit card numbers, electronic cash identifiers. The use herein of a credit card as a means of payment is merely exemplary and not limiting on the scope of the present invention.
  • The data may be transmitted from the customer device to the controller 110 in the embodiment of FIG. 1A, or to the vendor server 160 in the embodiment of FIG. 1B. A unique transaction identifier may be generated and the time of the transaction may be recorded (e.g. with reference to a clock signal generated by the customer terminal, vendor server, controller or other device). The transaction identifier and the time are stored in the fields 620 and 622 respectively of the entry corresponding to the new transaction. Once such information is stored for a transaction, it may be retrieved upon reference to the appropriate transaction identifier.
  • Referring to FIG. 7, a table 700 represents an embodiment of the subsidizer database 260 (FIG. 2). The table 700 includes entries 702, 704 and 706, each defining a subsidizing vendor that may subsidize purchases. Such information may be determined when a subsidizing vendor registers for participation in the subsidizing program described herein. Those skilled in the art will understand that the table 700 may include any number of entries. The table 700 also defines fields for each of the entries 702, 704 and 706. The fields specify (i) a subsidizing vendor identifier 720 that uniquely identifies the subsidizing vendor, (ii) a name 722 of the subsidizing vendor, (iii) an account 724 used to pay for the subsidies, (iv) an amount owed 726 by the subsidizing vendor, and (v) a rank 728 used to prioritize subsidizing vendors and/or subsidies from those subsidizing vendors. The ranks may be established periodically (e.g. once per year) based on various criteria. For example, the ranks may be adjusted dynamically based on the acceptance rates of offers from the subsidizing vendors and/or amount of funds the subsidizing vendors have provided in connection with their offers.
  • For each entry of the table 700, the data specified by fields 722 and 724 may be received from the corresponding subsidizing vendor (e.g. via the corresponding vendor server). For example, the data may be provided when the subsidizing vendor registers with the controller 110 in the embodiment of FIG. 1A, or with the vendor server 160 in the embodiment of FIG. 1B. Upon registration of a new subsidizing vendor, the controller 110 in the embodiment of FIG. 1A, or the vendor server 160 in the embodiment of FIG. 1B, would generate a unique subsidizing vendor identifier to store in the field 720 of the entry corresponding to the new subsidizing vendor. The amount owed is calculated and updated for each subsidizing vendor. Typically, the amount owed is updated when an offer from a particular subsidizing vendor is accepted by a customer. The rank of each subsidizing vendor is updated according to a ranking scheme. For example, subsidizing vendors may pay for a preferential rank, and/or rank may be determined by the number (or percentage) of corresponding offers that are accepted. Once such information is stored for a subsidizing vendor, it may be retrieved upon reference to the appropriate subsidizing vendor identifier.
  • Referring to FIG. 8, a table 800 represents an embodiment of the offer rules database 270 (FIG. 2). The table 800 includes entries 802, 804, 806, 808 and 810, each defining, among other things, an offer rule. When an offer rule is satisfied during a transaction, the vendor provides an offer for a specified benefit, such as a subsidy. Such information may be determined when a subsidizing vendor registers for participation in the subsidizing program described herein. Those skilled in the art will understand that the table 800 may include any number of entries. The table 800 also defines fields for each of the entries 802, 804, 806, 808 and 810. The fields specify (i) an offer rule identifier 820 that uniquely identifies the offer rule, (ii) a subsidizing vendor identifier 822 that uniquely identifies the subsidizing vendor, (iii) customer activity 824 that is required in order for an offer to be provided, (iv) a subsidy amount 826, (v) when the offer rule is effective 828 (i.e. other requirements in order to satisfy the offer rule), and (vi) an additional transaction 830 that is required of the customer in exchange for the subsidy. As described below, several types of transactions, such as additional purchases or initiating service agreements, may be required of the customer.
  • Some types of customer activity in a Web embodiment include a mouse click on a predetermined portion of a Web page, on a predetermined banner advertisement, and on an indication of an item. Similarly, a mouse-over (indication of cursor location and/or movement) on a predetermined portion of a Web page and on predetermined portions of Web pages at least a predetermined number of times may be desirable customer activities. Such customer activity can indicate, for example, that the customer is evaluating particular products on the Web site by clicking on particular links or placing the cursor over the links.
  • Some other types of customer activity in a Web embodiment include performing a search for a predetermined item, opening or accessing an electronic cash account (e.g. an e-cash “wallet”), accessing predetermined Web pages, a predetermined number of predetermined Web pages, predetermined Web pages in a predetermined sequence, or
  • predetermined Web pages during a predetermined time period; a duration that the Web site is open; and previous access to a predetermined Web site at least a predetermined number of times.
  • Other types of customer activity include a predetermined number of items that a customer is ready to purchase from a vendor (indicated, for example, by the content of the customer's virtual shopping cart), one or more predetermined items that the customer is ready to purchase from a vendor, a duration that an item is selected for purchase, requesting a coupon for a predetermined item, an item having at least a predetermined price that the customer is ready to purchase from the first vendor, at least a predetermined number of previous purchases from the first vendor, and frequent shopper status of the customer.
  • For each entry of the table 800, the data specified by fields 824, 826, 828 and 830 may be received from the corresponding subsidizing vendor (e.g. via the corresponding subsidizing vendor server) for each offer rule the subsidizing vendor establishes. For example, the data may be provided when the subsidizing vendor registers with the controller 110 in the embodiment of FIG. 1A, or with the vendor server 160 in the embodiment of FIG. 1B. Upon creation of an offer rule, the controller 110 in the embodiment of FIG. 1A, or the vendor server 160 in the embodiment of FIG. 1B, would generate a unique offer rule identifier to store in the field 820 of the entry corresponding to the new offer rule. The corresponding subsidizing vendor identifier would also be stored in the field 822. Once such information is stored for an offer rule, it may be retrieved upon reference to the appropriate offer rule identifier.
  • The customer activity that is required in order for an offer to be provided may be set by the subsidizing vendor. Alternatively, the required customer activity may be set by the controller 110 for each subsidizing vendor. For example, the subsidizing vendor may be unable to decide which type of customer activity should be required. In still another embodiment, the required customer activity may be set and thereafter dynamically adjusted based on acceptance rates of provided offers.
  • Referring to FIG. 9, a table 900 represents an embodiment of the offers database 280 (FIG. 2). The table 900 includes entries 902, 904, 906, 908 and 910, each defining an offer for a subsidy. The offer was provided to a customer during a transaction of the customer with the vendor. Those skilled in the art will understand that the table 900 may include any number of entries. The table 900 also defines fields for each of the entries 902, 904, 906, 908 and 910. The fields specify (i) an offer identifier 920 that uniquely identifies the offer, (ii) a transaction identifier 922 that uniquely identifies the transaction during which the offer was provided, (iii) a subsidizing vendor identifier 924 that uniquely identifies the subsidizing vendor, (iv) an identifier of an offer rule 926 that was applied during the transaction, (v) when the offer was provided 928, (vi) an expiration date 930 (if any) for the offer, (vii) a subsidy amount 932, (viii) a total price 934 that the customer would have to pay without the subsidy, (ix) a total price 936 that the customer would have to pay with the subsidy, and (x) when the offer was accepted 938 (if it was accepted). As described above with reference to FIG. 8, offer rules define specific subsidies. Thus, the identifier of an offer rule stored in field 926 may be used to determine a corresponding subsidy amount.
  • The subsidy amount may be a fixed amount, such as $50. The subsidy amount may further be dependent on various criteria such as the purchase total. For example, the subsidy amount could be for the lesser of the purchase total and $50. Similarly, the subsidy amount could be for the lesser of a portion of the purchase total and $50. For example, the subsidy amount could be for the lesser of $50 and half the purchase total.
  • For each entry of the table 900, the data specified by fields 928, 934, 936 and 938 may be received from the corresponding customer terminal for each offer that has been provided. For example, when the offer is provided a new entry of the table 900 may be created. At that time, the date and time that the offer was provided may be recorded (e.g. with reference to a clock signal generated by the customer terminal, vendor server, controller or other device), and the total price and the total price with the subsidy amount may be received, e.g., from the POS terminal. The field 938 of the new entry would initially be set to “open” to indicate that the offer is open (not yet accepted or rejected). Field 922, 924 and 926 of the new entry would be set to the appropriate identifiers. Field 930 could be calculated from the field 928 (e.g. a predetermined time after the time in field 928 or “none” if there is no desired expiration date). Field 932 is determined from the corresponding offer rule applied, as described above with respect to field 826. Upon creation of an entry in the table 900, the controller 110 in the embodiment of FIG. 1A, or the vendor server 160 in the embodiment of FIG. 1B, would generate a unique offer identifier to store in the field 920. Once such information is stored for an offer, it may be retrieved upon reference to the appropriate offer rule identifier. The field 938 may be updated when an offer is rejected or accepted.
  • Referring to FIG. 10, a table 1000 represents a record of an embodiment of the offer summary database 290 (FIG. 2). The offer summary database 290 typically includes a plurality of records, each defining a summary of offers for subsidies that have been provided on behalf of a particular subsidizing vendor. The table 1000 includes a subsidizing vendor identifier 1002 that uniquely identifies the subsidizing vendor, a total number of offers provided 1004 on behalf of the subsidizing vendor, a total number of those offers that were accepted 1006, and a total amount 1008 of the subsidies due in connection with accepted offers.
  • The table 1000 also includes entries 1010 and 1012, each defining offers provided due to satisfaction of an offer rule of the subsidizing vendor. Those skilled in the art will understand that the table 1000 may include any number of entries. The table 1000 also defines fields for each of the entries 1010 and 1012. The fields specify (i) an offer rule identifier 1020 that uniquely identifies the offer rule, (ii) a number 1022 of offers provided due to the offer rule, (iii) a number 1024 of these offers that were accepted, and (iv) an amount 1026 of the subsidies due in connection with these accepted offers. If desirable, the information stored in the offer summary database 290 (FIG. 2) may be organized by the vendor through which the offer was provided. Such an embodiment would allow a comparison of the acceptance rate of offers at different vendors.
  • For each subsidizing vendor, the controller 110 in the embodiment of FIG. 1A, or the vendor server 160 in the embodiment of FIG. 1B, would create a record such as the record 1000 and store the subsidizing vendor identifier 1002. For each offer rule associated with the subsidizing vendor, a corresponding entry is created and the offer rule identifier is stored in field 1020. For each entry in the record, the data specified by fields 1022, 1024 and 1026 may be adjusted as offers are provided and acceptances of the offers are received. For example, when an offer is provided, the corresponding offer rule is identified and thus the corresponding entry is identified. The field 1022 of that entry is increased by one to reflect the newly-provided offer. Similarly, when an offer is accepted, field 1024 of that entry is increased by one to reflect the new acceptance and the amount of the subsidy associated with the accepted offer is added to the field 1026 of the entry.
  • The sum of the number of offers indicated by the field 1022 for all entries is stored as the total number of offers 1004 for the corresponding record. Similarly, the number of offers accepted indicated by the field 1024 for all entries is stored as the total number of offers accepted 1006 for the corresponding record, and the sum of the amounts indicated by the field 1026 for all entries is stored as the total amount 1008 for the corresponding record. Once such information is stored for a subsidizing vendor, it may be retrieved upon reference to the appropriate subsidizing vendor identifier. Accordingly, information for, e.g., account reconciliation for each subsidizing vendor may be derived from such information.
  • Referring to FIG. 11, a table 1100 represents a record of another embodiment of the offer summary database 290 (FIG. 2). In the illustrated embodiment, information is organized by offer rule. In one embodiment, for each offer rule various types of customer activity may have been required. The results of each type of customer activity are summarized in the record.
  • Various types of customer activity may be required for an offer rule in order to test which customer activities are relatively successful in soliciting an acceptance of an offer. For example, every hour a different customer activity may be required in order for an offer to be provided in accordance with the offer rule. In such an embodiment, each hour the controller 110 (FIG. 1A) may update the customer activity field 824 of an entry of the offer rules database 270 to reflect the new customer activity that is required. The most successful customer activity requirement may then be used in the future.
  • The offer summary database 290 can include a plurality of records, each defining a summary of offers for subsidies that have been provided in response to a customer activity in accordance with the offer rule. The table 1100 includes an offer rule identifier 1102 that uniquely identifies the offer rule. The table 1100 also includes entries 1104, 1106 and 1108. Each entry defines offers provided in accordance with the offer rule and upon certain customer activity. Those skilled in the art will understand that the table 1100 may include any number of entries. The table 1100 also defines fields for each of the entries 1104, 1106 and 1108. The fields specify (i) customer activity 1120 required for the offer, (ii) a number 1122 of offers provided due to the particular customer activity for the offer rule, (iii) a number 1124 of these offers that were accepted, and (iv) an acceptance rate 1126 (the ratio of offers accepted to number of offers provided). If desirable, the information stored in the offer summary database 290 (FIG. 2) may be organized according to other information.
  • For each offer rule, the controller 110 in the embodiment of FIG. 1A, or the vendor server 160 in the embodiment of FIG. 1B, would create a record such as the record 1100 and store the offer rule identifier 1102. For each customer activity that was or is associated with the offer rule, a corresponding entry is created and an indication of the customer activity is stored in field 1120. For each entry in the record, the data specified by fields 1122, 1124 and 1126 may be adjusted as offers are provided and acceptances of the offers are received. For example, when an offer is provided in response to a particular customer activity, the corresponding entry is identified. The field 1122 of that entry is increased by one to reflect the newly-provided offer. Similarly, when an offer is accepted, field 1124 of that entry is increased by one to reflect the new acceptance and the acceptance rate is calculated and stored in the field 1126 of the entry. Once such information is stored for an offer rule, it may be retrieved upon reference to the appropriate offer rule identifier.
  • Referring to FIG. 12, a table 1200 represents an embodiment of the item database 340 (FIG. 3). The table 1200 includes entries 1202 and 1204, each defining an item sold via a vendor server. Those skilled in the art will understand that the table 1200 may include any number of entries. The table 1200 also defines fields for each of the entries 1202 and 1204. The fields specify (i) a item identifier 1220 that uniquely identifies the item, (ii) an item description 1222, (iii) an item price 1224 for which the item is typically sold, and (iv) an availability 1226 of the item which may be based on an inventory level of the item.
  • For each entry of the table 1200, the data specified by fields 1222, 1224 and 1226 may be received from the corresponding vendor. For example, the data may be provided when a vendor prepares to sell the item. Upon the entering of a new item, the vendor server would generate a unique customer identifier to store in the field 1220 of the entry corresponding to the new item. Once such information is stored for an item, it may be retrieved upon reference to the appropriate item identifier.
  • Referring to FIG. 13, a flow chart 1300 illustrates an embodiment of a method for providing an offer for a benefit (e.g. a reduced price) to a customer that is to purchase items from a vendor. Although the illustrated method is described below as being performed by the controller 110 in the embodiment of FIG. 1A, the illustrated method may alternatively be performed by the vendor server 160 in the embodiment of FIG. 1B.
  • Information relating to customer activity of a customer with a first vendor is received (step 1302). Such information may be received via a Web server, for example, in an embodiment where a vendor sells via the Internet. The Web server, which may be the vendor server, may receive data from the customer terminal that indicates, for example, hyperlinks that the customer clicks on, buttons that the customer actuates, or mouse movements of the customer terminal.
  • The information may be received from a “cookie” stored on the customer terminal (e.g. on a personal computer of the customer). Such a cookie is a block of data that a Web server (e.g. the vendor server) stores on a client system (e.g. a customer terminal). When a user returns to the same Web site, the browser of the customer terminal sends a copy of the cookie back to the Web server. Cookies may be used to identify users of the customer terminal, to instruct the Web server to send a customized version of a Web page, to submit account information for the user, and for other administrative purposes.
  • The information may be received via a telephone, for example, in an embodiment where a vendor sells via an IVRU. The information may also be received via a POS terminal, for example, in an embodiment where a vendor sells at a retail store. The POS terminal receives data such as UPC codes that identify items scanned with a bar code scanner, prices of those items, and information received from a customer's frequent shopper card. Similarly, the information may be received via a device, such as a PDA (Personal Digital Assistant) or a scanner mounted on a shopping cart, that the customer uses to indicate the items he has selected for purchase or the items in which he his otherwise interested.
  • The information may also be received via a sensor that senses the presence or location of a customer. For example, infrared or pressure sensors may be disposed in a store and operable to sense when a customer is near particular products or areas.
  • The information may also be received via a device that scans items with a bar code scanner and provides the prices of those items that are scanned. Such devices are known and are frequently disposed in supermarkets to allow customers to determine the prices of items, especially items that are on sale or otherwise subject to special pricing.
  • It is then determined whether an offer for a subsidy should be provided (step 1304). In one embodiment, the information relating to customer activity dictates whether the offer is provided. For example, as described in detail below there may be one or more rules specifying customer activity that is required. If an offer should not be provided, then the controller 110 interacts with the customer conventionally (step 1306).
  • Otherwise, an offer for a subsidy from a second vendor is determined (step 1308). For example, in an embodiment where one or more rules are included, if a rule is satisfied a corresponding offer for a subsidy is provided. An indication of the offer (or offers) is provided to the customer (step 1310). For example, text and/or images may be displayed on a Web page that is displayed on the customer terminal, text may be displayed on a monitor of a POS terminal, or an audio signal may be transmitted via an IVRU to a telephone.
  • The indication of the offer may be provided via a device, such as a PDA (Personal Digital Assistant) or a display mounted on a shopping cart of the customer, that accompanies the customer as he browses a store. Similarly, a display disposed in a particular location in the store (e.g. below a product display) may provide an offer to a customer that is near particular products or areas.
  • The indication of the offer may be provided via a device that scans items with a bar code scanner and provides the prices of those items scanned. In one embodiment, such a device could display an offer upon scanning the bar code of an item.
  • The offer typically specifies a subsidy amount and an obligation to fulfill in exchange for the subsidy. For example, an additional transaction may be required of the customer. In an embodiment where the second vendor provides services, the customer may be required to sign up for a service that is provided by the second vendor (e.g. initiate a service agreement with the second vendor). The customer may be required to switch from a current service provider to the second vendor, so that the service will no longer be provided by the current service provider.
  • Examples of services include telephone service, Internet service, banking services, credit card account services, insurance service, securities trading service, utilities service, satellite television service, or cable television service. Telephone service can include long distance service such as is provided by Sprint Communications Company, L.P or wireless service such as is provided by AT & T. Signing up for banking services may include the requirement to transfer a particular minimum balance to a new bank account. Signing up for credit card account services may similarly include the requirement to apply for a credit card account and/or transfer a particular minimum balance to a new or existing credit card account. Signing up for securities trading services may include the requirement to open an account with a particular minimum balance amount.
  • The controller 110 receives an indication of items the customer desires to purchase (step 1312). For example, the items may have been scanned by a bar code scanner and thus identified by a POS terminal. Alternatively, the items may have been selected by a customer via a Web page and put in a virtual “shopping cart”. Other ways to indicate items the customer desires to purchase will be apparent to those skilled in the art.
  • The controller 110 also receives a response to the offer from the customer terminal (step 1314). The customer may indicate his response by, for example, clicking a button on a Web page, actuating particular keys on a touch-tone telephone, actuating a button on a keypad in communication with a POS terminal, or verbally responding to a cashier that actuates buttons on the POS terminal.
  • If the response does not indicate an acceptance of the offer (step 1316), then the controller 110 interacts with the customer conventionally (step 1306). Otherwise, the offer is accepted and the customer is charged a lower price for the items than he otherwise would have been charged (step 1318). The customer may even get the items for free or receive a credit (e.g. money back or store credit). In another embodiment, the benefit to the customer may be different than a reduced price on the items he desires to purchase. For example, the customer may be given a product upgrade to another (higher value) item or the customer may be given an additional item at a discount or for free. The customer may also be provided with cash, store credit or other monetary award.
  • The customer may be charged the lower price in single transaction. For example, if an item is normally sold for $80, but is sold to a particular customer for $60 in connection with an offer for a subsidy, a credit card account of the customer may be charged $60 in one transaction. Alternatively, the customer's credit card account may be charged $80, and then subsequently credited for $20 ($20=$80−$60).
  • Referring to FIG. 14, a flow chart 1400 illustrates an embodiment of a method for providing an offer for a benefit to a customer that is to purchase items from a vendor. In particular, in the illustrated embodiment one or more rules determine which offers (if any) are provided to a customer. Although the illustrated method is described below as being performed by the controller 110 in the embodiment of FIG. 1A, the illustrated method may alternatively be performed by the vendor server 160 in the embodiment of FIG. 1B.
  • Information relating to customer activity of a customer with a first vendor is received (step 1402), as described above. The controller selects an offer rule to evaluate against the customer activity (step 1404). The rule may be defined by and selected from the offer rules database 270 (FIG. 2). For example, referring again to FIG. 8, each entry of the table 800 defines an offer rule. Accordingly, the controller 110 may select an entry of the offer rules database 270 (e.g. starting with the first entry).
  • As described above, each offer rule includes customer activity that is required in order for an offer to be provided. Accordingly, the received information relating to customer activity may be compared with the customer activity that is required by the offer rule (step 1406). If the customer activity does not satisfy the offer rule, then it is determined whether there are more offer rules that have not yet been so compared to the received information (step 1408). If there are not any more offer rules, then the controller 110 interacts conventionally with the customer (step 1410).
  • If there are more offer rules, then another offer rule is selected (step 1404). For example, the next entry in the offer rules database 270 may be selected. Those skilled in the art will realize that the offer rules need not be selected according to the sequence defined by the offer rules database 270.
  • If the customer activity does satisfy the offer rule, then the controller 110 determines if the offer rule is otherwise effective (step 1412). For example, referring to FIG. 8, each entry of the table 800 defines other requirements necessary in order to satisfy the offer rule (i.e. the field 828). If the rule is not otherwise effective (i.e. the other requirements are not satisfied), then it is determined whether there are more offer rules that have not yet been so compared to the received information (step 1408). If there are not any more offer rules, then the controller 110 interacts conventionally with the customer (step 1410). Otherwise, another offer rule is selected (step 1404).
  • If the offer rule is otherwise effective, then the controller 110 generates an offer (step 1414). The offer indicates the subsidy amount (specified by the field 826 of the corresponding entry) and an additional transaction required (specified by the field 830 of the corresponding entry). An indication of the offer is provided to the customer (step 1416), as described above. If there any more offer rules, then they are in turn selected and evaluated as described above.
  • The illustrated method allows one or more offers to be provided to a customer. The customer may in turn accept an offer as described above. In particular, if a plurality of offers are provided to the customer substantially simultaneously, the customer may be asked to select one (or more) of the plurality, and the selection would indicate an acceptance of the selected offer. Alternatively, if a plurality of offers are provided sequentially (i.e. another offer is provided if a prior offer is not accepted), then the sequence of the offers may be defined by, for example, the ranks of the corresponding subsidizing vendors.
  • Referring to FIGS. 15A and 15B, a flow chart 1500 illustrates an embodiment of a method for providing an offer for a benefit to a customer that is to purchase items from a vendor. In particular, in the illustrated embodiment a customer receives a subsidy subject to an obligation. The customer may receive an immediate benefit in exchange for participating or agreeing to participate in a transaction with the second vendor. For example, the customer may be required to participate in a future transaction with the second vendor. Although the illustrated method is described below as being performed by the controller 110 in the embodiment of FIG. 1A, the illustrated method may alternatively be performed by the vendor server 160 in the embodiment of FIG. 1B.
  • Information relating to customer activity of a customer with a first vendor is received (step 1502). It is then determined whether an offer for a subsidy should be provided (step 1504). If an offer should not be provided, then the controller 110 interacts with the customer conventionally (step 1506). Otherwise, an offer for a subsidy from a second vendor is determined (step 1508). For example, the information relating to customer activity may satisfy a rule, and the rule in turn specifies an offer. The controller 110 provides an indication of the offer (including its associated obligation) to the customer (step 1510).
  • The controller 110 receives an indication of items the customer desires to purchase (step 1512). The controller 110 also receives a credit card account identifier (step 1514), such as a credit card number. The credit card account identifier may be received, for example, via a credit card authorization terminal that is in communication with a POS terminal, as is known to those skilled in the art.
  • The credit card account is charged a lower price for the items than otherwise would have been charged (step 1516). The customer may even get the items for free. The controller 110 determines whether the customer has fulfilled the obligation of the offer (step 1518). For example, the obligation could be a requirement to sign up for a service provided by the second vendor. In such an embodiment, the second vendor may provide, for example, telephone service, Internet service, banking services, credit card account services, insurance service, securities trading service, satellite television service, or cable television service. The obligation may further include a requirement that the service be maintained for a particular amount of time.
  • In some embodiments, the customer may have been required to fulfill the obligation before his credit card account is charged. For example, the customer may have been required to fill out a credit card application before completing the purchase of his items. In other embodiments, the obligation may be need to be fulfilled at still other times.
  • The controller 110 can access a list of new or existing customers to determine whether the customer has fulfilled his obligation by signing up (and therefore becoming a new customer). The controller 110 could access such a list periodically (e.g. every week) or upon demand (e.g. the controller receives the names of new customers as they become available). Alternatively, the controller 110 could query the subsidizing vendor server, and in response receive a signal that indicates whether the customer had signed up for service from the second vendor. Similarly, the customer could be required to switch service providers from another service provider to the second vendor.
  • If the customer has fulfilled the obligation, then the controller 110 records the time and date the obligation was fulfilled (step 1520). The time and date may be stored, for example, in the field 938 of the entry corresponding to the offer. In such an embodiment, fulfilling the obligation may be considered acceptance of the offer.
  • If the customer has not fulfilled the obligation, then it is determined whether the offer has expired (step 1522). The expiration date and time of an offer is indicated by the field 930 of the offers database 280 (FIG. 2), and may be calculated based on the time the offer was provided. If the offer has expired without the obligation being fulfilled, the credit card account of the customer is charged for the difference between the item price and the lower price previously charged (step 1524). This step assesses a penalty against the customer by removing the benefit that was previously provided to the customer if the customer does not fulfill the obligation within the allotted time. For example, if the credit card account was previously charged $80 (in one or more transactions) in step 1516 for a $95 item, then in step 1524 the credit card account is charged $15 ($15=$95−$80). Thus, if the obligation is not fulfilled, the credit card account is charged $95 in total ($80 and $15), which is the conventional price for the item. An even larger amount may be charged (i.e. greater than $15 in the above example) if desired to deter customers from reneging on the obligation.
  • Referring to FIG. 16, a flow chart 1600 illustrates an embodiment of a method for determining whether customers have fulfilled their obligations associated with an offer for a benefit. Although the illustrated method is described below as being performed by the controller 110 in the embodiment of
  • FIG. 1A, the illustrated method may alternatively be performed by the vendor server 160 in the embodiment of FIG. 1B.
  • In the illustrated embodiment the obligation is to become a new customer of a subsidizing vendor. For example, the customer may have been obliged to initiate a new service agreement so that a particular service is provided to the customer by the subsidizing vendor. Those skilled in the art will understand the various modifications required in embodiments with other types of obligations.
  • The controller 110 selects a customer from a list of new customers (step 1602) of the subsidizing vendor. The list of new customers may be generated by the subsidizing vendor and transmitted to the controller 110 periodically (e.g. every week) or upon request. Such a list may be compiled by the subsidizing vendor as customers sign up for service and/or complete prerequisites for becoming a customer. Customers may be selected from the list, for example, in the order that they signed up during a predetermined period of time.
  • The controller 110 then determines if the selected customer has been offered a subsidy (step 1604). The controller may determine whether the selected customer is represented in any entry of the offers database 280. For example, referring again to FIG. 9, each entry of the table 900 includes in field 922 an indication of the transaction during which the offer was provided. The corresponding entry of the transaction database 250 in turn indicates a customer identifier (e.g. the field 632 of the table 600). If the selected customer has not been offered a subsidy, then the controller 110 determines whether there are more customers that have not yet been selected (step 1610). Another customer is selected (step 1602) as long as there are more customers in the list that have not been selected.
  • If the selected customer has been offered a subsidy, the controller 110 determines if the offer for the subsidy included an obligation to become a customer of the subsidizing vendor (step 1606). For example, referring again to FIG. 9, each entry of the table 900 includes in field 926 an indication of the offer rule applied during the transaction. The corresponding entry of the offer rules database 270 in turn indicates an additional transaction required of the customer (e.g. in the field 830 of the table 800). Thus, the controller 110 determines whether the presence of the selected customer on the list of new customers indicates fulfillment of a previous obligation.
  • If the offer for the subsidy included an obligation to become a customer of the subsidizing vendor, then the controller 110 records that the selected customer has fulfilled his obligation (step 1608). For example, the time and date that the customer became a new customer of the subsidizing vendor may be recorded in the field 938 of the corresponding entry of the table 900. Then additional customers, if any, are selected and processed similarly (e.g., steps 1610 and 1602). Customers that have not fulfilled their respective obligations may eventually be penalized in some manner, for example, by charging their credit card accounts a penalty fee amount.
  • In contrast to the above-described method, the controller 100 could search a list of customers that have accepted offers, rather than a list of new customers, in order to determine whether those customers have become new customers of the specified vendor.
  • Referring to FIG. 17, a flow chart 1700 illustrates an embodiment of a method for providing an offer for a benefit after a customer has made a purchase from a first vendor. Although the illustrated method is described below as being performed by the controller 110 in the embodiment of FIG. 1A, the illustrated method may alternatively be performed by the vendor server 160 in the embodiment of FIG. 1B.
  • The controller 110 selects a customer from the list of customers that have purchased from the first vendor (step 1702). For example, as is known in the art the first vendor may record the name, address, telephone number and/or e-mail address of each customer that purchases items within a predetermined time period (e.g. each month). The customer selected from the list may be, for example, the first customer that purchased items during a predetermined period of time. When a customer makes a purchase, the vendor server may determine if contact information of the customer is stored. For example, the vendor server may determine whether the customer is a member of a frequent shopper program (in which contact information is typically obtained upon registration). Alternatively, it may be determined whether the customer filled in a form on a Web page that requests contact information. If contact information of the customer is not stored, the vendor server can then request contact information of the customer, and wait for the customer to provide that contact information.
  • The controller then determines whether the selected customer should be provided an offer for a subsidy (step 1704) from a second vendor, as described above. If the customer should not be provided with an offer for a subsidy, then the controller determines whether there are more customers on the list (step 1708). If so, then another customer is selected (step 1702).
  • If the customer should be provided with an offer for a subsidy, then the controller 110 provides an indication of the offer for a subsidy to the selected customer using contact information of the customer (step 1706). The indication of an offer may be provided, for example, via e-mail, postal mail, and/or telephone. For example, the controller 110 may generate a textual message specifying the offer, and then transmit that message via e-mail to an e-mail address of the customer. The controller 110 may also generate a textual message which is printed onto a sheet of paper, and a postal mail address which is printed onto a mailing label. The mailing label is used in directing the sheet of paper to the customer via conventional postal mail. For example, the offer may be provided on a credit card billing statement of the customer. The controller 110 may also generate an audio message which is transmitted via a telephone to the customer by connecting to the appropriate telephone number.
  • Although the present invention has been described with respect to a preferred embodiment thereof, those skilled in the art will note that various substitutions may be made to those embodiments described herein without departing from the spirit and scope of the present invention. For example, although in many of the described embodiments above the benefit provided to the customer is a subsidy, there are many other types of benefits which are contemplated by the present invention.

Claims (18)

1. A method comprising:
receiving, by a controller device, an indication that a customer accepts an offer from a second vendor for a subsidy of a purchase, at a reduced price, of at least one item from a first vendor, the at least one item having an associated total price, and the offer defining an obligation for the customer to fulfill after purchasing the at least one item, the obligation being in addition to payment of the reduced price;
after receiving the indication of the acceptance of the offer, charging the reduced price for the at least one item to a credit card account of the customer;
determining, by the controller device, an expiration date of the offer by which the obligation must be fulfilled by the customer;
determining, by the controller device, that the customer did not fulfill the obligation before the expiration date; and
in response to determining that the customer did not fulfill the obligation before the expiration date, charging by the controller device to the credit card account of the customer at least the difference between the total price and the reduced price.
2. The method of claim 1, in which determining that the customer did not fulfill the obligation before the expiration date comprises:
receiving an indication that the customer did not initiate a new service agreement with the second vendor for a service.
3. The method of claim 2, in which the service comprises at least one of:
telephone service,
Internet service,
banking services,
credit card account service,
insurance service,
securities trading service,
satellite television service, and
cable television service.
4. The method of claim 1, in which determining that the customer did not fulfill the obligation before the expiration date comprises:
receiving an indication that the customer returned at least one of the at least one item to the first vendor.
5. The method of claim 1, further comprising:
receiving customer information from the customer; and
in which the step of determining that the customer did not fulfill the obligation before the expiration date comprises:
determining that the customer information is not accurate.
6. The method of claim 1,
in which the obligation includes a requirement that the customer make an additional purchase from the second vendor before the expiration date; and
in which determining that the customer did not fulfill the obligation before the expiration date comprises:
receiving an indication that the customer did not make an additional purchase from the second vendor before the expiration date.
7. A data storage device storing instructions configured to direct a controller device to perform a method, the method comprising:
receiving, by a controller device, an indication that a customer accepts an offer from a second vendor for a subsidy of a purchase, at a reduced price, of at least one item from a first vendor, the at least one item having an associated total price, and the offer defining an obligation for the customer to fulfill after purchasing the at least one item, the obligation being in addition to payment of the reduced price;
after receiving the indication of the acceptance of the offer, charging the reduced price for the at least one item to a credit card account of the customer;
determining, by the controller device, an expiration date of the offer by which the obligation must be fulfilled by the customer;
determining, by the controller device, that the customer did not fulfill the obligation before the expiration date; and
in response to determining that the customer did not fulfill the obligation before the expiration date, charging by the controller device to the credit card account of the customer at least the difference between the total price and the reduced price.
8. The data storage device of claim 7, in which determining that the customer did not fulfill the obligation before the expiration date comprises:
receiving an indication that the customer did not initiate a new service agreement with the second vendor for a service.
9. The data storage device of claim 8, in which the service comprises at least one of:
telephone service,
Internet service,
banking services,
credit card account service,
insurance service,
securities trading service,
satellite television service, and
cable television service.
10. The data storage device of claim 7, in which determining that the customer did not fulfill the obligation before the expiration date comprises:
receiving an indication that the customer returned at least one of the at least one item to the first vendor.
11. The data storage device of claim 7, the instructions being configured further to direct the controller device to perform:
receiving customer information from the customer; and
in which determining that the customer did not fulfill the obligation before the expiration date comprises:
determining that the customer information is not accurate.
12. The data storage device of claim 7,
in which the obligation includes a requirement that the customer make an additional purchase from the second vendor before the expiration date; and
in which determining that the customer did not fulfill the obligation before the expiration date comprises:
receiving an indication that the customer did not make an additional purchase from the second vendor before the expiration date.
13. An apparatus comprising:
a processor; and
a data storage device in communication with the processor, the data storage device storing instructions configured to direct the processor to perform a method, the method comprising:
receiving an indication that a customer accepts an offer from a second vendor for a subsidy of a purchase, at a reduced price, of at least one item from a first vendor, the at least one item having an associated total price, and the offer defining an obligation for the customer to fulfill after purchasing the at least one item, the obligation being in addition to payment of the reduced price;
after receiving the indication of the acceptance of the offer, charging the reduced price for the at least one item to a credit card account of the customer;
determining an expiration date of the offer by which the obligation must be fulfilled by the customer;
determining that the customer did not fulfill the obligation before the expiration date; and
in response to determining that the customer did not fulfill the obligation before the expiration date, charging to the credit card account of the customer at least the difference between the total price and the reduced price.
14. The apparatus of claim 13, in which determining that the customer did not fulfill the obligation before the expiration date comprises:
receiving an indication that the customer did not initiate a new service agreement with the second vendor for a service.
15. The data storage device of claim 14, in which the service comprises at least one of:
telephone service,
Internet service,
banking services,
credit card account service,
insurance service,
securities trading service,
satellite television service, and
cable television service.
16. The apparatus of claim 13, in which determining that the customer did not fulfill the obligation before the expiration date comprises:
receiving an indication that the customer returned at least one of the at least one item to the first vendor.
17. The apparatus of claim 13, the instructions being configured further to direct the processor to perform:
receiving customer information from the customer; and
in which determining that the customer did not fulfill the obligation before the expiration date comprises:
determining that the customer information is not accurate.
18. The apparatus of claim 13,
in which the obligation includes a requirement that the customer make an additional purchase from the second vendor before the expiration date; and
in which determining that the customer did not fulfill the obligation before the expiration date comprises:
receiving an indication that the customer did not make an additional purchase from the second vendor before the expiration date.
US12/938,046 1998-10-05 2010-11-02 Method and apparatus for providing cross-benefits based on a customer activity Expired - Fee Related US8700456B2 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US12/938,046 US8700456B2 (en) 1998-10-05 2010-11-02 Method and apparatus for providing cross-benefits based on a customer activity
US14/251,746 US9697553B2 (en) 1998-10-05 2014-04-14 Method and apparatus for providing cross-benefits based on a customer activity

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US16636798A 1998-10-05 1998-10-05
US09/219,267 US7831470B1 (en) 1996-09-04 1998-12-23 Method and apparatus for facilitating electronic commerce through providing cross-benefits during a transaction
US09/274,281 US7818284B1 (en) 1996-09-04 1999-03-22 Method and apparatus for providing cross-benefits via a central authority
US09/282,747 US7827057B1 (en) 1998-10-05 1999-03-31 Method and apparatus for providing cross-benefits based on a customer activity
US12/938,046 US8700456B2 (en) 1998-10-05 2010-11-02 Method and apparatus for providing cross-benefits based on a customer activity

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/282,747 Continuation US7827057B1 (en) 1998-10-05 1999-03-31 Method and apparatus for providing cross-benefits based on a customer activity

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/251,746 Continuation US9697553B2 (en) 1998-10-05 2014-04-14 Method and apparatus for providing cross-benefits based on a customer activity

Publications (2)

Publication Number Publication Date
US20110047022A1 true US20110047022A1 (en) 2011-02-24
US8700456B2 US8700456B2 (en) 2014-04-15

Family

ID=43016024

Family Applications (3)

Application Number Title Priority Date Filing Date
US09/282,747 Expired - Fee Related US7827057B1 (en) 1998-10-05 1999-03-31 Method and apparatus for providing cross-benefits based on a customer activity
US12/938,046 Expired - Fee Related US8700456B2 (en) 1998-10-05 2010-11-02 Method and apparatus for providing cross-benefits based on a customer activity
US14/251,746 Expired - Fee Related US9697553B2 (en) 1998-10-05 2014-04-14 Method and apparatus for providing cross-benefits based on a customer activity

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/282,747 Expired - Fee Related US7827057B1 (en) 1998-10-05 1999-03-31 Method and apparatus for providing cross-benefits based on a customer activity

Family Applications After (1)

Application Number Title Priority Date Filing Date
US14/251,746 Expired - Fee Related US9697553B2 (en) 1998-10-05 2014-04-14 Method and apparatus for providing cross-benefits based on a customer activity

Country Status (1)

Country Link
US (3) US7827057B1 (en)

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8694389B1 (en) 2002-08-27 2014-04-08 Formula Labs, Llc System for optimization of business transactions between a selling vendor and a shipping vendor
US9124957B1 (en) * 2011-02-07 2015-09-01 Christopher Fogel System and method for dynamic multifactor routing
US9760854B1 (en) 2012-05-21 2017-09-12 Formula Labs, Llc System and method for identifying and co-ordinating an alternate delivery of one or more selected items
US20170282736A1 (en) * 2016-04-01 2017-10-05 Ijuze Corporation Pte Ltd. Automated system for managing and providing a network of charging stations
US10318569B1 (en) 2017-12-29 2019-06-11 Square, Inc. Smart inventory tags
US10339548B1 (en) 2014-03-24 2019-07-02 Square, Inc. Determining pricing information from merchant data
US10467583B1 (en) 2015-10-30 2019-11-05 Square, Inc. Instance-based inventory services
US10878394B1 (en) 2018-11-29 2020-12-29 Square, Inc. Intelligent inventory recommendations
US10909486B1 (en) 2015-07-15 2021-02-02 Square, Inc. Inventory processing using merchant-based distributed warehousing
US10949796B1 (en) 2015-07-15 2021-03-16 Square, Inc. Coordination of inventory ordering across merchants
US20210080282A1 (en) * 2017-04-03 2021-03-18 Power Hero Corp. Universal automated system for identifying, registering and verifying the existence, location and characteristics of electric and other power outlets by random users and for retrieval and utilization of such parametric data and outlets by all users
US11017369B1 (en) 2015-04-29 2021-05-25 Square, Inc. Cloud-based inventory and discount pricing management system
US20230274346A1 (en) * 2008-10-02 2023-08-31 Ecoatm, Llc Kiosks for evaluating and purchasing used electronic devices and related technology
US11805207B2 (en) 2020-08-28 2023-10-31 Intermetro Communications, Inc. Systems and methods for configuring and dynamically applying call route groups
US11861579B1 (en) 2018-07-31 2024-01-02 Block, Inc. Intelligent inventory system

Families Citing this family (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7539628B2 (en) * 2000-03-21 2009-05-26 Bennett James D Online purchasing system supporting buyer affordability screening
US6876991B1 (en) 1999-11-08 2005-04-05 Collaborative Decision Platforms, Llc. System, method and computer program product for a collaborative decision platform
US20020198994A1 (en) * 2001-05-15 2002-12-26 Charles Patton Method and system for enabling and controlling communication topology, access to resources, and document flow in a distributed networking environment
US9064281B2 (en) 2002-10-31 2015-06-23 Mastercard Mobile Transactions Solutions, Inc. Multi-panel user interface
US20130332343A1 (en) 2005-10-06 2013-12-12 C-Sam, Inc. Multi-tiered, secure mobile transactions ecosystem enabling platform comprising a personalization tier, a service tier, and an enabling tier
US10032160B2 (en) 2005-10-06 2018-07-24 Mastercard Mobile Transactions Solutions, Inc. Isolating distinct service provider widgets within a wallet container
WO2007044500A2 (en) 2005-10-06 2007-04-19 C-Sam, Inc. Transactional services
US7703673B2 (en) 2006-05-25 2010-04-27 Buchheit Brian K Web based conversion of non-negotiable credits associated with an entity to entity independent negotiable funds
US8668146B1 (en) 2006-05-25 2014-03-11 Sean I. Mcghie Rewards program with payment artifact permitting conversion/transfer of non-negotiable credits to entity independent funds
US9704174B1 (en) 2006-05-25 2017-07-11 Sean I. Mcghie Conversion of loyalty program points to commerce partner points per terms of a mutual agreement
US8684265B1 (en) 2006-05-25 2014-04-01 Sean I. Mcghie Rewards program website permitting conversion/transfer of non-negotiable credits to entity independent funds
US8162209B2 (en) 2006-05-25 2012-04-24 Buchheit Brian K Storefront purchases utilizing non-negotiable credits earned from a game of chance
US10062062B1 (en) 2006-05-25 2018-08-28 Jbshbm, Llc Automated teller machine (ATM) providing money for loyalty points
US8342399B1 (en) 2006-05-25 2013-01-01 Mcghie Sean I Conversion of credits to funds
US8376224B2 (en) 2006-05-25 2013-02-19 Sean I. Mcghie Self-service stations for utilizing non-negotiable credits earned from a game of chance
US9076158B2 (en) * 2006-09-13 2015-07-07 Google Inc. Integrated system and method for managing electronic coupons
CN101247247B (en) * 2007-02-15 2012-06-27 华为技术有限公司 Method, system and server for propagating advertisement through presentation information
US10810619B1 (en) * 2007-10-15 2020-10-20 James William Clouse Method for internet marketing
US20090125442A1 (en) * 2007-11-09 2009-05-14 Jonathan Otto Wireless communications device configured for automated returns
US8180702B2 (en) * 2008-08-24 2012-05-15 Visa U.S.A. Inc. Transactional processing entity device support of an integrated offer network
US20120246064A1 (en) * 2011-03-23 2012-09-27 Ebay, Inc. Customer refunds using payment service providers
US10366085B2 (en) 2011-05-19 2019-07-30 Lead Intelligence, Inc. System, method, and computer program for audit scoring
US9495659B2 (en) * 2011-05-19 2016-11-15 Ross Shanken Apparatus, method, and a computer program for a form identification number
BR112014008941A2 (en) 2011-10-12 2017-05-02 C-Sam Inc platform that enables secure multilayer mobile transactions
JP6220556B2 (en) * 2013-05-28 2017-10-25 アズビル株式会社 Power suppression planning apparatus and method
US11461766B1 (en) 2014-04-30 2022-10-04 Wells Fargo Bank, N.A. Mobile wallet using tokenized card systems and methods
US10997592B1 (en) 2014-04-30 2021-05-04 Wells Fargo Bank, N.A. Mobile wallet account balance systems and methods
US11288660B1 (en) 2014-04-30 2022-03-29 Wells Fargo Bank, N.A. Mobile wallet account balance systems and methods
US11748736B1 (en) 2014-04-30 2023-09-05 Wells Fargo Bank, N.A. Mobile wallet integration within mobile banking
US11615401B1 (en) 2014-04-30 2023-03-28 Wells Fargo Bank, N.A. Mobile wallet authentication systems and methods
US11610197B1 (en) 2014-04-30 2023-03-21 Wells Fargo Bank, N.A. Mobile wallet rewards redemption systems and methods
US9652770B1 (en) 2014-04-30 2017-05-16 Wells Fargo Bank, N.A. Mobile wallet using tokenized card systems and methods
US9734670B2 (en) 2014-07-21 2017-08-15 Sam Johnson Providing a secondary service for a client application which is associated with a primary service
US10445739B1 (en) 2014-08-14 2019-10-15 Wells Fargo Bank, N.A. Use limitations for secondary users of financial accounts
US10068244B2 (en) 2014-08-25 2018-09-04 Capital One Services, Llc Systems and methods for suggesting financial account cards stored on a wireless device
US11853919B1 (en) 2015-03-04 2023-12-26 Wells Fargo Bank, N.A. Systems and methods for peer-to-peer funds requests
US20170286994A1 (en) * 2016-03-29 2017-10-05 SETA International LLC Power buy system
US10438197B2 (en) * 2016-04-13 2019-10-08 Paypal, Inc. Public ledger authentication system
US11182778B2 (en) 2016-05-26 2021-11-23 Visa International Service Association Platform for offer determination and presentation via internet of things
US11468414B1 (en) 2016-10-03 2022-10-11 Wells Fargo Bank, N.A. Systems and methods for establishing a pull payment relationship
US9973635B1 (en) * 2016-11-17 2018-05-15 Spotify Ab System and method for processing of a service subscription using a telecommunications operator
US11055653B2 (en) * 2017-03-06 2021-07-06 United States Postal Service System and method of providing informed delivery items using a hybrid-digital mailbox
US11295297B1 (en) 2018-02-26 2022-04-05 Wells Fargo Bank, N.A. Systems and methods for pushing usable objects and third-party provisioning to a mobile wallet
US11775955B1 (en) 2018-05-10 2023-10-03 Wells Fargo Bank, N.A. Systems and methods for making person-to-person payments via mobile client application

Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4718009A (en) * 1984-02-27 1988-01-05 Default Proof Credit Card System, Inc. Default proof credit card method system
US5434394A (en) * 1992-09-10 1995-07-18 Tandy Corporation Automated order and delivery system
US5515270A (en) * 1991-07-22 1996-05-07 Weinblatt; Lee S. Technique for correlating purchasing behavior of a consumer to advertisements
US5537314A (en) * 1994-04-18 1996-07-16 First Marketrust Intl. Referral recognition system for an incentive award program
US5619558A (en) * 1995-11-13 1997-04-08 Ncr Corporation ATM segment of one marketing method
US5636346A (en) * 1994-05-09 1997-06-03 The Electronic Address, Inc. Method and system for selectively targeting advertisements and programming
US5721827A (en) * 1996-10-02 1998-02-24 James Logan System for electrically distributing personalized information
US5734890A (en) * 1994-09-12 1998-03-31 Gartner Group System and method for analyzing procurement decisions and customer satisfaction
US5826240A (en) * 1996-01-18 1998-10-20 Rosefaire Development, Ltd. Sales presentation system for coaching sellers to describe specific features and benefits of a product or service based on input from a prospect
US5839117A (en) * 1994-08-19 1998-11-17 Andersen Consulting Llp Computerized event-driven routing system and method for use in an order entry system
US5852811A (en) * 1987-04-15 1998-12-22 Proprietary Financial Products, Inc. Method for managing financial accounts by a preferred allocation of funds among accounts
US5925865A (en) * 1994-07-11 1999-07-20 Steger; Paul Automated check verification and tracking system
US5974399A (en) * 1997-08-29 1999-10-26 Catalina Marketing International, Inc. Method and apparatus for generating purchase incentives based on price differentials
US6055513A (en) * 1998-03-11 2000-04-25 Telebuyer, Llc Methods and apparatus for intelligent selection of goods and services in telephonic and electronic commerce
US6289318B1 (en) * 1998-03-24 2001-09-11 Timothy P. Barber Method and architecture for multi-level commissioned advertising on a computer network

Family Cites Families (234)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3573747A (en) 1969-02-24 1971-04-06 Institutional Networks Corp Instinet communication system for effectuating the sale or exchange of fungible properties between subscribers
US4108361A (en) 1976-10-12 1978-08-22 Krause Stephen R Universal mark sense betting terminal system and method
FR2435270A1 (en) 1978-08-16 1980-04-04 Etude Systemes Avances Amenage ASSEMBLY IN PARTICULAR FOR TAKING ON THE CHALLENGES AND POSSIBLY THE DETERMINATION OF THE WINNERS IN A GAME SUCH AS A NATIONAL LOTTO GAME
US4247759A (en) 1978-10-10 1981-01-27 Cubic Western Data Self-service passenger ticketing system
US4689742A (en) 1980-12-11 1987-08-25 Seymour Troy Automatic lottery system
US4494197A (en) 1980-12-11 1985-01-15 Seymour Troy Automatic lottery system
US4500880A (en) 1981-07-06 1985-02-19 Motorola, Inc. Real time, computer-driven retail pricing display system
US4449186A (en) 1981-10-15 1984-05-15 Cubic Western Data Touch panel passenger self-ticketing system
US4484733A (en) 1982-04-05 1984-11-27 Hall Systems, Inc. Programmable packaging grid including gripper conveyor monitoring system
US4491725A (en) 1982-09-29 1985-01-01 Pritchard Lawrence E Medical insurance verification and processing system
EP0109189A1 (en) 1982-10-14 1984-05-23 ByVideo, Inc. Video display system for marketing items
US4547851A (en) 1983-03-14 1985-10-15 Kurland Lawrence G Integrated interactive restaurant communication method for food and entertainment processing
US4903201A (en) 1983-11-03 1990-02-20 World Energy Exchange Corporation Automated futures trading exchange
US4667292A (en) 1984-02-16 1987-05-19 Iameter Incorporated Medical reimbursement computer system
US5309355A (en) 1984-05-24 1994-05-03 Lockwood Lawrence B Automated sales system
US4723212A (en) 1984-07-18 1988-02-02 Catalina Marketing Corp. Method and apparatus for dispensing discount coupons
US4910672A (en) 1984-07-18 1990-03-20 Catalina Marketing Corporation Method and apparatus for dispensing discount coupons
US5173851A (en) 1984-07-18 1992-12-22 Catalina Marketing International, Inc. Method and apparatus for dispensing discount coupons in response to the purchase of one or more products
US4669730A (en) 1984-11-05 1987-06-02 Small Maynard E Automated sweepstakes-type game
US4815741A (en) 1984-11-05 1989-03-28 Small Maynard E Automated marketing and gaming systems
US4677553A (en) 1984-11-09 1987-06-30 International Totalizator Systems, Inc. Secure placement of confidential information on a circulated blank ticket
US4882675A (en) 1984-11-26 1989-11-21 Steven Nichtberger Paperless system for distributing, redeeming and clearing merchandise coupons
JPH0743748B2 (en) 1986-02-17 1995-05-15 株式会社オークネット Information transmission processing method of auction information transmission processing system
US5759101A (en) 1986-03-10 1998-06-02 Response Reward Systems L.C. Central and remote evaluation of responses of participatory broadcast audience with automatic crediting and couponing
US4876592A (en) 1986-03-10 1989-10-24 Henry Von Kohorn System for merchandising and the evaluation of responses to broadcast transmissions
US4760247A (en) 1986-04-04 1988-07-26 Bally Manufacturing Company Optical card reader utilizing area image processing
US4833308A (en) 1986-07-24 1989-05-23 Advance Promotion Technologies, Inc. Checkout counter product promotion system and method
USRE34380E (en) 1986-09-05 1993-09-14 Method and apparatus for applying messages in a telecommunications network
US4799156A (en) 1986-10-01 1989-01-17 Strategic Processing Corporation Interactive market management system
US4750119A (en) 1986-10-10 1988-06-07 Tradevest, Inc. Purchasing system with rebate feature
JPH0789394B2 (en) 1986-11-14 1995-09-27 オムロン株式会社 POS terminal device
US4751728A (en) 1987-03-27 1988-06-14 Treat John M Telephone call monitoring, metering and selection device
US4854590A (en) 1987-05-08 1989-08-08 Continental Brokers And Consultants, Inc. Cash register gaming device
US5025372A (en) 1987-09-17 1991-06-18 Meridian Enterprises, Inc. System and method for administration of incentive award program through use of credit
US4882473A (en) 1987-09-18 1989-11-21 Gtech Corporation On-line wagering system with programmable game entry cards and operator security cards
US4973952A (en) 1987-09-21 1990-11-27 Information Resources, Inc. Shopping cart display system
US5189607A (en) 1987-10-31 1993-02-23 Sharp Kabushiki Kaisha Method for sending selected data from electronic cash registers to a host unit
US4839507A (en) 1987-11-06 1989-06-13 Lance May Method and arrangement for validating coupons
US4982337A (en) 1987-12-03 1991-01-01 Burr Robert L System for distributing lottery tickets
US5021953A (en) 1988-01-06 1991-06-04 Travelmation Corporation Trip planner optimizing travel itinerary selection conforming to individualized travel policies
US5172328A (en) 1988-04-01 1992-12-15 Restaurant Technology, Inc. Food preparation system and method
US5003384A (en) 1988-04-01 1991-03-26 Scientific Atlanta, Inc. Set-top interface transactions in an impulse pay per view television system
US5132914A (en) 1988-04-01 1992-07-21 Restaurant Technology, Inc. Food preparation system and method
US4922522A (en) 1988-06-07 1990-05-01 American Telephone And Telegraph Company Telecommunications access to lottery systems
US4908761A (en) 1988-09-16 1990-03-13 Innovare Resourceful Marketing Group, Inc. System for identifying heavy product purchasers who regularly use manufacturers' purchase incentives and predicting consumer promotional behavior response patterns
US4902880A (en) 1988-09-30 1990-02-20 Peripheral Dynamics, Inc. Card reader system and method with printing and verification capability
US5200889A (en) 1988-10-31 1993-04-06 Teraoka Seiko Co., Ltd. System for maintaining continuous total of refund amounts due a customer and for allowing customer designation of the amount of refund to be applied to a purchase
US4982346A (en) 1988-12-16 1991-01-01 Expertel Communications Incorporated Mall promotion network apparatus and method
US5202826A (en) 1989-01-27 1993-04-13 Mccarthy Patrick D Centralized consumer cash value accumulation system for multiple merchants
US5621812A (en) 1989-05-01 1997-04-15 Credit Verification Corporation Method and system for building a database for use with selective incentive marketing in response to customer shopping histories
US5644723A (en) 1989-05-01 1997-07-01 Credit Verification Corporation Method and system for selective incentive point-of-sale marketing in response to customer shopping histories
US5687322A (en) 1989-05-01 1997-11-11 Credit Verification Corporation Method and system for selective incentive point-of-sale marketing in response to customer shopping histories
US5201010A (en) 1989-05-01 1993-04-06 Credit Verification Corporation Method and system for building a database and performing marketing based upon prior shopping history
US4937853A (en) 1989-05-03 1990-06-26 Agt International, Inc. Lottery agent data communication/telephone line interface
US5572653A (en) 1989-05-16 1996-11-05 Rest Manufacturing, Inc. Remote electronic information display system for retail facility
US5168446A (en) 1989-05-23 1992-12-01 Telerate Systems Incorporated System for conducting and processing spot commodity transactions
US5136501A (en) 1989-05-26 1992-08-04 Reuters Limited Anonymous matching system
US5101200A (en) * 1989-06-09 1992-03-31 Swett Paul H Fast lane credit card
US5353219A (en) 1989-06-28 1994-10-04 Management Information Support, Inc. Suggestive selling in a customer self-ordering system
US5128862A (en) 1989-06-28 1992-07-07 Management Information Support, Inc. Customer operable system for a retail store or fast-food restaurant having plural ordering stations
US5056019A (en) 1989-08-29 1991-10-08 Citicorp Pos Information Servies, Inc. Automated purchase reward accounting system and method
US5060165A (en) 1989-10-03 1991-10-22 Pitney Bowes Inc. Optimizing mail processing by matching publisher and printer entities
US5404291A (en) 1989-11-20 1995-04-04 Hyatt Corp. Inventory control process for reservation systems
US5119295A (en) 1990-01-25 1992-06-02 Telecredit, Inc. Centralized lottery system for remote monitoring or operations and status data from lottery terminals including detection of malfunction and counterfeit units
FR2658645B1 (en) 1990-02-16 1994-10-07 Sitour Electronic Systems INSTALLATION COMPRISING A SET OF REMOTE CONTROL DISPLAY MODULES.
US5297031A (en) 1990-03-06 1994-03-22 Chicago Board Of Trade Method and apparatus for order management by market brokers
US5216595A (en) 1990-03-20 1993-06-01 Ncr Corporation System and method for integration of lottery terminals into point of sale systems
US4993714A (en) 1990-03-27 1991-02-19 Golightly Cecelia K Point of sale lottery system
US5262941A (en) 1990-03-30 1993-11-16 Itt Corporation Expert credit recommendation method and system
US5231569A (en) 1990-06-12 1993-07-27 Sears Payment Systems, Inc. Account transaction system
US5192854A (en) 1990-07-26 1993-03-09 Counts Reginald D System for electronically recording and redeeming coupons
JP3031971B2 (en) 1990-07-31 2000-04-10 株式会社東芝 Terminal device of product sales system
US5361199A (en) 1990-07-31 1994-11-01 Texas Instruments Incorporated Automated procurement system with multi-system data access
US5136647A (en) 1990-08-02 1992-08-04 Bell Communications Research, Inc. Method for secure time-stamping of digital documents
US5319542A (en) 1990-09-27 1994-06-07 International Business Machines Corporation System for ordering items using an electronic catalogue
US5243515A (en) 1990-10-30 1993-09-07 Lee Wayne M Secure teleprocessing bidding system
US5177342A (en) 1990-11-09 1993-01-05 Visa International Service Association Transaction approval system
US5794220A (en) 1990-11-13 1998-08-11 Medcom Solutions, Inc. Method and means for ranking and pricing items
US5191613A (en) 1990-11-16 1993-03-02 Graziano James M Knowledge based system for document authentication
US5245533A (en) 1990-12-18 1993-09-14 A. C. Nielsen Company Marketing research method and system for management of manufacturer's discount coupon offers
US5224034A (en) 1990-12-21 1993-06-29 Bell Communications Research, Inc. Automated system for generating procurement lists
US5274547A (en) 1991-01-03 1993-12-28 Credco Of Washington, Inc. System for generating and transmitting credit reports
CA2059078C (en) 1991-02-27 1995-10-03 Alexander G. Fraser Mediation of transactions by a communications system
EP0574529A1 (en) 1991-03-05 1993-12-22 The Gift Certificate Center, Inc. Method and apparatus for generating gift certificates
US5223698A (en) 1991-04-05 1993-06-29 Telecredit, Inc. Card-activated point-of-sale lottery terminal
US5239165A (en) 1991-04-11 1993-08-24 Spectra-Physics Scanning Systems, Inc. Bar code lottery ticket handling system
US5832457A (en) 1991-05-06 1998-11-03 Catalina Marketing International, Inc. Method and apparatus for selective distribution of discount coupons based on prior customer behavior
CA2066056A1 (en) 1991-05-08 1992-11-09 Robert H. Savin System for tracking redemption of consumer discount coupons
US5510979A (en) 1991-07-30 1996-04-23 Restaurant Technology, Inc. Data processing system and method for retail stores
US5426281A (en) 1991-08-22 1995-06-20 Abecassis; Max Transaction protection system
US5333186A (en) 1991-09-05 1994-07-26 At&T Bell Laboratories Telecommunication call billing method and apparatus
US5256863A (en) 1991-11-05 1993-10-26 Comark Technologies, Inc. In-store universal control system
US5557518A (en) 1994-04-28 1996-09-17 Citibank, N.A. Trusted agents for open electronic commerce
AU3238793A (en) 1991-12-12 1993-07-19 Cellular Technical Services Company, Inc. Real-time information system for cellular telephones
US5467269A (en) 1991-12-20 1995-11-14 J. B. Laughrey, Inc. Method and means for telephonically crediting customers with rebates and refunds
US5297026A (en) 1992-01-03 1994-03-22 Frank Hoffman System for promoting account activity
US5283731A (en) 1992-01-19 1994-02-01 Ec Corporation Computer-based classified ad system and method
US5315093A (en) 1992-02-05 1994-05-24 A. C. Nielsen Company Market research method and system for collecting retail store market research data
JPH05257950A (en) 1992-03-12 1993-10-08 Nec Software Kansai Ltd Customer master updating system
US5305195A (en) 1992-03-25 1994-04-19 Gerald Singer Interactive advertising system for on-line terminals
US5655089A (en) 1992-04-10 1997-08-05 Bucci; Joseph J. Method for the consolidation summarization and transmission of a plurality of mailable materials
GB9211648D0 (en) 1992-06-02 1992-07-15 Racal Datacom Ltd Data communication system
AU4843393A (en) 1992-09-04 1994-03-29 Coinstar, Inc. Coupon/voucher dispensing machine and method
US5620079A (en) 1992-09-04 1997-04-15 Coinstar, Inc. Coin counter/sorter and coupon/voucher dispensing machine and method
US6076068A (en) 1992-09-17 2000-06-13 Ad Response Micromarketing Corporation Coupon delivery system
US5353218A (en) 1992-09-17 1994-10-04 Ad Response Micromarketing Corporation Focused coupon system
EP0692119A1 (en) 1992-10-22 1996-01-17 American Express Travel Related Services Company, Inc. Automated billing consolidation system and method
US5794219A (en) 1996-02-20 1998-08-11 Health Hero Network, Inc. Method of conducting an on-line auction with bid pooling
US5539189A (en) 1992-11-27 1996-07-23 Hopeman Enterprises Ltd. Card holder's paging system for commercial card data network
US5367450A (en) 1992-12-21 1994-11-22 Pitney Bowes Inc. System and method for selecting optional inserts with optimal value in an inserting machine
US5632010A (en) 1992-12-22 1997-05-20 Electronic Retailing Systems, Inc. Technique for communicating with electronic labels in an electronic price display system
JPH08509849A (en) 1993-02-16 1996-10-15 サイエンティフィック−アトランタ・インコーポレーテッド System and method for remote selection of subscribers and control of messages to subscribers in a cable television system
US5621640A (en) 1993-02-18 1997-04-15 Every Penny Counts, Inc. Automatic philanthropic contribution system
US5708782A (en) 1993-03-22 1998-01-13 Larson; Blaine Method and apparatus for dispensing discount coupons
US5523794A (en) 1993-04-16 1996-06-04 Mankovitz; Roy J. Method and apparatus for portable storage and use of data transmitted by television signal
US5884292A (en) 1993-05-06 1999-03-16 Pitney Bowes Inc. System for smart card funds refill
RU2183854C2 (en) 1993-05-20 2002-06-20 Мур Бизнес Формз, Инк. System of applications and application accompanying system
JP3022053B2 (en) 1993-05-28 2000-03-15 富士通株式会社 POS terminal device
US5794207A (en) 1996-09-04 1998-08-11 Walker Asset Management Limited Partnership Method and apparatus for a cryptographically assisted commercial network system designed to facilitate buyer-driven conditional purchase offers
US5553131A (en) 1993-07-09 1996-09-03 Mountain International Corporation Providing the most cost-effective long-distance telephone service based on milage band rates
AU7402294A (en) 1993-07-23 1995-02-20 Credit Verification Corporation Method and system for selective incentive point-of-sale marketing in response to customer shopping histories
US5420606A (en) 1993-09-20 1995-05-30 Begum; Paul G. Instant electronic coupon verification system
US5611052A (en) 1993-11-01 1997-03-11 The Golden 1 Credit Union Lender direct credit evaluation and loan processing system
US5380991A (en) 1993-11-16 1995-01-10 Valencia; Luis Paperless coupon redemption system and method thereof
CA2136038A1 (en) 1993-12-28 1995-06-29 Marilyn A. Holda-Fleck System and method to automatically provide an electronic consumer rebate
US5444630A (en) 1993-12-29 1995-08-22 Pitney Bowes Inc. Method and apparatus for applying customized rating adjustments to transaction charges
AU703349B2 (en) 1994-02-04 1999-03-25 Ic One, Inc. Method and system for allocating and redeeming incentive credits
US5420914A (en) 1994-02-28 1995-05-30 U S West Technologies, Inc. System and method for real time carrier selection
US5592375A (en) 1994-03-11 1997-01-07 Eagleview, Inc. Computer-assisted system for interactively brokering goods or services between buyers and sellers
US5893075A (en) 1994-04-01 1999-04-06 Plainfield Software Interactive system and method for surveying and targeting customers
US5519769C1 (en) 1994-04-04 2002-05-28 Rates Technology Inc Method and system for updating a call rating database
SV1994000033A (en) 1994-04-21 1995-10-30 Blen Georgina Borbon PUBLITEL INTERNACIONAL.
US5450938A (en) 1994-05-02 1995-09-19 Xcp, Inc. Card or cash actuated vending machine assembly
US5500513A (en) 1994-05-11 1996-03-19 Visa International Automated purchasing control system
US5642484A (en) 1994-05-13 1997-06-24 Captive Communications, Inc. Pump top advertisement distribution and display system with performance and sales information feedback
US5873068A (en) 1994-06-14 1999-02-16 New North Media Inc. Display based marketing message control system and method
US5459306A (en) 1994-06-15 1995-10-17 Blockbuster Entertainment Corporation Method and system for delivering on demand, individually targeted promotions
US5592376A (en) 1994-06-17 1997-01-07 Commonweal Incorporated Currency and barter exchange debit card and system
US5642279A (en) 1994-08-09 1997-06-24 New England Audio Company Technique for utilizing a computer system to provide price protection to retail customers
US5666649A (en) 1994-09-01 1997-09-09 Ericsson Inc. Communications system having variable system performance capability
US5655007A (en) 1994-10-13 1997-08-05 Bell Atlantic Network Services, Inc. Telephone based credit card protection
US5581064A (en) 1994-11-01 1996-12-03 Pennsylvania Food Merchants Association Automated coupon processing system employing coupon with identifying code and chosen second identifying code uniquely identifying the coupon
US5752238A (en) 1994-11-03 1998-05-12 Intel Corporation Consumer-driven electronic information pricing mechanism
US5724521A (en) 1994-11-03 1998-03-03 Intel Corporation Method and apparatus for providing electronic advertisements to end users in a consumer best-fit pricing manner
DE69511425T2 (en) 1994-11-08 2000-03-09 Vermeer Tech Inc PRODUCTION AID FOR ONLINE SERVICES WITH CHARGING CHARGES
US5774868A (en) 1994-12-23 1998-06-30 International Business And Machines Corporation Automatic sales promotion selection system and method
US5732400A (en) 1995-01-04 1998-03-24 Citibank N.A. System and method for a risk-based purchase of goods
US5745882A (en) 1995-01-09 1998-04-28 Us West Marketing Resources Group, Inc. Electronic classified advertising interface method and instructions with continuous search notification
US5822736A (en) 1995-02-28 1998-10-13 United Hardware Distributing Company Variable margin pricing system
US5602377A (en) 1995-03-01 1997-02-11 Metanetics Corporation Bar code dataform scanning and labeling apparatus and method
US5689100A (en) 1995-03-21 1997-11-18 Martiz, Inc. Debit card system and method for implementing incentive award program
US5673317A (en) 1995-03-22 1997-09-30 Ora Electronics, Inc. System and method for preventing unauthorized programming of wireless network access devices
US5570417A (en) 1995-03-28 1996-10-29 Lucent Technologies Inc. System for automatically providing customer access to alternative telephony service providers
US5710884A (en) 1995-03-29 1998-01-20 Intel Corporation System for automatically updating personal profile server with updates to additional user information gathered from monitoring user's electronic consuming habits generated on computer during use
CA2142691A1 (en) * 1995-04-05 1996-10-06 Ralph Moxness Long distance loyalty rewards device
US6321208B1 (en) 1995-04-19 2001-11-20 Brightstreet.Com, Inc. Method and system for electronic distribution of product redemption coupons
US5845265A (en) 1995-04-26 1998-12-01 Mercexchange, L.L.C. Consignment nodes
US5689652A (en) 1995-04-27 1997-11-18 Optimark Technologies, Inc. Crossing network utilizing optimal mutual satisfaction density profile
US5734838A (en) 1995-05-04 1998-03-31 American Savings Bank, F.A. Database computer architecture for managing an incentive award program and checking float of funds at time of purchase
US6119587A (en) 1995-05-11 2000-09-19 Restaurant Technology, Inc. Cooked food staging device and method
AU5847396A (en) 1995-05-18 1996-11-29 Recognition Group Limited Multilevel marketing systems
US5774869A (en) 1995-06-06 1998-06-30 Interactive Media Works, Llc Method for providing sponsor paid internet access and simultaneous sponsor promotion
US5727153A (en) 1995-06-06 1998-03-10 Powell; Ken R. Retail store having a system of receiving electronic coupon information from a portable card and sending the received coupon information to other portable cards
US5664115A (en) 1995-06-07 1997-09-02 Fraser; Richard Interactive computer system to match buyers and sellers of real estate, businesses and other property using the internet
US5794221A (en) 1995-07-07 1998-08-11 Egendorf; Andrew Internet billing method
US5761648A (en) 1995-07-25 1998-06-02 Interactive Coupon Network Interactive marketing network and process using electronic certificates
US5857175A (en) 1995-08-11 1999-01-05 Micro Enhancement International System and method for offering targeted discounts to customers
US5826244A (en) 1995-08-23 1998-10-20 Xerox Corporation Method and system for providing a document service over a computer network using an automated brokered auction
US5809144A (en) 1995-08-24 1998-09-15 Carnegie Mellon University Method and apparatus for purchasing and delivering digital goods over a network
US5710887A (en) * 1995-08-29 1998-01-20 Broadvision Computer system and method for electronic commerce
US5812769A (en) 1995-09-20 1998-09-22 Infonautics Corporation Method and apparatus for redirecting a user to a new location on the world wide web using relative universal resource locators
US5717860A (en) 1995-09-20 1998-02-10 Infonautics Corporation Method and apparatus for tracking the navigation path of a user on the world wide web
US5873069A (en) 1995-10-13 1999-02-16 American Tv & Appliance Of Madison, Inc. System and method for automatic updating and display of retail prices
US5606602A (en) 1995-11-06 1997-02-25 Summit Telecom Systems, Inc. Bidding for telecommunications traffic
US5715402A (en) 1995-11-09 1998-02-03 Spot Metals Online Method and system for matching sellers and buyers of spot metals
EP0867008A4 (en) 1995-11-30 1999-12-22 Inter Act Systems Inc Method and system for presenting customized promotional offers
US5794210A (en) 1995-12-11 1998-08-11 Cybergold, Inc. Attention brokerage
US5864757A (en) 1995-12-12 1999-01-26 Bellsouth Corporation Methods and apparatus for locking communications devices
US5970469A (en) * 1995-12-26 1999-10-19 Supermarkets Online, Inc. System and method for providing shopping aids and incentives to customers through a computer network
US6014634A (en) * 1995-12-26 2000-01-11 Supermarkets Online, Inc. System and method for providing shopping aids and incentives to customers through a computer network
US5615269A (en) 1996-02-22 1997-03-25 Micali; Silvio Ideal electronic negotiations
US5665953A (en) 1996-02-14 1997-09-09 Lobar Code Inc. Self-contained personal data collector for redeeming coupons
US5890135A (en) 1996-02-20 1999-03-30 Powell; Ken R. System and method for displaying product information in a retail system
US5806044A (en) 1996-02-20 1998-09-08 Powell; Ken R. System and method for distributing coupons through a system of computer networks
US5758328A (en) 1996-02-22 1998-05-26 Giovannoli; Joseph Computerized quotation system and method
JPH09231274A (en) 1996-02-26 1997-09-05 Fujitsu Ltd Retrieval server system
CA2250283A1 (en) 1996-03-06 1997-09-25 Michael Walden Incentive based information generation system
US5835896A (en) 1996-03-29 1998-11-10 Onsale, Inc. Method and system for processing and transmitting electronic auction information
US5870030A (en) 1996-04-04 1999-02-09 Motorola, Inc. Advertiser pays information and messaging system and apparatus
US5848396A (en) * 1996-04-26 1998-12-08 Freedom Of Information, Inc. Method and apparatus for determining behavioral profile of a computer user
US6002771A (en) 1996-05-22 1999-12-14 Sun Microsystems, Inc. Method and system for regulating discounts on merchandise distributed through networked computer systems
US5761647A (en) 1996-05-24 1998-06-02 Harrah's Operating Company, Inc. National customer recognition system and method
US5819241A (en) 1996-05-28 1998-10-06 Reiter; Joshua J. Interactive process for applying or printing information on letters or parcels
US6178411B1 (en) 1996-05-28 2001-01-23 Joshua J. Reiter Interactive process for applying or printing information on letters or parcels
US5918211A (en) * 1996-05-30 1999-06-29 Retail Multimedia Corporation Method and apparatus for promoting products and influencing consumer purchasing decisions at the point-of-purchase
US5864822A (en) 1996-06-25 1999-01-26 Baker, Iii; Bernard R. Benefits tracking and correlation system for use with third-party enabling organization
US5845259A (en) 1996-06-27 1998-12-01 Electronic Consumer Concepts, L.L.C. Electronic coupon dispensing system
US5825881A (en) 1996-06-28 1998-10-20 Allsoft Distributing Inc. Public network merchandising system
US5717866A (en) 1996-06-28 1998-02-10 Codesaver International, Inc. Method for comparative analysis of consumer response to product promotions
US7225142B1 (en) 1996-08-01 2007-05-29 At&T Corp. Interactive multimedia advertising and electronic commerce on a hypertext network
US6332126B1 (en) * 1996-08-01 2001-12-18 First Data Corporation System and method for a targeted payment system discount program
US5839119A (en) 1996-09-27 1998-11-17 Xerox Corporation Method of electronic payments that prevents double-spending
US6259908B1 (en) 1996-11-25 2001-07-10 Bellsouth Intellectual Property Management Corporation Method of limiting access to the data stored in a cellular telephone
US5923016A (en) 1996-12-03 1999-07-13 Carlson Companies, Inc. In-store points redemption system & method
US5905974A (en) 1996-12-13 1999-05-18 Cantor Fitzgerald Securities Automated auction protocol processor
WO1998028699A1 (en) 1996-12-24 1998-07-02 Meridian Enterprises, Inc. System and method for administration of an incentive award program through use of credit
JPH10187318A (en) 1996-12-26 1998-07-14 Nec Corp Automatic setting processing system for customer attribute information
US6052730A (en) * 1997-01-10 2000-04-18 The Board Of Trustees Of The Leland Stanford Junior University Method for monitoring and/or modifying web browsing sessions
DK10797A (en) 1997-01-30 1997-01-30 Autocom Aps Procedure for holding an auction, as well as uses of the method
US6138105A (en) 1997-03-21 2000-10-24 Walker Digital, Llc System and method for dynamic assembly of packages in retail environments
US6064987A (en) 1997-03-21 2000-05-16 Walker Digital, Llc Method and apparatus for providing and processing installment plans at a terminal
US6223163B1 (en) 1997-03-21 2001-04-24 Walker Digital, Llc Method and apparatus for controlling offers that are provided at a point-of-sale terminal
US6298331B1 (en) 1997-03-21 2001-10-02 Walker Digital, Llc Method and apparatus for selling an aging food product
US6298329B1 (en) 1997-03-21 2001-10-02 Walker Digital, Llc Method and apparatus for generating a coupon
US5937037A (en) 1998-01-28 1999-08-10 Broadpoint Communications, Inc. Communications system for delivering promotional messages
US6035281A (en) 1997-06-16 2000-03-07 International Business Machines Corporation System and method of multiparty billing for Web access
US6144948A (en) 1997-06-23 2000-11-07 Walker Digital, Llc Instant credit card marketing system for reservations for future services
US6026370A (en) 1997-08-28 2000-02-15 Catalina Marketing International, Inc. Method and apparatus for generating purchase incentive mailing based on prior purchase history
US6393407B1 (en) * 1997-09-11 2002-05-21 Enliven, Inc. Tracking user micro-interactions with web page advertising
MXPA00002497A (en) 1997-09-12 2003-07-21 Amazon Com Inc Method and system for placing a purchase order via a communications network.
US6049778A (en) * 1997-10-31 2000-04-11 Walker Asset Management Limited Partnership Method and apparatus for administering a reward program
US6349288B1 (en) 1997-11-18 2002-02-19 Timothy P. Barber Architecture for access over a network to pay-per-view information
US20010014868A1 (en) 1997-12-05 2001-08-16 Frederick Herz System for the automatic determination of customized prices and promotions
US6405174B1 (en) 1998-10-05 2002-06-11 Walker Ditial, Llc Method and apparatus for defining routing of customers between merchants
US6965870B1 (en) * 1997-12-24 2005-11-15 Nortel Networks Limited Method and system for activity responsive telemarketing
US5890718A (en) 1998-02-27 1999-04-06 Byon; Ok-Sun Self-service gasoline pump system with game function
US6332128B1 (en) 1998-07-23 2001-12-18 Autogas Systems, Inc. System and method of providing multiple level discounts on cross-marketed products and discounting a price-per-unit-volume of gasoline
US6076069A (en) 1998-09-25 2000-06-13 Oneclip.Com, Incorporated Method of and system for distributing and redeeming electronic coupons
JP2000113334A (en) 1998-09-30 2000-04-21 Ncr Internatl Inc Method and device for displaying advertisement message for customer by using sales management terminal equipment
WO2000021004A1 (en) 1998-10-05 2000-04-13 Walker Digital, Llc Method and apparatus for providing a discount to a customer that participates in transactions at a plurality of merchants
US6059142A (en) 1998-10-15 2000-05-09 Inland Finance Company Apparatus and method for vending multiple products
MXPA01004945A (en) 1998-11-17 2003-03-10 Prenet Corp Electronic payment system utilizing intermediary account.
US6173274B1 (en) 1998-12-30 2001-01-09 Pitney Bowes Inc. Production mail system having subsidies for printing of third party messages on mailpieces
US6154733A (en) 1998-12-30 2000-11-28 Pitney Bowes Inc. Postage printing system having variable subsidies for printing of third party messages

Patent Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4718009A (en) * 1984-02-27 1988-01-05 Default Proof Credit Card System, Inc. Default proof credit card method system
US5852811A (en) * 1987-04-15 1998-12-22 Proprietary Financial Products, Inc. Method for managing financial accounts by a preferred allocation of funds among accounts
US5515270A (en) * 1991-07-22 1996-05-07 Weinblatt; Lee S. Technique for correlating purchasing behavior of a consumer to advertisements
US5434394A (en) * 1992-09-10 1995-07-18 Tandy Corporation Automated order and delivery system
US5537314A (en) * 1994-04-18 1996-07-16 First Marketrust Intl. Referral recognition system for an incentive award program
US5636346A (en) * 1994-05-09 1997-06-03 The Electronic Address, Inc. Method and system for selectively targeting advertisements and programming
US5925865A (en) * 1994-07-11 1999-07-20 Steger; Paul Automated check verification and tracking system
US5839117A (en) * 1994-08-19 1998-11-17 Andersen Consulting Llp Computerized event-driven routing system and method for use in an order entry system
US5734890A (en) * 1994-09-12 1998-03-31 Gartner Group System and method for analyzing procurement decisions and customer satisfaction
US5619558A (en) * 1995-11-13 1997-04-08 Ncr Corporation ATM segment of one marketing method
US5826240A (en) * 1996-01-18 1998-10-20 Rosefaire Development, Ltd. Sales presentation system for coaching sellers to describe specific features and benefits of a product or service based on input from a prospect
US5721827A (en) * 1996-10-02 1998-02-24 James Logan System for electrically distributing personalized information
US5974399A (en) * 1997-08-29 1999-10-26 Catalina Marketing International, Inc. Method and apparatus for generating purchase incentives based on price differentials
US6055513A (en) * 1998-03-11 2000-04-25 Telebuyer, Llc Methods and apparatus for intelligent selection of goods and services in telephonic and electronic commerce
US6289318B1 (en) * 1998-03-24 2001-09-11 Timothy P. Barber Method and architecture for multi-level commissioned advertising on a computer network

Cited By (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8694389B1 (en) 2002-08-27 2014-04-08 Formula Labs, Llc System for optimization of business transactions between a selling vendor and a shipping vendor
US20230274346A1 (en) * 2008-10-02 2023-08-31 Ecoatm, Llc Kiosks for evaluating and purchasing used electronic devices and related technology
US11546477B1 (en) 2011-02-07 2023-01-03 Intermetro Communications, Inc. System and method for dynamic multifactor routing
US10298775B1 (en) 2011-02-07 2019-05-21 Intermetro Communications, Inc. System and method for traffic burst protection
US9124957B1 (en) * 2011-02-07 2015-09-01 Christopher Fogel System and method for dynamic multifactor routing
US10701218B1 (en) 2011-02-07 2020-06-30 Intermetro Communications, Inc. System and method for dynamic multifactor routing
US11900442B1 (en) 2012-05-21 2024-02-13 Formula Labs, Llc System and method for identifying and co-ordinating an alternate delivery of one or more selected items
US10043148B1 (en) 2012-05-21 2018-08-07 Formula Labs, Llc System and method for identifying and co-ordinating an alternate delivery of one or more selected items
US9760854B1 (en) 2012-05-21 2017-09-12 Formula Labs, Llc System and method for identifying and co-ordinating an alternate delivery of one or more selected items
US10445818B1 (en) 2012-05-21 2019-10-15 Formula Labs, Llc System and method for identifying and co-ordinating an alternate delivery of one or more selected items
US11321766B1 (en) 2012-05-21 2022-05-03 Formula Labs, Llc System and method for identifying and co-ordinating an alternate delivery of one or more selected items
US10339548B1 (en) 2014-03-24 2019-07-02 Square, Inc. Determining pricing information from merchant data
US11210725B2 (en) 2014-03-24 2021-12-28 Square, Inc. Determining pricing information from merchant data
US11017369B1 (en) 2015-04-29 2021-05-25 Square, Inc. Cloud-based inventory and discount pricing management system
US10949796B1 (en) 2015-07-15 2021-03-16 Square, Inc. Coordination of inventory ordering across merchants
US10909486B1 (en) 2015-07-15 2021-02-02 Square, Inc. Inventory processing using merchant-based distributed warehousing
US10467583B1 (en) 2015-10-30 2019-11-05 Square, Inc. Instance-based inventory services
US20170282736A1 (en) * 2016-04-01 2017-10-05 Ijuze Corporation Pte Ltd. Automated system for managing and providing a network of charging stations
US11912153B2 (en) 2016-04-01 2024-02-27 Power Hero Corp. Electric vehicle charging stations
US10857902B2 (en) * 2016-04-01 2020-12-08 Power Hero Corp. Automated system for managing and providing a network of charging stations
US11796340B2 (en) * 2017-04-03 2023-10-24 Power Hero Corp. Universal automated system for identifying, registering and verifying the existence, location and characteristics of electric and other power outlets by random users and for retrieval and utilization of such parametric data and outlets by all users
US20210080282A1 (en) * 2017-04-03 2021-03-18 Power Hero Corp. Universal automated system for identifying, registering and verifying the existence, location and characteristics of electric and other power outlets by random users and for retrieval and utilization of such parametric data and outlets by all users
US20230417568A1 (en) * 2017-04-03 2023-12-28 Power Hero Corp. Universal automated system for identifying, registering and verifying the existence, location and characteristics of electric and other power outlets by random users and for retrieval and utilization of such parametric data and outlets by all users
US11913801B2 (en) * 2017-04-03 2024-02-27 Power Hero Corp. Universal automated system for identifying, registering and verifying the existence, location and characteristics of electric and other power outlets by random users and for retrieval and utilization of such parametric data and outlets by all users
US10318569B1 (en) 2017-12-29 2019-06-11 Square, Inc. Smart inventory tags
US11861579B1 (en) 2018-07-31 2024-01-02 Block, Inc. Intelligent inventory system
US10878394B1 (en) 2018-11-29 2020-12-29 Square, Inc. Intelligent inventory recommendations
US11805207B2 (en) 2020-08-28 2023-10-31 Intermetro Communications, Inc. Systems and methods for configuring and dynamically applying call route groups

Also Published As

Publication number Publication date
US8700456B2 (en) 2014-04-15
US7827057B1 (en) 2010-11-02
US20140222609A1 (en) 2014-08-07
US9697553B2 (en) 2017-07-04

Similar Documents

Publication Publication Date Title
US9697553B2 (en) Method and apparatus for providing cross-benefits based on a customer activity
US8645202B2 (en) System for providing offers using a billing statement
US8543451B2 (en) Method and apparatus for facilitating electronic commerce through providing cross-benefits during a transaction
US20020169664A1 (en) System for providing offers using a billing statement
US8781894B2 (en) System to provide price adjustments based on indicated product interest
US20020147663A1 (en) Systems and methods for facilitating a transaction by use of third party subsidies
US7818284B1 (en) Method and apparatus for providing cross-benefits via a central authority
WO1999066443A1 (en) Method and apparatus for providing cross-benefits via a central authority
WO2000039720A1 (en) Method and apparatus for providing cross-benefits based on a customer activity
US20060218050A1 (en) Method and apparatus for facilitating electronic commerce through providing cross-benefits during a transaction
EP1221108A2 (en) Systems and methods for evaluating information associated with a transaction to determine a subsidy offer
EP1208450A2 (en) Systems and methods for providing a subsidy offer through a customer device
WO2000039727A2 (en) Method and apparatus for providing cross benefits and penalties
JP2003528361A (en) System and method for evaluating information about a transaction that determines a grant application

Legal Events

Date Code Title Description
AS Assignment

Owner name: INVENTOR HOLDINGS, LLC, CONNECTICUT

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:WALKER DIGITAL, LLC;REEL/FRAME:032207/0318

Effective date: 20131101

STCF Information on status: patent grant

Free format text: PATENTED CASE

AS Assignment

Owner name: WALKER DIGITAL, LLC, CONNECTICUT

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:WALKER DIGITAL CORPORATION;REEL/FRAME:034106/0608

Effective date: 19991124

Owner name: WALKER DIGITAL CORPORATION, CONNECTICUT

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WALKER, JAY S.;TEDESCO, DANIEL E.;TULLEY, STEPHEN C.;AND OTHERS;REEL/FRAME:034106/0533

Effective date: 19990331

AS Assignment

Owner name: PAYPAL, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INVENTOR HOLDINGS, LLC;REEL/FRAME:039277/0523

Effective date: 20160610

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551)

Year of fee payment: 4

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20220415