CA2422658A1 - System and method for transacting purchases with a cash vendor using points - Google Patents
System and method for transacting purchases with a cash vendor using points Download PDFInfo
- Publication number
- CA2422658A1 CA2422658A1 CA002422658A CA2422658A CA2422658A1 CA 2422658 A1 CA2422658 A1 CA 2422658A1 CA 002422658 A CA002422658 A CA 002422658A CA 2422658 A CA2422658 A CA 2422658A CA 2422658 A1 CA2422658 A1 CA 2422658A1
- Authority
- CA
- Canada
- Prior art keywords
- participant
- vendor
- purchase
- points
- api
- 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.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/20—Point-of-sale [POS] network systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
- G06Q30/0226—Incentive systems for frequent usage, e.g. frequent flyer miles programs or point systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S715/00—Data processing: presentation processing of document, operator interface processing, and screen saver display processing
- Y10S715/961—Operator interface with visual structure or function dictated by intended use
- Y10S715/962—Operator interface for marketing or sales
Abstract
A system for permitting a participant to transact a purchase using awarded points with a vendor system which transacts purchases in currency. A loyalty program awards points to the participant. The awarded points are maintained in a point account for the participant. An application programming interface (API) interfaces with the vendor system. A program account for use in currency transactions provides the basis for the purchase with the vendor system. A graphical user interface (GUI) provides an interface between the participant and the API and for communicating with the loyalty program.
Description
SYSTEM AND METHOD FOR T'RANSACTItNG PURCHASES
WITH A CASH VENDOR USING :POINTS
TECHNICAL FIELD OF THE INVENTION
The invention generally relates to a system and method for redeeming points ardd, in particular, to a system and method in which a participant of a program which awards points to the participant allows the participant to transact a purchase using the awarded points with a vendor system vrhich transacts purchases in currency.
BACKGROUND OF THE INVENTION
Customer incentive programs, such as loyalty programs, issue points to customers (i.e., participants) as a reward for certain activities such as the purchase of certain products or services or performing a certain action. These points create a loyalty or affinity with the customer and encourage the customer to continue a desired behavior. The customer is motivated through some type of reward offering which allows the customer to redeem the points for rewards. Frequently, such loyalty programs provide the customer with a limited listing of rewards from selected redemption vendors in the firm of merchandise, certificates, or other products or services (henceforth referred to as rewards) and the number of points needed to obtain one of the rewards from the list. In general, the selected redemption vendors are a limited number which have some type of relationship, contractual or otherwise, with the loyalty program. The cusl:omer selects a reward for purchase with the points and indicates to the loyalty program that the particular product or service has been selected. The loyalty program obtains the product or service on behalf of the customer from one of the limited number of selective redemption vendors and provides it to the customer. Some rewards are of a nature that human intervention is needed to redeem/fulfill a reward. For example, if the customer selects a roundtrip airline ticket, the loyalty program on behalf of the customer or the customer directly would purchase the ticket through a selected travel agent or a selected airline employee and provide the ticket (or have it sent) to the customer. The points needed to obtain the reward (e.g., the ticket) are deducted from the customer's point account by the agent or employee.
As such, when a customer wants to redeem points for "high-touch" rewards, the customer has to work through a third-party organization. There is an opportunity to eliminate the human intervention to redeem such rewards by allowing the customer to systematically redeem their points for rewards using redemption vendors that otherwise deal in currency.
SU1VI1VIAR~' ~F THE INVENTI~N
The invention addresses the above needs as well as others by providing a method and system for permitting a participant of a program to transact purchases with a currency vendor using points or a combination of points and currency rather than currency alone.
The invention particularly addresses the needs for permitting a loyalty program participant to purchase airline tickets by providing the ability for a system and method which integrates to the reservation system indicating what the participant is attempting to buy (redeem). In addition, it provides fulfillment capability without having to involve highly specialized third party organizations. The invention enables participants to get greater satisfaction and more immediate gratification from their loyalty program regardless of their preferred method of interaction.
In one form, the invention comprises a system for use by a participant of a program which awards points to the participant, wherein the awarded points are maintained in a point account for the participant. The system permits the participant to transact a purchase using the awarded points with a vendor system which transacts purchases in currency. An application programming interface (API) interfaces with the vendor system. The system also uses a program account for use in currency transactions.. A graphical user interface (GUI) provides an interface between the participant and the .API and communicates with the program. The GUI includes instructions for receiving participant-related information from the participant and providing the received participant-related information to the API.
The API is adapted to receive the participant-related information from the GUI
and adapted to provide the received participant-related information to the vendor system. T'he API is adapted to receive vendor-related information from th.e vendor system and adapted to provide the received vendor-related information to the GUI. The GUI
includes instructions for receiving vendor-related information from the API and for providing the received vendor-related information to the participant. From the perspective of the participant, the participant uses the GUI to conduct a purchase transaction with the vendor system based in whole or in part on the points in the participant's point account. From the perspective of the vendor system, the vendor system conducts the purchase transaction with the participant based on the program account.
In another form, the irmention is a method for use by a participant of a program which awards points to the participant, wherein the awarded points are maintained in a point account for the participant. The method permits the participant to transact a purchase using the awarded points with a vendor system which transacts purchases in currency. The method comprises the steps of providing an interface between the participant and the vendor system;
converting a purchase request from the participant based in whole or in part on points into a corresponding purchase request based cm a program account if the participant's account has sufficient points to cover the purchase; and causing the points for the purchase to be deducted from the participant's account in response to a received vendor purchase confirmation..
In another form, the invention is a graphical user interface for use by a participant of a program which awards points to the participant, wherein the awarded points are maintained in a point account for the participant. The interface permits the participant to transact a purchase using the awarded points with a vendor system which transacts purchases in currency. The interface comprises an applicati~an programming interface (API) for interfacing with the vendor system; a program account for use in currency transactions; and a graphical user interface (GUI) for providing an interface between the participant and the API and for communicating with the pro;;ram. The GUI
includes instructions for receiving participant-related information from the participant and providing the received participant-related information to the API. The API is adapted to receive the participant-related information from the GUI and to provide the received participant-related information to the vendor system. The API is adapted to receive vendor-related information from the vendor system and provide the received vendor-related information to the GUI. The GUI includes instructions for receiving vendor-related information from the API and providing the received vendor-related information to the participant. From the perspective of the participant, the participant uses the GUI to conduct a purchase transaction with the vendor system based in whole or in part on the points in the participant's point account. From the perspective of the vendor system, the vendor system conducts the purchase transaction with the participant based on the program account.
In another form, the invention is a system for permitting a participant to transact a purchase using awarded pointa with a vendor system which transacts purchases in currency, the system comprising:
a loyalty program which awards points to a participant, wherein the awarded points are maintained in a point account for the participant:
an application programming interface (API) for interfacing with the vendor system;
a program account for use in currency transactions; and a graphical user interface (GUI) for providing an interface between the participant and the API and for communicating vrith the program.
Other objects and features will be in part apparent arid in part pointed out hereinafter.
BRIEF DESCRIPTION OF TIIE DRAWINGS
FIGURE 1 is a block diagram of the system according to the invention.
FIGURE 2 is a flow diagram illustrating the flow of information between the participant, the GUI, the API and the vendor system according to the invention.
FIGURE 3 is an architecture overview in block diagram form of one system for implementing the invention.
FIGURES 4 and 5 are; flow charts of one preferred f.mbodiment of implementation of the system and method of the invention.
FIGURE SA is a flow chart of block 502 of Figure :5 which illustrates one preferred embodiment of the function of selecting an itinerary and presenting flight results.
FIGURE SB is a flow chart illustrating one preferred embodiment of the booking process 506 of the flow chart of Figure 5.
Corresponding reference characters indicate corresponding parts throughout the drawings.
DETAILED DESCRIPTION OF THE INVENTION
Figure 1 illustrates in block diagram form a system 100 according to one prefewed embodiment of the invention. A participant 102 is a member of a participant/customer incentive program such as a loyalty program 104 which inchzdes individual participant accounts 106 indicating the number of points that a participant has been awarded by the loyalty program. In one form, the loyalty program 104 monitors transactions 108 with the participant 102 and provides points to the participant's point account for completed transactions. For example, the loyalty program may reward. participants for purchases of widgets from a particular vendor or group of vendors. For Every dollar spent in purchasing a widget and completing a transaction, the participant would be awarded points which is added to the participant's point account.
From time-to-time, the participant 102 may use a communications link such as an Internet connection 110 to connect to a graphical user interface (GUI) 112 to access the loyalty program 104. In addition to checking the participant's point balance in the participant's account 106, the participant may check the rules of the loyalty program to determine how to obtain more points or to obtain the best use of points. In addition, the participant 102 may use the graphical user interface 112 to redeem points in the participant's account.
For example, suppose the participant 102 would like to purchase an airline ticket from an airline reservation system 114 using the points in the participant's account 10E>.
Suppose further that the airline reservation system 114 is a standard third party vendor that has no particular connection to the transactions 108 or to the loyalty program 104.
Suppose further that the airline reservation system 114 deals. in currency only such as credit card transactions only and that the website provides an application programming interface (API) for use by others who desire to transact business with the third-party vendor through the website 11.4. By using the graphical user interface 112, a participant can access the airline reservation system via an airline reservation system API 116 which provides an interface between the airline reservation system 114 and the graphical user interface 112. Through the interface, the participant 102 can select a particular airline ticket for purchase and advise the graphical user interface 112 that the participant would like to purchase the airline ticket which has been selected. The graphical user interface 112 would then interface with the loyalty program 104 and t:he participant's point account 106 to confirm that the participant has sufficient points in their point account to cover the desired purchase. Assuming there are suff eient points, the graphical user interface 112 completes the transaction on behalf of the participant 102 by using a program account such as a cash account or a shadow credit card 118. The cash account is referred to as a program account because it is connected to the loyalty program 104. The program account may be an account acceptable to website 114 including credit or debit cards or other means of payment.
For example, the interface 112 may use a credit carol which in the system 100 is referred to as a shadow credit card 118 because the credit card is hidden or "shadowed"
from the participant so that the participant is not aware that the transaction is actually being transacted using the shadow credit card or other program account 118.
Thus, the, interface completes the transaction via the API 116 and purchases the desired ticket for the participant from the website 114 using the credit card 118. The interface 1 I2 then advises the loyalty program 104 when the transaction has been completed so that the loyalty program can deduct the appropriate points from the particip'ant's point account 106 which appropriate points correspond to the amount of points needed to purchase the airline ticket in the first place. Finally, the participant 102 is noticed by l;he interface 112 of the completion of the purchase. In the case of an electronic ticket, the participant 102 would be sent a confirmation with the information relating to the ticket. In the event of a non-electronic ticket, the interface 112 would pass along the necessary participant information via the API 116 to the website 114 of the participant so that the website could arrange to have the ticket delivered or otherwise made available directly to the participant 102.
The system 100 as illustrated in Figure 1 also contemplates that other currency vendor systems 120 may be available to the participant 102 via the interface 112 and a corresponding vendor API 122 (supplied by the vendor) so that the participant can select other goods or services by which points can be used to purchase the goods or services.
For example, vendor system 120 rnay be a third party goods vendor on the Internet which vendor makes available its AF'I 122 so that the graphical user interface 112 may provide interface between the participant and the API 122 of the vendor system 120 All that is needed is the vendor API 122 so that the GUI 112 can interface with the vendor system 120.
In summary, Figure 1 illustrates system 100 for use by participants 102 of the loyalty program 104. The loyalty program 104 awards points to the participants wherein the awarded points are maintained in the participants' point account 106. The system 100 permits the participants I02 to transact a purchase using the awarded points with vendor systems 114, 120 which transacts purchases in currency. The transacted purchase occurs via GUI 112 and API 116 based on shadow credit card 118.
Alternatively, it is contemplated that the GUI 112 and the API 116 may be integrated into a single software package of instructions or that the loyalty program 104, GUI
112 and API 116 may be integrated or 'that the loyalty program and the GUI 112 may be integrated.
The above scenario assumes that the points in the account must be sufficient to pay for or cover the entire purchase of the reward, i.e., the airline ticket.
Generally, other scenarios are also contemplated. Far example, the system and method may be configured to allow the participant to select an amount of points to be used by the participant to pay for a portion of a particular transaction. In this case, the participant would be provided with the ability to supplement payment with their own currency or credit or debit card. As another example, the system and method may be configured to limit the amount of points to be used by the participant for a particular transaction. In this case, the participant would be required to supplement payment with their own currency or credit or debit card. As another example, suppose the participant has insufficient points to cover or pay for a particular reward. In this cask the system and method may be configured to allow the participant to select some or all of their points to be used by the participant to pay for a portion of a particular transaction and the participant would supplement payment with their own currency or credit or debit card. Those skilled in the art will recognize other scenarios as well.
In summary with regard to Figure 1, the system 100 includes the API 122 for interfacing with the currency vendor system 120, a program account for use in currency transactions such as the shadow credit card 118 and the graphical user interface 116 for providing an interface between the participant 102 and the API 122 and for communicating with the loyalty program 104. The GUI 116 includes instructions for receiving participant-related information from the participant via the Internet 110 or by other means and providing the received participant-related information to the API 122.
The API 122 is adapted to receive the participant-related information from the and provide the received participant-related information to the vendor system 120. In addition, the API 122 is adapted to receive the vendor-related information from the vendor system 120 and provide the received vendor-related information to the GUI 112.
In particular, the GUI 112 provides instructions for receiving the vendor-related information from the API 122 and providing the received vendor-related information to the participant 102 via the Internet or other means. Thus, from the perspective of the participant 102, the participant uses the GUI 112 to conduct a purchase transaction with the vendor system 120 using the points in the participant's account 106. Thus from the perspective of the vendor system 120, the vendor system conducts the purchase transaction with the participant 120 using the shadow credit card 118.
Figure 2 is a flow diagram illustrating the flow information between the participant 202 and the vendor system 208 via the interface including CiUI 204 and API
206. In addition, the GUI 204 interfaces with a loyalty program 210. In general, the provides participant-related information from the participant 202 to the API
206 and provides vendor-related information from the API 206 to the participant 202.
As illustrated in Figure 2, participant-related information generally flows left to right from the participant 202 to the vendor system 208 via the GUI 204 and API 206 whereas the vendor-related information generally flows right to left frorr~ the vendor system 208 to the participant 202 via the API 206 and GUI 204.
Participant-related information includes any participant information that originates from the participant such as a participant's name and address. Participant information also includes selections which the participant makes. For example, after the participant logs onto the GUI 204 and establishes their identity, a participant may indicate that he or she is interested in purchasing products or services from a particul;~r vendor system and that the participant is interested in using points to make such a purchase. The GUI 204 will transfer the participant information to the API 206 of the vendor system 208.
The API 206 in turn transfers the participant information to the vendor system 208. For example, if the participant 202 is interested in purchasing widgets, the participant information would include such an indication which is passed by the GUI 204 to the API 206 and then passed by the API 206 to the vendor system 208. In return, the vendor system 208 provides vendor-related information. Vendor-related information is a:ny vendor information that originates from the vendor. In this example, the vendor system 208 would provide a listing of the widgets available and the price of each. This vendor information would be provided via the API 206 to the GUI 204 which would then provide the vendor information to the participant 202. The participant 202 could select a particular class of widgets or request additional information with regard to a particular widget which request would be participant information passed via the GUI 204 via the API 206 to the vendor system 208. Once again, the system 208 would respond to the request from the participant and provide vendor information.
In this process of exchanging participant information from the participant 202 to the vendor system 208 via the GUI 204 and API 206 and in this process of exchanging vendor information from the vendor system 208 to the participant 202 via the API 206 and the GUI 204, the participant 202 may eventually determine that a particular product or service is of interest to the participant 202 for purchase. Thus, the participant information also includes a purchase request based on points, generally referred to by reference character 212. Essentially the participant 202 is requesting a purchase based on points in the participant's account 214, In one preferred embodiment according to the invention, the GUI 204 is implemented in software which includes instructions for receiving the purchase request 212 from the participant 202, which purchase request intends to conduct a purchase with the vendor system 208 based on the points in the participant's account 214. The GUI 204 converts the received purchase request x;12 into a corresponding purchase request 216 based on the shadow credit card 218. In order to accomplish this conversion, the GUI 204 communicates with the loyalty program 210 to determine the points that are available in thE; participant's point account 2:14. The purchase request 212 based on points is converted t:o a corresponding purchase request 216 based on the shadow credit card or other program account if the participant's point account 214 has sufficicnt points to cover the purchase requested by the participant. The GUI 204 provides the corresponding purchase request 216 based on the shadow credit card to the API
206. The API 206 performs its standard function of transmitting information to the vendor system 208 and in particular the API 206 is adapted to receive the corresponding purchase request 216 from the GUI 204 and provide the received corresponding purchase request 216 to the vendor system 20$.
In general, the vendor system 208 responds to the corresponding purchase request 216 based on the shadow credit card in the same way that it would respond to any other purchase request from a consumer that presents a credit card. Assuming that all the information to consummate the purchase has been provided to the vendor system 208, and assuming that the shadow credit card is validated, the vendor system 208 generates a vendor purchase confirmation 218. The API 206 is adapted to receive the vendor purchase confirmation 218 based on the shadow credit card and provide the received confirmation 218 to the GUI 204. In its software implementation, the GUI 204 includes instructions for receiving the vendor purchase confirmation 218 based on the shadow credit card. The GUI 204 also includes instructions for causing the points for the purchase to be deducted from the participant's point account 214 in response to the received vendor purchase confirmation 218 based on the; program account. In particular, the GUI 204 indicates to the loyalty program 210 the amount of points that have been used to complete the transaction. The GUI 204 also includes instructions for converting the received vendor purchase confirmation 2I8 based on the shadow credit card into a corresponding purchase confirmation 220 based on the points and instructions for providing to the participant 202 the corresponding purchase confirmatian 220 based on the points. This is in response to the received vendor purchase confirmation 218 based on the program account.
5 Referring to Figure 3, a diagram of the architectural view of one preferred embodiment of the system according to the invention is illustrated. A loyalty program database 302 includes information relating to the loyalty program including the listing of the accounts of the participants. In Figure 3, the architecture illustrates a GUI system 304 for interfacing with a SABRE host system 306. A participant 308 uses a core GUI
10 application 310 of the GUI system 304 via a com-link 312 and an API 314 to communicate with the SABRE host system 306. The GUI core application 310 also interfaces with an XML agent 316 to convert information provided by the SABRE
host system 306 into XML.
Figures 4 and 5 illustrate a flow diagram of the steps involved in a participant purchasing an airline ticket from a SABRE host 402. After .agreeing to terms and conditions at 404, the participant proceeds to search for flights by the steps generally referred to by arrow 406. If a flight is found at 408, the participant proceeds to make an itinerary selection at 502 of Figure S, which selection is illustrated in more detail in Figure SA. After the participant selects the desired itinerary, at 504, the participant proceeds to check out and complete the process. This includes actually booking the ticket as indicated by box 506 and illustrated in more detail in Figure SB.
The above discussion has generally been focused on purchase of goods or services in situations where the participant has sufficient points in their point account to cover the purchase. However, it is also contemplated that the participant could use their points to conduct a partial purchase so that the transaction may be based in whole or in part on th.e points in the participant's account. For example, some points may be applied to part of the purchase price and the remainder of the purchase could be paid for by the participant by their our credit or debit card, cash or other participant account. Thus, "purchase as used herein includes a partial purchase as well as a complete purchase. Sometimes, this partial purchase arrangement is structured as a discount to the participant. Also, in some configurations, it may be necessary or desirable to charge or transact the full purchase with the vendor site using the shadow credit card. In this case, the; portion of the purchase price paid for by the participant would be provided to the program or to the shadow credit card or other program account.
When introducing elements of the present invention or the preferred embodiments) thereof, the ar:~icles "a", "an", "the" and "said" are intended to mean that there are one or more of the elements. The terms "comprising", "including" and "having"
are intended to be inclusive and mean that there may be additional elements other than the listed elements.
In view of the above, it will be seen that the several objects of the invention are;
achieved and other advantageous results attained.
As various changes could be made in the above constructions, products, and methods without departing from the scope of the invention, it is intended that all matter contained in the above description and shown in the accompanying drawing shall be interpreted as illustrative and not in a limiting sense.
WITH A CASH VENDOR USING :POINTS
TECHNICAL FIELD OF THE INVENTION
The invention generally relates to a system and method for redeeming points ardd, in particular, to a system and method in which a participant of a program which awards points to the participant allows the participant to transact a purchase using the awarded points with a vendor system vrhich transacts purchases in currency.
BACKGROUND OF THE INVENTION
Customer incentive programs, such as loyalty programs, issue points to customers (i.e., participants) as a reward for certain activities such as the purchase of certain products or services or performing a certain action. These points create a loyalty or affinity with the customer and encourage the customer to continue a desired behavior. The customer is motivated through some type of reward offering which allows the customer to redeem the points for rewards. Frequently, such loyalty programs provide the customer with a limited listing of rewards from selected redemption vendors in the firm of merchandise, certificates, or other products or services (henceforth referred to as rewards) and the number of points needed to obtain one of the rewards from the list. In general, the selected redemption vendors are a limited number which have some type of relationship, contractual or otherwise, with the loyalty program. The cusl:omer selects a reward for purchase with the points and indicates to the loyalty program that the particular product or service has been selected. The loyalty program obtains the product or service on behalf of the customer from one of the limited number of selective redemption vendors and provides it to the customer. Some rewards are of a nature that human intervention is needed to redeem/fulfill a reward. For example, if the customer selects a roundtrip airline ticket, the loyalty program on behalf of the customer or the customer directly would purchase the ticket through a selected travel agent or a selected airline employee and provide the ticket (or have it sent) to the customer. The points needed to obtain the reward (e.g., the ticket) are deducted from the customer's point account by the agent or employee.
As such, when a customer wants to redeem points for "high-touch" rewards, the customer has to work through a third-party organization. There is an opportunity to eliminate the human intervention to redeem such rewards by allowing the customer to systematically redeem their points for rewards using redemption vendors that otherwise deal in currency.
SU1VI1VIAR~' ~F THE INVENTI~N
The invention addresses the above needs as well as others by providing a method and system for permitting a participant of a program to transact purchases with a currency vendor using points or a combination of points and currency rather than currency alone.
The invention particularly addresses the needs for permitting a loyalty program participant to purchase airline tickets by providing the ability for a system and method which integrates to the reservation system indicating what the participant is attempting to buy (redeem). In addition, it provides fulfillment capability without having to involve highly specialized third party organizations. The invention enables participants to get greater satisfaction and more immediate gratification from their loyalty program regardless of their preferred method of interaction.
In one form, the invention comprises a system for use by a participant of a program which awards points to the participant, wherein the awarded points are maintained in a point account for the participant. The system permits the participant to transact a purchase using the awarded points with a vendor system which transacts purchases in currency. An application programming interface (API) interfaces with the vendor system. The system also uses a program account for use in currency transactions.. A graphical user interface (GUI) provides an interface between the participant and the .API and communicates with the program. The GUI includes instructions for receiving participant-related information from the participant and providing the received participant-related information to the API.
The API is adapted to receive the participant-related information from the GUI
and adapted to provide the received participant-related information to the vendor system. T'he API is adapted to receive vendor-related information from th.e vendor system and adapted to provide the received vendor-related information to the GUI. The GUI
includes instructions for receiving vendor-related information from the API and for providing the received vendor-related information to the participant. From the perspective of the participant, the participant uses the GUI to conduct a purchase transaction with the vendor system based in whole or in part on the points in the participant's point account. From the perspective of the vendor system, the vendor system conducts the purchase transaction with the participant based on the program account.
In another form, the irmention is a method for use by a participant of a program which awards points to the participant, wherein the awarded points are maintained in a point account for the participant. The method permits the participant to transact a purchase using the awarded points with a vendor system which transacts purchases in currency. The method comprises the steps of providing an interface between the participant and the vendor system;
converting a purchase request from the participant based in whole or in part on points into a corresponding purchase request based cm a program account if the participant's account has sufficient points to cover the purchase; and causing the points for the purchase to be deducted from the participant's account in response to a received vendor purchase confirmation..
In another form, the invention is a graphical user interface for use by a participant of a program which awards points to the participant, wherein the awarded points are maintained in a point account for the participant. The interface permits the participant to transact a purchase using the awarded points with a vendor system which transacts purchases in currency. The interface comprises an applicati~an programming interface (API) for interfacing with the vendor system; a program account for use in currency transactions; and a graphical user interface (GUI) for providing an interface between the participant and the API and for communicating with the pro;;ram. The GUI
includes instructions for receiving participant-related information from the participant and providing the received participant-related information to the API. The API is adapted to receive the participant-related information from the GUI and to provide the received participant-related information to the vendor system. The API is adapted to receive vendor-related information from the vendor system and provide the received vendor-related information to the GUI. The GUI includes instructions for receiving vendor-related information from the API and providing the received vendor-related information to the participant. From the perspective of the participant, the participant uses the GUI to conduct a purchase transaction with the vendor system based in whole or in part on the points in the participant's point account. From the perspective of the vendor system, the vendor system conducts the purchase transaction with the participant based on the program account.
In another form, the invention is a system for permitting a participant to transact a purchase using awarded pointa with a vendor system which transacts purchases in currency, the system comprising:
a loyalty program which awards points to a participant, wherein the awarded points are maintained in a point account for the participant:
an application programming interface (API) for interfacing with the vendor system;
a program account for use in currency transactions; and a graphical user interface (GUI) for providing an interface between the participant and the API and for communicating vrith the program.
Other objects and features will be in part apparent arid in part pointed out hereinafter.
BRIEF DESCRIPTION OF TIIE DRAWINGS
FIGURE 1 is a block diagram of the system according to the invention.
FIGURE 2 is a flow diagram illustrating the flow of information between the participant, the GUI, the API and the vendor system according to the invention.
FIGURE 3 is an architecture overview in block diagram form of one system for implementing the invention.
FIGURES 4 and 5 are; flow charts of one preferred f.mbodiment of implementation of the system and method of the invention.
FIGURE SA is a flow chart of block 502 of Figure :5 which illustrates one preferred embodiment of the function of selecting an itinerary and presenting flight results.
FIGURE SB is a flow chart illustrating one preferred embodiment of the booking process 506 of the flow chart of Figure 5.
Corresponding reference characters indicate corresponding parts throughout the drawings.
DETAILED DESCRIPTION OF THE INVENTION
Figure 1 illustrates in block diagram form a system 100 according to one prefewed embodiment of the invention. A participant 102 is a member of a participant/customer incentive program such as a loyalty program 104 which inchzdes individual participant accounts 106 indicating the number of points that a participant has been awarded by the loyalty program. In one form, the loyalty program 104 monitors transactions 108 with the participant 102 and provides points to the participant's point account for completed transactions. For example, the loyalty program may reward. participants for purchases of widgets from a particular vendor or group of vendors. For Every dollar spent in purchasing a widget and completing a transaction, the participant would be awarded points which is added to the participant's point account.
From time-to-time, the participant 102 may use a communications link such as an Internet connection 110 to connect to a graphical user interface (GUI) 112 to access the loyalty program 104. In addition to checking the participant's point balance in the participant's account 106, the participant may check the rules of the loyalty program to determine how to obtain more points or to obtain the best use of points. In addition, the participant 102 may use the graphical user interface 112 to redeem points in the participant's account.
For example, suppose the participant 102 would like to purchase an airline ticket from an airline reservation system 114 using the points in the participant's account 10E>.
Suppose further that the airline reservation system 114 is a standard third party vendor that has no particular connection to the transactions 108 or to the loyalty program 104.
Suppose further that the airline reservation system 114 deals. in currency only such as credit card transactions only and that the website provides an application programming interface (API) for use by others who desire to transact business with the third-party vendor through the website 11.4. By using the graphical user interface 112, a participant can access the airline reservation system via an airline reservation system API 116 which provides an interface between the airline reservation system 114 and the graphical user interface 112. Through the interface, the participant 102 can select a particular airline ticket for purchase and advise the graphical user interface 112 that the participant would like to purchase the airline ticket which has been selected. The graphical user interface 112 would then interface with the loyalty program 104 and t:he participant's point account 106 to confirm that the participant has sufficient points in their point account to cover the desired purchase. Assuming there are suff eient points, the graphical user interface 112 completes the transaction on behalf of the participant 102 by using a program account such as a cash account or a shadow credit card 118. The cash account is referred to as a program account because it is connected to the loyalty program 104. The program account may be an account acceptable to website 114 including credit or debit cards or other means of payment.
For example, the interface 112 may use a credit carol which in the system 100 is referred to as a shadow credit card 118 because the credit card is hidden or "shadowed"
from the participant so that the participant is not aware that the transaction is actually being transacted using the shadow credit card or other program account 118.
Thus, the, interface completes the transaction via the API 116 and purchases the desired ticket for the participant from the website 114 using the credit card 118. The interface 1 I2 then advises the loyalty program 104 when the transaction has been completed so that the loyalty program can deduct the appropriate points from the particip'ant's point account 106 which appropriate points correspond to the amount of points needed to purchase the airline ticket in the first place. Finally, the participant 102 is noticed by l;he interface 112 of the completion of the purchase. In the case of an electronic ticket, the participant 102 would be sent a confirmation with the information relating to the ticket. In the event of a non-electronic ticket, the interface 112 would pass along the necessary participant information via the API 116 to the website 114 of the participant so that the website could arrange to have the ticket delivered or otherwise made available directly to the participant 102.
The system 100 as illustrated in Figure 1 also contemplates that other currency vendor systems 120 may be available to the participant 102 via the interface 112 and a corresponding vendor API 122 (supplied by the vendor) so that the participant can select other goods or services by which points can be used to purchase the goods or services.
For example, vendor system 120 rnay be a third party goods vendor on the Internet which vendor makes available its AF'I 122 so that the graphical user interface 112 may provide interface between the participant and the API 122 of the vendor system 120 All that is needed is the vendor API 122 so that the GUI 112 can interface with the vendor system 120.
In summary, Figure 1 illustrates system 100 for use by participants 102 of the loyalty program 104. The loyalty program 104 awards points to the participants wherein the awarded points are maintained in the participants' point account 106. The system 100 permits the participants I02 to transact a purchase using the awarded points with vendor systems 114, 120 which transacts purchases in currency. The transacted purchase occurs via GUI 112 and API 116 based on shadow credit card 118.
Alternatively, it is contemplated that the GUI 112 and the API 116 may be integrated into a single software package of instructions or that the loyalty program 104, GUI
112 and API 116 may be integrated or 'that the loyalty program and the GUI 112 may be integrated.
The above scenario assumes that the points in the account must be sufficient to pay for or cover the entire purchase of the reward, i.e., the airline ticket.
Generally, other scenarios are also contemplated. Far example, the system and method may be configured to allow the participant to select an amount of points to be used by the participant to pay for a portion of a particular transaction. In this case, the participant would be provided with the ability to supplement payment with their own currency or credit or debit card. As another example, the system and method may be configured to limit the amount of points to be used by the participant for a particular transaction. In this case, the participant would be required to supplement payment with their own currency or credit or debit card. As another example, suppose the participant has insufficient points to cover or pay for a particular reward. In this cask the system and method may be configured to allow the participant to select some or all of their points to be used by the participant to pay for a portion of a particular transaction and the participant would supplement payment with their own currency or credit or debit card. Those skilled in the art will recognize other scenarios as well.
In summary with regard to Figure 1, the system 100 includes the API 122 for interfacing with the currency vendor system 120, a program account for use in currency transactions such as the shadow credit card 118 and the graphical user interface 116 for providing an interface between the participant 102 and the API 122 and for communicating with the loyalty program 104. The GUI 116 includes instructions for receiving participant-related information from the participant via the Internet 110 or by other means and providing the received participant-related information to the API 122.
The API 122 is adapted to receive the participant-related information from the and provide the received participant-related information to the vendor system 120. In addition, the API 122 is adapted to receive the vendor-related information from the vendor system 120 and provide the received vendor-related information to the GUI 112.
In particular, the GUI 112 provides instructions for receiving the vendor-related information from the API 122 and providing the received vendor-related information to the participant 102 via the Internet or other means. Thus, from the perspective of the participant 102, the participant uses the GUI 112 to conduct a purchase transaction with the vendor system 120 using the points in the participant's account 106. Thus from the perspective of the vendor system 120, the vendor system conducts the purchase transaction with the participant 120 using the shadow credit card 118.
Figure 2 is a flow diagram illustrating the flow information between the participant 202 and the vendor system 208 via the interface including CiUI 204 and API
206. In addition, the GUI 204 interfaces with a loyalty program 210. In general, the provides participant-related information from the participant 202 to the API
206 and provides vendor-related information from the API 206 to the participant 202.
As illustrated in Figure 2, participant-related information generally flows left to right from the participant 202 to the vendor system 208 via the GUI 204 and API 206 whereas the vendor-related information generally flows right to left frorr~ the vendor system 208 to the participant 202 via the API 206 and GUI 204.
Participant-related information includes any participant information that originates from the participant such as a participant's name and address. Participant information also includes selections which the participant makes. For example, after the participant logs onto the GUI 204 and establishes their identity, a participant may indicate that he or she is interested in purchasing products or services from a particul;~r vendor system and that the participant is interested in using points to make such a purchase. The GUI 204 will transfer the participant information to the API 206 of the vendor system 208.
The API 206 in turn transfers the participant information to the vendor system 208. For example, if the participant 202 is interested in purchasing widgets, the participant information would include such an indication which is passed by the GUI 204 to the API 206 and then passed by the API 206 to the vendor system 208. In return, the vendor system 208 provides vendor-related information. Vendor-related information is a:ny vendor information that originates from the vendor. In this example, the vendor system 208 would provide a listing of the widgets available and the price of each. This vendor information would be provided via the API 206 to the GUI 204 which would then provide the vendor information to the participant 202. The participant 202 could select a particular class of widgets or request additional information with regard to a particular widget which request would be participant information passed via the GUI 204 via the API 206 to the vendor system 208. Once again, the system 208 would respond to the request from the participant and provide vendor information.
In this process of exchanging participant information from the participant 202 to the vendor system 208 via the GUI 204 and API 206 and in this process of exchanging vendor information from the vendor system 208 to the participant 202 via the API 206 and the GUI 204, the participant 202 may eventually determine that a particular product or service is of interest to the participant 202 for purchase. Thus, the participant information also includes a purchase request based on points, generally referred to by reference character 212. Essentially the participant 202 is requesting a purchase based on points in the participant's account 214, In one preferred embodiment according to the invention, the GUI 204 is implemented in software which includes instructions for receiving the purchase request 212 from the participant 202, which purchase request intends to conduct a purchase with the vendor system 208 based on the points in the participant's account 214. The GUI 204 converts the received purchase request x;12 into a corresponding purchase request 216 based on the shadow credit card 218. In order to accomplish this conversion, the GUI 204 communicates with the loyalty program 210 to determine the points that are available in thE; participant's point account 2:14. The purchase request 212 based on points is converted t:o a corresponding purchase request 216 based on the shadow credit card or other program account if the participant's point account 214 has sufficicnt points to cover the purchase requested by the participant. The GUI 204 provides the corresponding purchase request 216 based on the shadow credit card to the API
206. The API 206 performs its standard function of transmitting information to the vendor system 208 and in particular the API 206 is adapted to receive the corresponding purchase request 216 from the GUI 204 and provide the received corresponding purchase request 216 to the vendor system 20$.
In general, the vendor system 208 responds to the corresponding purchase request 216 based on the shadow credit card in the same way that it would respond to any other purchase request from a consumer that presents a credit card. Assuming that all the information to consummate the purchase has been provided to the vendor system 208, and assuming that the shadow credit card is validated, the vendor system 208 generates a vendor purchase confirmation 218. The API 206 is adapted to receive the vendor purchase confirmation 218 based on the shadow credit card and provide the received confirmation 218 to the GUI 204. In its software implementation, the GUI 204 includes instructions for receiving the vendor purchase confirmation 218 based on the shadow credit card. The GUI 204 also includes instructions for causing the points for the purchase to be deducted from the participant's point account 214 in response to the received vendor purchase confirmation 218 based on the; program account. In particular, the GUI 204 indicates to the loyalty program 210 the amount of points that have been used to complete the transaction. The GUI 204 also includes instructions for converting the received vendor purchase confirmation 2I8 based on the shadow credit card into a corresponding purchase confirmation 220 based on the points and instructions for providing to the participant 202 the corresponding purchase confirmatian 220 based on the points. This is in response to the received vendor purchase confirmation 218 based on the program account.
5 Referring to Figure 3, a diagram of the architectural view of one preferred embodiment of the system according to the invention is illustrated. A loyalty program database 302 includes information relating to the loyalty program including the listing of the accounts of the participants. In Figure 3, the architecture illustrates a GUI system 304 for interfacing with a SABRE host system 306. A participant 308 uses a core GUI
10 application 310 of the GUI system 304 via a com-link 312 and an API 314 to communicate with the SABRE host system 306. The GUI core application 310 also interfaces with an XML agent 316 to convert information provided by the SABRE
host system 306 into XML.
Figures 4 and 5 illustrate a flow diagram of the steps involved in a participant purchasing an airline ticket from a SABRE host 402. After .agreeing to terms and conditions at 404, the participant proceeds to search for flights by the steps generally referred to by arrow 406. If a flight is found at 408, the participant proceeds to make an itinerary selection at 502 of Figure S, which selection is illustrated in more detail in Figure SA. After the participant selects the desired itinerary, at 504, the participant proceeds to check out and complete the process. This includes actually booking the ticket as indicated by box 506 and illustrated in more detail in Figure SB.
The above discussion has generally been focused on purchase of goods or services in situations where the participant has sufficient points in their point account to cover the purchase. However, it is also contemplated that the participant could use their points to conduct a partial purchase so that the transaction may be based in whole or in part on th.e points in the participant's account. For example, some points may be applied to part of the purchase price and the remainder of the purchase could be paid for by the participant by their our credit or debit card, cash or other participant account. Thus, "purchase as used herein includes a partial purchase as well as a complete purchase. Sometimes, this partial purchase arrangement is structured as a discount to the participant. Also, in some configurations, it may be necessary or desirable to charge or transact the full purchase with the vendor site using the shadow credit card. In this case, the; portion of the purchase price paid for by the participant would be provided to the program or to the shadow credit card or other program account.
When introducing elements of the present invention or the preferred embodiments) thereof, the ar:~icles "a", "an", "the" and "said" are intended to mean that there are one or more of the elements. The terms "comprising", "including" and "having"
are intended to be inclusive and mean that there may be additional elements other than the listed elements.
In view of the above, it will be seen that the several objects of the invention are;
achieved and other advantageous results attained.
As various changes could be made in the above constructions, products, and methods without departing from the scope of the invention, it is intended that all matter contained in the above description and shown in the accompanying drawing shall be interpreted as illustrative and not in a limiting sense.
Claims (17)
1. A system for use by a participant of a program which awards points to the participant, wherein the awarded points are maintained in a point account for the participant, said system for permitting the participant to transact a purchase using the awarded points with a vendor system which transacts purchases in currency, said system comprising:
an application programming interface (API) for interfacing with the vendor system a program account for use in currency transactions;
a graphical user interface (GUI) for providing an interface between the participant and the API and for communicating with the program;
wherein said GUI includes instructions for receiving participant-related information from the participant and providing the received participant-related information to the API;
wherein said API is adapted to receive the participant-related information from the GUI and adapted to provide the received participant-related information to the vendor system;
wherein said API is adapted to receive vendor-related information from the vendor system and adapted to provide the received vendor-related information to the GUI; and wherein said GUI includes instructions for receiving vendor-related information from the API and for providing the received vendor-related information to the participant;
whereby, from the perspective of the participant, the participant uses the GUI
to conduct a purchase transaction with the vendor system based in whole or in part on the points in the participant's point account; and whereby, from the perspective of the vendor system, the vendor system conducts the purchase transaction with the participant based on the program account.
an application programming interface (API) for interfacing with the vendor system a program account for use in currency transactions;
a graphical user interface (GUI) for providing an interface between the participant and the API and for communicating with the program;
wherein said GUI includes instructions for receiving participant-related information from the participant and providing the received participant-related information to the API;
wherein said API is adapted to receive the participant-related information from the GUI and adapted to provide the received participant-related information to the vendor system;
wherein said API is adapted to receive vendor-related information from the vendor system and adapted to provide the received vendor-related information to the GUI; and wherein said GUI includes instructions for receiving vendor-related information from the API and for providing the received vendor-related information to the participant;
whereby, from the perspective of the participant, the participant uses the GUI
to conduct a purchase transaction with the vendor system based in whole or in part on the points in the participant's point account; and whereby, from the perspective of the vendor system, the vendor system conducts the purchase transaction with the participant based on the program account.
2. The system of claim 1 wherein the GUI includes instructions for:
receiving a purchase request from the participant to conduct a purchase with the vendor system based on the points in the participant's point account;
converting the received purchase request based on the points into a corresponding purchase request based on the point account if the point account has sufficient points to cover the purchase; and providing the corresponding purchase request based on the program account to the API wherein the API is adapted to receive the corresponding purchase request from the GUI and provide the received corresponding purchase request to the vendor system.
receiving a purchase request from the participant to conduct a purchase with the vendor system based on the points in the participant's point account;
converting the received purchase request based on the points into a corresponding purchase request based on the point account if the point account has sufficient points to cover the purchase; and providing the corresponding purchase request based on the program account to the API wherein the API is adapted to receive the corresponding purchase request from the GUI and provide the received corresponding purchase request to the vendor system.
3. The system of claim 1 wherein the API is adapted to receive a vendor purchase confirmation based on the program account and provide the; received confirmation based on the program account to the GUI, and wherein the GUI includes instructions for:
receiving the vendor purchase confirmation based on the program account from the API;
causing the points for the purchase to be deducted from the participant's point account in response to the received vendor purchase confirmation based on the program account;
converting the received vendor purchase confirmation based on the program account into a corresponding purchase confirmation based on the points;
and providing the corresponding purchase confirmation based on the points to the participant in response to the received vendor purchase confirmation based on the program account.
receiving the vendor purchase confirmation based on the program account from the API;
causing the points for the purchase to be deducted from the participant's point account in response to the received vendor purchase confirmation based on the program account;
converting the received vendor purchase confirmation based on the program account into a corresponding purchase confirmation based on the points;
and providing the corresponding purchase confirmation based on the points to the participant in response to the received vendor purchase confirmation based on the program account.
4. The system of claim 1 wherein the program is a loyalty program and wherein the program account is a shadow credit card.
5. A method for use by a participant of a program which awards points to the participant, wherein the awarded points are maintained in a :point account for the participant, said method permitting the participant to transact a purchase using the awarded points with a vendor system which transacts purchases in currency said method comprising the steps of providing an interface between the participant and the vendor system;
converting a purchase request from the participant based in whole or in part on points into a corresponding purchase request based on a program account if the participant's account has sufficient points to cover the purchase; and causing the points for the purchase to be deducted from the participant's account in response to a received vendor purchase confirmation.
converting a purchase request from the participant based in whole or in part on points into a corresponding purchase request based on a program account if the participant's account has sufficient points to cover the purchase; and causing the points for the purchase to be deducted from the participant's account in response to a received vendor purchase confirmation.
6. The method of claim 5 wherein the interface comprises a graphical user interface (GUI) and a application programming interface (API) for the vendor system and:
wherein said GUI includes instructions for receiving participant-related information from the participant and providing the received participant-related information to the API;
wherein said API is adapted to receive the participant-related information from the GUI and to provide the received participant-related information to the vendor system;
wherein said API is adapted to receive vendor-related information from the vendor system and provide the received vendor-related information. to the GUI; and wherein said GUI includes instructions for receiving; vendor-related information from the API and providing the received vendor-related information to the participant;
whereby, from the perspective of the participaixt, the participant uses the GUI to conduct a purchase transaction with the vendor system based on the points in the participant's point account; and whereby, from the perspective of the vendor system, the vendor system conducts the purchase transaction with the participant based on the program account.
wherein said GUI includes instructions for receiving participant-related information from the participant and providing the received participant-related information to the API;
wherein said API is adapted to receive the participant-related information from the GUI and to provide the received participant-related information to the vendor system;
wherein said API is adapted to receive vendor-related information from the vendor system and provide the received vendor-related information. to the GUI; and wherein said GUI includes instructions for receiving; vendor-related information from the API and providing the received vendor-related information to the participant;
whereby, from the perspective of the participaixt, the participant uses the GUI to conduct a purchase transaction with the vendor system based on the points in the participant's point account; and whereby, from the perspective of the vendor system, the vendor system conducts the purchase transaction with the participant based on the program account.
7. The method of claim 6 wherein the GUI includes instructions for:
receiving a purchase request from the participant to conduct a purchase with the vendor system based on the points in the participant's point account;
converting the received purchase request based on the points into a corresponding purchase request based on the point account if the point account has sufficient points to cover the purchase; and providing the corresponding purchase request based on the program account to the API wherein the API is adapted to receive the corresponding purchase request from the GUI and provide the received corresponding purchase request to the vendor system.
receiving a purchase request from the participant to conduct a purchase with the vendor system based on the points in the participant's point account;
converting the received purchase request based on the points into a corresponding purchase request based on the point account if the point account has sufficient points to cover the purchase; and providing the corresponding purchase request based on the program account to the API wherein the API is adapted to receive the corresponding purchase request from the GUI and provide the received corresponding purchase request to the vendor system.
8. The method of claim 7 wherein the API is adapted to receive a vendor purchase confirmation based on the program account and provide the received confirmation based on the program account to the GUI, and wherein the GUI includes instructions for:
receiving the vendor purchase confirmation based on the program account from the API;
causing the points for the purchase to be deducted from the participant's point account in response to the received vendor purchase confirmation based on the program account;
converting the received vendor purchase confirmation based on the program account into a corresponding purchase confirmation based on the points;
and providing the corresponding purchase confirmation based on the points to the participant in response to the received vendor purchase confirmation based on the program account.
receiving the vendor purchase confirmation based on the program account from the API;
causing the points for the purchase to be deducted from the participant's point account in response to the received vendor purchase confirmation based on the program account;
converting the received vendor purchase confirmation based on the program account into a corresponding purchase confirmation based on the points;
and providing the corresponding purchase confirmation based on the points to the participant in response to the received vendor purchase confirmation based on the program account.
9. The method of claim 5 wherein the program is a loyalty program and wherein the program account is a shadow credit card.
10. A graphical user interface for use by a participant of a program which awards points to the participant, wherein the awarded points are maintained in a point account for the participant, said interface for permitting the participant to transact a purchase using the awarded points with a vendor system which transacts purchases in currency, said interface comprising:
an application prograrnrning interface (API) for interfacing with the vendor system;
a program account for use in currency transactions;
a graphical user interface (GUI) for providing an interface between the participant and the API and for communicating with the program;
wherein said GUI includes instructions for receiving participant-related information from the participant and providing the received ;participant-related information to the API;
wherein said API is adapted to receive the participant-related information from the GUI and to provide the received participant-related information to the vendor system;
wherein said API is adapted to receive vendor-related information from the vendor system and provide the received vendor-related information to the GUI; and wherein said GUI includes instructions for receiving vendor-related information from the API and providing the received vendor-related information to the participant;
whereby, from the perspective of the participant, the participant uses the GUI
to conduct a purchase transaction with the vendor system based in whole or in part on the points in the participant's point account; and whereby, from the perspective of the vendor system, the vendor system conducts the purchase transaction with the participant based on the program account.
an application prograrnrning interface (API) for interfacing with the vendor system;
a program account for use in currency transactions;
a graphical user interface (GUI) for providing an interface between the participant and the API and for communicating with the program;
wherein said GUI includes instructions for receiving participant-related information from the participant and providing the received ;participant-related information to the API;
wherein said API is adapted to receive the participant-related information from the GUI and to provide the received participant-related information to the vendor system;
wherein said API is adapted to receive vendor-related information from the vendor system and provide the received vendor-related information to the GUI; and wherein said GUI includes instructions for receiving vendor-related information from the API and providing the received vendor-related information to the participant;
whereby, from the perspective of the participant, the participant uses the GUI
to conduct a purchase transaction with the vendor system based in whole or in part on the points in the participant's point account; and whereby, from the perspective of the vendor system, the vendor system conducts the purchase transaction with the participant based on the program account.
11. The interface of claim 10 wherein the GUI includes instructions for:
receiving a purchase request from the participant to conduct a purchase with the vendor system based on the points in the participant's point account;
converting the received purchase request based on the points into a corresponding purchase request based on the point account if the point account has sufficient points to cover the purchase; and providing the corresponding purchase request based on the program account to the API wherein the API is adapted to receive the corresponding purchase request from the GUI and provide the received corresponding purchase request to the vendor system.
receiving a purchase request from the participant to conduct a purchase with the vendor system based on the points in the participant's point account;
converting the received purchase request based on the points into a corresponding purchase request based on the point account if the point account has sufficient points to cover the purchase; and providing the corresponding purchase request based on the program account to the API wherein the API is adapted to receive the corresponding purchase request from the GUI and provide the received corresponding purchase request to the vendor system.
12. The interface of claim 10 wherein the API is adapted to receive a vendor purchase confirmation based on the program account and provide the received confirmation based on the program account to the GUI, and wherein the GUI
includes instructions for:
receiving the vendor purchase confirmation based on the program account from the API;
causing the points for the purchase to be deducted from the participant's point account in response to the received vendor purchase confirmation based on the program account;
converting the received vendor purchase confirmation based on the program account into a corresponding purchase confirmation based on the points;
and providing the corresponding purchase confirmation based in whole or in part on the points to the participant in response to the received vendor purchase confirmation based on the program account.
includes instructions for:
receiving the vendor purchase confirmation based on the program account from the API;
causing the points for the purchase to be deducted from the participant's point account in response to the received vendor purchase confirmation based on the program account;
converting the received vendor purchase confirmation based on the program account into a corresponding purchase confirmation based on the points;
and providing the corresponding purchase confirmation based in whole or in part on the points to the participant in response to the received vendor purchase confirmation based on the program account.
13. The interface of claim 10 wherein the program is a loyalty program and wherein the program account is a shadow credit card.
14. A system for permitting a participant to transact a purchase using awarded points with a vendor system which transacts purchases in currency, said system comprising:
a loyalty program which awards points to a participant, wherein the awarded points are maintained in a point account for the participant;
an application programming interface (API) for interfacing with the vendor system;
a program account for use in currency transactions;
a graphical user interface (GUI) for providing an interface between the participant and the API and for communicating with the program;
wherein said GUI includes instructions for receiving participant-related information from the participant and providing the received participant-related information to the API;
wherein said API is adapted to receive the participant-related information from the GUI and to provide the received participant-related information to the vendor system;
wherein said API is adapted to receive vendor-related information from the vendor system and provide the received vendor-related information to the GUI; and wherein said GUI includes instructions for receiving vendor-related information from the API and providing the received vendor-related information to the participant;
whereby, from the perspective of the participant, the participant uses the GUI
to conduct a purchase transaction with the vendor system based in whole or in part on the points in the participant's point account; and whereby, from the perspective of the vendor system, the vendor system conducts the purchase transaction with the participant based on the program account.
a loyalty program which awards points to a participant, wherein the awarded points are maintained in a point account for the participant;
an application programming interface (API) for interfacing with the vendor system;
a program account for use in currency transactions;
a graphical user interface (GUI) for providing an interface between the participant and the API and for communicating with the program;
wherein said GUI includes instructions for receiving participant-related information from the participant and providing the received participant-related information to the API;
wherein said API is adapted to receive the participant-related information from the GUI and to provide the received participant-related information to the vendor system;
wherein said API is adapted to receive vendor-related information from the vendor system and provide the received vendor-related information to the GUI; and wherein said GUI includes instructions for receiving vendor-related information from the API and providing the received vendor-related information to the participant;
whereby, from the perspective of the participant, the participant uses the GUI
to conduct a purchase transaction with the vendor system based in whole or in part on the points in the participant's point account; and whereby, from the perspective of the vendor system, the vendor system conducts the purchase transaction with the participant based on the program account.
15. The system of claim 14 wherein the GUI includes instructions for:
receiving a purchase request from the participant to conduct a purchase with the vendor system based on the points in the participant's point account;
converting the received purchase request based on the points into a corresponding purchase request based on the point account if the point account has sufficient points to cover the purchase; and providing the corresponding purchase request based. on the program account to the API wherein the API is adapted to receive the corresponding purchase request from the GUI and provide the received corresponding purchase request to the vendor system.
receiving a purchase request from the participant to conduct a purchase with the vendor system based on the points in the participant's point account;
converting the received purchase request based on the points into a corresponding purchase request based on the point account if the point account has sufficient points to cover the purchase; and providing the corresponding purchase request based. on the program account to the API wherein the API is adapted to receive the corresponding purchase request from the GUI and provide the received corresponding purchase request to the vendor system.
16. The system of claim 14 wherein the API is adapted to receive a vendor purchase confirmation based on the program account and provide the received confirmation based on the program account to the GUI, and wherein the GUI
includes instructions for:
receiving the vendor purchase confirmation based on the program account from the API;
causing the points for the purchase to be deducted from the participant's point account in response to the received vendor purchase confirmation based on the program account;
converting the received vendor purchase confirmation based on the program account into a corresponding purchase confirmation based on the points;
and providing the corresponding purchase confirmation based on the points to the participant in response to the received vendor purchase confirmation based on the program account.
includes instructions for:
receiving the vendor purchase confirmation based on the program account from the API;
causing the points for the purchase to be deducted from the participant's point account in response to the received vendor purchase confirmation based on the program account;
converting the received vendor purchase confirmation based on the program account into a corresponding purchase confirmation based on the points;
and providing the corresponding purchase confirmation based on the points to the participant in response to the received vendor purchase confirmation based on the program account.
17. The system of claim 14 wherein the program account is a shadow credit card.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US10/117,309 | 2002-04-05 | ||
| US10/117,309 US7134087B2 (en) | 2002-04-05 | 2002-04-05 | System and method for transacting purchases with a cash vendor using points |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2422658A1 true CA2422658A1 (en) | 2003-10-05 |
Family
ID=29248199
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002422658A Abandoned CA2422658A1 (en) | 2002-04-05 | 2003-03-19 | System and method for transacting purchases with a cash vendor using points |
Country Status (2)
| Country | Link |
|---|---|
| US (1) | US7134087B2 (en) |
| CA (1) | CA2422658A1 (en) |
Families Citing this family (72)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7249112B2 (en) * | 2002-07-09 | 2007-07-24 | American Express Travel Related Services Company, Inc. | System and method for assigning a funding source for a radio frequency identification device |
| US7680688B2 (en) * | 2002-05-28 | 2010-03-16 | American Express Travel Related Services Company, Inc. | System and method for exchanging loyalty points for acquisitions |
| US8108231B2 (en) | 2002-06-14 | 2012-01-31 | The Crawford Group, Inc. | Method and apparatus for improved customer direct on-line reservation of rental vehicles |
| US20040039612A1 (en) | 2002-06-14 | 2004-02-26 | Neil Fitzgerald | Method and apparatus for customer direct on-line reservation of rental vehicles |
| US20050144071A1 (en) * | 2003-09-30 | 2005-06-30 | Jay Monahan | Method and apparatus to facilitate the electronic accumulation and redemption of a value in an account |
| US20050165641A1 (en) * | 2003-10-27 | 2005-07-28 | Chu Peter Z. | Method and system to associate a gift certificate with an email address |
| US8005714B2 (en) | 2004-02-02 | 2011-08-23 | David Shaw | System and method for providing a discount |
| US7925533B2 (en) * | 2004-02-02 | 2011-04-12 | Destination Rewards, Inc. | System and method for providing a discount |
| US8676614B2 (en) * | 2004-03-12 | 2014-03-18 | Amr Corporation | Automated airlines reservations system |
| WO2005098702A2 (en) * | 2004-03-26 | 2005-10-20 | Citicorp Credit Services, Inc. | Methods and systems for integration of multiple rewards programs |
| US8271309B2 (en) | 2006-03-16 | 2012-09-18 | The Crawford Group, Inc. | Method and system for providing and administering online rental vehicle reservation booking services |
| US7591419B2 (en) * | 2006-03-28 | 2009-09-22 | HSBC Card Services Inc. | User selectable functionality facilitator |
| US10062062B1 (en) | 2006-05-25 | 2018-08-28 | Jbshbm, Llc | Automated teller machine (ATM) providing money for loyalty points |
| 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 |
| 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 |
| US8126773B2 (en) * | 2006-07-27 | 2012-02-28 | Oracle International Corporation | Configurable enrollment data capture framework |
| US7837099B2 (en) * | 2006-07-27 | 2010-11-23 | Oracle International Corporation | Partner account debit process |
| US7562810B2 (en) * | 2006-07-27 | 2009-07-21 | Oracle International Corporation | Method and system for enabling multiple payment options in loyalty program transactions |
| US20080027797A1 (en) * | 2006-07-31 | 2008-01-31 | Oracle International Corporation | Management of package offerings by loyalty programs and automation of accrual recalculation |
| US8515840B2 (en) | 2007-10-02 | 2013-08-20 | American Express Travel Related Services Company, Inc. | Modular electronic wallet |
| US9747598B2 (en) | 2007-10-02 | 2017-08-29 | Iii Holdings 1, Llc | Dynamic security code push |
| US8622308B1 (en) | 2007-12-31 | 2014-01-07 | Jpmorgan Chase Bank, N.A. | System and method for processing transactions using a multi-account transactions device |
| CA2736215A1 (en) * | 2008-09-04 | 2010-03-11 | Mastercard International Incorporated | System and method for performing a real time redemption transaction by leveraging a payment network |
| US20100145786A1 (en) * | 2008-12-06 | 2010-06-10 | Fordyce Iii Edward W | Loyalty program service |
| US20100145778A1 (en) * | 2008-12-08 | 2010-06-10 | Fordyce Iii Edward W | Consumer commercial behavior modification through multiple merchant incentive program |
| US8831976B2 (en) * | 2009-01-22 | 2014-09-09 | Maritz Holdings Inc. | System and method for transacting purchases with a cash vendor using points and a virtual credit card |
| US20100191652A1 (en) * | 2009-01-23 | 2010-07-29 | Eckert Daniel J | Systems and methods for adding functionality to a uis for use at a point of interaction |
| US9721238B2 (en) | 2009-02-13 | 2017-08-01 | Visa U.S.A. Inc. | Point of interaction loyalty currency redemption in a transaction |
| US9031859B2 (en) | 2009-05-21 | 2015-05-12 | Visa U.S.A. Inc. | Rebate automation |
| US8463706B2 (en) | 2009-08-24 | 2013-06-11 | Visa U.S.A. Inc. | Coupon bearing sponsor account transaction authorization |
| US10089606B2 (en) | 2011-02-11 | 2018-10-02 | Bytemark, Inc. | System and method for trusted mobile device payment |
| US20120296826A1 (en) | 2011-05-18 | 2012-11-22 | Bytemark, Inc. | Method and system for distributing electronic tickets with visual display |
| US10453067B2 (en) | 2011-03-11 | 2019-10-22 | Bytemark, Inc. | Short range wireless translation methods and systems for hands-free fare validation |
| US8494967B2 (en) * | 2011-03-11 | 2013-07-23 | Bytemark, Inc. | Method and system for distributing electronic tickets with visual display |
| US10762733B2 (en) | 2013-09-26 | 2020-09-01 | Bytemark, Inc. | Method and system for electronic ticket validation using proximity detection |
| US10360567B2 (en) | 2011-03-11 | 2019-07-23 | Bytemark, Inc. | Method and system for distributing electronic tickets with data integrity checking |
| US20120296720A1 (en) * | 2011-05-17 | 2012-11-22 | Maritz Holdings Inc. | Mobile rewards redemption system and method |
| US10558995B2 (en) * | 2011-07-29 | 2020-02-11 | Ncr Corporation | Value management system |
| US10223707B2 (en) | 2011-08-19 | 2019-03-05 | Visa International Service Association | Systems and methods to communicate offer options via messaging in real time with processing of payment transaction |
| US10360578B2 (en) | 2012-01-30 | 2019-07-23 | Visa International Service Association | Systems and methods to process payments based on payment deals |
| US9460436B2 (en) | 2012-03-16 | 2016-10-04 | Visa International Service Association | Systems and methods to apply the benefit of offers via a transaction handler |
| US8880431B2 (en) | 2012-03-16 | 2014-11-04 | Visa International Service Association | Systems and methods to generate a receipt for a transaction |
| US9922338B2 (en) | 2012-03-23 | 2018-03-20 | Visa International Service Association | Systems and methods to apply benefit of offers |
| US9495690B2 (en) | 2012-04-04 | 2016-11-15 | Visa International Service Association | Systems and methods to process transactions and offers via a gateway |
| US9864988B2 (en) | 2012-06-15 | 2018-01-09 | Visa International Service Association | Payment processing for qualified transaction items |
| US9626678B2 (en) | 2012-08-01 | 2017-04-18 | Visa International Service Association | Systems and methods to enhance security in transactions |
| US10438199B2 (en) | 2012-08-10 | 2019-10-08 | Visa International Service Association | Systems and methods to apply values from stored value accounts to payment transactions |
| US10685367B2 (en) | 2012-11-05 | 2020-06-16 | Visa International Service Association | Systems and methods to provide offer benefits based on issuer identity |
| CA2845327A1 (en) * | 2013-03-12 | 2014-09-12 | Maritz Holdings Inc. | Rewards redemption system and method (cpg/oem loyalty program) |
| US20150112816A1 (en) | 2013-10-21 | 2015-04-23 | Disney Enterprises, Inc. | Systems and methods for providing a graphical user interface for providing brand integration within online content, managing brand integration within online content, and/or managing compensation associated with online content |
| US9990646B2 (en) | 2013-10-24 | 2018-06-05 | Visa International Service Association | Systems and methods to provide a user interface for redemption of loyalty rewards |
| US10438236B2 (en) * | 2013-10-29 | 2019-10-08 | Yoshinori Matsumoto | Advertisement distribution program, advertisement distribution method for executing advertisement distribution program and advertisement control device |
| US10489754B2 (en) | 2013-11-11 | 2019-11-26 | Visa International Service Association | Systems and methods to facilitate the redemption of offer benefits in a form of third party statement credits |
| US9672516B2 (en) | 2014-03-13 | 2017-06-06 | Visa International Service Association | Communication protocols for processing an authorization request in a distributed computing system |
| US10354268B2 (en) | 2014-05-15 | 2019-07-16 | Visa International Service Association | Systems and methods to organize and consolidate data for improved data storage and processing |
| US11803784B2 (en) | 2015-08-17 | 2023-10-31 | Siemens Mobility, Inc. | Sensor fusion for transit applications |
| BR112018002131A2 (en) | 2015-08-17 | 2018-09-11 | Bytemark, Inc. | method on a mobile device, method for facilitating fare validation, mobile device and controller unit |
| US10621242B2 (en) | 2015-12-28 | 2020-04-14 | Disney Enterprises, Inc. | System and method for generating online content creator profiles and providing a searchable platform for the online content creator profiles |
| US10769163B2 (en) | 2017-09-25 | 2020-09-08 | Splunk Inc. | Cross-system nested journey monitoring based on relation of machine data |
| US10678804B2 (en) | 2017-09-25 | 2020-06-09 | Splunk Inc. | Cross-system journey monitoring based on relation of machine data |
| US10776377B2 (en) | 2018-03-26 | 2020-09-15 | Splunk Inc. | User interface and process to generate journey instance based on one or more pivot identifiers and one or more step identifiers |
| US10909182B2 (en) | 2018-03-26 | 2021-02-02 | Splunk Inc. | Journey instance generation based on one or more pivot identifiers and one or more step identifiers |
| US10909128B2 (en) | 2018-03-26 | 2021-02-02 | Splunk Inc. | Analyzing journey instances that include an ordering of step instances including a subset of a set of events |
| US10885049B2 (en) | 2018-03-26 | 2021-01-05 | Splunk Inc. | User interface to identify one or more pivot identifiers and one or more step identifiers to process events |
| US10997192B2 (en) | 2019-01-31 | 2021-05-04 | Splunk Inc. | Data source correlation user interface |
| US10754638B1 (en) | 2019-04-29 | 2020-08-25 | Splunk Inc. | Enabling agile functionality updates using multi-component application |
| US11151125B1 (en) | 2019-10-18 | 2021-10-19 | Splunk Inc. | Efficient updating of journey instances detected within unstructured event data |
| US11809447B1 (en) | 2020-04-30 | 2023-11-07 | Splunk Inc. | Collapsing nodes within a journey model |
| US11741131B1 (en) | 2020-07-31 | 2023-08-29 | Splunk Inc. | Fragmented upload and re-stitching of journey instances detected within event data |
| US11880875B2 (en) * | 2021-04-01 | 2024-01-23 | The Toronto-Dominion Bank | Systems and methods for providing product recommendations |
Family Cites Families (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5202826A (en) * | 1989-01-27 | 1993-04-13 | Mccarthy Patrick D | Centralized consumer cash value accumulation system for multiple merchants |
| AU7512194A (en) | 1993-10-26 | 1995-05-22 | Radisson Hotels International, Inc. | System and method for awarding credits to persons who book travel-related reservations |
| WO1995021428A1 (en) | 1994-02-04 | 1995-08-10 | Card One Development Company | Method and system for allocating and redeeming incentive credits |
| 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 |
| US5774870A (en) | 1995-12-14 | 1998-06-30 | Netcentives, Inc. | Fully integrated, on-line interactive frequency and award redemption program |
| US5937391A (en) | 1996-07-11 | 1999-08-10 | Fujitsu Limited | Point-service system in online shopping mall |
| US6016504A (en) * | 1996-08-28 | 2000-01-18 | Infospace.Com, Inc. | Method and system for tracking the purchase of a product and services over the Internet |
| US5923016A (en) | 1996-12-03 | 1999-07-13 | Carlson Companies, Inc. | In-store points redemption system & method |
| US6330544B1 (en) | 1997-05-19 | 2001-12-11 | Walker Digital, Llc | System and process for issuing and managing forced redemption vouchers having alias account numbers |
| US6148330A (en) | 1997-11-17 | 2000-11-14 | Netscape Communications Corp. | System and method for automatically generating content for a network channel |
| US6336098B1 (en) | 1997-12-11 | 2002-01-01 | International Business Machines Corp. | Method for electronic distribution and redemption of coupons on the world wide web |
| US5966700A (en) * | 1997-12-23 | 1999-10-12 | Federal Home Loan Bank Of Chicago | Management system for risk sharing of mortgage pools |
| US6199762B1 (en) | 1998-05-06 | 2001-03-13 | American Express Travel Related Services Co., Inc. | Methods and apparatus for dynamic smartcard synchronization and personalization |
| US6076069A (en) | 1998-09-25 | 2000-06-13 | Oneclip.Com, Incorporated | Method of and system for distributing and redeeming electronic coupons |
| US6032136A (en) | 1998-11-17 | 2000-02-29 | First Usa Bank, N.A. | Customer activated multi-value (CAM) card |
| US6598028B1 (en) * | 1999-09-03 | 2003-07-22 | Lynn Sullivan | Computer-implemented universal financial management/translation system and method |
| CA2341819A1 (en) | 2000-03-23 | 2001-09-23 | Deepak Puri | System and method for providing e-commerce based on a reward currency |
| CA2406001A1 (en) | 2000-04-14 | 2001-10-25 | American Express Travel Related Services Company, Inc. | A system and method for using loyalty points |
| US20010037243A1 (en) | 2000-04-21 | 2001-11-01 | Rouston W. Graeme | System and method for redeeming frequent flyer miles |
| US20010054010A1 (en) | 2000-05-05 | 2001-12-20 | Bernabeo Gregory S. | Electronic redemption system |
| US6675178B1 (en) * | 2000-11-09 | 2004-01-06 | Accenture Llp | Method and system for enhancing a commercial transaction conducted via a communications network |
| US20020147678A1 (en) * | 2001-02-02 | 2002-10-10 | Mellon Bank, N.A. | Adjudication method and system |
| US20020111859A1 (en) * | 2001-02-15 | 2002-08-15 | Gregory Sheldon | Integrated frequency and award redemption program for installment based receivables behavior modification and customer loyalty management |
| US20020186254A1 (en) * | 2001-06-11 | 2002-12-12 | Apps4Biz.Com Holding Ag | Information handling method and apparatus and intuitive graphical user interface for navigating business application software |
| US6819340B2 (en) * | 2001-07-23 | 2004-11-16 | Paul E. Burke | Adding a shortcut to a web site |
| US6745179B2 (en) * | 2001-10-12 | 2004-06-01 | Shipley Company, L.L.C. | Method and system for facilitating viewer navigation through online information relating to chemical products |
| US20030189589A1 (en) * | 2002-03-15 | 2003-10-09 | Air-Grid Networks, Inc. | Systems and methods for enhancing event quality |
-
2002
- 2002-04-05 US US10/117,309 patent/US7134087B2/en not_active Expired - Lifetime
-
2003
- 2003-03-19 CA CA002422658A patent/CA2422658A1/en not_active Abandoned
Also Published As
| Publication number | Publication date |
|---|---|
| US7134087B2 (en) | 2006-11-07 |
| US20040230481A1 (en) | 2004-11-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7134087B2 (en) | System and method for transacting purchases with a cash vendor using points | |
| CA2441547C (en) | Hybrid credit card transaction system | |
| US6243688B1 (en) | Internet-based credit interchange system of converting purchase credit awards through credit exchange system for purchase of investment vehicle | |
| US8234164B2 (en) | Method and apparatus for facilitating electronic commerce through providing cross-benefits during a transaction | |
| US20030093355A1 (en) | Method, system and computer site for conducting an online auction | |
| US20030065572A1 (en) | Charity donation method | |
| US20030204470A1 (en) | Method, apparatus, and code for issuing a dual credit card | |
| US20080201230A1 (en) | Internet-based method of and system for equity ownership optimization within a financial and retail marketplace | |
| US20070179888A1 (en) | System for organizational fundraising using retail gift cards | |
| JP2000048108A (en) | Method and system to perform electronic value exchange and settlement among heterogeneous payment schemes with heterogeneous currencies | |
| US20030097298A1 (en) | On-line bonus program | |
| US7818284B1 (en) | Method and apparatus for providing cross-benefits via a central authority | |
| US7024373B1 (en) | Auto purchase system and method | |
| US20100305957A1 (en) | Method and system of redeeming gold for cash or other value | |
| US20090292601A1 (en) | Profit-Sharing Incentive System For Account Vendors | |
| WO1999066443A1 (en) | Method and apparatus for providing cross-benefits via a central authority | |
| AU2257801A (en) | Combined in-store and on-line interactive reward redemption system and method | |
| WO2001031529A1 (en) | Incentive program associated with equity acquisition | |
| US20060218050A1 (en) | Method and apparatus for facilitating electronic commerce through providing cross-benefits during a transaction | |
| KR100626307B1 (en) | Method for mediating transactions at a reduced price using a cyber salesman | |
| CA2373367A1 (en) | Systems and methods for evaluating information associated with a transaction to determine a subsidy offer | |
| CA2358084A1 (en) | Charity donation method | |
| WO2002017191A1 (en) | Method and system for redemption of electronic coupons | |
| AU2007203694A1 (en) | Apparatus, network and method for performing commercial transactions | |
| IES20030289A2 (en) | A computer implemented reward system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| FZDE | Discontinued |
Effective date: 20170228 |