JP2017528822A - Method and system for processing real-time rebate in transaction authorization - Google Patents

Abstract

Disclosed are systems and methods for processing payment transactions involving reward accounts. One exemplary method includes receiving an authorization request for a payment transaction involving a reward account. The authorization request includes at least the transaction amount. The method also determines, based on the reward preference, whether the payment transaction is eligible for a reward rebate and, when the payment transaction is eligible, sends a request for reward rebate Including.

Description

  This application is a PCT international application filed on August 21, 2014, US patent application Ser. No. 14 / 465,063, and claims priority to that application. US patent application Ser. No. 14 / 465,063 is a continuation-in-part of US patent application Ser. No. 14 / 058,548, filed Oct. 21, 2013. The entire disclosure of the above application is incorporated herein by reference.

  The present disclosure relates to initiating a rebate of a payment transaction funded using a compensation account, and more particularly, to automatically initiating a rebate on a compensation account after processing a payment transaction based on a compensation balance. .

  This section provides background information related to the present disclosure, which is not necessarily prior art.

  In an effort to increase usage, many payment card issuers offer cardholders a reward for using their payment card. Compensation points include reward points that can be redeemed for cash or products, cashbacks, airline mileage, reward points from specific sources (eg travel services, hotels, merchants, retailers, etc.) at each level It can be provided in various forms, such as activity-based reward levels that can have benefits. However, these conventional reward schemes often require a significant amount of action that must be performed by the cardholder to benefit. In addition, cardholders are generally not able to use rewards directly at the point of sale, but instead are required to redeem rewards, receive rewards, and then use the rewards at the point of sale. .

US Patent Application Publication No. 2010/0057553

  Several systems and methods have been developed to allow reward points or other benefits to be redeemed when using special payment cards in order to simplify redeeming reward benefits at point of sale. Has been. For example, the system described in U.S. Patent Application Publication No. 2010/0057553, filed September 4, 2009, which is incorporated herein by reference in its entirety, is Use a payment card that is authorized only for the use of the reward balance. However, since the card is only authorized for the use of points, the card is not available to be used for traditional payment transactions, which is particularly desirable for consumers to carry multiple payment cards. Failure to do so may cause consumer dissatisfaction or confusion. Another system has been developed that includes a physical switch on the payment card that can be switched by the cardholder to switch between use as a traditional payment card and payment by reward balance. ing. However, this can also be frustrating to consumers who may forget to switch between usage types. In addition, the difference between the two payment methods may prevent the cardholder from paying using both credit and reward balance.

  The scope of the present disclosure is best understood from the following detailed description of exemplary embodiments when read in conjunction with the accompanying drawings. The drawings include the following figures.

1 is a high-level architecture illustrating a system for initiating a rebate of a payment transaction funded using a reward account according to an exemplary embodiment. FIG. FIG. 2 is a block diagram illustrating the processing server of FIG. 1 for initiating a rebate of a payment transaction funded by a reward account according to an exemplary embodiment. 6 is a flow diagram illustrating a process for processing payment transactions funded using a reward account and initiating and processing a rebate for a reward account based on the reward balance, according to an exemplary embodiment. 3 is a flow diagram illustrating a process for initiating a rebate request by the processing server of FIG. 2 after a payment transaction funded using a reward account, according to an exemplary embodiment. FIG. 3 is an exemplary interface for receiving consumer preference selections. 6 is a flow diagram illustrating an exemplary method for initiating a rebate of a payment transaction funded using a reward account in accordance with an exemplary embodiment. FIG. 6 is a block diagram of another exemplary system of the present disclosure suitable for use in processing payment transactions involving a reward account. 8 is a flow diagram of an exemplary method for processing a payment transaction involving a reward account according to the system of FIG. 8 is a flowchart of an exemplary method for processing a payment transaction involving a reward account associated with a third party, according to the system of FIG. 1 is a block diagram illustrating a computer system architecture according to an exemplary embodiment. FIG.

  Further areas of applicability of the present disclosure will become apparent from the detailed description provided below. It should be understood that the detailed description of the exemplary embodiments is intended for purposes of illustration only and is therefore not necessarily intended to limit the scope of the present disclosure.

  Exemplary embodiments will now be described more fully with reference to the accompanying drawings.

(Definition of terms)

Payment network—A system or network used to move money by using a cash substitute. The payment network can use a variety of different protocols and procedures to handle money transfers for different types of transactions.
Transactions that can be carried out via a payment network may include purchases of products or services, credit purchases, debit transactions, funds transfers, account withdrawals, and the like. The payment network can be configured to conduct transactions with cash alternatives that may include payment cards, letters of credit, checks, financial accounts, and the like. Examples of networks or systems configured to function as payment networks include MasterCard (R), VISA (R), Discover (R), American Express (R), PayPal (R), etc. Including those operated. Where the term “payment network” is used herein, this refers to both an organizational payment network and a physical payment network, such as equipment, hardware, and software that includes the payment network. May point.

  Payment account—a financial account that can be used to fund a transaction, such as a checking account, savings account, credit account, virtual payment account, and the like. A payment account may be associated with an organization that may include individuals, families, businesses, corporations, government agencies, and the like. In some instances, the payment account may be virtual, such as an account operated by PayPal® or the like.

  Payment card-a card or data associated with a payment account that can be presented to a merchant to fund a financial transaction via the associated account. Payment cards may include credit cards, debit cards, charge cards, stored value cards, prepaid cards, fleet cards, virtual payment numbers, virtual card numbers, control payment numbers, and the like. A payment card may be a physical card that can be presented to a merchant, or data representing an associated payment account (eg, as stored in a communication device such as a smartphone or computer). ). For example, in some instances, data that includes a payment account number may be considered a payment card for processing transactions funded by an associated payment account. In some instances, a check may be considered a payment card if desired.

  Reward Account—A payment account that can earn a reward for the account owner when funding a transaction. The reward may be in the form of points, levels, cashbacks, mileage, or other suitable frequency values as will be appreciated by those skilled in the art. The amount of unpaid reward may be referred to as the reward balance, for example, the reward balance may increase (become higher) as a result of more reward being acquired by the account owner. As used herein, “points” may generally refer to reward account rewards, and “point balances” may generally refer to reward account reward balances.

  Merchant—An organization that provides products (eg, goods and / or services) for purchase by another organization, such as a consumer or another merchant. A merchant may be a consumer, retailer, wholesaler, manufacturer, or any other type of organization that can provide products for purchase, as appreciated by those skilled in the art. . In some cases, the merchant may have special knowledge in the goods and / or services offered for purchase. In other cases, the merchant may not have or need any special knowledge in the products provided. In some embodiments, an organization involved in a single transaction can be considered a merchant.

  Issuer—An organization that establishes (eg, opens) a letter of credit or credit line that is in the interest of the recipient and provides a discount that is drawn by the recipient against the amount specified in the letter of credit or credit line. In many cases, the issuer may be a bank or other financial institution authorized to open a credit line. In some cases, any organization that can give a credit line to a recipient can be considered an issuer. The credit line opened by the issuer may be represented in the form of a payment account and can be withdrawn by the recipient by using a payment card.

  Acquirer—An organization that can process payment card transactions on behalf of merchants. The earner may be a bank or other financial institution that is authorized to process payment card transactions on behalf of the merchant. In many instances, the earner can open a merchant credit line that acts as a payee. The acquirer shall exchange funds with the issuer in the case where a consumer, who may be a recipient of the credit line provided by the issuer, transacts with a merchant represented by the acquirer via a payment card. Can do.

  Payment transaction—a transaction between two organizations where money or other financial gain is exchanged from one organization to the other. A payment transaction may be the transfer of funds for the purchase of goods or services, the repayment of debt, or any other exchange of financial gain as will be appreciated by those skilled in the art. In some instances, a payment transaction may refer to a transaction funded via a payment card and / or payment account, such as a credit card transaction. Such payment transactions can be processed through issuers, payment networks, and acquirers. Processes for processing such as payment transactions may include at least one of authorization, batch processing, checkout, settlement, and funding. Authorization is used to provide payment details to the merchant by the consumer, to submit transaction details (eg, including payment details) from the merchant to their acquirer, and to fund the transaction Verification of the payment details by the issuer of the consumer's payment account to be made. Batch processing may refer to accumulating authorized transactions in a batch with other authorized transactions for distribution to the acquirer. Checkout may include sending the transaction being batched from the acquirer to the payment network for processing. Settlement may include debiting the issuer through a payment network for a transaction involving the issuer's payee. In some cases, the issuer can pay the acquirer via a payment network. In other cases, the issuer can pay the acquirer directly. Funding may include payments from the acquirer to the merchant for payment transactions that are settled and settled. Those skilled in the art will appreciate that the ordering and / or classification steps described above are performed as part of the payment transaction process.

(System for processing rebate requests for reward accounts)

  FIG. 1 illustrates a system 100 for initiating and processing rebate of payment transactions funded using a reward account.

  The system can interact with the consumer 102. The consumer 102 may have a payment account (eg, a reward account) that is maintained by the issuer 104 and that is rewarded. In some instances, the issuer 104 may issue a payment card associated with the reward account to the consumer 102 for use in funding payment transactions using the reward account. The consumer 102 can conduct a payment transaction with the merchant 106 that will be funded by the reward account.

  The merchant 106 (eg, or an earner associated with the merchant 106) can submit an authorization request to the payment network 108 for a payment transaction funded by the reward account. Payment network 108 can process payment transactions using systems and methods understood by those skilled in the art. As part of the process or after the process, payment network 108 can send a copy of the authorization request to process server 110. The authorization request sent to the processing server 110 can include at least payment information (eg, indicating a reward account used to fund the payment transaction) and a transaction amount.

  The processing server 110, described in more detail below, can be configured to initiate a rebate request for a reward account based on the reward balance. The processing server 110 can calculate the transaction reward value based on at least the transaction amount and at least one conversion rule. Conversion rules may be based on merchants 106, consumers 102, issuers 104, transaction data for payment transactions, or any other suitable value. The transaction reward value may be representative of the value of the reward in the reward account that is required to fund the entire payment transaction via the reward. For example, the transaction reward value may be calculated to be 150 points for a $ 150 transaction.

  The processing server 110 may also store account data entries corresponding to the consumer 102 in the account database 112, as will be described in more detail below. The account data entry can include at least the reward balance of the reward account used by the consumer 102 to fund the payment transaction. In some embodiments, the processing server 110 can be associated with the issuer 104 and / or receive account information (eg, reward balance) from the issuer 104. The processing server 110 can identify the return amount of the account data entry, and the return amount is based on the lesser of the transaction reward value and the reward balance included in the account data entry. In such cases, the return amount is a scenario where the compensation balance exceeds the compensation amount required to fund the payment transaction, or the compensation balance does not exceed the compensation amount and partially funds the payment transaction. Scenarios that can only be used for this purpose can be considered.

  The processing server 110 can then update the reward balance in the account data entry associated with the consumer 102 based on the return amount. The processing server 110 can also calculate a rebate amount of the rebate to be processed for the payment amount of the payment transaction based on the reduction amount and at least one conversion rule. The processing server 110 can then submit a rebate request to the payment network 108 so that the rebate amount is paid to the issuer 104 of the reward account based on the rewards redeemed. The payment network 108 can process the rebates using systems and methods understood by those skilled in the art.

  In some embodiments, the processing server 110 can send a notification to the consumer 102 indicating that the rebate request has been successfully sent to the payment network 108. Notifications can be sent to the consumer 102 or a computing device associated with the consumer 102, short message service (SMS) message, multimedia service message, email, traditional mail, telephone, website, application It may be sent to the consumer 102 via a program or any other suitable method as will be appreciated by those skilled in the art. In other embodiments, the processing server 110 may send another notification indicating successful processing of the rebate request in addition to or instead of the notification indicating successful transmission of the rebate request. Can do. In some embodiments, the processing server 110 may also send a notification to the issuer 104, such as to provide an update regarding the reward balance of the reward account, based on the calculated updated reward balance. it can.

  In some cases, the processing server 110 requests permission to submit a reimbursement request for a payment transaction from the consumer 102 when the reward balance of the account data entry associated with the consumer 102 is lower than the transaction reward value. can do. In such instances, the processing server 110 may request the consumer 102 (eg, a mobile computing device or a computing device associated with the consumer 102, such as a point-of-sale device on which a payment transaction was made). Can be submitted. The consumer 102 can respond to requests received by the processing server 110 and can be processed accordingly. The processing server 110 can submit a rebate request as described above if the consumer 102 wants to use his reward balance, or the consumer 102 uses his reward balance. If you do not wish to do so, you may not submit any request. In some embodiments, the processing server 110 can be configured to submit a rebate request based on the partial use of the reward balance.

  The systems and methods described herein provide several improvements over conventional systems and methods for allowing consumers 102 to fund payment transactions using rewards from reward accounts. Can bring. The processing server 110 may provide a reward balance to fund the payment transaction without requiring the consumer 102 to use a second payment card or perform some action prior to conducting the transaction. Because it can be utilized, the processing server 110 can enable faster and more efficient funding of payment transactions via rewards. As a result, the system 100 may be more acceptable by consumers, and as a result, it can provide higher utilization and can benefit both the consumer 102 and the issuer 104.

  In addition, by treating the use of the reward as a rebate request, the payment transaction itself can be performed conventionally without any modifications to the existing payment system. Furthermore, the rebate request can be sent as a settlement record after the payment transaction, resulting in a very quick rebate request processing. In such cases, the initial authorization request submitted by the merchant 106 to the payment network 108 can be submitted conventionally without interruption or intervention by the processing server 110, thereby maintaining conventional processing speed. As a result of combining this with the rate of rebate request reimbursement, the delay to the consumer 102 associated with the processing of reimbursement of payment transactions using rewards can be made inconspicuous.

(Processing device)

  FIG. 2 illustrates one embodiment of the processing server 110 of the system 100. The embodiment of the processing server 110 shown in FIG. 2 is provided for illustrative purposes only, and covers all possible configurations of the processing server 110 that are suitable for performing the functions described herein. Those skilled in the art will appreciate that this is not possible. For example, the computer system 600 shown in FIG. 6 and described in more detail below may be a suitable configuration for the processing server 110.

  The processing server 110 can include a receiving unit 202. The receiving unit 202 can be configured to receive data via one or more networks according to one or more network protocols. The receiving unit 202 can be configured to receive an authorization request from the payment network 108 corresponding to a payment transaction funded by the reward account, the authorization request including at least the transaction amount and payment information. The payment information may include an account identifier or other suitable information as appreciated by those skilled in the art that can be used to identify the reward account used to fund the payment transaction. .

  The processing server 110 can further include a processing unit 204. The processing unit 204 can use the payment information to identify an account data entry 208 stored in the account database 112 associated with the reward account used to fund the payment transaction. Each account data entry 208 stored in the account database 112 may include data related to a consumer reward account including at least an account identifier and a reward balance. The account identifier may be a unique value used for identification, such as an identification number, a payment account number (eg, for an associated reward account), a username, an email address, a telephone number, and the like. The reward balance may be a balance of rewards earned by the consumer 102 of the associated reward account. In some instances, the reward balance may be received by issuer 104 by processing server 110 (eg, via receiving unit 202).

  The processing unit 204 can be configured to calculate a transaction reward value based at least on the transaction amount and one or more conversion rules, which can be stored in the memory 210. In some cases, the transaction reward value is determined by the consumer 102 (eg, the account level of the consumer 102), the issuer 104 (eg, issuer preferences, issuer category, etc.), as will be appreciated by those skilled in the art. Merchant 106 (eg, merchant preferences, merchant category, merchant industry, etc.), transaction data (eg, product data, transaction time and / or date, geographic location, etc.) included in the authorization request It may be further based on at least one of the following.

  The processing unit 204 may also be configured to identify a return amount that may be the lesser of the transaction reward value and the reward balance included in the identified account data entry 208. The processing unit 204 can then update the reward balance included in the identified account data entry 208 based on the current reward balance and return amount, and the identified return amount and at least one The rebate amount can be calculated based on the conversion rule. The processing unit 204 can generate a rebate request for the calculated rebate amount. In one example, the transaction amount may be $ 100 and the processing unit 204 may calculate a transaction reward value of 100 points. The identified account data entry 208 may include a reward balance of 75 points. Processing unit 204 may therefore identify a 75 point return amount, which may update the reward balance to zero points, resulting in a calculated rebate amount of $ 75. Processing unit 204 may then generate a $ 75 rebate request for the reward account.

  The processing server 110 can also include a transmission unit 206. The transmission unit 206 can be configured to transmit data over one or more networks according to one or more network protocols. The sending unit 206 can be configured to send the generated rebate request to the payment network 108 for processing.

  The sending unit 206 may also be configured to send a notification to the consumer 102 and / or issuer 104 indicating that the rebate request has been successfully sent.

  In some embodiments, the receiving unit 202 can receive a notification from the payment network 108 upon successful processing of the rebate request. In such embodiments, the sending unit 206 can be further configured to send a notification to the consumer 102 and / or the issuer 104 indicating that the processing was successful. In some cases, this notification may be sent in addition to or instead of the previous notification indicating that the rebate request was successfully sent.

  In embodiments where the reward balance of the identified account data entry 208 is less than the transaction reward value of the payment transaction, the processing server 110 is stored (eg, in the account data entry 208 identified as an example). When requesting consumer 102 consent to partially fund the payment transaction using rewards (based on previously received consumer preferences), sending unit 206 may continue Can be configured to send a request to the consumer 102 for consumer 102 approval. The request is made to those skilled in the art, such as via a computing device associated with the consumer 102 (eg, as shown in the authorization request) or a point of sale device used to conduct payment transactions. It may be sent to the consumer 102 via any suitable method as will be appreciated. The receiving unit 202 may be configured to receive a response from the consumer 102 indicating that it will process a rebate request for a portion of the transaction amount or hold the rebate request. The processing unit 204 can identify the instructions included in the response and can operate accordingly as described above. In some embodiments, the account data entry 208 can indicate whether the processing unit 204 should generate a rebate request if the reward balance is lower than the calculated transaction reward value.

(Process payment transactions and subsequent rebate requests)

  FIG. 3 illustrates a process for processing payment transactions funded using a reward account and subsequent processing of rebate requests using rewards earned on the reward account.

  At step 302, the consumer 102 can initiate a payment transaction with the merchant 106 to purchase goods or services using the reward account. As part of initiating a payment transaction, the consumer 102 can provide the merchant 106 with an account number for a reward account (eg, via a payment card or other suitable method). At step 304, merchant 106 (eg, or an acquirer associated with merchant 106) can generate an authorization request and submit it to payment network 108 for processing. In step 306, payment network 108 can forward the authorization request to reward account issuer 104. The issuer 104 can approve the payment transaction at step 308 (eg, based on sufficient funding in the reward account), and at step 310 an authorization response indicating the approval is sent to the payment network 108. You can reply.

  At step 312, payment network 108 can forward an authorization response indicating approval of the payment transaction to merchant 106. One skilled in the art will appreciate that steps 304-312 are illustrative of processing payment transactions using conventional systems and methods, and that additional steps and / or additional organizations may be included. Like. In step 314, merchant 106 can provide receipt of goods or services and / or transaction details to consumer 102.

  At step 316, the payment network 108 can send a copy of the approval request for the payment transaction, including at least payment information and the transaction amount, to the processing server 110. In step 318, the processing server 110 can identify an account data entry 208 associated with the reward account used to fund the payment transaction, and is further included within the identified account data entry 208. Remuneration based on the transaction balance and transaction reward value calculated based on the transaction amount and at least one conversion rule, and possibly based on preferences as described below Whether payment transactions can be funded can be identified. For example, a preference (eg, reward preference) is used for all transactions, only for the next transaction, or for any transaction regarding the use of rewards to fund payment transactions. May be used, only used for transactions that exceed the minimum threshold, only used for transactions that can be fully funded using rewards, and so on. In a case where the consumer 102 may be required to authorize the use of the reward to fund the payment transaction in full or in part, in step 320, the processing server 110 may request the consumer 102 to approve. Can be submitted.

  At step 322, the consumer 102 can approve the use of points via a computing device (eg, mobile computing device, point of sale device at the merchant 106, etc.) or other suitable method. At step 324, an approval response indicating consumer approval may be sent to the processing server 110. In step 326, the processing server 110 may then generate a rebate request for a rebate amount based on the return amount and at least one conversion rule, and possibly based on approval or preference. In step 328, the processing server 110 can send a rebate request to the payment network 108.

  In step 330, payment network 108 can process the rebate request using system methods as appreciated by those skilled in the art. The rebate can be processed from an account associated with the merchant 106 to a reward account associated with the consumer 102. In step 332, payment network 108 may send a rebate response indicating that the rebate of the rebate amount to the reward account has been successfully processed. In step 334, the processing server 110 can send a notification to the consumer 102 indicating that the rebate process was successful. In some cases, the notification may further include an updated reward amount and other suitable information as would be appreciated by one skilled in the art.

(Method for generating and initiating rebate requests)

  FIG. 4 illustrates generating and processing a rebate reward request for a rebate of a payment transaction funded using a reward account, as executed via the processing server 110 of the system 100. The method is shown. The reward account may include a selection of consumer preferences in the use of reward balance, and a program for use of reward balance as selected by issuer 104, payment network provider, merchant 106 and / or earner Preferences can be included.

  In step 402, the receiving unit 202 of the processing server 110 may receive an authorization request for a payment transaction funded using a reward account. The authorization request can include at least payment information and a transaction amount. In step 404, processing unit 204 may determine whether the payment transaction is a valid transaction for full or partial funding of the payment transaction using the reward. Step 404 may include identifying the account data entry 208 stored in the account database 112 using the payment information included in the authorization request. If a valid account data entry 208 is not identified, the transaction can be considered invalid and the process can end.

  Referring again to FIG. 4, if a valid account data entry 208 is identified and the reward can be used to fully or partially fund the transaction, at step 405, the processing server 110 may include one or more. Based on the consumer and / or program preferences (eg, reward preferences), it is determined whether the payment transaction is eligible for a rebate reward request. Each account data entry 208 in the account database 112 may include a consumer preference associated with the reward account. Consumer preferences indicate that in any case a rebate should be required for purchases made at the point of sale terminal (physical or virtual) and vice versa. It can indicate whether it is not eligible for a return request. Consumer preferences may be received from a mobile computing device or even a computing device associated with the consumer 102, such as a point-of-sale device on which a payment transaction was made by the consumer 102. Often, the consumer 102 selects or provides reward preferences through the consumer computing device before reaching the merchant 106, which is received by the processing server 110 and stored in the account data entry 208. The Alternatively, the consumer 102 may select reward preferences from the mobile computing device or point-of-sale device at the merchant 106 while shopping, immediately prior to a payment purchase, or as part of a payment transaction.

  Consumer preferences (e.g., consumer reward preferences) can include a variety of different indications in which cases a reward rebate should or should not be required for a purchase.

  For example, the consumer preference option disables the use of rebate rebate requests for payment transactions, uses rebate rebate requests for all payment transactions, rebates remuneration only for the next payment transaction It may include using a request or the like. This allows the consumer 102 to decide in which case he wants a rebate request for the payment transaction. If the reward balance is relatively small, or if the consumer 102 wants to accumulate the reward balance to a larger amount for a higher purchase in the future, for example, the consumer 102 may , You can stop using rewards for the time being. Alternatively, if the consumer 102 has accumulated a large reward balance in the reward account or wishes to use the reward as soon as possible, for example, the consumer 102 may You can choose to use reward rebate requests. Further, if the consumer 102 wants to make a single purchase using reward rebate but then allow the reward balance to increase after the purchase, for example, the consumer 102 You can choose to use remuneration rebate requests only for purchases. If the consumer 102 decides to purchase an item that he / she wishes to use the reward rebate request, the consumer 102 may select this reward preference at the merchant 106 while shopping, for example. it can. After the next purchase is made, consumer preferences automatically change back to invalid. The consumer 102 can then change their preferences later so that a rebate request is used for subsequent payment transactions.

  In yet another example, the consumer preference is for a particular merchant (s) such that the rebate request should only be used for payment transactions at the particular merchant (s). Can be included.

  As another example of possible reward preferences, the processing server 110 and / or the consumer 102 can select the minimum criteria that must be met in order for reward rebates to be required for payment transactions. In one example, the consumer can select a minimum purchase amount of $ 20 such that the reward rebate request is used only for payment transactions involving at least $ 20. The consumer 102 uses, for example, the normal payment account method for smaller purchases, while saving the reward balance so that the consumer can be used for higher, larger purchases. This minimum purchase amount can be selected so that it can be paid (e.g., billing / withdrawing to a compensation account). Of course, various other reasons for choosing one minimum amount, rather than another, may be utilized by the consumer 102. In at least one embodiment, consumer preferences can include a maximum purchase amount.

  Each of the above exemplary consumer preferences, as well as other consumer preferences, can be communicated via an interface on the consumer's computing device or through other interactions between the consumer 102 and the processing server 110 (directly). Or indirectly) whereby the processing server 110 subsequently receives consumer preferences.

  For example, FIG. 5 illustrates an interface 450 suitable for being displayed on a consumer's mobile computing device. Interface 450 includes an account number input field 452 that can receive an account number (eg, an account identifier) associated with the consumer's reward account from consumer 102. The interface 450 further includes a passcode field 454 that can receive a passcode associated with the reward account to prevent others from accessing and / or modifying the consumer's reward account preferences. The interface 450 may allow a rebate request to be requested only if the payment transaction is greater than or equal to the minimum purchase amount entered by the consumer 102 in the face value field 458, as described above. It includes a radio button for selecting 456.

  Interface 450 is used for all transactions, not used for all transactions, and used only for the next transaction to match the preferences described above with reference to FIG. It further includes a radio button 460 associated with the preference. Once the consumer 102 has selected some or all of the preferences at the interface 450 and presented the account number and passcode at 452, 454, the consumer 102 activates the send button 462 to activate the processing server 110. Submit your preferences to The processing server 110 then receives the preference and stores the associated account data entry 208.

  It should be appreciated that any number of different preferences from the consumer may be included and / or selected from an interface, such as interface 450. In general, consumer preferences specify in advance how the consumer 102 should use the reward balance, ie, through one or more reward preferences, and then utilize the reward balance. Without having to perform any additional actions and / or activities in order to simply use the payment card associated with the reward account as usual, resulting in the use of the reward account for the consumer 102. It becomes easier.

  Further, in various embodiments, the reward account issuer 104 may set a minimum purchase amount of the reward account such that reward rebates are only required for payment transactions involving at least that amount. it can. This may allow issuer 104 to restrict consumer 102 from using the rebate request for all purchases of any size, thereby allowing issuer 104 to Protected from any overhead associated with the processing of each separate reward rebate request for a large number of small purchases. Additionally or alternatively, the issuer 104 can request the consumer 102 to submit a minimum purchase amount preference, as described above. Program preferences can further limit the number of reward rebate requests within a period of time and limit the merchants 106 and / or various other options for which rewards can be used, thereby causing failures in the reward program. Protect against (consumers do not use up their points), create reward program level variables, reduce the amount of reward redemptions processed, reduce the amount of reward redemption costs, etc. it can. Any criteria established by issuer 104, merchant 106, payment network provider, or earner may be considered a program preference (eg, program reward preference).

  With further reference to FIG. 4, particularly step 405, processing server 110 may qualify payment transactions for rebate requests based on one or more consumer preferences and / or reward program preferences, including those described above. It is determined whether or not. As will be appreciated, in other exemplary embodiments, step 405 may be located at other points in the method (eg, after step 406, after step 408, etc.) or absent from the method. It may be.

  Still referring to FIG. 4, if the transaction is eligible based on one or more preferences, at step 406, the processing unit 204 has sufficient reward balance in the account to fund the payment transaction in full. It can be determined whether or not there is. Step 406 calculates a transaction reward value based on the transaction amount of the payment transaction and one or more conversion rules, and a transaction for which the reward balance included in the identified account data entry 208 is calculated. It may include identifying whether it is greater than or equal to the reward value.

  If the reward balance is not sufficient to fund the payment transaction in full, at step 408, processing unit 204 may determine a portion of the payment transaction based on data contained within the identified account data entry 208, etc. It can be determined whether there is a default approval, consumer preference, and / or program preference from the consumer associated with the reward account for the specific funding. Default approval can be indicated by consumer preference and / or program preference. For example, the issuer 104 may choose to allow a reward rebate request only if the reward balance is sufficient to fund the full amount of the transaction (ie, the full amount is funded). Issuer 104 selects this requirement to avoid processing separate payment methods (ie, using reward points and using normal payment account operations) for a single payment transaction. , Expenses associated with reward point redemption can be reduced. In this case, no rebate request is generated unless the remuneration balance is greater than or equal to the transaction amount (or transaction reward value). The cash equivalent to the consumer's current reward point balance must be greater than the transaction amount.

  Alternatively, the program preferences can indicate that partial reward balance usage is permitted. If consumer preferences indicate that partial payments are allowed by default, the rebate request is even if the remuneration balance is sufficient to fund a portion of the payment transaction amount. Can also be generated. The reward balance is used even if the cash equivalent to the reward balance is less than the transaction amount.

  If a default approval is not provided by the consumer 102, the sending unit 206 of the processing server 110 can send an approval request to the consumer 102 at step 410. In some embodiments, a method for communicating an authorization request may be included in the identified account data entry 208. In step 412, receiving unit 202 may receive a response from consumer 102 that indicates approving or refusing to use the reward to partially fund the payment transaction. In step 414, the processing unit 204 can identify whether the use of the reward is approved in the consumer response. If the use is not approved, the process can be completed.

  In some embodiments, points can be redeemed in predefined increments according to preferences. For example, if consumer 102 has 10,400 reward points and each point is worth $ 0.01, then the consumer has a cash equivalent balance of $ 104 through the use of conversion rules. If the program increment is set to $ 5 and the consumer attempts to make a purchase of $ 136.23, $ 100 will be redeemed. The consumer 102 will have 400 points equivalent to $ 4. The consumer 102 will not be able to use reward points until the unpaid points for the consumer 102 are again at least 500 points. Further, if the program minimum is $ 10, then the consumer 102 will not be able to use reward points until the consumer's unpaid points are at least 1,000 points.

  In a consumer response, if the use is approved by the consumer 102, or if the use is approved by default by the consumer 102, or there is enough remuneration to fund the payment transaction in full If so, at step 416, the processing unit 204 can subtract the corresponding reward amount from the reward balance in the identified account data entry 208. Processing unit 204 can then process the rebate of the payment transaction at step 418. The rebate process consists of calculating transaction remuneration value, remuneration return, and rebate amount that can be based on at least one conversion rule, generating a rebate request for the rebate amount being calculated, and transmitting unit 206. In response to its transmission to the payment network 108 for processing. In step 420, the sending unit 206 can send a notification indicating the rebate process to the consumer 102. In some instances, the notification may include at least one of a return amount, a rebate amount, and an updated reward balance.

(Method for initiating a rebate of payment transactions funded using a compensation account)

  FIG. 6 illustrates a method 500 for initiating a rebate of a payment transaction funded using a reward account.

  In step 502, a plurality of account data entries (eg, account data entry 208) can be stored in a database (eg, account database 112), each account data entry 208 including a consumption including at least an account identifier and a reward balance. Includes data related to employee compensation accounts. In step 504, an authorization request for a payment transaction involving a merchant (eg, merchant 106) can be received by a receiving device (eg, receiving unit 202), the authorization request including at least payment information and a transaction amount. Including. In step 506, a transaction reward value may be calculated by the processing device (eg, processing unit 204) based at least on the transaction amount and at least one conversion rule. In one embodiment, at least one trading rule is associated with at least one of merchant 106, trading value, account level, and merchant category.

  In step 508, the amount of the return can be identified by the processing device 204, which is the transaction reward value and the specific account data entry 208 in the database 112 for which the included account identifier corresponds to payment information. It is the smaller of the remuneration balances included. In one embodiment, each account data entry 208 may further include an indication of whether the corresponding reward balance should be used if the reward balance is less than the calculated transaction reward value. it can. In some embodiments, the payment information included in the authorization request can include an account identifier included in the specific account data entry 208.

  In step 510, the reward balance included in the particular account data entry 208 may be updated based on the identified redemption amount in the database 112. In step 512, the processing device 204 may calculate a rebate amount based on the transaction reward value and the identified redemption amount and at least one conversion rule. In step 514, a rebate for a calculated rebate amount from a payment account associated with merchant 106 to a payment account corresponding to the payment information included in the authorization request by a transmitting device (eg, transmission unit 206). A request can be sent. In some embodiments, the rebate request can be sent to a payment network (eg, payment network 108).

  In one embodiment, the method 500 sends a notification by the sending device 206 to a consumer (eg, consumer 102) associated with a particular account data entry 208 indicating that the rebate request has been successfully sent. Can further be included. In another embodiment, the method 500 receives, in response to a rebate request being sent by the receiving device 202, an indication that the rebate process was successful, Sending a notification to the consumer 102 associated with the account data entry indicating that the rebate process was successful.

  In some embodiments, the method 500 receives an indication by the receiving device 202 to continue sending a rebate request before sending a rebate request when the reward balance is less than the transaction reward value. Can further include. In a further embodiment, an indication to continue may be received in response to sending a request to continue by sending device 206 to a computing device associated with a particular account data entry 208. In yet a further embodiment, the request to continue may include at least a reward balance included within a particular account data entry 208, a short message service message, a multimedia message service message, The email can be sent via at least one of a send to a point of sale device associated with the payment transaction.

(Method processing fee through third-party compensation program)

  In some embodiments, the reward balance associated with the reward account may be stored by a third party (eg, airline, retailer, etc.). The reward account can include a third party indicator that indicates that the reward balance associated with the reward account is stored by the third party. The third party may be a point bank that holds the reward point balance of the consumer 102. In these cases, the processing server 110 is configured to send transaction reward value to a third party based on the transaction amount of a payment transaction involving a reward account whose reward balance is stored by the third party. Can do. The transaction reward value can indicate the amount of reward balance (e.g., amount of reward points, cash equivalent, etc.) required to fund the payment transaction. Transaction reward values may be based on reward programs, third party and / or consumer composition. For example, a payment service provider, a third party, a consumer, etc. can set a standard for calculating the transaction reward value. If the payment transaction is deemed eligible based on criteria (eg, consumer preferences, program preferences, etc.), the transaction reward value is sent to a third party.

  The processing server 110 can also send payment transaction information to a third party, which can include, but is not limited to, transaction position, local currency amount, settlement currency amount, merchant position, and the like. The processing server 110 may also send scoring rules that are used to calculate the amount of points required that may include the cost per point (eg, 100 basis points, 0 for each point). Worth $ .01). The third party processor can then determine whether the consumer 102 has sufficient reward balance to complete the redemption. If the consumer has sufficient reward balance, the third party processor can send a message indicating that points have been deducted and statement credit can be given to the consumer. The third party can send a rebate request to the issuer of the compensation account, payment network provider, merchant and / or earner.

  FIG. 7 illustrates an exemplary system for processing a payment transaction involving a reward account in which the reward balance is stored by a third party, according to another exemplary embodiment of the present disclosure. A consumer 550 (eg, a MasterCard ™ consumer) makes a purchase at a point-of-sale (POS) terminal 552 of the merchant. A payment transaction authorization is sent to the acquirer 554 and then to the payment network 556. Payment network 556 may be linked to or include a system for sending and receiving information between banks (eg, BankNet ASA). The authorization request is then sent to issuer 558.

  Transaction authorization is added to a queue that is read by a real-time reward (RTR) engine 560. RTR engine 560 may be part of payment network 556 and may be implemented by a processing server. The RTR engine 560 applies applicable filtering logic (including consumer eligibility) and how many points are needed to cover the full transaction amount or partial transaction Determine details about how to process the amount. The RTR engine 560 applies any consumer and / or program preferences, including those described herein, to determine whether a transaction authorization is eligible for a rebate request. can do.

  If the transaction authorization is eligible for a rebate request according to consumer preferences and / or program preferences, the RTR engine 560 may calculate as described above (eg, based on at least one conversion rule, etc.). Generate possible transaction reward value (ie, the transaction result being scored).

  The RTR engine 560 then determines, at 562, whether the reward account associated with the authorization request is a third party reward account. If the reward account is not a third party account, the payment transaction is processed by the payment network, which generates a rebate request as described herein (e.g., based on reward transaction value). And calculating a rebate amount).

  If the payment transaction is for a compensation account involving a third party, the RTR engine 560 sends the transaction compensation value to the third party (or third party transaction processor) in a fire and forget message. . The fire and forget message informs the third party (or third party transaction processor) of the possibility of requesting a reward rebate for the transaction. The third party transaction processor may be internal to payment network 556.

  Whether the third-party transaction processor should result in a statement credit as a result of the transaction (ie, the compensation balance should be applied to the transaction) and whether the necessary points should be deducted To determine whether or not, call the issuer 558 application programming interface (API) associated with the reward account. If the reward balance is to be applied to the transaction, the rebate is sent to rebate service 564, which may be part of payment network 556. The rebate service 564 stores the rebate redemption in a database such as the MasterCard® Reward System (MRS) database. The rebate can then be settled, such as sent via batch to the MasterCard® Global Checkout Management System (GCMS). The rebate may also be reported to the reward account issuer 558 for the issuer 558 to apply the rebate to the reward account.

  If the third party decides to apply the remuneration balance to the payment transaction and sends the corresponding rebate request, the third party reduces the remuneration balance associated with the remuneration account based on the face value of the rebate request can do.

  FIG. 8 shows an exemplary method flow for processing a payment transaction in accordance with the system shown in FIG. The method flow is divided into multiple areas that specify operations at the consumer 550, payment network, eg, a merchant, acquirer 554, payment network 556, which may include BankNet, MRS and GCMS, and issuer 558. The

  According to this exemplary method flow, consumer 550 initially signs up at 565 for a reward-based payment-real-time reward (PWR-RTR) service, at which point payment network 556 is (E.g., by creating a new reward account and associating the reward balance and account identifier with an existing account).

  When a consumer 550 passes a payment card associated with a reward account for purchase at a merchant through the machine, a transaction authorization request may be received by payment network 556 and stored in a queue (eg, a transaction authorization request copy Provided by BankNet to the MRS, which then acknowledges receipt of the transaction to the BankNet and stores the authorization transaction).

  Payment network 556 then determines at 568 whether the transaction passes validation, which may include consumer preferences, program preferences, and the like. If the transaction does not pass verification, the transaction is complete. If the transaction passes validation, payment network 556 calculates points to redeem based on the transaction amount (eg, by calculating transaction reward value based on at least one conversion rule).

  Once the points required for redemption are calculated, payment network 556 then checks 570 whether the reward account is associated with a third party bank. If the compensation account is stored by a third party bank, the payment network 556 may send an external fire and forget message to the third party (eg, the third party rather than the payment network 556 may receive additional compensation balances). The message is sent to a third party to handle usage decisions, reward balance updates, rebate request generation, etc., and the process is complete. The transmitted message may include transaction reward value as well as other transaction and / or reward account information.

  If the reward account is not associated with a third party bank, payment network 556 determines whether the reward balance of the consumer's reward account can cover at least a portion of the transaction at 572 (eg, consumption Whether the person's reward account has enough points to pay at least a portion of the transaction. If the consumer reward balance does not have enough points, an optional message (eg, short message service (SMS), email, etc.) indicating a lack of reward points may be sent to the consumer.

  Cashback in return if the consumer does not have enough reward balance points to cover at least a portion of the transaction (or if partial payment is not allowed but the reward balance is greater than the full transaction amount) The process is started. A rebate request file is generated for the transaction based on the schedule. The rebate request file is then processed (eg, by submitting the file to GCMS). The payment transaction can then be processed by payment network 556, and settlement of the payment transaction is performed by reward account issuer 558.

  Redemption costs are calculated (which may be based on the face value of the rebate request) and sent to issuer 558. A redemption notification may optionally be sent to the consumer 550 indicating the status of the payment transaction and / or the success of the rebate request.

  FIG. 9 shows an exemplary method flow for processing a payment transaction involving a reward account associated with a third party in accordance with the system shown in FIG. The illustrated method flow is divided into third party operations, payment network 556 (including MRS services, MRS, and GCMS) and operations at issuer 558.

  The third party initially processes the reward point redemption at 574 (eg, the consumer wishes to use the consumer's reward account reward balance from the payment network 556 to fund the payment transaction. In response to receiving a message indicating The third party then sends a rebate request to payment network 556 (eg, by initiating a MRS rebate redemption request).

  The payment network 556 then processes the rebate request at 576 (eg, the MRS service then initiates redemption after a cashback process where no points can be requested). The payment network sends a message to the third party that can indicate whether the rebate request was successful. If the rebate request is indicated as successful, the third party process is complete (and the third party can update the reward balance accordingly). If the rebate request is not successful, the third party can repeat the step of sending the rebate request to the payment network.

  At 578, based on the received rebate request, the payment network can create a rebate file based on the schedule. The rebate file is then processed (eg, by submitting the file to GCMS). The payment transaction can then be processed by payment network 556, and settlement of the payment transaction is performed by reward account issuer 558.

  Redemption costs are calculated and sent to the issuer 558 associated with the reward account. An option redemption notification may be sent to the consumer 550.

  Further details of the steps of FIGS. 8 and 9 are described within the blocks of the flow charts of FIGS. 8 and 9, which limit the exemplary process illustrated in FIGS. Should not be considered as. As will be appreciated, in other exemplary embodiments, the order of the steps may be varied, some steps may be absent, and several, without departing from the scope of the present disclosure. Additional steps may be added.

(Computer architecture)

  FIG. 10 illustrates a computer system 600 in which embodiments of the present disclosure or portions thereof may be implemented as computer readable code. For example, the processing server 110 of FIG. 1 may be implemented in the computer system 600 using hardware, software, firmware, non-transitory computer readable media, or a combination thereof in which executable instructions are stored, It may be implemented in one or more computer systems or other processing systems. Hardware, software, or any combination thereof may embody the modules and components used to implement the methods of FIGS.

  Where programmable logic is used, such logic can be executed on commercially available processing platforms or dedicated devices. Embodiments of the disclosed subject matter include multi-core multi-processor systems, minicomputers, mainframe computers, computers linked or clustered by distributed functions, and pervasive that can be virtually integrated into any device Or, those skilled in the art can appreciate that various computer system configurations can be practiced, including miniature computers. For example, at least one processor device and memory may be used to implement the above-described embodiments.

  A processor unit or device as discussed herein may be a single processor, multiple processors, or a combination thereof. A processor device may have one or more processor “cores”. The terms “computer program medium”, “non-transitory computer readable medium”, and “computer usable medium”, as discussed herein, are removable storage unit 618, removable storage unit 622, and Generally refers to a tangible medium such as a hard disk installed in the hard disk drive 612.

  Various embodiments of the present disclosure are described with respect to this exemplary computer system 600. After reading this specification, it will become apparent to a person skilled in the art how to implement the present disclosure using other computer systems and / or computer architectures. Although the operations may be described as sequential processes, some of the operations are actually in parallel, simultaneously and / or locally or remotely for program code access by a single or multiprocessor machine It may also be implemented in a distributed environment stored as such. In addition, in some embodiments, the order of operations may be reconfigured without departing from the spirit of the disclosed subject matter.

  The processor device 604 may be a dedicated or general purpose processor device. The processor device 604 can be connected to a communication infrastructure 606, such as a bus, message queue, network, multi-core message passing scheme, and the like. The network may be any network suitable for performing functions as disclosed herein, such as a local area network (LAN), a wide area network (WAN), a wireless network (eg, WiFi). Mobile communications networks, satellite networks, the Internet, fiber optics, coaxial cables, infrared, radio frequency (RF), or any combination thereof. Other suitable network types and configurations will be appreciated by those skilled in the art. Computer system 600 can also include main memory 608 (eg, random access memory, read only memory, etc.) and can also include secondary memory 610. Secondary memory 610 may include a hard disk drive 612 and a removable storage drive 614 such as a floppy disk drive, magnetic tape drive, optical disk drive, flash memory, and the like.

  The removable storage drive 614 can read from and / or write to the removable storage unit 618 in a known manner. The removable storage unit 618 can include a removable storage medium that can be read and written by the removable storage drive 614. For example, if the removable storage drive 614 is a floppy disk drive, the removable storage unit 618 can be a floppy disk. In one embodiment, removable storage unit 618 may be a non-transitory computer readable recording medium.

  In some embodiments, secondary memory 610 may be an alternative means that allows computer programs or other executable instructions to be loaded into computer system 600, such as removable storage unit 622 and interface 620. May be included. Examples of such means include program cartridges and cartridge interfaces (as found in video game systems), removable memory chips (eg, EEPROM, PROM, etc.) and associated sockets, as will be appreciated by those skilled in the art. Other removable storage units 622 and interfaces 620 may be included.

  Data stored in computer system 600 (eg, in main memory 608 and / or secondary memory 610) may be stored in an optical storage device (eg, compact disc, digital versatile disc, Blu-ray® disc, etc.). ) Or a magnetic tape storage device (eg, hard disk drive), etc., may be stored on any type of suitable computer readable medium. The data may be comprised of any type of suitable database configuration, such as a relational database, structured query language (SQL) database, distributed database, object database, etc. Appropriate configurations and storage device types will be appreciated by those skilled in the art.

  Computer system 600 can also include a communication interface 624. Communication interface 624 may be configured to allow software and data to be transferred between computer system 600 and external devices. Exemplary communication interface 624 may include a modem, a network interface (eg, an Ethernet card), a communication port, a PCMCIA slot, a card, and the like. The software and data transferred via the communication interface 624 may be in the form of signals, which may be electronic signals, electromagnetic signals, optical signals, or other signals, as will be appreciated by those skilled in the art. . The signal can be configured to carry a signal and travels through a communication path 626 that may be implemented using wires, cables, fiber optics, telephone lines, cell phone links, radio frequency links, etc. be able to.

  The computer program media and computer usable media may refer to memory, such as main memory 608 and secondary memory 610, which may be a memory semiconductor (eg, DRAM, etc.). These computer program products may be a means for providing software to computer system 600. Computer programs (eg, computer control logic) may be stored in main memory 608 and / or secondary memory 610. The computer program may also be received via communication interface 624. Such computer programs, when executed, can enable computer system 600 to perform the methods of the invention as discussed herein. In particular, when the computer program is executed, the processor device 604 performs the method illustrated by FIGS. 3-4, 6 and 8-9 as discussed herein. Can be made possible. Accordingly, such a computer program can represent a controller of computer system 600.

  When the present disclosure is implemented using software, the software is stored within the computer program product and is used to the computer system 600 using the removable storage drive 614, interface 620, and hard disk drive 612, or communication interface 624. And can be loaded.

  Techniques consistent with this disclosure provide systems and methods for initiating rebate of payment transactions funded using a compensation account, among other features. While various exemplary embodiments of the disclosed system and method have been described above, it should be understood that they are presented by way of illustration only and not limitation. This is not exhaustive and does not limit the disclosure to the precise form disclosed. Modifications and variations are possible in light of the above teachings, without departing from its breadth or scope, and can be obtained from practicing the present disclosure.

  As will be appreciated based on the above specification, the above-described embodiments of the present disclosure use computer programming or engineering techniques including computer software, firmware, hardware, or any combination or subset thereof. The technical effect is that the following steps are received: (a) receiving an authorization request for a payment transaction involving a reward account, wherein the authorization request includes at least the transaction amount (B) determining whether the payment transaction is eligible for reward rebate based on the reward preference; (c) requesting a reward rebate when the payment transaction is eligible. Sending (d) a transaction report based on at least the transaction amount and at least one conversion rule; A step of calculating a value, (e) a step of calculating a rebate amount based on a smaller one of the transaction reward value and the reward balance, (f) a step of updating the reward balance based on the rebate amount, (g) This can be accomplished by performing at least one of the steps of sending transaction reward value and payment transaction information to a third party.

  The description of the above embodiments is provided for purposes of illustration and description. It is not intended to be exhaustive or to limit the present disclosure. Individual elements or features of a particular embodiment are generally not limited to that particular embodiment and are interchangeable where applicable, even if not specifically shown or described. Can be used in selected embodiments. This can also be changed in many ways. Such variations are not to be regarded as a departure from the present disclosure, and all such modifications are intended to be included within the scope of the present disclosure.

Claims (21)

A computer-implemented method for initiating a rebate for a reward account, wherein the reward account is associated with an account data entry in a database, the account data entry comprising at least an account identifier of the reward account, a reward balance And reward preferences, the method comprising:
Receiving, by a processing server, an authorization request for a payment transaction involving the reward account, wherein the authorization request includes at least a transaction amount;
In the processing server, determining whether the payment transaction is eligible for reward rebate based on the payment preference;
Transmitting from the processing server a request for the reward rebate when the payment transaction is eligible. Calculating a transaction reward value by the processing server based on at least the transaction amount and at least one conversion rule;
The method of claim 1, further comprising calculating a rebate amount by the processing server based on the lesser of the transaction reward value and the reward balance. The method
Updating the reward balance based on the rebate amount in the database;
Sending the request for remuneration rebate includes requesting the remuneration rebate based on the calculated rebate amount when the payment transaction is eligible for the remuneration rebate. The method of claim 2 including the step of transmitting.   The reward preference includes a consumer reward preference, and the consumer reward preference is a reward request only for the next transaction and a reward rebate only for a transaction that exceeds the consumer minimum purchase amount. The method of claim 1, comprising at least one of a preference for requesting.   When the consumer reward preference includes a preference to request reward rebate only for the next transaction, the consumer reward preference is rewarded for any transaction after sending the rebate request. 5. The method of claim 4, further comprising the step of automatically changing to a preference that does not require. The reward preference includes at least one program reward preference associated with the reward account;
Determining whether the payment transaction is eligible is determining whether the payment transaction is eligible for reward rebate based on the program reward preference and the consumer reward preference. The method of claim 4 comprising:   The program reward preference is a preference that permits a rebate request only when the transaction amount exceeds the program minimum, and only when the reward balance is sufficient to fund the transaction in full. 7. A preference for allowing a request for rebates and a preference for granting a request for reward when the reward balance is insufficient to fund the transaction in full. The method described in 1.   The step of sending a request for remuneration rebate includes a rebate amount based on the remuneration balance when the program remuneration preference includes a remuneration preference that allows remuneration rebate to be requested for a portion of the transaction. The method of claim 7, comprising sending a reward rebate request for Receiving at least one consumer selection of consumer reward preferences by the processing server;
The method of claim 1, further comprising updating the reward preference in the account data entry in the database based on the received consumer selection. The method
Further comprising causing an interface providing a plurality of selectable consumer reward preferences to be displayed on the consumer computer system;
The step of receiving the consumer selection includes receiving the selection of at least one of the plurality of selectable consumer reward preferences from the consumer computer system via the interface. 9. The method according to 9. Calculating a transaction reward value by the processing server based on at least the transaction amount and at least one conversion rule;
Transmitting the transaction reward value and payment transaction information to a third party by the processing server when the reward balance associated with the reward account is stored at a third party, whereby the first The method of claim 1, further comprising the step of: allowing a tripartite to manage the reward balance. A system for processing payment transactions involving reward balances,
A processing server comprising an account database, the account database comprising a plurality of account data entries, each account data entry comprising at least an account identifier and a consumer reward preference;
When the processing server is executed by the processing server, the processing server
Receiving an authorization request for a payment transaction involving a reward account, wherein the payment transaction has a transaction balance;
Determining whether the payment transaction is eligible for reward rebate based on the consumer reward preference. The account data entry includes a third party indicator, the third party indicator indicating whether a reward balance associated with the reward account is stored by the third party;
When the instructions are executed by the processing server, the processing server
Calculating a transaction reward value based at least on the transaction amount and at least one conversion rule;
13. The method of claim 12, further comprising: transmitting the transaction reward value to the third party when the third party indicator indicates that the reward balance is stored by the third party. System. The consumer reward preference indicates a minimum purchase amount,
When the instructions are executed by the processing server, the processing server
Determining whether the transaction amount is at least a minimum purchase amount;
If the transaction amount is at least the minimum purchase amount,
Calculating a transaction reward value based at least on the transaction amount and at least one conversion rule;
Calculating a rebate amount based on the lesser of the transaction reward value and the reward balance associated with the reward account;
13. The step of updating the reward balance based on the rebate amount, wherein the face value of the rebate rebate is updated based on the calculated rebate amount. System.   The system of claim 12, wherein the instructions are executable by the processing server to cause the processing server to request a rebate when the transaction is eligible.   The consumer reward preference is at least one reward of requesting a reward rebate only for the next transaction and requesting a reward rebate only for a transaction that exceeds the consumer minimum purchase amount. The system of claim 12, wherein the system indicates a preference.   The instructions, when executed by the processing server, cause the processing server to determine whether the payment transaction is eligible for reward rebate based on the consumer reward preference and program reward preference. The system of claim 12.   The program reward preference is sufficient to allow the reward rebate to be requested only when the transaction exceeds the program minimum, and the reward balance of the reward account is sufficient to fund the transaction in full. Allow the reward rebate to be requested only at certain times, and to request the reward rebate when the reward balance is insufficient to fund the transaction in full. The system of claim 17, wherein the system indicates at least one preference of allowing. A non-transitory computer readable medium, when executed by at least one processor,
Receiving a consumer reward preference associated with a reward account, the consumer reward preference indicating in which case a reward rebate should be required for a payment transaction involving the reward account Receiving, and
Receiving an authorization request for a payment transaction involving the reward account, wherein the payment transaction includes a transaction balance;
A non-transitory computer readable medium comprising instructions for determining whether the payment transaction is eligible for a reward rebate request based on the consumer reward preference.   The non-transitory computer readable medium of claim 19, wherein the consumer reward preference includes a preference to request reward rebates only for the next transaction. When the instructions are executed by the processor, the processor
Determining whether the payment transaction is eligible for a rebate reward request based on the consumer reward preference and the program reward preference;
Sending the rebate reward request when the payment transaction is eligible for the rebate reward request; and
The program reward preference is a preference to allow the reward rebate request only when the transaction amount exceeds the program minimum and / or the reward balance is insufficient to fund the transaction in full The non-transitory computer readable medium of claim 19, comprising a preference that sometimes grants the reward rebate request.

Images