Patents-Review.com
🔗 Share
Patent application title:

Method and system for implementing a loyalty merchant component

Publication number:

-

Publication date:
Application number:

10/402,917

Filed date:

2003-03-27

✅ Patent granted

Patent number:

US 6,920,611 B1

Grant date:

2005-07-19

PCT filing:

-

PCT publication:

-

Examiner:

Kristine Kincaid | Boris Pesin

Adjusted expiration:

2023-03-27

Abstract:

A loyalty merchant component for facilitating communications amongst cardholder systems, merchant servers and a loyalty host for purposes of processing loyalty transactions is provided. The loyalty merchant component performs a number of interface functions between the loyalty host and the merchant systems and the cardholder systems.

Inventors:

Assignee:

Interested in similar patents?

Get notified when new applications in this technology area are published.

Create Free Alert

Classification:

Description

CROSS-REFERENCES TO RELATED APPLICATION(S)

The present application claims the benefit of priority under 35 U.S.C. §119 from U.S. Provisional Patent Application Ser. No. 60/429,178, entitled “METHOD AND SYSTEM FOR IMPLEMENTING A LOYALTY MERCHANT COMPONENT”, filed on Nov. 25, 2002, the disclosure of which is hereby incorporated by reference in its entirety for all purposes.

BACKGROUND OF THE INVENTION

The present invention generally relates to computerized loyalty programs, and more specifically, to an interface component designed to communicate with a computerized loyalty program over a computer network.

A number of software products are available on the market today that are capable of handling loyalty programs in a computerized and automated manner. These products, however, are designed to work independently with back office systems located at respective merchant locations. That is, the software product is usually confined to a single merchant location. The software product only manages the loyalty program associated with that particular merchant location. Different copies of the same software product do not communicate with one another. Very often, these products only capture data at their respective locations and then forward the data to a central location on a periodic basis for merely reporting purposes. Remote access to these products from an external location is typically not provided at all or only on a minimal basis. Moreover, user interfaces for customers are usually nonexistent or lacking user-friendly features. This is because, under conventional practice, customers generally do not interact directly with the software product managing the loyalty program.

With electronic commerce moving onto the Internet, the management of loyalty programs has taken on a more centralized approach. The software product for managing the loyalty program is now generally located on a central server at a single location. Client computers located at merchant locations are used to communicate with the central server to process the desired loyalty transaction via the Internet. Furthermore, a large number of customers are conducting purchase transactions over the Internet, often in the convenience of their own homes or places of work. As a result, functions relating to a loyalty transaction that used to be performed by a store clerk may now need to be handled by the customer him/herself.

Hence, it would be desirable to provide an interface component that is capable of providing more effective and user-friendly communications with a computerized loyalty program over a computer network.

BRIEF SUMMARY OF THE INVENTION

A loyalty merchant component for facilitating communications amongst cardholder systems, merchant servers and a loyalty host for purposes of processing loyalty transactions is provided. In one exemplary aspect, the loyalty merchant component performs a number of interface functions between the loyalty host and the merchant systems and the cardholder systems.

Reference to the remaining portions of the specification, including the drawings and claims, will realize other features and advantages of the present invention. Further features and advantages of the present invention, as well as the structure and operation of various embodiments of the present invention, are described in detail below with respect to accompanying drawings, like reference numbers indicate identical or functionally similar elements.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified schematic diagram illustrating one exemplary embodiment in accordance with the present invention; and

FIG. 2 is a flow chart illustrating the operations of an exemplary embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention in the form of one or more exemplary embodiments will now be described. Referring to FIG. 1, there is shown an exemplary embodiment of the present invention. This exemplary embodiment includes a system 10 having a loyalty host 12, an open programming engine (OPE) 14, a merchant server 18, a customer or cardholder system 20 and a loyalty merchant component (LMC) 16. While only one merchant server 18 and one cardholder system 20 are shown, it should be understood that the system 10 is able to accommodate multiple merchant servers and multiple cardholder systems. It should also be understood that while a loyalty program is described below in connection with the loyalty host 12, the loyalty host 12 is capable of maintaining rules and logic for multiple loyalty programs.

In an exemplary embodiment, a smartcard is used to facilitate loyalty transactions conducted in connection with a cardholder and store the relevant transaction information. The cardholder system 20 includes a personal computer (PC), a card reader coupled to the PC for accessing the smartcard, and client loyalty component installed on the PC. The client loyalty component interfaces with one or more smartcard applications residing on the smartcard and with a web browser on the PC, sending information from the web browser to the OPE 14 and the merchant server 18. The client loyalty component is installed on PCs that are eligible to participate in corresponding loyalty programs maintained by the loyalty host 12. In an alternative embodiment, the respective functionality of the card reader, the client loyalty component, the web browser and/or one or more smartcard applications can be combined on the PC. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will know of other ways and/or methods to implement the functionality of the cardholder system 20 as described above in either an integrated or modular manner and a person of ordinary skill in the art will also appreciate other systems that can be used as the cardholder system 20. For example, in addition to the smartcard, other portable devices or tokens can be used including a cellular phone, a personal digital assistant, a pager, a payment card (such as a credit card and an ATM card), a security card, an access card, smart media, a transponder and the like; and in addition to the PC, other access systems that are able to communicate with different portable devices can be used including a point-of-sale device, a cellular phone, a PDA, a handheld specialized reader, a set-top box, a kiosk, a security system, an access system, and the like.

The OPE 14 is used by the loyalty host 12 to communicate with the outside world. The OPE 14 is a middleware application that acts as an authentication mechanism to authenticate the stored rewards on the smartcard. The OPE 14 also provides rules and logic to authenticate and validate rewards available for each transaction at a merchant website. The merchant website is managed by the merchant server 18 whose function is to handle transactions and payment processing.

The LMC 16 is a hosted programmatic entity that coordinates communications amongst the OPE 14, the cardholder system 20 and the merchant server 18 to allow loyalty transactions to be processed. For example, the LMC 16 delivers webpages and client controls to the web browser associated with the cardholder system 20. In an exemplary implementation, the LMC 16 and the OPE 14 reside on the same server. In other exemplary implementations, however, the LMC 16 and the OPE 14 may reside on separate servers, or operate as the same application.

The LMC 16 coordinates the communications amongst the OPE 14, the cardholder system 20 and the merchant server 18 in the following exemplary manner. FIG. 2 is a flow chart illustrating the operations of the system 10 in accordance with the present invention. At 30, when the cardholder has finished shopping a merchant website and is ready to check out the purchased items, the merchant server 18 communicates with the cardholder system 20 to determine if the cardholder is entitled or eligible to participate in a loyalty program, i.e., whether the cardholder is a loyalty program client or participant in the loyalty program. In one exemplary implementation, this is accomplished by the merchant server 18 checking with the cardholder system 20 to determine if the client loyalty component is installed on the PC. In other exemplary implementations, however, the merchant server 18 may communicate with the LMC 16 to determine if the cardholder is entitled or eligible to participate in a loyalty program.

If it is determined that the cardholder is a loyalty program client, at 32, the merchant server 18 forwards or posts a script to the web browser on the PC, in effect, redirecting the cardholder system 20 to the LMC 16 for further processing. That is, based on the script provided by the merchant server 18, the web browser establishes a communication session with the LMC 16. In addition, the script sent by the merchant server 18 also includes certain transaction information relating to the loyalty transaction to be processed for the cardholder. The transaction information includes, for example, item purchased, purchase amount, and merchant identification information. As will be further described below, the transaction information is eventually forwarded to the loyalty host 12 and used to calculate the appropriate loyalty reward for the transaction being processed. In other exemplary implementations, messages or function calls can be used in lieu of the script. A person of ordinary skill in the art will know of other ways and/or methods to implement the functionality of the script as described herein.

When the web browser executes the script received from the merchant server 18, the web browser is redirected to the LMC 16. During this redirect process, at 34, some or all of the transaction information previously received from the merchant server 18 is passed from the cardholder system 20 to the LMC 16 which, in turn, forwards the information to the OPE 14.

At 36, using the transaction information forwarded by the LMC 16, the OPE 14 generates a transaction ID for the transaction being processed. The transaction information is then linked to the transaction ID. The OPE 14 retains the transaction ID and forwards a copy of the transaction ID to the LMC 16.

At 38, the LMC 16 then forwards a processing page including, scripts and/or applets, to the web browser. The processing page also includes the transaction ID that has been generated by the OPE 14. From a cardholder perspective, one or more of the scripts direct the web browser to construct a processing window which is then displayed to the cardholder. One or more of the applets are used to communicate with the client loyalty component. The client loyalty component includes a transaction interface applet that is capable of establishing communication with the OPE 14.

At 40, the applet(s) received from LMC 16 activates the transaction interface applet and causes a separate communication session to be established between the OPE 14 and the web browser. In other words, the LMC 16 provides a wake-up call to the client loyalty component, more specifically, the transaction interface applet. At this point, there are two concurrent communication sessions. In addition to the communication session between the web browser and the OPE 14, as mentioned above, the web browser also has an active communication session with the LMC 16.

When the transaction interface applet is activated, the card image is retrieved from the smartcard via the cardholder system 20. The card image contains information about the cardholder. In instances where portable devices or tokens are used, images from such devices or tokens are retrieved. At 42, the card image and the transaction ID are passed from the web browser to the LMC 16. The LMC 16 then relays the card image and the transaction ID to the OPE 14. The OPE 14 has a record of all the transaction IDs. Therefore, in a situation where the OPE 14 is in contact with multiple web browsers, the OPE 14 is able to match up and specifically identify the respective card images with the relevant transaction information.

At this point at 44, using the transaction ID, the OPE 14 is able to associate the card image with the transaction information relating to the transaction being processed that was previously generated by the merchant server 18 and forwarded to the OPE 14 from the LMC 16.

At 46, using the transaction information, the OPE 14 then communicates with the loyalty host 12 and retrieves the proper rules and logic for processing the loyalty transaction. For example, the OPE 14 uses the transaction information to retrieve rules and logic that are specific to the merchant. The merchant may have different sets of rules and logic for different types of loyalty programs. For instance, the merchant may co-sponsor a specific loyalty program with a particular issuer.

At 48, the transaction information and information from the card image are checked against the rules and logic to determine the appropriate loyalty amount to be awarded. In other words, the purchase and merchant information and the cardholder information are evaluated by the OPE 14 to determine the appropriate loyalty amount to be awarded.

In some situations, the transaction being processed may be eligible for reward under a number of loyalty programs. When those situations occur, the OPE 14 first determines which loyalty program(s) are to be used for calculating the loyalty reward(s). In order to determine which loyalty programs apply, the OPE 14 directs the LMC 16 to request the cardholder to make a choice. In one exemplary implementation, the LMC 16 forwards a script or webpage to the web browser causing the relevant information to be displayed. The cardholder may be allowed to redeem one or more rewards under different loyalty programs. Upon the cardholder making a choice, the information is relayed from the cardholder system 20 to the OPE 14. The OPE 14 then accordingly calculates the appropriate loyalty reward(s).

Next, the merchant website is to be updated with the information relating to the selected loyalty reward(s). This is done so that the cardholder is given the latest information relating to his/her purchase. More specifically, at 50, the OPE 14 forwards the information relating to the selected loyalty reward(s) to the LMC 16 which, in turn, passes the information to the merchant website. The merchant website then uses the information to regenerate the appropriate webpage for the cardholder showing the latest purchase information. For example, the webpage can show the loyalty reward(s) redeemed and the updated total purchase price. In addition, the OPE 14 also passes certain information relating to the smartcard to the merchant website via the LMC 16. This information includes, for example, the PAN, i.e., the credit card account number and the associated expiration date. This information is retrieved from the card image. This information from the card image allows the merchant website to know that the smartcard offered for payment is the same as the one that is entitled to participate in the loyalty program.

At 52, the PAN and other information are then displayed by the merchant website to the cardholder for approval. When the cardholder approves or confirms payment for the transaction, the merchant website accordingly processes the payment. Other exemplary implementations allow the cardholder to cancel or reselect loyalty reward(s), without canceling the transaction.

At 54, once the payment is processed, the merchant website notifies the LMC 16 that payment has processed and that loyalty status is to be updated. The merchant website also passes certain transaction information to the LMC 16 including, for example, the loyalty reward applied. The LMC 16, in turn, relays the appropriate information to the OPE 14. This transaction information can be further checked against the information that was previously forwarded from the OPE 14 to the merchant website. For example, the loyalty reward applied by the merchant website should be the same as the loyalty reward previously calculated by the OPE 14. The OPE 14 then updates the smartcard to reflect the status of the cardholder's participation in the loyalty program. More specifically, the OPE 14 creates an updated card image for the smartcard and forwards the updated card image to the cardholder system 20 to allow the cardholder system 20 to update the smartcard.

Finally, the LMC 16 can also forward a script or webpage to the web browser causing a window to be display to the cardholder confirming update of the smartcard and showing the relevant information.

In exemplary applications, the present invention is used to allow loyalty program participants to participate in loyalty programs via computers located at home and/or places of work.

In one alternative exemplary embodiment, there are multiple OPEs 14, LMCs 16 and merchant servers 18. Each OPE 14 is associated with a LMC 16 which, in turn, is associated with a merchant server 18. In another alternative exemplary embodiment, a single OPE 16 is capable of handling communications from a number of LMCs 16. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will know of other ways and/or methods to construct different configurations in accordance with the present invention.

It should be understood that the present invention as described above can be implemented using software, hardware, or a combination of both, in the form of control logic. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will know of the appropriate ways and/or methods to implement the present invention.

It is understood that the examples and embodiments described herein are for illustrative purposes only and that various modifications or changes in light thereof will be suggested to persons skilled in the art and are to be included within the spirit and purview of this application and scope of the appended claims. All publications, patents, and patent applications cited herein are hereby incorporated by reference for all purposes in their entirety.

Claims

1. A system for processing a transaction under a loyalty program, comprising:

a loyalty host configured to maintain rules and logic relating to the loyalty program;

a cardholder system configured to retrieve and forward a device image from a portable device, the device image including portable device information and loyalty program information relating to a cardholder;

a merchant server configured to provide transaction information relating to the transaction;

an open programming engine (OPE) configured to retrieve the rules and logic relating to the loyalty program based on the transaction information and determine a loyalty amount for the transaction using the rules and logic and the device image; and

a loyalty merchant component (LMC) configured to facilitate interactions amongst the OPE, the cardholder system and the merchant server for purposes of processing the transaction under the loyalty program, wherein the LMC is configured to receive the transaction information from the merchant server and forward the transaction information to the OPE and configured to receive the device image from the cardholder system and forward the device image to the OPE.

2. The system of claim 1 wherein the LMC is further configured to:

receive the transaction information from the merchant server via the cardholder system;

forward the transaction information to the OPE to allow the OPE to generate a transaction ID linked to the transaction information;

forward the transaction ID from the OPE to the cardholder system to allow the device image to be linked to the transaction ID; and

forward the device image and the transaction ID from the cardholder system to the OPE to allow the OPE to match the transaction information to the device image.

3. The system of claim 2 wherein the LMC is further configured to forward information relating to the loyalty amount and the device image from the OPE to the merchant server to allow the merchant server to seek approval of the transaction from the cardholder system by displaying some or all of the forwarded information to the cardholder.

4. The system of claim 3 wherein the LMC is further configured to forward processed payment information from the merchant server to the OPE to allow the OPE to instruct the cardholder system to update the portable device.

5. The system of claim 1 wherein the portable device includes at least one of a smartcard, a cellular phone, a personal digital assistant, a pager, a payment card, a security card, an access card, smart media and a transponder.

6. The system of claim 1 wherein the cardholder system includes at least one of a point-of-sale device, a cellular phone, a PDA, a computer, a handheld specialized reader, a set-top box, a kiosk, a security system, and an access system.

7. A system for processing transactions under a plurality of loyalty programs, comprising:

a loyalty host configured to maintain corresponding rules and logic relating to the plurality of loyalty programs;

a plurality of cardholder systems, each cardholder system configured to retrieve and forward respective device images from a plurality of portable devices, each device image including portable device information and loyalty program information relating to a cardholder;

a plurality of merchant servers, each merchant server configured to provide respective transaction information relating to an associated transaction;

a plurality of open programming engines (OPEs) configured to retrieve the corresponding rules and logic relating to the plurality of loyalty programs based on the respective transaction information relating to the transactions associated with one or more merchant servers and determine respective loyalty amounts for the transactions using the corresponding rules and logic and the respective device images; and

a plurality of loyalty merchant components (LMCs) configured to facilitate interactions amongst the plurality of OPEs, the plurality of cardholder systems and the plurality of merchant servers for purposes of processing the transactions under the plurality of loyalty programs, wherein a first LMC is configured to receive the transaction information from the merchant server and forward the transaction information to the OPE and configured to receive the device image from the cardholder system and forward the device image to the OPE.

8. The system of claim 7 wherein at least one OPE is further configured to communicate with one or more LMCs.

9. The system of claim 7 wherein the first LMC is further configured to:

receive a first transaction information for a first transaction from a first merchant server via a first cardholder system;

forward the first transaction information to a first OPE to allow the first OPE to generate a transaction ID linked to the first transaction information;

forward the transaction ID from the first OPE to the first cardholder system to allow a first device image to be linked to the transaction ID; and

forward the first device image and the transaction ID from the first cardholder system to the first OPE to allow the first OPE to match the first transaction information to the first device image.

10. The system of claim 9 wherein the first LMC is further configured to forward information relating to a first loyalty amount and the first device image from the first OPE to the first merchant server to allow the first merchant server to seek approval of the first transaction from the first cardholder system by displaying some or all of the forwarded information to a first cardholder.

11. The system of claim 10 wherein the first LMC is further configured to forward processed payment information from the first merchant server to the first OPE to allow the first OPE to instruct the first cardholder system to update a first portable device having the first device image.

12. The system of claim 7 wherein the plurality of portable devices include at least one of a smartcard, a cellular phone, a personal digital assistant, a pager, a payment card, a security card, an access card, smart media and a transponder.

13. The system of claim 7 wherein the plurality of cardholder systems include at least one of a point-of-sale device, a cellular phone, a PDA, a computer, a handheld specialized reader, a set-top box, a kiosk, a security system, and an access system.

14. A method for processing a transaction in connection with a loyalty program using a system having a loyalty host, an open programming engine (OPE), a loyalty merchant component (LMC), a cardholder system and a merchant server, the method comprising:

directing the merchant server to communicate with the cardholder system to determine whether a cardholder is eligible to participate in the loyalty program, the cardholder having a portable device, the portable device having stored thereon a device image, the device image including portable device information and loyalty program information relating to the cardholder;

upon determining that the cardholder is eligible to participate in the loyalty program, directing the merchant server to forward transaction information to the cardholder system and redirect the cardholder system to communicate with the LMC and pass the transaction information to the LMC;

passing the transaction information from the LMC to the OPE;

directing the OPE to generate a transaction ID and linking the transaction ID to the transaction information;

passing the transaction ID to the LMC;

directing the LMC to forward a processing page to the cardholder system, the processing page including the transaction ID;

directing the cardholder system to establish communication with the OPE using the processing page;

directing the cardholder system to forward the device image retrieved from the portable device and the transaction ID to the OPE via the LMC;

directing the OPE to match the transaction information with the device image using the transaction ID;

directing the OPE to retrieve rules and logic pertaining to the loyalty program from the loyalty host based on the transaction information; and

directing the OPE to use the rules and logic to determine a loyalty amount for the transaction based on the transaction information and the device image.

15. The method of claim 14 further comprising:

directing the OPE to forward information relating to the loyalty amount and the device image to the merchant server via the LMC;

directing the merchant server to seek approval of the transaction from the cardholder by displaying some or all of the forwarded information to the cardholder; and

directing the merchant server to process payment for the transaction upon receiving approval from the cardholder.

16. The method of claim 15 further comprising:

once payment is processed, directing the merchant server to forward processed payment information to the OPE via the LMC; and

directing the OPE to instruct the cardholder system to update the portable device.

17. The method of claim 16 further comprising:

directing the cardholder system to display information relating to the updated portable device to the cardholder.

18. The method of claim 15 further comprising:

directing the merchant server to retrieve the device image from the cardholder system, the device image retrieved from the portable device offered by the cardholder for payment for the transaction; and

directing the merchant server to compare some or all of the device image retrieved from the cardholder system with some or all of the device image forwarded by the OPE to ensure that the portable device offered for payment for the transaction is the same as the portable device determined to be eligible to participate in the loyalty program.

19. The method of claim 14 wherein determining whether the cardholder is eligible to participate in the loyalty program further comprises:

checking whether the cardholder system includes a client loyalty component relating to the loyalty program.

20. The method of claim 14 wherein directing the merchant server to forward the transaction information to the cardholder system and redirect the cardholder system to communicate with the LMC and pass the transaction information to the LMC further comprises:

directing the merchant server to forward a call to the cardholder system; and

using the call to establish a communication session between the cardholder system and the LMC;

wherein the call includes the transaction information.

21. The method of claim 20 wherein the call includes a script.

22. The method of claim 14 wherein the transaction information includes item purchased by the cardholder in the transaction, purchase amount and merchant identification information relating to a merchant associated with the merchant server.

23. The method of claim 14 further comprising:

if the cardholder is determined to be eligible for two or more loyalty programs, directing the OPE to request the cardholder system to elect which one or more of the two or more loyalty programs are to apply for the transaction.

24. The method of claim 14 wherein the portable device includes at least one of a smartcard, a cellular phone, a personal digital assistant, a pager, a payment card, a security card, an access card, smart media and a transponder.

25. The method of claim 14 wherein the cardholder system includes at least one of a point-of-sale device, a cellular phone, a PDA, a computer, a handheld specialized reader, a set-top box, a kiosk, a security system, and an access system.

26. A method for handling a transaction in connection with a loyalty program using a system having a loyalty host, an open programming engine (OPE), a loyalty merchant component (LMC), a cardholder system and a merchant server, comprising:

directing the cardholder system to communicate with the LMC upon determining that a cardholder is eligible to participate in the loyalty program, the cardholder having a portable device, the portable device having stored thereon a device image, the device image including loyalty program information relating to the cardholder;

directing the cardholder system to forward transaction information relating to the transaction to the LMC;

forwarding the transaction information to the OPE;

directing the OPE to generate a transaction ID and linking the transaction ID to the transaction information;

using the LMC to pass the transaction ID from the OPE to the cardholder system;

directing the cardholder system to link the transaction ID received from the OPE with the device image retrieved from the portable device;

using the LMC to forward the linked transaction ID and device image from the cardholder system to the OPE;

directing the OPE to match the transaction information with the device image using the transaction ID;

directing the OPE to retrieve rules and logic pertaining to the loyalty program from the loyalty host based on the transaction information; and

directing the OPE to use the rules and logic to determine a loyalty amount for the transaction based on the transaction information and the matched device image.

27. The method of claim 26 further comprising:

using the LMC to forward information relating to the loyalty amount and the device image from the OPE to the merchant server;

directing the merchant server to seek approval of the transaction from the cardholder by displaying some or all of the forwarded information to the cardholder; and

directing the merchant server to process payment for the transaction upon receiving approval from the cardholder.

28. The method of claim 27 further comprising:

once payment is processed, using the LMC to forward processed payment information from the merchant server to the OPE; and

directing the OPE to instruct the cardholder system to update the portable device.

29. The method of claim 28 further comprising:

directing the cardholder system to display information relating to the updated portable device to the cardholder.

30. The method of claim 27 further comprising:

directing the merchant server to retrieve the device image from the cardholder system, the device image retrieved from the portable device offered by the cardholder for payment for the transaction; and

directing the merchant server to compare some or all of the device image retrieved from the cardholder system with some or all of the device image forwarded by the OPE to ensure that the portable device offered for payment for the transaction is the same as the portable device determined to be eligible to participate in the loyalty program.

31. The method of claim 26 wherein determining the cardholder is eligible to participate in the loyalty program further comprises:

checking whether the cardholder system includes a client loyalty component relating to the loyalty program.

32. The method of claim 26 wherein directing the cardholder system to forward transaction information relating to the transaction to the LMC further comprises:

directing the merchant server to forward a call to the cardholder system, the call including the transaction information;

using the call to establish a communication session between the cardholder system and the LMC; and

forwarding the transaction information from the cardholder system to the LMC during the communication session.

33. The method of claim 32 wherein the call includes a script.

34. The method of claim 26 wherein the transaction information includes item purchased by the cardholder in the transaction, purchase amount and merchant identification information relating to a merchant associated with the merchant server.

35. The method of claim 26 further comprising:

if the cardholder is determined to be eligible for two or more loyalty programs, directing the OPE to request the cardholder system to elect which one or more of the two or more loyalty programs are to apply for the transaction.

36. The method of claim 26 wherein the portable device includes at least one of a smartcard, a cellular phone, a personal digital assistant, a pager, a payment card, a security card, an access card, smart media and a transponder.

37. The method of claim 26 wherein the cardholder system includes at least one of a point-of-sale device, a cellular phone, a PDA, a computer, a handheld specialized reader, a set-top box, a kiosk, a security system, and an access system.

38. A system for processing a transaction under a loyalty program, comprising:

a loyalty host configured to maintain rules and logic relating to the loyalty program;

a cardholder system configured to retrieve and forward a device image from a portable device, the device image including portable device information and loyalty program information relating to a cardholder;

a merchant server configured to provide transaction information relating to the transaction;

an open programming engine (OPE) configured to retrieve the rules and logic relating to the loyalty program based on the transaction information and determine a loyalty amount for the transaction using the rules and logic and the device image; and

a loyalty merchant component (LMC) configured to facilitate interactions amongst the OPE, the cardholder system and the merchant server for purposes of processing the transaction under the loyalty program, wherein the OPE, cardholder system and merchant server are separate entities from each other and interact through the LMC.

39. The system of claim 38 wherein the LMC is further configured to:

receive the transaction information from the merchant server via the cardholder system;

forward the transaction information to the OPE to allow the OPE to generate a transaction ID linked to the transaction information;

forward the transaction ID from the OPE to the cardholder system to allow the device image to be linked to the transaction ID; and

forward the device image and the transaction ID from the cardholder system to the OPE to allow the OPE to match the transaction information to the device image.

40. The system of claim 38 wherein the LMC is further configured to forward information relating to the loyalty amount and the device image from the OPE to the merchant server to allow the merchant server to seek approval of the transaction from the cardholder system by displaying some or all of the forwarded information to the cardholder.

41. The system of claim 40 wherein the LMC is further configured to forward processed payment information from the merchant server to the OPE to allow the OPE to instruct the cardholder system to update the portable device.

42. The system of claim 38 wherein the portable device includes at least one of a smartcard, a cellular phone, a personal digital assistant, a pager, a payment card, a security card, an access card, smart media and a transponder.

43. The system of claim 38 wherein the cardholder system includes at least one of a point-of-sale device, a cellular phone, a PDA, a computer, a handheld specialized reader, a set-top box, a kiosk, a security system, and an access system.

Resources

Images & Drawings included:

Fig. 01 - Method and system for implementing a loyalty merchant component
Fig. 01
Fig. 02 - Method and system for implementing a loyalty merchant component
Fig. 02
Fig. 03 - Method and system for implementing a loyalty merchant component
Fig. 03

Sources:

Recent applications in this class:

Recent applications for this Assignee: