This application relates generally to consumer transactions. More specifically, this application relates to operating loyalty programs in connection with consumer transactions.
In recent years, there has been a steady proliferation of loyalty programs offered to consumers. There are a variety of different models on which such loyalty programs are based, but a common feature of all is that they offer an incentive designed to encourage customers to conduct business preferentially with one organization rather than with competitor organizations. For example, such loyalty systems often take the form of point systems in which a customer is credited with a number of points for each transaction and is entitled to exchange certain numbers of points for goods and/or services.
A prototypical example of such a loyalty system is used in the airline industry. An airline typically offers some number of points to each consumer that is correlated with the distance traveled. At certain levels, the points may be exchanged by the consumer for airline tickets; generally, a larger number of points is required for more valuable international or intercontinental tickets. Sometimes, additional incentives may be used to induce customers to reach certain point levels, such as by providing preferential seating and booking privileges. Similar loyalty systems are also used in environments for the retail sale of goods, with customers of a particular store being entitled to rewards in exchange for certain levels of business. Generally, however, such loyalty systems are limited in flexibility and are narrow in scope.
There is a general recognition in the industry of a need for more sophisticated loyalty-based systems capable of responding to long-term competitive threats such as retail overcapacity, mass advertising spending, consumer attrition issues, etc. For example, it is desirable for the system to be sufficiently flexible that rewards can be provided quickly, even in real time at the moment the desired point level is reached. Similarly, it is desirable for the system not to be reliant on a specific type of tender, such as a specific type of loyalty-program card, but instead to be capable of accepting any type of tender, whether it be a loyalty-program card, credit card, debit card, store-specific coupon, or other instrument.
Accordingly, embodiments of the invention provide a method for operating a loyalty system that may achieve such increased flexibility. In one embodiment, a loyalty program is integrated with a financial infrastructure, such as may provided to supply authorizations for transactions. Such a financial infrastructure is generally configured more broadly to accommodate transactions that may involve participants in the loyalty program but also transactions that do not involve participants. When a transaction is initiated by a customer at a merchant, regardless of who are the parties to the transaction, it is intercepted by a loyalty switch, which determines whether the customer and merchant are participants in the loyalty program. The switch transmits the transaction instruction to the financial infrastructure so that authorization may be received. If it is determined that the customer and merchant are participants in the loyalty program, a loyalty process is executed that conforms with the criteria of the loyalty program.
This arrangement permits the loyalty switch to monitor the criteria for multiple loyalty programs that may exist between various combinations of consumers and merchants. Whenever it encounters a transaction between parties that comes within the scope of one of the loyalty programs, the appropriate loyalty process is executed by a loyalty host. The loyalty host is configured to act as an administration authority and includes administration criteria for multiple distinct loyalty programs. Information regarding the loyalty programs, including such features as point levels and available rewards, is thus stored and administered remotely by the loyalty host rather than being integrated as a function of a loyalty device such as a smart card.
Generally, execution of the loyalty process will proceed at the same time as waiting for authorization for the transaction from the financial infrastructure. If the transaction is authorized, the authorization is transmitted back to the merchant. In some instances where the loyalty program provides the customer with an instant reward, the transmission back to the merchant may be accompanied with instructions for implementing the instant reward. If the transaction is not authorized, the loyalty process will be backed out by removing its application before returning a transmission to the merchant.
This arrangement is especially suitable where a point-of-sale terminal is used to process the transaction. The point-of-sale terminal may be configured to recognize a variety of instruments that may be used by the customer to effect the transaction, and such instruments may also serve to identify the customer as a participant in the loyalty program.
In some embodiments, the applicable loyalty program may involve distinct merchants, so that points accumulated within the loyalty program for transactions at a first merchant may be used towards a reward from a second merchant. The different merchants may value the point total differently so that point-settlement functions among the merchants may also be provided. In addition, reporting functions may be performed to provide summary information to any of the parties involved with the loyalty system.
The methods of the present invention may be embodied in a computer-readable storage medium having a computer-readable program embodied therein for directing operation of a computer system. Such a computer system may include a communications system, a processor, and a storage device. The computer-readable program includes instructions for operating the computer system to operate loyalty programs in accordance with the embodiments described above.
A further understanding of the nature and advantages of the present invention may be realized by reference to the remaining portions of the specification and the drawings wherein like reference numerals are used throughout the several drawings to refer to similar components. In some instances, a sublabel is associated with a reference numeral and follows a hyphen to denote one of multiple similar components. When reference is made to a reference numeral without specification to an existing sublabel, it is intended to refer to all such multiple similar components.
1. Overview
Various loyalty systems may involve a variety of different entities. A simple example of a traditional prior-art loyalty system is shown in
The loyalty systems illustrated in
The increased versatility of loyalty programs that may be administered with this system 140 exploit the existence of multiple, and sometimes competing, issuer associations 116. For example, any instrument associated with an issuer association that also bears an identification of the aggregator 118 may be used to participate in a loyalty program. In some instances, the loyalty program will be for a single retail organization, but may in other instances span across multiple organizations. A variety of examples of loyalty programs that may be administered with the structure of
The basic structure of
While
2. Integration of Loyalty System with Financial Infrastructure
When a transaction is executed using a point-of-sale terminal 208, an electronic packet identifying the terms of the transaction and including an identification of the payment instrument is forwarded to the loyalty switch 212, which makes a determination whether the merchant and customer who are parties to the transaction are registered within the loyalty system. Such a comparison is performed by comparing the identification of the parties included within the electronic packet with a database listing of registered participants. If either party is not registered, the loyalty switch 212 only forwards the electronic packet to an appropriate authorization authority 220 through communication networks comprised by the financial infrastructure. This authority 220 will generally comprise an issuer 108, but may comprise an issuer association 116 according to different embodiments. The authority 220 determines whether to authorize the transaction in accordance with its own standards and communicates its decision back through the financial infrastructure and the loyalty switch 212 to the originating point-of-sale terminal 208.
If the parties to the transaction are registered, indicating that the customer is participating in one or more forms of loyalty programs integrated with the financial infrastructure, the loyalty switch forwards the electronic packet through the financial infrastructure to a loyalty host 216. The loyalty host 216 will generally be comprised by an aggregator 118 configured within the financial architecture as illustrated in
The loyalty switch 212 may be configured also to forward the electronic packet to the authorization authority 220 to approve the transaction, although in some embodiments that function will be performed by the loyalty host 216 to ensure that loyalty credit is given only if the transaction is properly authorized and satisfactorily executed.
The coordinated operation of the loyalty switch 212, loyalty host 216, and authorization authority 220 with respect to a transaction is illustrated with the flow diagram of
If both the customer and merchant participate in any loyalty program operated by the loyalty system, the appropriate loyalty process is executed at block 316 in accordance with the arrangements for that particular merchant and/or that particular customer. Such execution may include making a decision to provide a reward to the customer immediately at the point of sale. A determination is made at block 320 whether the transaction requires authorization from an authorization authority 220. Examples of transaction types that require authorization include credit and debit transactions; examples of transaction types that do not require authorization include use of a stored-value card or coupon, and payment by cash with presentment of a dedicated loyalty card. If necessary, authorization for the transaction is sought at block 324 and an evaluation of the response is made at 332. If the transaction is declined, the loyalty transaction is backed out at block 340 and the payment response is returned to the point-of-sale terminal 208 at block 344.
In this arrangement, execution of the loyalty process is generally initiated before authorization for the transaction is received. This is preferred primarily for reasons of efficiency so that the transaction authorization may be sought at the same time as the loyalty process is being executed. It is expected that a large majority of transactions will be authorized so that the need to back out of the loyalty transaction will be exceptional. In an alternative embodiment, authorization may be sought before initiating the loyalty process. This has the advantage of avoiding the need to back out of a transaction at block 340, but is expected to be less efficient overall.
At block 336, whether reached through the flow diagram because no authorization is needed for the transaction or because the transaction was authorized, a response is returned to the point-of-sale terminal 208. This response includes the loyalty characteristics, such as a change in points or the availability of an award, as well as an indication that the transaction has been authorized.
The loyalty host 216 may be configured in a variety of different ways to effect the functions described with respect to
The database information regarding merchants, issuers, and/or individual customers is generally stored on the storage devices 404. The database information stored on the storage devices 404 is sometimes referred to herein as defining a “central database,” although there is no requirement that such a central database be stored on any single storage device. For example, the central database may comprise a distributed database by being stored across multiple storage devices 404. A central database excludes, however, the storage of database information only on instruments local with individual customers and/or merchants. For example, in embodiments where transactions are initiated with chip cards that identify the customers that hold them, the use of a central database permits customer records to be stored remotely from the individual chip cards.
The communications system 406 is configured to effect communications as needed with merchants and issuers. It thus receives the electronic packet from the point-of-sale device 208 and transmits any loyalty or payment authorizations as needed back to the point-of-sale device 208. In addition to providing such infrastructure communications links internal to the system, the communications system 406 may also provide a connection to other networks such as the internet and may comprise a wired, wireless, modem, and/or other type of interfacing connection. Such additional connections may be useful for support functions that may be assisted by the loyalty host 216 described below and provided for merchants, issuers, and customers.
The loyalty host 216 also comprises software elements, shown as being currently located within working memory 491, including an operating system 492 and other code 493, such as a program designed to implement methods of the invention. It will be apparent to those skilled in the art that substantial variations may be used in accordance with specific requirements. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets), or both. Further, connection to other computing devices such as network input/output devices may be employed.
3. Loyalty Programs
The systems described above are suitable for accommodating a large variety of different types of loyalty programs. Individual programs may be specific to an individual store or organization or may span across multiple otherwise unrelated organizations as part of a more comprehensive loyalty system. In one aspect, individual customers may participate in multiple loyalty programs that are managed as independent programs by the aggregator 118. Points maintained for the different programs are identified and distinguished by different point types. In this way, the customer may be able to use a single instrument identified with the aggregator's logo for participation in all her loyalty programs.
For each of the loyalty programs, rewards may be accumulated in at least three ways. First, rewards may be based on recency criteria, in which a reward is triggered either by completing a transaction within a specified time interval or by completing a specified number of transactions within a given time interval. Second, rewards may be based on frequency, in which a reward is triggered by completing a specified number of transactions. Third, rewards may be monetarily based so that a reward is triggered when a specified total transaction amount is reached. Such triggers may be specified for individual transactions or may be specified for accumulated transaction amounts over multiple transactions.
In addition, reward triggers may be conditional. Examples of conditional triggers include a requirement that points be accumulated only for transaction above a certain amount, and perhaps that points be accumulated more generally at different rates for transactions of different sizes. Other conditional triggers may be associated with time constraints so that points may only be accumulated only after a specified date, only before a specified date, only an certain days of the week, only during certain holiday periods, etc. Accumulation of points may also be conditionally restricted to certain tender types and to transactions where no reward is applied.
Accumulation of rewards is generally tracked in terms of points. Such points will generally be correlated with aspects of a transaction, and may be set to expire after a certain time period or at a predetermined time. Thus, for a recency loyalty system, points will generally be set to expire within the time period required for completion of the transactions. For a frequency loyalty system, points will usually be integers corresponding to the number of transactions completed. For a monetary loyalty system, points will be correlated with the dollar amount of the transaction. The correlation rates may differ for different issuers, even within the same loyalty program, requiring use of the settlement functions described below. Points may generally be structured to expire periodically or after a specified period of inactivity to prevent excess accumulation by individual customers. Furthermore, point totals for individuals may be conditioned to reset when awards are given, to reset on a cyclical basis (e.g., monthly or annually), to continue to accumulate (rewards given for different levels reached), or to be permanently eliminated upon issuance of a reward (such as for a one-time reward).
In certain embodiments, points may be accumulated collectively by multiple customers. For example, each member of a family may have a separate card that identifies them individually, but points are accumulated into an account for the family as a whole. In other embodiments, points may be transferred among customers.
The manner in which such loyalty programs function may be illustrated with specific examples. First, consider a loyalty program in which points are given for every dollar spent at any of a plurality of stores having diverse retail practices, such as a clothing chain, a hardware chain, and a restaurant chain. A customer who uses a card bearing a logo for the aggregator that manages this program accumulates points at any of the stores and may exchange the accumulated points for goods at any of the stores. For example, the customer may make a series of purchases at the hardware chain over a period of time and may subsequently redeem the points for dinner at a restaurant that forms part of the restaurant chain. This is an example of a purely monetary loyalty program that operates by the individual chains determining how to allocate point values among themselves to accommodate their respective benefits of participating in the program. This is also an example where different money-point correlation rates may be appropriate to account for differences in retail practices among the merchants.
As another example, consider a loyalty program in which a pizza chain and a video-rental chain cooperate. They advertise collectively that anyone who buys three pizzas at the pizza chain may receive a free video rental at the video-rental chain and anyone who rents fifteen videos at the video-rental chain is entitled to a free pizza at the pizza chain. Customers having cards bearing the aggregator logo have their purchases of pizzas and rentals of videos recorded so that the reward may be issued when the criteria have been fulfilled. Such rewards may be given automatically at the point of sale when the customer uses his card. This is an example of a frequency-based reward system that uses the aggregator to integrate separate organizations into the plan in a cooperative way.
As a further example, consider a loyalty program in which a movie-theater chain, a bookstore chain, and a music-store chain that are otherwise independent from one another cooperate. They offer a program in which, in any monthly period, a $25.00 purchase at each of two of the chains entitles the customer to a $5.00 rebate towards a purchase at the third chain. The purchases of customers having cards bearing the aggregator logo are recorded whenever they visit any of the three chains and issue the appropriate reward when the conditions are met. This example combines aspects of recency-based and monetary-based loyalty systems that use the aggregator to permit separate organizations to cooperate to their mutual benefit.
4. Support Functions
At block 524, the aggregator 118 accesses records from the storage device(s) 404 of the loyalty host 216 as necessary to respond to a request from the customer 436. Three examples of the types of request are shown in the figure, although many other types of customer care services may also be provided with the information stored by the loyalty host 216. For example, at block 528, the aggregator 118 may access the storage device(s) 404 to provide an activity summary for the customer 436, including such information as total number and type of loyalty points, when those points were acquired, and the number needed to reach certain target levels for awards.
At block 532, the aggregator 118 may access the storage device(s) 404 to provide rewards for a customer 436 who has accumulated the requisite number of loyalty points. Such activity comprises verifying the number and type of accumulated loyalty points for a particular customer and performing a comparison with the requirements of the loyalty program. In one embodiment, one or more coupons, such as electronic coupons over the internet, may be provided to the customer 436 as the reward.
The activity denoted at block 536 is similar, but the reward is coordinated by the aggregator 118 instead of being provided in the form of a coupon. For example, with a loyalty program that permits the customer to redeem points for rewards with different types of merchants, the aggregator 118 may record a reward selection for that merchant and arrange for it to be automatically redeemed when the customer next visits the merchant. More specifically, suppose a loyalty program permits, and a customer chooses, to redeem points for 10% off any purchase at Store X. The aggregator 118 accepts the selection of the customer 436 to choose such a reward and records that choice in the storage device(s) 404. The next time the customer visits Store X, the record of his reward selection is applied by the loyalty host 116 at block 336 of
In addition to such functions, it is also desirable for the loyalty host 216 to perform reporting functions. The flow diagram of
Various types of reports may be generated depending on the type of information desired. For example, in one embodiment, an audit report is generated to describe all activity that occurs on a daily basis, include points-issuance transactions and points-redemption transactions. For each transaction, the report may include an identifier for the consumer involved in the transaction, a transaction date, the amount of the transaction, an identifier for the merchant and location where the transaction was executed, an identifier for the specific point-of-sale terminal used in the transaction, and an identification of the type of transaction. In another embodiment, the report may comprise a settlement report that indicates how points have been settled in accordance with the settlement functions described above. In a further embodiment, the report may comprise a liability report that indicates the extent to which an issuer 108 has outstanding liability of pending points for redemption. Such a liability report typically includes a daily and monthly total report classifying the number of outstanding points by customer. Such reporting features are useful for participants in the loyalty programs to monitor their success quantitatively.
Having described several embodiments, it will be recognized by those of skill in the art that various modifications, alternative constructions, and equivalents may be used without departing from the spirit of the invention. Accordingly, the above description should not be taken as limiting the scope of the invention, which is defined in the following claims.
Number | Name | Date | Kind |
---|---|---|---|
5117355 | McCarthy | May 1972 | A |
4723212 | Mindrum et al. | Feb 1988 | A |
4910672 | Off et al. | Mar 1990 | A |
4941090 | McCarhty | Jul 1990 | A |
5025372 | Burton et al. | Jun 1991 | A |
5056019 | Schultz et al. | Oct 1991 | A |
5173851 | Off et al. | Dec 1992 | A |
5185695 | Pruchnicki | Feb 1993 | A |
5200889 | Mori | Apr 1993 | A |
5202826 | McCarhty | Apr 1993 | A |
5305196 | Deaton et al. | Apr 1994 | A |
5448471 | Deaton et al. | Sep 1995 | A |
5471669 | Kidman | Nov 1995 | A |
5483444 | Heintzeman et al. | Jan 1996 | A |
5530232 | Taylor | Jun 1996 | A |
5537314 | Kanter | Jul 1996 | A |
5578808 | Taylor | Nov 1996 | A |
5612868 | Off et al. | Mar 1997 | A |
5642485 | Deaton et al. | Jun 1997 | A |
5644723 | Deaton et al. | Jul 1997 | A |
5649114 | Deaton et al. | Jul 1997 | A |
5659469 | Deaton et al. | Aug 1997 | A |
5687322 | Deaton et al. | Nov 1997 | A |
5689100 | Carrithers et al. | Nov 1997 | A |
5734838 | Robinson et al. | Mar 1998 | A |
5774870 | Storey | Jun 1998 | A |
5804806 | Haddad et al. | Sep 1998 | A |
5806045 | Biorge et al. | Sep 1998 | A |
5832457 | O'Brien et al. | Nov 1998 | A |
RE36116 | McCarthy | Feb 1999 | E |
5903880 | Biffar | May 1999 | A |
5909486 | Walker et al. | Jun 1999 | A |
5915007 | Klapka | Jun 1999 | A |
5923016 | Fredregill et al. | Jul 1999 | A |
5924080 | Johnson | Jul 1999 | A |
5926795 | Williams | Jul 1999 | A |
5969318 | Mackenthun | Oct 1999 | A |
5974399 | Giuliani et al. | Oct 1999 | A |
5983196 | Wendkos | Nov 1999 | A |
5991376 | Hennessy et al. | Nov 1999 | A |
6000608 | Dorf | Dec 1999 | A |
6009411 | Kepecs | Dec 1999 | A |
6009412 | Storey | Dec 1999 | A |
6009415 | Shurling et al. | Dec 1999 | A |
6012635 | Shimada et al. | Jan 2000 | A |
6024288 | Gottlich et al. | Feb 2000 | A |
6026370 | Jermyn | Feb 2000 | A |
6032136 | Brake, Jr. et al. | Feb 2000 | A |
6061860 | Eggleston et al. | May 2000 | A |
6119933 | Wong et al. | Sep 2000 | A |
6138911 | Fredregill et al. | Oct 2000 | A |
6189787 | Dorf | Feb 2001 | B1 |
6195644 | Bowie | Feb 2001 | B1 |
6222914 | McMullin | Apr 2001 | B1 |
6229879 | Walker et al. | May 2001 | B1 |
6278979 | Williams | Aug 2001 | B1 |
6282516 | Giuliani | Aug 2001 | B1 |
6292786 | Deaton et al. | Sep 2001 | B1 |
6321210 | O'Brein et al. | Nov 2001 | B1 |
6334108 | Deaton et al. | Dec 2001 | B1 |
6351735 | Deaton et al. | Feb 2002 | B1 |
6377935 | Deaton et al. | Apr 2002 | B1 |
6409080 | Kawagishi | Jun 2002 | B2 |
6419161 | Haddad et al. | Jul 2002 | B1 |
6424949 | Deaton et al. | Jul 2002 | B1 |
6424951 | Shurling et al. | Jul 2002 | B1 |
6450407 | Freeman et al. | Sep 2002 | B1 |
20010025879 | Kawagishi | Oct 2001 | A1 |
20010034720 | Armes | Oct 2001 | A1 |
20010054003 | Chien et al. | Dec 2001 | A1 |
20020046116 | Hohle et al. | Apr 2002 | A1 |
20020062253 | Dosh, Jr. et al. | May 2002 | A1 |
20020065712 | Kawan | May 2002 | A1 |
20020065716 | Kushchill | May 2002 | A1 |
20020082920 | Austin et al. | Jun 2002 | A1 |
20020099601 | Farrell | Jul 2002 | A1 |
20020107797 | Combaluzier | Aug 2002 | A1 |
20020112236 | Sukeda et al. | Aug 2002 | A1 |
20020120514 | Hagmeier et al. | Aug 2002 | A1 |
20020123926 | Bushold et al. | Sep 2002 | A1 |
20020143626 | Voltmer et al. | Oct 2002 | A1 |
20030182247 | Mobed et al. | Sep 2003 | A1 |
Number | Date | Country |
---|---|---|
0253240 | Jan 1988 | EP |
0933717 | Aug 1999 | EP |
0 987 642 | Mar 2000 | EP |
1011060 | Jun 2000 | EP |
0933717 | Feb 2001 | EP |
1139252 | Oct 2001 | EP |
1232776 | Aug 2002 | EP |
2274349 | Jul 1994 | GB |
WO 9308546 | Apr 1993 | WO |
WO 9806050 | Feb 1998 | WO |
WO 0021004 | Apr 2000 | WO |
Number | Date | Country | |
---|---|---|---|
20030158818 A1 | Aug 2003 | US |