System and method for granting promotional rewards to financial account holders

Description

RELATED APPLICATIONS

This application claims the benefit U.S. Provisional Application Ser. No. 60/948,127, filed Jul. 5, 2007, titled “System and Method for Granting Promotional Rewards to Financial Account Holders.” The specification and drawings of the above application is incorporated herein by reference in their entirety.

This application is related to: (1) U.S. patent application Ser. No. 11/634,159, filed Dec. 6, 2006, titled “System and Method for Offering Reward Programs, which claims priority to U.S. Provisional Application No. 60/822,609, filed on Aug. 16, 2006, and titled “System and Method for Offering Reward Programs”; (2) co-pending U.S. patent application Ser. No. 10/284,394, filed Oct. 31, 2002, titled “System and Method for Establishing or Modifying and Account with User Selectable Terms,” which claims priority to U.S. Provisional Application Ser. No. 60/330,871, filed Nov. 1, 2001, titled “System and Method for Establishing or Modifying an Account with User Selectable Terms”; and (3) U.S. Provisional Application No. 60/842,015, filed on Sep. 5, 2006, and titled “For Dynamically Identifying, Prioritizing And Offering Reward Categories.”

FIELD OF THE INVENTION

The present invention relates to the dynamic identification and offering of rewards. More particularly, the present invention relates to systems and methods that enable issuers, sponsors, or account administrators, for example, to dynamically identify and offer its customers rewards.

BACKGROUND

Rewards programs are becoming increasingly popular. Card or account issuers and account administrators, such as banks, for example, commonly offer their customers reward cards (e.g., credit cards, debit cards, stored value cards, or gift cards) that aim to encourage or induce customer behavior by rewarding all or select transactions. Rewards are typically based on any number of transaction particulars, such as spending levels, types of transaction, identity of merchant or vendor, location of transactions, or any other data or information that demonstrates user behavior. For example, a bank may provide incentives (e.g., rebates or discounts) on purchases made through a particular vendor or merchant. Rewards may also include cash-back deals where the customer earns a percentage of the transaction amounts as cash value that gets added to the customer's account.

In some cases, reward cards may be “branded” with the name of a particular sponsor or merchant so that use of the card earns the customer points that may be redeemed through the sponsor or merchant. For example, a credit card sponsored by an airline may reward the user with airline miles that may be redeemed for free or discounted travel. Likewise, some cards earn store dollars that can be used as virtual cash to make purchases through select merchants and vendors.

Although conventional systems and methods enable banks and sponsors to provide customers with a wide variety of reward categories, they nonetheless suffer from several notable drawbacks. For example, current systems and methods do not enable sponsors and account administrators to randomly or selectively identify and offer customers rewards on an ongoing basis. More specifically, current systems and methods do not enable sponsors or account administrators, for example, to prioritize or organize its customers' transactions and thereafter randomly (or according to an algorithm(s) or other selection technique) select at least one customer or transaction which will receive or redeem a reward. For example, current systems and methods do not enable a bank to organize its customers' transactions by date and time and thereafter select at least one customer or transaction which will be paid for by the bank. In addition, existing systems and methods do not allow users to selectively identify transaction(s), at the point-of-sale, that the customer would like to apply rewards to.

Thus, what is needed is a reward system and method that enables an account administrator or sponsor, for example, to prioritize or organize its customers' transactions and thereafter randomly (or according to an algorithm(s) or other selection technique) select at least one customer or transaction which will receive or redeem a reward.

SUMMARY OF THE INVENTION

According to various embodiments, the systems and methods described herein may relate to systems and methods that prioritize or organize customers or account transactions, for example, according to a particular priority or ordering scheme and thereafter randomly (or according to an algorithm(s) or other selection technique) select at least one customer or transaction that will receive or redeem a reward. In some embodiments, the customer is not aware that a reward is being given until such time as the customer is notified that the reward has been made or is being offered by the sponsor or account administrator, such as a bank, for example. In some embodiments, the reward may be related to the particular transaction(s) selected, such as, for example, a reward that the bank or sponsor will pay for, cover or discount the expense associated with the transaction. In some embodiments, the reward may be presented to the winning customer or account in the form of a gift card or points, miles or any other currency or unit that may be issued as a redeemable reward, for example. Other rewards and types of rewards are possible. In some embodiments, the customer may be offered a choice of rewards or transactions to select from.

A bank or sponsor utilizing the systems and methods described herein may prioritize or order all customer transactions (e.g., by date or time; amount spent; merchant; product or good purchased; type of transaction; customer; account type; or any other parameter which may be used to prioritize or order transactions) and thereafter randomly or according to an algorithm(s) or other selection technique select which transaction(s) or customer(s) the bank or sponsor will reward. In some embodiments, prioritizing or ordering of transactions may occur randomly, according to a schedule, or periodically, such as, daily, weekly, monthly, or other periodic period of time. For example, every day, week or month, the sponsor or bank may prioritize or order all transactions that have been made during that period of time. In some embodiments, a customer may receive bonus entries for purchases made at specific merchants, merchant categories, amount spent or other parameter. In some embodiments, after transactions have been prioritized or ordered, the sponsor or bank may exclude certain customers or transactions for any particular reason, such as, for example, a particular customer or transaction is not located within a specific geographic area or location.

In some embodiments, determining which customer(s) or transaction(s) is/are to receive or redeem a reward may be based on any selection technique or method. For example, a customer or transaction may be selected based on the customer's demonstrated behavior (e.g., the most frequent shopper among the customer's in the prioritized or ordered list), the date or time of a transaction, the type of transaction conducted, the total amount spent by the customer in a given or group of transactions, the specific products or services (or types or categories of products or services) the customer purchased or routinely purchases, the merchants or other entities through which purchases or other transactions are entered into, the types of rewards the customer has historically preferred or actually redeemed in the past, or any other data or information that may be used to particularly identify and select customer(s) or transaction(s) for the purposes set forth herein.

Once at least one customer or transaction is selected, the systems and methods described herein may notify the customer that a reward has been or will be applied to the selected transaction, or that a reward is available for selection by the customer. Notification may be made in any manner, such as by electronic mail or other electronic messaging, telephone, mail, or other appropriate manner. In some embodiments, a customer may be notified on the electronic or hardcopy statement of account, such that the winning transaction, for example, may include a designation that a reward has been received in connection therewith. Thus, the customer's statement may indicate that the transaction has been paid for in full or discounted, for example, by the bank or sponsor. In some embodiments, notifications may be sent to the customer's PDA, computer, telephone or other device. In some embodiments, notifications may be sent to the point-of-sale, such as, for example, a customer representative terminal, or point-of sale device or kiosk. Notifications may comprise text, audio or visual representations. In some embodiments, notifications may be provided at the point-of-sale, immediately, in real-time, shortly after a transaction is consummated, periodically, randomly, according to a schedule, at redemption,

In some embodiments, the systems and methods described herein may permit customers to opt-in to participate in the program. For example, a customer (e.g., a card holding customer of a bank) may opt-in to participate in the program. In addition, a customer may opt-in to the program either online, by voice response unit (VRU), with the help of their banker at a branch, by receiving a targeted enrollment offer at an ATM, point-of-sale device or other terminal, or by any other technique or manner. A customer may selectively opt-in when an account is opened or anytime thereafter. In some embodiments, a customer may be automatically enrolled in the program at the time an account is opened, any time thereafter, or upon the occurrence of an event. In some embodiments, once a customer enrolls or is enrolled in the program the customer's transactions via an account, for example, may be tracked and prioritized or ordered along with the transactions of other customers and considered for a reward. For example, customer purchases may be sorted by date and time of when each was posted to their checking, credit, debit, savings, or any other type of account.

In some embodiments, the account through which customer transactions are tracked and considered for rewards may comprise an account associated or affiliated with a checking or savings account, a credit card, a debit card (e.g., a business banking debit card), a stored value card, RFID, and Equiline (Home Equity) access card, FOB card, any other card or identifier, or any other account through or to which transactions may be entered or posted. In some embodiments, transactions may be conducted over a telephone, computer, or other communication device. Transactions may also be conducted through contact or contact-less methods or devices.

In some embodiments, any numbers of parameters may be imposed to determine eligibility in the program or systems and methods described herein. For example, the program may be offered in specific geographic locations or in the entire country or world. Other selectable parameters may include, for example, only select customers or transactions are eligible to receive or redeem a reward; only select rewards are available to particular customers or transactions; only certain types of accounts are eligible to receive reward; only select entry modes (e.g., cards or other devices, RFID, contact-less online purchases, or other modes of entering into a transaction) are eligible; and only transactions through specific merchant categories qualify. Other parameters are of course possible.

In some embodiments, the various systems and methods described herein may permit a customer to use, redeem or expend, for example, earned reward points or other units of earned value to select particular transactions that are to receive or redeem a reward. For example, a customer may be presented with a listing or log of transactions that are eligible for a reward. In selecting a transaction or transactions, the customer may use “x” points that have been earned through previous transactions and that are maintained in a points bank in order to be able to select at least one transaction from the listing or log presented. The points redeemed may be converted to dollars and added to the customer's checking account, for example. That is, points are used initially to enter into a transaction and debited from the points account, and dollars are subsequently added to the customer's account as the reward received on the particular transaction selected. In some embodiments, a user's card or transaction device may be associated with a points or other value bank of the user so that purchases made with the card are paid for using points.

According to one embodiment of the invention, a method for offering rewards. The method comprising the steps of: receiving at least one transaction occurrence relating to at least one account; ordering the at least one transaction occurrence based on an ordering scheme; selecting a winning transaction from the at least one transaction occurrence based on a reward selection scheme; and rewarding at least one reward to a user associated with the winning transaction. In some embodiments, a customer may select or determine the parameters to be considered in determining transactions to automatically receive rewards.

In yet another embodiment of the invention, a system for identifying and offering rewards is provided. The system comprising: a transaction reception module or processor for receiving at least one transaction occurrence; an ordering module or processor for ordering the at least one transaction occurrence based on an ordering scheme; and a rewards selection module or processor for rewarding at least one reward to a user associated with at least one of the at least one transaction occurrence based on a reward selection scheme.

In yet another embodiment of the invention, a method for offering a reward is provided. The method comprising the steps of: receiving at least one transaction occurrence, wherein the at least one transaction occurrence is associated with a user or account; assigning at least one reward value to the at least one transaction occurrence, wherein the at least one reward value is based on the amount of the at least one transaction, the identity of the user or account, the identity of a sponsor, or any other particular associated with the at least one transaction; storing the at least one reward value in a rewards database; generating a statement to the user based on the at least one transaction occurrence, wherein the statement lists each of the at least one transaction occurrence and a balance of receiving a transaction selection from the user designating a transaction; and applying at least a portion of the at least one reward value to a balance corresponding to the designated transaction.

In yet another embodiment of the invention, a method for offering rewards is provided. The method comprising the steps of: receiving at least one transaction occurrence relating; selecting a winning transaction from the at least one received transaction occurrence based on a reward selection scheme; and applying at least one reward to the winning transaction.

In yet another embodiment of the invention, a method for redeeming rewards at the point of purchase is provided. The method comprising the steps of: receiving a transaction particular associated with a purchase by a user; notifying the user that rewards or other redeemable value is available to be applied against the transaction; receiving a selection from the user on whether to pay with reward points; redeeming select rewards or other redeemable value against the transaction amount; and treating any balance owed as a split tender.

In another embodiment of the invention, a method for offering rewards, is provided. The method comprising the steps of: receiving a plurality transaction occurrences from a plurality of merchants relating to at least one account; ordering the plurality of transaction occurrences based on an ordering scheme; selecting a winning transaction from the plurality of transaction occurrences based on a reward selection scheme; and rewarding at least one reward to a user associated with the winning transaction.

In yet another embodiment of the invention, a system for identifying and offering rewards is provided. The system comprising: a transaction reception module or processor for receiving a plurality of transaction occurrences from a plurality of merchants; an ordering module or processor for ordering the plurality of transaction occurrences based on an ordering scheme; and a rewards selection module or processor for rewarding at least one reward to a user associated with at least one of the plurality of transaction occurrences based on a reward selection scheme.

A method for offering a reward, comprising: receiving a plurality of transaction occurrences from a plurality of merchants, wherein each of the plurality transaction occurrences is associated with a user or account; assigning at least one reward value to at least one of the plurality of transaction occurrences, wherein the at least one reward value is based on the amount of the at least one transaction, the identity of the user or account, the identity of a sponsor, or any other particular associated with the at least one transaction; storing the at least one reward value in a rewards database; generating a statement to the user based on the at least one of the plurality of transaction occurrences, wherein the statement lists each of the at least one transaction occurrence and a balance of receiving a transaction selection from the user designating a transaction; and applying at least a portion of the at least one reward value to a balance corresponding to the designated transaction.

A method for offering rewards, comprising the steps of: receiving a plurality of transaction occurrences from a plurality of merchants relating to a user or account; selecting a winning transaction from the plurality of received transaction occurrences based on a reward selection scheme; and applying at least one reward to the winning transaction.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an exemplary system 100 for offering rewards, according to various embodiments of the invention.

FIG. 1a illustrates a process flow 118 for offering rewards, according to various embodiments of the invention.

FIG. 2 illustrates various exemplary modules that may be associated with rewards station 105, according to various embodiments of the invention.

FIG. 3 illustrates an exemplary process flow 300 for offering rewards, according to various embodiments of the invention.

FIG. 4 illustrates an exemplary process flow 400 for offering rewards, according to various embodiments of the invention.

FIG. 5 illustrates an exemplary process flow 500 for offering rewards, according to various embodiments of the invention.

FIG. 6 illustrates an exemplary process flow 600 for offering rewards, according to various embodiments of the invention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Reference will now be made to the present preferred embodiments of the invention, examples of which are illustrated in the accompanying drawings in which like reference characters refer to corresponding elements.

The present invention is described in relation to a system and method for identifying, prioritizing and offering rewards. Nonetheless, the characteristics and parameters pertaining to the system and method may be applicable to transactions associated with other types of promotions and incentive programs.

While the exemplary embodiments illustrated herein may show the various embodiments of the invention (or portions thereof) collocated, it is to be appreciated that the various components of the various embodiments may be located at distant portions of a distributed network, such as a local area network, a wide area network, a telecommunications network, an intranet and/or the Internet, or within a dedicated object handling system. Thus, it should be appreciated that the components of the various embodiments may be combined into one or more devices or collocated on a particular node of a distributed network, such as a telecommunications network, for example. As will be appreciated from the following description, and for reasons of computational efficiency, the components of the various embodiments may be arranged at any location within a distributed network without affecting the operation of the respective system.

FIG. 1 illustrates a system 100 for offering rewards according to one embodiment of the invention. System 100 may comprise a reward station 105 for identifying and offering reward categories based on customer particulars, such as past transactions and expressed interests and needs. In some embodiments, rewards station 105 may be administered by a bank or financial institution, for example, that issues, maintains or administers cards (e.g., a card-issuer) or accounts, a merchant or vendor that sponsors rewards (e.g., a sponsor), or any third party that, for example, coordinates, manages or administers customer interaction with merchants 110 via cards, accounts and corresponding rewards programs. In some embodiments, rewards station 105 may maintain particulars about customers, rewards, sponsors, and any data and information that may be used to offer rewards according to the systems and methods described herein. In some embodiments, rewards station 105 may comprise the central headquarters or repository of the various features and functions of the systems and methods described herein, and may be maintained by any party or entity that administers the coordination of data and information in connection with the offering of rewards according to the systems and methods described herein.

Rewards station 105 may comprise a single server or engine (as shown). In another embodiment, rewards station 105 may comprise a plurality of servers or engines, dedicated or otherwise, which may further host modules for performing desired system functionality. Rewards station 105, for example, may host one or more applications or modules that function to permit interaction between the users of system 100 (e.g., sponsors, customers, the administrator of rewards station 105, and any other relevant parties) as it relates to exchanging and processing of data and information related to the offering of rewards, for example. For instance, rewards station 105 may include an administration module that serves to permit interaction between the system 100 and the individual(s) or entity(ies) charged with administering system 100 or rewards station 105. Such an administration module may enable the agent of rewards station 105, for example, to input information related to rewards, including but not limited to parameters used to order or prioritize transactions or to select transactions which will be offered rewards. Such parameters may comprise variables, algorithms or formulas, for example, that define an ordering or prioritization scheme or a reward selection scheme for issuing rewards as described herein.

According to various embodiments, an agent of rewards station 105 may interface with a graphical user interface (or GUI) to input: (1) data or information (e.g., terms, words, phrases, or digits) that enable the agent to define particular customers or transactions that are eligible to participate and receive rewards, (2) data or information that enable the agent to define particular transaction ordering or prioritization or reward selection schemes, (3) data or information that enable the agent to define particulars about sponsors or other merchants or vendors through which rewards will be delivered or made available, (4) rules, parameters and algorithms used to identify which rewards to offer to customers, (5) data or information used to notify customers that a rewards has been issued or made available, (6) information or data regarding how customers, transactions or rewards are stored (e.g., categorized) in a database 112, for example and (7) data or information used to perform or carry any of the features or functionality described herein. Other modules may permit processing of the various features and functionality described herein for offering rewards (See FIG. 2 for modules associated with rewards station 105).

Rewards station 105 may include, for instance, a workstation or workstations running the Microsoft Windows™ XP™ operating system, Microsoft Windows™ NT™ operating system, the Windows™ 2000 operating system, the Unix operating system, the Linux operating system, the Xenix operating system, the IBM AIX™ operating system, the Hewlett-Packard UX™ operating system, the Novell Netware™ operating system, the Sun Microsystems Solaris™ operating system, the OS/2 system, the BeOS™ operating system, the Macintosh operating system, the Apache operating system, an OpenStep™ operating system or another operating system or platform.

Data and information maintained by rewards station 105 may be stored and cataloged in database 112 which may comprise or interface with a searchable database. Database 112 may comprise, include or interface to a relational database. Other databases, such as a query format database, a Standard Query Language (SQL) format database, a storage area network (SAN), or another similar data storage device, query format, platform or resource may be used. Database 112 may comprise a single database or a collection of databases, dedicated or otherwise. In one embodiment, database 112 may store or cooperate with other databases to store the various data and information described herein. In some embodiments, database 112 may comprise a file management system, program or application for storing and maintaining data and information used or generated by the various features and functions of the systems and methods described herein. In some embodiments, database 112 may store, maintain and permit access to customer information, sponsor or reward information, and general information used to offer rewards as described herein.

Rewards station 105 may, in some embodiments, be accessed via a communication network 107. Communications network 107 may be comprised of, or may interface to any one or more of, the Internet, an intranet, a Personal Area Network (PAN), a Local Area Network (LAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), a storage area network (SAN), a frame relay connection, an Advanced Intelligent Network (AIN) connection, a synchronous optical network (SONET) connection, a digital T1, T3, E1 or E3 line, a Digital Data Service (DDS) connection, a Digital Subscriber Line (DSL) connection, an Ethernet connection, an Integrated Services Digital Network (ISDN) line, a dial-up port such as a V.90, a V.34 or a V.34bis analog modem connection, a cable modem, an Asynchronous Transfer Mode (ATM) connection, a Fiber Distributed Data Interface (FDDI) connection, or a Copper Distributed Data Interface (CDDI) connection.

Communications network 107 may also comprise, include or interface to any one or more of a Wireless Application Protocol (WAP) link, a General Packet Radio Service (GPRS) link, a Global System for Mobile Communication (GSM) link, a Code Division Multiple Access (CDMA) link or a Time Division Multiple Access (TDMA) link such as a cellular phone channel, a Global Positioning System (GPS) link, a cellular digital packet data (CDPD) link, a Research in Motion, Limited (RIM) duplex paging type device, a Bluetooth radio link, or an IEEE 802.11-based radio frequency link. Communications network 107 may further comprise, include or interface to any one or more of an RS-232 serial connection, an IEEE-1394 (Firewire) connection, a Fibre Channel connection, an infrared (IrDA) port, a Small Computer Systems Interface (SCSI) connection, a Universal Serial Bus (USB) connection or another wired or wireless, digital or analog interface or connection.

In some embodiments, communication network 107 may comprise a satellite communications network, such as a direct broadcast communication system (DBS) having the requisite number of dishes, satellites and transmitter/receiver boxes, for example. Communications network 107 may also comprise a telephone communications network, such as the Public Switched Telephone Network (PSTN). In another embodiment, communication network 120 may comprise a Personal Branch Exchange (PBX), which may further connect to the PSTN. Communications network 107 may also comprise a transaction network, such as a credit or debit processing network, or any other network through which transactions may be processed.

As shown in FIG. 1, merchant station 110 and customer station 115 may communicate with reward station 105 via communication network 107. Merchant station 110 may comprise, for example, a station or terminal utilized by an agent of a card or account issuer or a sponsor or other merchant or vendor to interact or communicate with customers or reward station 105. For example, station 110 may comprise a point-of-sale (POS) terminal, a call center facility or station of a card or account issuer or sponsor that is manned by an operator to receive calls from customers, or other terminal that a card or account issuer or a sponsor or other merchant or vendor may use to communicate with a customer or reward station 105. In some embodiments, merchant station 110 may comprise or host web site(s), web page(s) or other interfaces of the card or account issuer, sponsor or other merchant or vendor, for example, that a customer can access or interact with to make purchases or enter into other transactions with the card or account.

Customer station 115 may, in some embodiments, enable a customer to interact with, make purchases or other transactions, or communicate with a card or account issuer or sponsor, merchant or other vendor as represented by merchant station 110. For example, customer station 115 may enable a customer to call or access the web site or page of a card or account issuer or sponsor to make purchases, inquire about account particulars, make payment on an account, or inquire about available balance, for example. In some embodiments, customer station 115 may comprise any terminal (e.g., a typical home or personal computer system) whereby a customer may interact with a network, such as communications network 107, for example, that is responsible for transmitting and delivering data and information used by the various systems and methods described herein. Customer station 115 may comprise or include, for instance, a personal or laptop computer. Customer station 115 may include a microprocessor, a microcontroller or other general or special purpose device operating under programmed control. Customer station 115 may further include an electronic memory such as a random access memory (RAM) or electronically programmable read only memory (EPROM), a storage such as a hard drive, a CDROM or a rewritable CDROM or another magnetic, optical or other media, and other associated components connected over an electronic bus, as will be appreciated by persons skilled in the art. Customer station 115 may be equipped with an integral or connectable cathode ray tube (CRT), a liquid crystal display (LCD), electroluminescent display, a light emitting diode (LED) or another display screen, panel or device for viewing and manipulating files, data and other resources, for instance using a graphical user interface (GUI) or a command line interface (CLI). Customer station 115 may also include a network-enabled appliance, a browser-equipped or other network-enabled cellular telephone, or another TCP/IP client or other device.

FIG. 1a illustrates an exemplary process flow 118 for offering rewards, according to one embodiment of the system and methods described herein. At step 120, any number of transactions are received by rewards station 105. In some embodiments, such transactions correspond to the transactions of any number of customers throughout the world. The receipt of transactions by rewards station 105 may comprise the reception of transaction particulars such as, for example, the date or time of a transaction, the type of transaction (e.g., purchase, balance inquiry, payment, transfer, etc.), the identity or location of the customer, card or account, the customer, card or account transaction history, the amount of a transaction (e.g., purchase amount, transfer amount, payment amount, etc.), the identity or location of a sponsor or other merchant or vendor through which the transaction is entered, the product or service purchased or sold, or any other particular of a transaction that may be used to order or prioritize transactions, select customers or transactions to receive rewards, and otherwise offer rewards as described herein. In some embodiments, the transactions are received over a particular period of time, such as, for example, daily, weekly, monthly

At step 125, rewards station 105 may order or prioritize the received transactions according to any given scheme, rule or algorithm. For example, transaction particulars may be used to order or prioritize transactions into a particular list that can then be used to select a particular transaction(s) or customer(s) to receive or redeem a reward. Such ordering or prioritization may be based on any of the transaction particulars described above in step 120. For example, transactions may be ordered or prioritized based on a time or date; amount spent or transacted; identity, location or type of merchant or vendor; identity or type of product or service purchased or transacted; identity, location or type of customer; identity, location or type of transaction; or any other particular that may be used to order and prioritize transactions or customers.

At step 130, a transaction(s) or customer(s) from the ordered or prioritized list is selected to receive or redeem a reward. In some embodiments, selection of a transaction or customer may be based on any selection scheme, rule or algorithm. Such selection scheme, rule or algorithm may be based on a random selection; the customer with the most transactions; the customer with the greatest amount or total amount spent or transacted; the customer that shopped or transacted with a particular merchant or vendor (specific or type); the largest transaction amount; the largest non-purchase transaction; first or most occurrence of a particular transaction type; or any other scheme, rule or algorithm that may be used to offer rewards in the manner described herein. In some embodiments, the reward may comprise paying for or covering the particular transaction selected. Thus, if the selected transaction is a customer's $500 purchase of a television set, the reward may comprise paying for the television set on behalf of the customer. In some embodiments, the systems and methods described herein may reimburse the customer the amount of the transaction. Thus, instead of paying for the $500 on behalf of the customer, the systems and methods described herein may simply reimburse the customer the $500. In some embodiments, a reward is given by the issuer or administrator of a card or account used to make the purchase, a sponsor of the reward, a merchant or vendor, the administrator of rewards station 105, or any other individual or entity that may issue rewards through the systems and methods described herein. Other rewards are possible. In some embodiments, the customer associated with the selected transaction(s) may be notified in any appropriate manner, such as, for example, via electronic mail, instant messaging, electronic statement or other electronic means, or mail, telephone or other appropriate manner. In some embodiments, a customer may be offered a choice of rewards to select from. In some embodiments, if a customer subsequently returns a rewarded item, the various systems and methods described herein may charge the appropriate amount to the customer's account or otherwise obtain reimbursement directly from the merchant or other party. For example, if the customer returned the $500 television set after being reimbursed the cost, the merchant where the television set was returned may inform the administrator of the systems and methods described herein of the return so that appropriate reconciliation may be accomplished.

FIG. 2 illustrates exemplary modules that may be associated with central rewards station 105 for carrying out (or administering) the various functions and features of the embodiments described herein. While the modules may not be used in all embodiments to perform some or all of the functions of the present invention, they are nonetheless presented as possible embodiments:

Transaction reception module 200 may, in some embodiments, receive customer transactions that are made or entered into by a customer with a card or account, for example. In some embodiments, transaction reception module 200 may interact with any transaction network (e.g., ATM, Visa, MasterCard), for example, through which purchase or other transactions are conducted and receive therefrom transaction particulars that are used by the various systems and methods described herein to offer rewards. For example, transaction reception module 200 may receive from any number of sponsors or other merchants or vendors particulars of transactions entered into by a customer using a card or account, for example. Such particulars may include, for example, the date or time of a transaction, the type of transaction (e.g., purchase, balance inquiry, payment, transfer, etc.), the identity or location of the customer, card or account, the customer, card or account transaction history, the amount of a transaction (e.g., purchase amount, transfer amount, payment amount, etc.), the identity or location of a sponsor or other merchant or vendor through which the transaction is entered, the product or service purchased or sold, or any other particular of a transaction that may be used to order or prioritize transactions, select customers or transactions to receive rewards, and otherwise offer rewards as described herein. In some embodiments, transaction reception module 200 may receive particulars on transactions that are entered into with cash. For example, the merchant or vendor in a transaction paid for in cash may provide any of the above transaction particulars to transaction reception module 200. In some embodiments, transaction reception module 200 may organize and otherwise queue transactions received for further processing by the systems and methods described herein.

Transaction ordering module 205 may, in some embodiments, order or prioritize customer transactions that have been received by transaction reception module 200. Such ordering or prioritization may be used to designate a listing of customers or transactions that are eligible to receive or redeem a reward according to the systems and methods described herein. In some embodiments, transaction ordering module 205 may prioritize or order transactions by date or time. For example, transactions entered into by any number of customers may be queued and organized so that the most recent transaction occurs first and the oldest transaction appears last on the list. Of course, the listing may be ordered such that that oldest transaction appears first and the most recent appears last. Other ordering or prioritization schemes are possible.

In another example, ordering or prioritization module 205 may organize or prioritize transactions based on the amount of the transaction. For example, transactions of all customers may be organized or prioritized based on the amount spent on particular goods or services, transferred from an account, withdrawn, paid, or otherwise transacted. Thus, a customer who spent $1,000 on the purchase of a television set would be listed higher (or lower, depending on the particular ordering scheme being used) than a customer who purchased a $500 bicycle. In some embodiments, transactions may be ordered irrespective of the transaction type. Thus, an ATM withdrawal of $1,000 would rank higher (or lower) than a purchase for $300. In some embodiments, only select transactions may be considered for rewards. For example, the systems and methods described herein may only consider transactions where a purchase was made. Other parameters are of course possible. The designation of transactions that are eligible to receive rewards may be made by the customer, the administrator of the systems and methods described herein, a merchant, or any other individual or entity that may make such designations.

In some embodiments, customers may be ordered and prioritized based on the total amount of transactions entered into during a particular period of time. For example, assume the customer spends $135 at a restaurant, $233 on groceries, $50 at a gas station, withdraws $200 from an ATM, and transfers $500, all on a given day or over the course of a period of time. For ordering or prioritization purposes, the customer may be considered to have $1,118 in transactions, or the total sum of the above transactions. In some embodiments, only select transaction types (or other transaction particular(s)) is considered in determining total transaction amounts.

While the above ordering and prioritization schemes are offered as examples, transaction ordering module 205 may, of course, utilize any scheme, rules or algorithms to determine how customers or transactions are to be are to be prioritized or ordered. For example, any of the following transaction particulars may be used to order or prioritize transactions: the date or time of a transaction, the type of transaction (e.g., purchase, balance inquiry, payment, transfer, etc.), the identity or location of the customer, card or account, the customer, card or account transaction history, the amount of a transaction (e.g., purchase amount, transfer amount, payment amount, etc.), the identity or location of a sponsor or other merchant or vendor through or with which the transaction is entered into or processed, the product or service purchased or sold, or any other particular of a transaction that may be used to order or prioritize transactions, select customers or transactions to receive rewards, and otherwise offer rewards as described herein.

Bonus reward module 210 may, in some embodiments, issue bonus rewards based on any given transaction particular. For example, certain transactions may be counted multiple times or moved up or down the ordered or prioritized list generated during the ordering or prioritization stage so as to increase the likelihood that the transaction will be selected during the transaction selection stage. In some embodiments, a transaction amount may be increased as a bonus for meeting a specified criteria, such as, for example, shopping at a particular merchant or vendor, meeting a transaction or spending threshold, buying a particular product or service, conducting a particular transaction. Other criteria are possible. For example, assume a customer entered into $1,000 in transactions during the month of June. Assume further that the customer shopped at a particular retailer that is issuing bonus rewards in the form of an increased transaction amount (e.g., double amount) through the systems and methods described herein. Thus, if the customer purchased $100 worth of goods at the retailer, then the systems and methods described herein would register $200 worth of purchases through the retailer, leading to an amount total of $1100 for the customer. In some embodiments, the bonus reward may be increasing the number of transactions for the customer; creating new transactions for the customer.

In some embodiments, bonus rewards may be issued across transaction types. For example, if a customer shops at or conducts a particular with a particular merchant or vendor, the customer may be issued a bonus reward in the form of a free ATM or other transaction that will be added to the ordered or prioritized list of transactions. In some embodiments, the bonus reward given may be based on the particular reward selection scheme, rule or algorithm being utilized. Thus, if the reward is being given to the customer that shops the most at a given retailer, the bonus reward may comprise an additional transaction entry associated with that retailer. This way, the customer's chances of being selected for a reward can be increased. Other bonus reward schemes are possible. In some embodiments, any transaction particular may be used to determine which transactions or customers are selected to receive a bonus reward.

Transaction selection module 215 may, in some embodiments, select a transaction or transactions or customer or customers to receive or redeem a reward according to the systems and methods described herein. Customer or transaction selection may be made according to any selection scheme, rule or algorithm. Examples of such selection scheme, rule or algorithm may include, but are not limited to random selection or selecting the customer(s) or transaction(s) appearing at the top of the ordered or prioritized list. In some embodiments, the steps of ordering or the customer with the most transactions; the customer with the greatest amount or total amount spent or transacted, the customer that shopped or transacted with a particular merchant or vendor (specific or type), the largest transaction amount, the largest non-purchase transaction (e.g., a funds transfer, withdrawal, or deposit), first or most occurrence of a particular transaction type, or any other scheme, rule or algorithm that may be used to offer rewards in the manner described herein. For example, transaction selection module 215 may receive the ordered or prioritized listing and select therefrom the top entry on the list. In some embodiments, transaction selection module 215 may further process the transactions according to additional selection parameters. For example, the list may include the transactions in order by date or time. Transaction selection module 215 may then further process the transactions according to other selection parameters set forth above.

In some embodiments, the reward may comprise paying for, covering, or discounting the amount associated with the selected transactions. For example, a customer buying a $500 television set may wind up getting the television set for free or at a discount price if the amount is paid for by, for example, the issuer or administrator of a card or account used to make the purchase, a sponsor of the reward, a merchant or vendor, the administrator of rewards station 105, or any other individual or entity that may issue rewards through the systems and methods described herein. In some embodiments, the reward is applied without the customer becoming aware of the reward until such time as the customer checks the statement or is otherwise notified. For example, the customer may see in his statement that the outstanding balance for the television set has been reduced to zero. In some embodiments, the reward may be extending the due date for the payment or suppressing the accumulation of interest on the outstanding balance of a transaction. In some embodiments, the customer may be given a list of rewards to choose from to apply against the selected transaction(s). In some embodiments, the customer may be given a reward and asked to designate a transaction to which it should be applied. Other rewards are possible.

Selection parameters module 220 may, in some embodiments, enable an agent of rewards station 105 a sponsor, merchant or vendor, for example, to designate parameters that are to be used as part of the ordering or prioritization schemes, rules or algorithms, or the customer or transaction selection schemes, rules or algorithms. For example, an agent of rewards station 105, a sponsor, merchant or vendor or any other individual or entity involved in the offering of rewards as described herein may designate particular schemes, rules or algorithms to use in particular situations or promotional campaigns In some embodiments, such designations may be made by interacting with an interface (e.g., a graphical user interface) that presents the agent of rewards station 105 a sponsor, merchant or vendor with selectable options of parameters. In some embodiments, such designations may be altered or modified as needed. In some embodiments, parameters may be selected so that a customer is offered the opportunity to select a transaction or transactions that is/are to receive or redeem a reward. For example, a customer may be presented with three (or any number) transactions and asked to select one which is to receive or redeem a reward.

Customer notification module 225 may, in some embodiments, notify a customer that a reward has been issued, has been applied against a transaction(s), or is available for redemption against a selected transaction(s). In some embodiments, a customer may be notified that the customer is being considered or is eligible to receive or redeem a reward for any number of transactions entered into by the customer. In some embodiments, the reward may be issued, applied against a transaction, or made available for redemption without the customer becoming aware of the reward until such time as the customer views the statement or is otherwise notified. For example, the systems and methods described herein may select a transaction(s) that is to receive or redeem a reward. In some embodiments, any number of possible rewards are determined and made available to be redeemed or applied against the selected transaction(s). The determined rewards are then presented to the customer as possible options to select from. The customer may select one of the proffered rewards, or, in some embodiments, may request a different reward be applied.

In some embodiments, the systems and methods described herein may notify the customer that he has the option of selecting a transaction(s) to receive or redeem a reward. For example, the systems and methods described herein may select a reward that is to be applied to a customer's transaction(s). The customer may be notified and queried to select any number of transactions that should receive all or a portion of the reward. Other notification schemes are possible. In some embodiments, notification to a customer may be made electronically, such as, for example, via electronic mail or instant messaging, via telephone, facsimile, over the mail, or other form of communication.

Rewards issuance module 230 may, in some embodiments, issue rewards as appropriate based on customer or transaction selections made by transaction selection module 215, for example, or a customer. For example, rewards issuance module 230 may interface and communicate with the appropriate systems (external or internal) to reconcile account balances whenever a reward results in the lowering or paying off of a customer's outstanding balance associated with a transaction. In some embodiments, reward issuance module 230 may interface and communicate with reward systems that may cooperate with the systems and methods described herein to issue and offer rewards. For example, if a selected reward is a particular discount, coupon, or other reward, incentive or promotion of a merchant or vendor, for example, the systems and methods described herein—particularly rewards issuance module 230—may interface and communicate with the appropriate systems of such merchant or vendor to fulfill the reward. In some embodiments, rewards issuance module 230 may interface and communicate with any systems that coordinate the generation, reconciliation and provision of notifications, customer statements, catalogs and other appropriate communications to ensure that accurate and reliable information is presented to the customer.

In some embodiments, rewards issuance module 230 may calculate reward points or other earned or redeemable value based on any transaction particular. For example, rewards issuance module 230 may issue reward points based on any transaction particular, such as, for example, the date or time of a transaction, the type of transaction (e.g., purchase, balance inquiry, payment, transfer, etc.), the identity or location of the customer, card or account, the customer, card or account transaction history, the amount of a transaction (e.g., purchase amount, transfer amount, payment amount, etc.), the identity or location of a sponsor or other merchant or vendor through which the transaction is entered, the product or service purchased or sold, or any other particular of a transaction that may be used to issue reward points or other earned or redeemable value. In some embodiments, earned points may be stored and accumulated in corresponding customer point accounts. In some embodiments, a customer may apply earned reward points or other earned or redeemable value against outstanding balances. In some embodiments, rewards issuance module 230 may confirm that a customer has sufficient points to pay for a transaction, and may further reconcile the customer's account so that any funds which have been applied against the transaction are reimbursed or credited.

Statement/Catalog generation module 235 may, in some embodiments, present a customer associated with a selected transaction, for example, a statement that indicates the reward(s) obtained and/or the transactions selected. For example, if the customer's transaction involving the purchase of groceries at a grocery store is selected as the recipient of a reward by the systems and methods described herein, statement/catalog generation module 235 may present the customer with an electronic or paper statement indicating that the transaction has been paid off or discounted, for example, or that some other reward has been applied thereto. In some embodiments, statement/catalog generation module 235 may generate a catalog of rewards that the customer may utilize to select a reward(s) to apply to the selected transaction(s). In some embodiments, the statement or catalog may comprise a list of transactions that the customer may select from to designate a transaction(s) that is to receive the benefit of a reward. In some embodiments, the statement or catalog may offer the customer the opportunity to select a transaction and a reward. Such statement or catalog may be presented with the notification to the customer that a transaction has been selected or reward has been issued, applied or made available for redemption, while in some embodiments the statement or catalog may comprise the notification.

In some embodiments, the statement or catalog may be interactive such that a customer may, among other things, select a reward or transaction, decline a proffered reward or selected transaction, or request that the reward or selected transaction be changed or modified. For example, a statement or catalog may include any number of icons the customer may initiate to express its approval, denial or designation of a reward(s) or transaction(s). For example, a statement or catalog may indicate that a particular transaction was paid for, and afford the customer the opportunity to request that another transaction be the recipient of the reward or that another reward be applied. The statement or catalog may provide alternative options for the customer to specify that another transaction should receive the benefit. In some embodiments, the customer's request may be considered by the systems and methods described herein and a determination made as to whether the requested selection (e.g., a desired transaction or reward) is appropriate. In some embodiments, the statement or catalog is presented to the customer electronically, such as through electronic mail or instant messaging, for example, presented or made available to the customer via a web site or other interface, or presented in paper or other tangible form over the mail or any appropriate form of communication.

Customer selection module 240 may, in some embodiments, receive and process user input, designations or selections in connection with the selection of a reward or the selection of a transaction to receive the benefit of the reward. For example, upon being notified that a reward is available for redemption, customer selection module 240 may receive and process customer input relating to which transaction(s) the customer wants to receive the benefit of the reward. Similarly, customer selection module 240 may receive and process user input designating which reward(s) the customer wants to receive. In some embodiments, customer selection module 240 may determine whether a customer designation or selection is appropriate. For example, assume the systems and methods described herein select a particular transaction and apply a particular reward to the transaction. Upon being notified, the customer may express a desire—e.g., by interacting with a statement or catalog—that a different transaction receive the benefit, or that a different reward be applied to the selected transaction. Customer selection module 240 may receive the customer's input and determine whether the designation or selection is appropriate. In so doing, customer selection module 240 may consider, for example, rewards and transactions that are available to the customer, as well as any other data or information that may be relied upon to determine whether a customer's input or designation is appropriate. If the customer's input is appropriate, customer selection module 240 may further interface ensure that the proper reward(s) or transaction(s) are effected. If the input is not proper, however, customer selection module 240 may so inform the customer or proceed with a default or other proper reward or transaction selection.

Customer accounts module 245 may, in some embodiments, process and maintain data and information relating to customers, such as, for example, the identity of the customer, the location (e.g., residential or work address) of the customer, the customer's preferred or favorite merchants, vendors, products or services, the card(s) or account(s) associated with the customer, preferred transactions, the rewards associated with the customer, or any other data or information that may be used to dynamically identify, prioritize or order transactions, or select rewards or transactions according to the systems and methods described herein. In some embodiments, customer accounts module 245 may cooperate with the various modules described herein, for example, to associate customers with particular rewards to enable the various systems and methods described herein to dynamically select transactions and identify and offer rewards that are relevant and of interest to customers.

In some embodiments, customer accounts module 245 may, in some embodiments, process and maintain data and information relating to customer transactions. For example, customer accounts module 245 may, for a particular customer or customer, maintain and update data and information on any and all transactions (e.g., purchases) that the customer has processed or entered into, including the date of the transaction, the identity of the merchant or vendor, type of transaction, the amount of the transaction, the location of the transaction, the goods or services purchased (e.g., identified by SKU number), the reward earned (e.g., redeemable points, cash, sponsor or issuer redeemable value), or any other data or information that may be used to classify the transaction in such a way that it may be used to identify and offer rewards according to the systems and methods described herein. In some embodiments, customer accounts module 245 may also process and maintain data and information relating to customer transaction and rewards selections made by the customer or carried out by the systems and methods described herein.

Merchant accounts module 250 may, in some embodiments, maintain data and information on particular sponsors and other merchants and vendors, such as, for example, particular rewards that may be offered as a result of transactions with a particular merchant or vendor. In some embodiments, merchant accounts module 250 may maintain data and information on the types of transactions that may be rewarded, the customers that may receive rewards, and any other data or information that may be used to select transactions, customers or rewards as described herein. For example, merchant accounts module 250 may maintain data indicating that merchant A only wants to give rewards associated with purchases of a minimum amount, or that only customer in a particular state or geographic region, for example, are eligible to receive or redeem a reward. Other merchant parameters and preferences are possible. In some embodiments, particular sponsors or other merchants or vendors may selectively designate or modify parameters or preferences, such as by interacting with merchant accounts module 250 via merchant station 110, for example.

Administration module 240 may, in some embodiments, enable an administrator of rewards station 105, for example, to interact with the various modules, features and functionality described herein. For example, an agent of rewards station 105 may interact with administration module 255 to input, revise and remove data and information used by the various systems and methods described herein, such as, for example, customer information, transaction or reward information, or any other data or information that may be used to identify and offer reward to customers as described herein. In some embodiments, administration module 255 may enable an administrator of rewards station 105 to establish parameters or rules associated with the various features and functionality described herein. For example, an administrator may establish rules depending on specific business needs or fees associated with a merchant or vendor, or customer's use of the features and functionality described herein. Thus, a customer may be limited to a predetermined number of transaction or reward selections over a predetermined period of time, such as annually or monthly, for example. Other predetermined periods of time are of course possible. A customer may also be required to pay a fee to be able to be able to switch transactions or rewards. Such a fee may be, for example, annually or monthly imposed or may be charged on a one-time or per-transaction basis. In some embodiments, the fee may comprise a monetary amount or any other form of value. In some embodiments, delays may be imposed to verify that a particular exchange or movement of points was done properly and in good-faith (e.g., accrue rewards before they are actually available for redemption).

FIG. 3 illustrates a process flow 300 for offering rewards, according to an embodiment of the systems and methods described herein. In particular, FIG. 3 depicts the three stages of processing set forth in FIG. 1a above, namely: the reception of transactions; the ordering of transactions; and the selection of a winning transaction. As shown, the transaction reception stage shows seven (7) transactions being entered into by customers #1, #2 and #3. In this example, customer #1 has entered into three (3) transactions, customer #2 into two (2) transactions, and customer #3 into two (2) transactions. Each of the individual transactions is received by remote station 105 as described herein. In some embodiments, transactions received may correspond to a single customer, while in some embodiments transactions may be received from a plurality of customers, as shown. Once received, the transactions are then ordered or prioritized into a listing according to a particular ordering or prioritizing scheme, rule or algorithm. As shown, the transactions are ordered on a weekly basis according to date. Thus, during the week of Oct. 1, 2007, for example, the ordered listing of transactions would start with customer #1's ATM withdrawal of $10 on October 1^st and end with customer #1's purchase of an airline ticket on October 6^th. Of course, the transactions may be ordered hourly, daily, monthly, or according to any other time schedule, predetermined, random or otherwise. Similarly, other ordering or prioritization schemes, rules or algorithms may be utilized. Also shown in the listing of ordered transactions is the issuance of bonus rewards in the form of multiple entries for a single transactions. For example, transactions #s 6, 7 and 10 are repeated entries for the transaction #s 5 and 9, respectively. More specifically, bonus rewards in the form of two additional entries are issued for entering into transactions with a particular dry cleaning establishment, hence additional transaction #s 6 and 7, and an additional entry is added for purchases through a particular airline, hence additional transaction #10. Other schemes, rules or algorithms are possible for determining and issuing bonus rewards.

Once the transactions are ordered and prioritized, a winning customer or transaction may be selected. In some embodiments, the winning customer or transaction may be selected according to a particular selection scheme, rule or algorithm. For example, if the selection scheme is the first transaction or customer listed, then customer #1 would win because his is the first transaction appearing on the list. If the selection scheme is random selection, then anyone may win, but note that customer #1 has the greatest chance of winning given that he has three (3) transactions in comparison to customers #2 and #3, each of which has two (2) transactions. If the selection scheme is the most transactions, then customer #1 would win. If the selection scheme is who spent the most, then the winner would be customer #3 because he spent a total of $305 (not including bonus rewards). If, however, bonus rewards are included, then customer #1 would win. Other selection schemes, rules or algorithms are possible, including, for example, the other selection schemes, rules or algorithms shown in FIG. 3.

Once a winning customer or transaction is selected, the systems and methods described herein may notify the customer of the reward and either designate a reward and transaction to realize the reward, or permit the winning customer to designate a reward or a transaction to realize the reward, such as through an interactive statement or catalog, for example. Thus, if the first entry in the ordered list wins, then the systems and methods described herein may deposit $10 in the account from which customer #1 withdrew $10 via an ATM. In some embodiments, the system and methods described may reward $10 to customer #1 and have him designate which transaction(s) should realize the benefit. For example, customer #1 may opt to apply some or all of the $10 reward towards the $45 balance associated with dry cleaning. In some embodiments, customer #1 may request that, rather than receiving $10, no interest be charged on his outstanding balances on all transactions for a month. In some embodiments, the systems and methods described herein may determine whether the customer's request is appropriate. Other possibilities for selecting transactions or rewards are possible.

FIG. 4 illustrates a process flow 400 for offering rewards, according to an embodiment of the systems and methods described herein. In some embodiments, the systems and methods described herein may permit a customer to resolve balances or transactions with accumulated reward points or other earned value. For example, at step 405 a customer makes a purchase using a card or account (or cash). At step 410, reward station 105 may calculate reward points based on the amount spent on the transaction. At step 415, the points earned are stored in a points account. In some embodiments, the account may be associated with the particular customer. At step 420, if the purchase was made with a card or account, the purchase amount of the transaction is debited from the corresponding account. At step 425, the customer may receive an statement or catalog (online or paper) with details of the purchases, such as, for example, a list of purchases or transactions that the customer may apply earned points to. In some embodiments, the statement or catalog may be interactive. At step 430, the customer may choose which transaction(s) he would like to pay for with points. In some embodiments, a customer may proceed from step 405 directly to step 430, as indicated by the dashed line. At step 435, a determination is made as to whether the customer has enough points. In some embodiments, if the customer does not have enough points, then only the available points may be applied against the selected transaction(s). If the customer has enough points, then the transaction is approved and the points bank is debited the appropriate number of points, otherwise the transaction is denied at step 440. In some embodiments, the appropriate number of points is based on a predetermined ratio between points and cash, for example, or according to any scheme, rule or algorithm. At step 450, the customer's account may be credited for the purchase amount for the selected transaction(s). At step 455, the customer may receive a notification (e.g., an email) confirming the points transaction. At step 460, the transaction is completed. In some embodiments, points earned may be used to buy down a rate for a mortgage or home equity or other loan; pay for loans any other balance; increase rate for savings account; add funds to accounts or savings; and any other transaction that involves funds, cash or other value, for example.

FIG. 5 illustrates a process flow 500 for offering rewards, according to an embodiment of the systems and methods described herein. As shown, process flow 500 may be performed by the various systems and methods described herein. At step 505, at least one transaction occurrence is received. In some embodiments, a transaction occurrence may comprise a purchase, funds transfer, deposit, withdrawal, balance inquiry, or any other transaction that may be conducted with cash, a card or other device, or an account. At step 510, the at least one transaction is ordered or prioritized according to an ordering or prioritization scheme, rule or algorithm. At step 515, at least one reward is rewarded to a user associated with the at least one of the at least one transaction based on a reward selection scheme, rule or algorithm.

FIG. 6 illustrates a process flow 600 for offering rewards, according to an embodiment of the systems and methods described herein. At step 605, the various systems and methods described herein may select at least one reward or at least one customer or transaction that is to receive or redeem a reward. At step 610, a customer associated with the reward or the transaction that is to receive or redeem a reward may be notified of the selection. In some embodiments, the notification may be provided via a statement or catalog or other appropriate manner of communication. At step 615, a determination is made as to whether the customer approves, declines or requests a change or modification to the selected reward or transaction. For example, the customer may prefer that another reward or transaction be selected. In some embodiments, the customer's designation may be communicated via an interactive statement, catalog or other form of communication. If the customer approves of the reward and transaction, then the systems and methods described herein may proceed to apply the selected reward to the selected transaction. If the customer disapproves, or requests a change or modification to either the selected reward or transaction, then a determination is made at step 625 as to whether the customer has a preference for either a reward or a transaction. If not, then the process proceeds to 605 where another reward or transaction is selected. The process continues until such time as the customer approves of the selected reward and transaction.

If, however, the customer does have a preference at step 625, then a determination is made at step 630 on whether the preference is appropriate. In some embodiments, determining whether a reward or transaction selection of the customer is proper may comprise determining whether the selection conforms with applicable parameters that set forth or limit the types of transactions or rewards that are available to the customer. Other parameters are possible. If the preference is appropriate, then the reward is applied to the transaction—either of which may be selected by the customer—at step 620. If the preference is not proper, then the customer is so informed and the process proceeds to step 625 until such time as a proper preference or selection is put forward, either by the customer or the systems or methods described herein.

The embodiments of the present inventions are not to be limited in scope by the specific embodiments described herein. For example, although many of the embodiments disclosed herein have been described with reference to rewards programs, the principles herein are equally applicable to the any type of program, rewards or otherwise, that may enroll customer or users. In addition, although many of the embodiments disclosed herein have been described with reference to a rewards station that is associated with a card or account issuer, such as a bank, for example, it should be appreciated that various aspects of the invention may be accomplished when various system components are located elsewhere. For instance, the rewards station described herein may be maintained and administered by a third party service provider. Indeed, various modifications of the embodiments of the present inventions, in addition to those described herein, will be apparent to those of ordinary skill in the art from the foregoing description and accompanying drawings. Thus, such modifications are intended to fall within the scope of the following appended claims.

Further, although the embodiments of the present inventions have been described herein in the context of a particular implementation in a particular environment for a particular purpose, those of ordinary skill in the art will recognize that its usefulness is not limited thereto and that the embodiments of the present inventions can be beneficially implemented in any number of environments for any number of purposes. In some embodiments, for example, a merchant may use the systems and methods described herein to offer rewards in the manner described. For example, a particular electronics retailer may initiate a promotion wherein a customer entering into a transaction with a card, account, or cash, for example, may be selected to receive the good or service purchased for free. That is, the various systems and methods described herein may provide a platform for merchants to provide reward programs and other like incentives. Accordingly, the claims set forth below should be construed in view of the full breadth and spirit of the embodiments of the present inventions as disclosed herein.