Mobile payer authentication

An address of a computing device for conducting a transaction with a merchant on an account of an account holder is used to obtain display attributes of the computing device. An authentication request is formatted using the obtained display attributes of the computing device. The formatted authentication request is sent for delivery to the logical address of the computing device. In response to the formatted authentication request, authentication information for the account holder is received from the logical address of the computing device. A validation attempt is performed on the received authentication information for the account holder. If the received authentication information for the account holder was successfully validated by the performance of the validation attempt, the authentication response is transmitted for delivery to a logical address for the merchant.

FIELD

The invention is related to a payment processing system in which a transaction between a merchant and a consumer conducted on an account issued by an issuer, where the transaction is acquired from the merchant by an acquirer for collection on the account from the issuer through a transaction handler or transaction processor.

BACKGROUND

During a transaction using a transaction card, such as a credit card, a debit card, a stored value card, a bank card, a loyalty card, a smart card and/or the like, it is important to verify a cardholder's ownership of an account to avoid a variety of problems, such as unauthorized use. Cardholder authentication is the process of verifying that the account is owned by the cardholder. For example, cardholder authentication during a “card present” transaction is performed when a merchant's representative verifies that the signature on a transaction card matches the cardholder's signature on a receipt.

Technological improvements have allowed businesses and individuals to engage in transactions in a plurality of environments. For example, cardholders can engage in traditional “in person” transactions, transactions via the internet, transactions over the telephone and transactions through mail systems. In many cases, cardholders desire the convenience of performing transactions without having to directly visit a service provider. In doing so, the cardholder may seek to eliminate transportation time and reduce the hassle associated with, for example, shopping in a retail environment or waiting in line at a bank by performing these transactions from the privacy of their own home.

“Card Not Present” (“CNP”) transaction volumes are increasing at least in part because of such convenience provided to cardholders and the extra sales provided to merchants. However, as CNP transaction volume increase, fraudulent transactions and the monetary losses due to such transactions are increasing as well.

FIG. 1depicts a system diagram for a conventional transaction processing system according to the prior art. As shown inFIG. 1, a transaction processing system is logically divided into an issuer domain110, an interoperability domain120and an acquirer domain130. The issuer domain110includes a consumer112and an access control server114(“ACS”). The interoperability domain120includes a directory server122(“DS”). The acquirer domain130includes a merchant purchase interface132(“MPI”) and an acquirer bank134. The lines represent data transfers performed between the connected entities. Such data transfers are described more fully below in reference toFIG. 2.

FIG. 2depicts a conventional CNP transaction flow according to the prior art. As shown inFIG. 2, a consumer adds items to a shopping cart and finalizes205a transaction. The MPI132sends210an enrollment verification request to a DS122to verify enrollment of the consumer112in the authentication service. If the consumer112is enrolled in the authentication service, the DS122forwards215the enrollment verification request to the ACS114. The ACS114responds220to the DS122with an enrollment verification response indicating whether authentication is available for the consumer's card. The DS122then forwards225the enrollment verification response to the MPI132. If the consumer is participating in the authentication service, the DS122creates and sends230a response to the MPI132.

If card authentication is available, the MPI132sends235a request for payer authentication to the ACS114via the consumer's internet browser112. The ACS114receives240the payer authentication request. The ACS114then displays245a window to the consumer displaying payment details such as, for instance, a merchant name, merchant location, total cost, purchase date and card number. The window also prompts the cardholder for the cardholder's authentication information, such as a password, personal identification number, or chip cryptogram. After the consumer enters submits the authentication information, the ACS114validates250the consumer's authentication information. If the consumer's authentication information is valid, the ACS114generates and sends255a payer authentication response to the MPI132in response to the payer authentication request, thereby authenticating the consumer112. The ACS114may digitally signs the payer authentication request. The MPI132then receives260the payer authentication response and validates265the response signature if the response signature was signed by the ACS114. The MPI132then commences270an authorization exchange with its acquirer134.

When the consumer is using an internet enabled cellular telephone, the above-referenced and method may be inadequate. Thus, there is a need for solutions to the inadequacies

SUMMARY

An address of a computing device is received. The address is used to access display attributes of a display on the computing device. An authentication request is formatted using the obtained display attributes and is sent to computing device. In response to the, authentication information for an account holder is received from the computing device. A validation attempt is performed on the received authentication information for the account holder. If the received authentication information for the account holder was successfully validated, the authentication response is transmitted for delivery to a merchant with whom the account holder is conducting a transaction with the merchant upon an account of the account holder by use of the computing device. In another implementation, the foregoing computing device is a cellular telephone having address is its telephone number, where the cellular telephone is enable to conduct the transaction as an e-commerce transaction with a web site of the merchant over the internet.

DETAILED DESCRIPTION

In one implementation, there is received a logical address of a computing device having a display with display attributes. The computing device is being used to conduct a transaction and the logical address is received while the transaction being conducted by a merchant upon an account of an account holder. Display attributes of the display of the computing device are obtained by accessing, using at least the logical address of the computing device, a database stored on a network device of the network. An authentication request is formatted using the obtained display attributes of the computing device. The formatted authentication request is sent for delivery to the logical address of the computing device. In response to the formatted authentication request, authentication information for the account holder is received from the logical address of the computing device. A validation attempt is performed on the received authentication information for the account holder. If the received authentication information for the account holder was successfully validated by the performance of the validation attempt, the authentication response is transmitted for delivery to a logical address for the merchant.

In a variation of the foregoing implementation, if the received authentication information for the account holder was successfully validated by the performance of the validation attempt, the authentication response is digitally signed. The, the authentication response that is transmitted for delivery to the logical address is a digitally signed authentication response In another variation of the foregoing implementation, the computing device is a cellular telephone whose logical address is a cellular telephone number. In yet another variation, a transmission is received containing information confirming the authorization of the transaction by the issuer of the account. A message is formatted, using the obtained display attributes of the computing device, to contain the information confirming the authorization of the transaction by the issuer of the account. The formatted message is transmitted for delivery to the logical address of the computing device.

In another implementation, there is received, at one of a plurality of network devices on a network, from a logical address of an e-commerce website of a merchant, incident to an e-commerce transaction being conducted by the merchant upon an account of an account holder: (i) a telephone number of a web enabled cellular telephone having a display with display attributes that is being used to conduct the e-commerce transaction; and (ii) an enrollment verification request.

In response to the enrollment verification request, a verification is made that the account and the web enabled cellular telephone are both enrolled in an authentication service. A verification that the account and the web enabled cellular telephone are both enrolled in the authentication service is transmitted for delivery to the logical address of the e-commerce website of the merchant. There is thereafter received, in response to the verification that the account and the web enabled cellular telephone are both enrolled in the authentication service, at one of the plurality of network devices on the network: (i) the telephone number of the web enabled cellular telephone; (ii) an identifier for the merchant; (iii) a total currency amount for the transaction; and (iv) an identifier for the account. The display attributes of the display of the web enabled cellular telephone are obtained by accessing a display attributes database using at least the telephone number of the web enabled cellular telephone. An authentication request is formatted using the obtained display attributes of the display of the web enabled cellular telephone. The formatted authentication request is transmitted for delivery to the telephone number of the web enabled cellular telephone. The formatted authentication request includes: (i) an identifier for the merchant; (ii) the total currency amount of the transaction; and (iii) an identifier for the account. Authentication information for the account holder that includes an access code is received from the telephone number of the web enabled cellular telephone in response to the formatted authentication request. A validation attempt is made using at least the access code on the received authentication information for the account holder. If the received authentication information for the account holder was successfully validated by the performance of the validation attempt, then the authentication response is digitally signed and transmitted for delivery to the logical address of the e-commerce website of the merchant from one of the plurality of network devices on the network. As such, an authorization request for the transaction being conducted on the account can be sent to an acquirer for the merchant that identifies the received authentication information for the account holder as being successfully validated.

In a variation of the foregoing implementation, the display attributes of the display of the web enabled cellular telephone can be a mark-up language and a character set supported by the web enabled cellular telephone. In another variation, the can be received, at one of the plurality of network devices on the network, a transmission containing information confirming the authorization of the transaction by the issuer of the account. A message can be formatted using the obtained display attributes of the web enabled mobile computing device and containing data representing the confirmation of the authorization of the transaction by the issuer of the account. The formatted message can then be transmitted, from one of the plurality of network devices on the network, for delivery to the logical address of the web enabled mobile computing device.

FIG. 3depicts a system diagram for an exemplary transaction processing system according to an embodiment. A system according to a preferred embodiment comprises a consumer112, MPI132, DS122, ACS114, Acquirer Bank134, and mobile authentication component (MAC)116. The MAC116further comprises a Consumer Mobile Device database (CMDD)124contains information allowing the MAC116to determine a mobile device's supporting mark-up languages and character sets based upon the mobile device's number.

FIG. 4depicts a flow diagram for an exemplary transaction flow400using a mobile internet device according to an embodiment. As shown inFIG. 4, a consumer may select one or more items for purchase via an MPI132and finalize402purchased items. The MPI132may then extract404the consumer's mobile number from the internet message headers of messages sent to the MPI132by the consumer112. The MPI132may then flag406the transaction as a mobile transaction. The MPI132may transmit408an enrollment verification request (“VEReq”) to a DS122so that the MPI132may verify enrollment of the consumer112in an authentication service. The VEReq should include the consumer's mobile number and the mobile transaction flag. If the consumer is enrolled in the authentication service, the DS122may forward410the VEReq to an appropriate ACS114. The VEReq should still, of course, include the consumer's mobile number and the mobile transaction flag. The ACS114may provide412an enrollment verification response (“VERes”) to the DS122that indicates whether authentication is available for the consumer's cellular telephone and account upon which the transaction is to be conducted with the merchant. The DS122may then forward414the VERes provided by the ACS114to the MPI132.

If authentication is available for the consumer's cellular telephone, the MPI132may transmit416a payer authentication request (“PAReq”) to the ACS114via the DS122. The ACS114then determines418whether the transaction is a mobile transaction by reviewing the mobile transaction flag.

Once the ACS114has determined that the transaction is a mobile transaction, the ACS114may send420a mobile authentication request to the MAC116. The mobile authentication request should include at least the consumer's mobile number. In a preferred embodiment, the mobile authentication request also includes a merchant name, merchant location, total cost, purchase date and card number. The MAC116then determines422the mark-up language and character set supported by the customer's mobile device by accessing the CMDD124using the consumer's mobile number. The MAC116then formats424an authentication information request to the consumer using the consumer's mobile device's supported mark-up language and character set. The MAC116may then transmit426the authentication information request to the consumer. The authentication information request may prompt the cardholder for the cardholder's authentication information, such as a password, personal identification number, or chip cryptogram.

The authentication information request may further display payment details such as, for instance, a merchant name, merchant location, total cost, purchase date and card number. After a consumer submits the authentication information to the MAC116, the MAC116may forward428the authentication information to the ACS114. The ACS114may then validate430the consumer's authentication information. If the consumer's authentication information is valid, the ACS114generates and sends432, in response to the payer authentication request, a payer authentication response to the MPI132(through the DS122), thereby authenticating the consumer112.

The ACS114may digitally sign the payer authentication request. The MPI132then receives434the payer authentication response and validates436the signature of the ACS114if the payer authentication response was signed by the ACS114. The MPI132then commences438an authorization exchange with its acquirer134by sending an authorization request message to the acquirer134.

The authorization exchange is complete when the acquirer134sends an authorization response message to MPI132indicating that the issuer of the account upon which the transaction is being conducted is an authorized transaction. Receipt by MPI132of the authorization of the transaction from the acquirer134, the transaction may be completed440. The ACS may send442a transaction complete message to the MAC116indicating that the transaction was successfully completed. The MAC116may format444the transaction complete message and transmit446the message to the consumer112.

Payment Processing System

The Payment System illustrated inFIG. 5depicts an exemplary process which can be used by the foregoing Implementations with respective modifications as described therein.

A transaction includes participation from different entities that are a component of a payment processing system500including an issuer502, a transaction handler504, such as a credit card company, an acquirer506, a merchant508, or a user510such as an account holder and/or consumer. The acquirer506and the issuer502can communicate through the transaction handler504. Merchant508will be a person or entity that sells goods or services. Merchant508may utilize at least one Point-of-Service (POS) terminal that can communicate with the acquirer506, the transaction handler504, or the issuer502. Thus, the POS terminal is in operative communication with the payment processing system500.

Typically, a transaction begins with the user510, such as an account holder or a consumer, wirelessly presenting a Consumer Portable Transaction Payment Device (CPTPD)512, for instance an cellular telephone, a World Wide Web enabled mobile device, to merchant508to initiate an exchange for a good or service. The CPTPD512may include a volatile or non-volatile memory to store information such as an identifier for an account issued by the issuer502to the user510(e.g., the account holder), where the transaction is to be conducted upon the account.

Merchant508may use the POS terminal to obtain account information, such as an account number, from the CPTPD512. The CPTPD512may interface with the POS terminal using a mechanism that may include a contactless system using a radio frequency and/or magnetic field recognition system. The POS terminal sends a transaction authorization request to the issuer502of the account. Alternatively, or in combination, the CPTPD512may communicate with the issuer502, the transaction handler504, or the acquirer506.

The issuer502may authorize the transaction using the transaction handler504. The transaction handler504may also clear the transaction. Authorization includes the issuer502, or the transaction handler504on behalf of the issuer502, authorizing the transaction in connection with the issuer's502instructions such as through the use of business rules. The business rules could include instructions or guidelines from the transaction handler504, the user510, merchant508, the acquirer506, the issuer502, a financial institution, or combinations thereof. The transaction handler504may maintain a log or history of authorized transactions. Once approved, merchant508will record the authorization, allowing the user510to receive the good or service for the completion of the transaction.

Merchant508may, at discrete periods, such as the end of the day, submit a list of authorized transactions to the acquirer506or other components of the payment processing system500. The transaction handler504may compare the submitted authorized transaction list with its own log of authorized transactions. If a match is found, the transaction handler504may route authorization transaction amount requests from the corresponding acquirer506to the corresponding issuer502involved in each transaction. Once the acquirer506receives the payment of the authorized transaction amount from the issuer502, it can forward the payment to merchant508less any transaction costs, such as fees. If the transaction involves a debit or pre-paid card, the acquirer506may choose not to wait for the initial payment prior to paying the merchant508.

There may be intermittent steps in the foregoing process, some of which may occur simultaneously. For example, the acquirer506can initiate the clearing and settling process, which can result in payment to the acquirer506for the amount of the transaction. The acquirer506may request from the transaction handler504that the transaction be cleared and settled. Clearing includes the exchange of financial information between the issuer502and the acquirer506and settlement includes the exchange of funds. The transaction handler504can provide services in connection with settlement of the transaction. The settlement of a transaction includes depositing an amount of the transaction settlement from a settlement house, such as a settlement bank, which the transaction handler504typically chooses, into a clearinghouse, such as a clearing bank, that the acquirer506typically chooses. The issuer502deposits the same from a clearinghouse, such as a clearing bank, which the issuer502typically chooses into the settlement house. Thus, a typical transaction involves various entities to request, authorize, and fulfill processing the transaction.

FIG. 6depicts an exemplary process for the provision of a service by a merchant to a consumer in authorizing and remunerating electronic payment by a account holder (p)608in conducting a financial transaction with the merchant (i.e.; a credit card transaction). The diagram ofFIG. 6depicts an exemplary process600of a particular financial transaction system which can be used by the foregoing Implementations with respective modifications as described therein. By way of explanation for the nomenclature of reference numerals used in the Figures and described in the specification, a lower case letter in parenthesis is intended to mean an integer variable having a value from 1 to the capital case of the lower case letter, which value can be large (i.e., approaching infinity). Thus ‘(b)’ is intended to mean that the integer ‘b’ can have a value from 1 to B, and ‘(c)’ is intended to mean that the integer ‘c’ can have a value from 1 to C, etc. As such, drawing elements604,606,608,610,680,682, and684inFIG. 6are illustrated with a block, but indicate one or more elements can be present. For example, Issuer (j)604is one of a possible plurality of issuers, where j may range from 1 to a large integer.

Account holder (p)608communicates660an identifier for a mobile consumer transaction payment device to a web service662for authentication thereof as described about relative toFIGS. 4-5, which authentication may include communication with an other database (v)686. Upon such authentication, the Account holder (p)608communicates an identifier for an account to a Merchant (m)610(at step658) by use of a mobile payment device that contains the identifier for the account. The communication of the account can be through the hardware, software, and telecommunications mechanisms of web service662. The account is to be used as tender for a financial transaction with the such as a purchase of goods. Those of skill in the art will recognize that other financial transactions and instruments other than credit cards may also be used, including, but not limited to, a prepaid card and a debit card. For purposes of illustration and explanation, however, reference will be made to a credit card.

As part of the transaction, the Account holder's608mobile payment device can be a cellular telephone, a web enabled Personal Digital Assistant (PDA) or other mobile device, etc. The mobile payment device sends information to and from the Merchant (m)610, whereupon the information for the account is read from the payment device. Merchant (m)610then sends a request for authorization to the Merchant's610Acquirer (i)606(at step662). Each Acquirer (i)606is a financial organization that processes credit card transactions for businesses, for example merchants, and is licensed as a member of a transaction handler (TH)602such as a credit card association (i.e., Visa Inc., MasterCard, etc.) As such, each Acquirer (i)606establishes a financial relationship with one or more Merchants (n)610.

The Acquirer (i)606transmits the account information to the TH602(at step670), who in turn routes the request to the account holder's issuing bank, or Issuer (j)604(at step676). The Issuer (j)604returns authorization information to the TH602(at step674) who returns the information to the Merchant (m)610through the Acquirer (i)606(by steps668and666). The Merchant (m)610now knowing whether the Issuer's (j)604credit card account is valid and supports a sufficient credit balance, may complete the transaction and the Account holder (p)608in turn receives goods and/or services in exchange (at step656). Most credit card associations instruct merchants that, after receiving authorization, the detailed credit card account information obtained from the point of sale magnetic stripe scanner must be deleted.

To reconcile the financial transactions and provide for remuneration, information about the transaction is provided by the Merchant (m)610to Acquirer (i)606(at step662), who in turn routes the transaction data to the TH602(at step670) who then provides the transaction data to the appropriate Issuer (j)604(at step676). The Issuer (j)604then provides funding for the transaction to the TH602(at step674) through a settlement bank (not shown). The funds are then forwarded to the Merchant's (n)610Acquirer (i)606(at step668) who in turn pays the Merchant (m)610for the transaction conducted at step662less a merchant discount, if applicable. The Issuer (j)604, then bills the Account holder (p)608(at step650), and the Account holder (p)608pays the Issuer604(at step652), with possible interest or fees.

Each of the Issuer (j)604, Merchants (n)610, Acquirer (i)606and the TH602may have access to information resources having one or more of the following databases: transaction database (z)682, merchant database (y)684, or account database (w)680. These databases can be connected by a network, internet, virtual private network, or by other means known to those skilled in the art. Moreover, not every participant must necessarily have access to any or all of the databases. Each database can assign read, write, and query permissions as appropriate to the various participants. For example, a Merchant (m)610have read access to the account database (w)680and the Issuer (j) may have read and write access.

The transaction database (z)682is designed to store some or all of the transaction data originating at the Merchants (n)610that use a payment device for each transaction conducted between an Account holder (p)608and the Merchant (m)610. The transaction data can include information associated with the account of an Account holder (p)608, date, time, and location among other more specific information including the amount of the transaction. The database can be searched using account information, date and time (or within proximity thereof), or by any other field stored in the database.

The Merchant database (y)684is designed to store information about each Merchant (m)610. The Merchant database (y) can contain information such as the unique identification of each Merchant (n)810, an identifier for each point of sale device in use by the Merchant (m)610, and location of the Merchant (m)610.

The account database (w)680is designed to store account information for payment devices associated with Account holder (p). The account database (w)660can store part or all of an account number, unique encryption key, account information, account name. The information from the account database (w)680can be associated with information from the transaction database (z)682.

An Account holder (p)608initiates a transaction with a Merchant (m)610by presenting a payment device at step658to the Merchant (m)610. The payment device is typically presented at the Point Of Service terminal (POS) at which data thereon is read. Certain transaction information is transmitted from the POS in route to the Merchant's (n)610Acquirer (i)606. The transaction information can include account information, account name, transaction balance, transaction time, transaction date, and transaction location. Sensitive information includes information such account number and account holder name that identify and associate a particular account with a particular account holder. This transaction information may be transmitted via a less secure communication medium. In addition, a transmission of transaction data may occur with weak or no encryption between two or more points from the point of origin, such as the point of sale device at the Merchant (m)610, and the ultimate destination, such as the Acquirer (i)606. These points can include, without limitation, from the reader at the POS, the POS at the Merchant (m)610and a network router or computer that is connected to a network but is housed and maintained by the Merchant (m)610and between the Merchant (m)610and the Acquirer (i)606. The communication channel could be Ethernet, wireless internet, satellite, infrared transmission, or other known communication protocols. Some or all of the transmission may also be stored for record keeping, archival or data mining purposes with little or no encryption. For example, the Merchant (m)610may store transaction data, including certain account information in the Merchant's (n)610accounts on file database for reuse later.

In this process, transaction information is retrieved from the POS at a Merchant (m)610. The transaction information is comprised of account information together with other information about the transaction itself: time, date, location, value, etc. Certain of the transaction information is considered sensitive information including, without limitation, account number, credit card verification number, and account name.

In FIGS.3and5-6illustrates exemplary telecommunications networks that each may make use of any suitable telecommunications network and may involve different hardware, different software and/or different protocols then those discussed below. These global telecommunications networks supports purchase and cash transactions using any bankcard, travel and entertainment cards, and other private label and proprietary cards. The network also supports ATM transactions for other networks, transactions using paper checks, transactions using smart cards and transactions using other financial instruments.

These transactions are processed through the network's authorization, clearing and settlement services. Authorization is when an issuer approves or declines a sales transaction before a purchase is finalized or cash is dispersed. Clearing is when a transaction is delivered from an acquirer to an issuer for posting to the customer's account. Settlement is the process of calculating and determining the net financial position of each member for all transactions that are cleared. The actual exchange of funds is a separate process.

Transactions can be authorized, cleared and settled as either a dual message or a single message transaction. A dual message transaction is sent twice-the first time with only information needed for an authorization decision, an again later with additional information for clearing and settlement. A single message transaction is sent once for authorization and contains clearing and settlement information as well. Typically, authorization, clearing and settlement all occur on-line.

FIGS. 5-6include one or more transaction handlers504,602, access points630,632, acquirers506,606, and issuers502,606. Other entities such as drawee banks and third party authorizing agents may also connect to the network through an access point. An interchange center is a data processing center that may be located anywhere in the world. In one embodiment, there are two in the United States and one each in the United Kingdom and in Japan. Each interchange center houses the computer system that performs the network transaction processing. The interchange center serves as the control point for the telecommunication facilities of the network, which comprise high speed leased lines or satellite connections based on IBM SNA protocol. Preferable, the communication lines that connect an interchange center (transaction handlers504,602) to remote entities use dedicated high-bandwidth telephone circuits or satellite connections based on the IBM SNA-LU0 communication protocol. Messages are sent over these lines using any suitable implementation of the ISO 8583 standard.

Access points630,632are typically made up of small computer systems located at a processing center that interfaces between the center's host computer and the interchange center The access point facilitates the transmission of messages and files between the host and the interchange center supporting the authorization, clearing and settlement of transaction. Telecommunication links between the acquirer (q)606and its access point, and between the access point and issuer (i)604are typically local links within a center and use a proprietary message format as preferred by the center.

A data processing center (such as is located within an acquirer, issuer, or other entity) houses processing systems that support merchant and business locations and maintains customer data and billing systems. Preferably, each processing center is linked to one or two interchange centers. Processors are connected to the closest interchange, and if the network experiences interruptions, the network automatically routes transactions to a secondary interchange center. Each interchange center is also linked to all of the other interchange centers. This linking enables processing centers to communicate with each other through one or more interchange centers. Also, processing centers can access the networks of other programs through the interchange center. Further, the network ensures that all links have multiple backups. The connection from one point of the network to another is not usually a fixed link; instead, the interchange center chooses the best possible path at the time of any given transmission. Rerouting around any faulty link occurs automatically.

Various terms may be used herein, which are to be understood according to the following descriptions 1 through 8:

1. Acceptance point device includes a device capable of communicating with a payment device, where the acceptance point device can include a Point of Device (POS) device, a smartcard, a payment card such as a credit or debit card with a magnetic strip and without a microprocessor, a keychain device such as the SPEEDPASS® commercially available from ExxonMobil® Corporation, a cellular telephone, personal digital assistant (PDA), a pager, a security card, an access card, a smart media, a transponder, personal computer (PC), tablet PC, handheld specialized reader, set-top box, electronic cash register (ECR), automated teller machine (ATM), virtual cash register (VCR), kiosk, security system, or access system;

2. Account holder or user includes any person or entity with an account and/or a payment device associated with an account, where the account is within a payment system;

3. Issuer includes any entity that issues one or more accounts and/or payment devices;

4. Merchant includes any entity that supports an acceptance point device;

5. Participant includes any user, person, entity, charitable organization, machine, hardware, software, merchant or business who accesses and uses the system of the invention, such as any consumer (such as primary member and supplementary member of an aggregate consumer account), retailer, manufacturer, and third-party provider, and any subset, group or combination thereof;

6. Redemption includes obtaining a reward using any portion of points, coupons, cash, foreign currency, gift, negotiable instruments, or securities;

8. Payment device includes a card, smartcard, ordinary credit or debit cards (with a magnetic strip and without a microprocessor), a keychain device (such as the SPEEDPASS™ commercially available from Exxon-Mobil Corporation), cellular telephone, personal digital assistant (PDA), pager, payment card, security card, access card, smart media, or transponder, where each payment device can include a loyalty module with a computer chip with dedicated hardware, software, embedded software, or any combination thereof that is used to perform actions associated with a loyalty program.

The limited to the particular methodologies or protocols described herein, as these may vary. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to limit the scope of the present disclosure, which will be limited only by the appended claims.

It must be noted that as used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural reference unless the context clearly dictates otherwise. Thus, for example, reference to a “transaction” is a reference to one or more transactions and equivalents thereof known to those skilled in the art, and so forth. Unless defined otherwise, all technical and scientific terms used herein have the same meanings as commonly understood by one of ordinary skill in the art. Although any methods and materials similar or equivalent to those described herein can be used in the practice or testing of the present invention, the preferred methods, devices, and materials are now described. All publications mentioned herein are incorporated herein by reference. Nothing herein is to be construed as an admission that the invention is not entitled to antedate such disclosure by virtue of prior invention.

The steps of a method, process, or algorithm described in connection with the implementations disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The various steps or acts in a method or process may be performed in the order shown, or may be performed in another order. Additionally, one or more process or method steps may be omitted or one or more process or method steps may be added to the methods and processes. An additional step, block, or action may be added in the beginning, end, or intervening existing elements of the methods and processes.

The above description of the disclosed implementations is provided to enable any person of ordinary skill in the art to make or use the disclosure. Various modifications to these implementations will be readily apparent to those of ordinary skill in the art, and the generic principles defined herein may be applied to other implementations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the implementations shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.