WO2016028889A1 - Procédé et système de traitement d'un rabais en temps réel lors d'une autorisation de transaction - Google Patents

Procédé et système de traitement d'un rabais en temps réel lors d'une autorisation de transaction Download PDF

Info

Publication number
WO2016028889A1
WO2016028889A1 PCT/US2015/045887 US2015045887W WO2016028889A1 WO 2016028889 A1 WO2016028889 A1 WO 2016028889A1 US 2015045887 W US2015045887 W US 2015045887W WO 2016028889 A1 WO2016028889 A1 WO 2016028889A1
Authority
WO
WIPO (PCT)
Prior art keywords
reward
transaction
rebate
consumer
preference
Prior art date
Application number
PCT/US2015/045887
Other languages
English (en)
Inventor
Kyle P. Clark
Christopher A. Guiney
Jensen James E. Pastrana
Original Assignee
Mastercard International Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US14/465,063 external-priority patent/US20150112781A1/en
Application filed by Mastercard International Incorporated filed Critical Mastercard International Incorporated
Priority to EP15833649.5A priority Critical patent/EP3192034A4/fr
Priority to RU2017109095A priority patent/RU2017109095A/ru
Priority to AU2015305524A priority patent/AU2015305524A1/en
Priority to CA2958551A priority patent/CA2958551A1/fr
Priority to BR112017003415A priority patent/BR112017003415A2/pt
Priority to JP2017510295A priority patent/JP2017528822A/ja
Priority to CN201580057280.2A priority patent/CN107077677A/zh
Publication of WO2016028889A1 publication Critical patent/WO2016028889A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/387—Payment using discounts or coupons
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/405—Establishing or using transaction specific rules
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising

Definitions

  • the present disclosure relates to the initiating of a rebate for a payment transaction funded using a reward account, specifically the automatic initiating of a rebate on a reward account following the processing of a payment transaction based on a reward balance.
  • Rewards may come in a variety of forms, such as reward points that may be redeemed for cash or products, cash back, airline miles, reward points with a specific vendor (e.g., a travel service, hotel, merchant, retailer, etc.), a reward level based on activity where each level may have corresponding benefits, and more.
  • a specific vendor e.g., a travel service, hotel, merchant, retailer, etc.
  • these traditional reward schemes often require a significant amount of actions to be taken by the cardholder in order to receive the benefit.
  • the cardholder is typically unable to take advantage of rewards directly at a point-of-sale, instead being required to redeem a reward, receive the reward, and then utilize the reward at a point-of-sale.
  • FIG. 1 is a high level architecture illustrating a system for initiating a rebate for a payment transaction funded using a reward account in accordance with exemplary embodiments.
  • FIG. 2 is a block diagram illustrating the processing server of FIG. 1 for the initiating of the rebate for the reward account-funded payment transaction in accordance with exemplary embodiments.
  • FIG. 3 is a flow diagram illustrating a process for the processing of a payment transaction funded using a reward account and the initiating and processing of a rebate for the reward account based on a reward balance in accordance with exemplary embodiments.
  • FIG. 4 is a flow diagram illustrating a process for the initiating of a rebate request by the processing server of FIG. 2 following a payment transaction funded using a reward account in accordance with exemplary embodiments.
  • FIG. 5 is a diagram of an exemplary interface for receiving consumer preference selections.
  • FIG. 6 is a flow chart illustrating an exemplary method for initiating a rebate for a payment transaction funded using a reward account in accordance with exemplary embodiments.
  • FIG. 7 is a block diagram of another exemplary system of the present disclosure suitable for use in processing payment transactions involving reward accounts.
  • FIG. 8 is an exemplary method flowchart for processing payment transactions involving reward accounts, according to the system of FIG. 7.
  • FIG. 9 is an exemplary method flowchart for processing payment transactions involving reward accounts associated with a third party, according to the system of FIG. 7.
  • FIG. 10 is a block diagram illustrating a computer system architecture in accordance with exemplary embodiments.
  • Payment Network A system or network used for the transfer of money via the use of cash-substitutes. Payment networks may use a variety of different protocols and procedures in order to process the transfer of money for various types of transactions.
  • Transactions that may be performed via a payment network may include product or service purchases, credit purchases, debit transactions, fund transfers, account withdrawals, etc.
  • Payment networks may be configured to perform transactions via cash-substitutes, which may include payment cards, letters of credit, checks, financial accounts, etc. Examples of networks or systems configured to perform as payment networks include those operated by MasterCard®, VISA®, Discover®, American Express®, PayPal®, etc.
  • Use of the term "payment network” herein may refer to both the payment network as an entity, and the physical payment network, such as the equipment, hardware, and software comprising the payment network.
  • Payment Account A financial account that may be used to fund a transaction, such as a checking account, savings account, credit account, virtual payment account, etc.
  • a payment account may be associated with an entity, which may include a person, family, company, corporation, governmental entity, etc.
  • a payment account may be virtual, such as those accounts operated by PayPal®, etc.
  • Payment Card - A card or data associated with a payment account that may be provided to a merchant in order to fund a financial transaction via the associated payment account.
  • Payment cards may include credit cards, debit cards, charge cards, stored-value cards, prepaid cards, fleet cards, virtual payment numbers, virtual card numbers, controlled payment numbers, etc.
  • a payment card may be a physical card that may be provided to a merchant, or may be data representing the associated payment account (e.g., as stored in a communication device, such as a smart phone or computer).
  • data including a payment account number may be considered a payment card for the processing of a transaction funded by the associated payment account.
  • a check may be considered a payment card where applicable.
  • Reward Account A payment account that, when used to fund a transaction, may earn rewards for the account holder.
  • Rewards may be in the form of points, levels, cash back, miles, or other suitable frequency value as will be apparent to persons having skill in the relevant art.
  • the amount of accrued rewards may be referred to as a reward balance, such as the more rewards earned by an account holder may result in an increased (e.g., higher) reward balance.
  • points may refer to rewards for a reward account generally and “point balance” may refer to the reward balance for a reward account generally.
  • a merchant may be a consumer, a retailer, a wholesaler, a manufacturer, or any other type of entity that may provide products for purchase, as will be apparent to persons having skill in the relevant art.
  • a merchant may have special knowledge in the goods and/or services provided for purchase.
  • a merchant may not have or require any special knowledge in offered products.
  • an entity involved in a single transaction may be considered a merchant.
  • Issuer An entity that establishes (e.g., opens) a letter or line of credit in favor of a beneficiary, and honors drafts drawn by the beneficiary against the amount specified in the letter or line of credit.
  • the issuer may be a bank or other financial institution authorized to open lines of credit.
  • any entity that may extend a line of credit to a beneficiary may be considered an issuer.
  • the line of credit opened by the issuer may be represented in the form of a payment account, and may be drawn on by the beneficiary via the use of a payment card.
  • Acquirer An entity that may process payment card transactions on behalf of a merchant.
  • the acquirer may be a bank or other financial institution authorized to process payment card transactions on a merchant's behalf. In many instances, the acquirer may open a line of credit with the merchant acting as a beneficiary.
  • the acquirer may exchange funds with an issuer in instances where a consumer, which may be a beneficiary to a line of credit offered by the issuer, transacts via a payment card with a merchant that is represented by the acquirer.
  • Payment Transaction A transaction between two entities in which money or other financial benefit is exchanged from one entity to the other.
  • the payment transaction may be a transfer of funds, for the purchase of goods or services, for the repayment of debt, or for any other exchange of financial benefit as will be apparent to persons having skill in the relevant art.
  • payment transaction may refer to transactions funded via a payment card and/or payment account, such as credit card transactions.
  • Such payment transactions may be processed via an issuer, payment network, and acquirer.
  • the process for processing such a payment transaction may include at least one of authorization, batching, clearing, settlement, and funding.
  • Authorization may include the furnishing of payment details by the consumer to a merchant, the submitting of transaction details (e.g., including the payment details) from the merchant to their acquirer, and the verification of payment details with the issuer of the consumer's payment account used to fund the transaction.
  • Batching may refer to the storing of an authorized transaction in a batch with other authorized transactions for distribution to an acquirer.
  • Clearing may include the sending of batched transactions from the acquirer to a payment network for processing.
  • Settlement may include the debiting of the issuer by the payment network for transactions involving beneficiaries of the issuer.
  • the issuer may pay the acquirer via the payment network. In other instances, the issuer may pay the acquirer directly.
  • Funding may include payment to the merchant from the acquirer for the payment transactions that have been cleared and settled. It will be apparent to persons having skill in the relevant art that the order and/or categorization of the steps discussed above are performed as part of payment transaction processing.
  • FIG. 1 illustrates a system 100 for the initiating and processing of a rebate for a payment transaction funded using a reward account.
  • the system may interact with a consumer 102.
  • the consumer 102 may have a payment account with rewards enabled (e.g., a reward account) that is held by an issuer 104.
  • the issuer 104 may issue the consumer 102 a payment card associated with the reward account for use in funding payment transactions using the reward account.
  • the consumer 102 may conduct a payment transaction with a merchant 106 to be funded by the reward account.
  • the merchant 106 may submit an authorization request for the payment transaction funded by the reward account to a payment network 108.
  • the payment network 108 may process the payment transaction using systems and methods that will be apparent to persons having skill in the relevant art.
  • the payment network 108 may transmit a copy of the authorization request to a processing server 110.
  • the authorization request transmitted to the processing server 110 may include at least payment information (e.g., indicating the reward account used to fund the payment transaction) and a transaction amount.
  • the processing server 110 may be configured to initiate a rebate request for the reward account based on a reward balance.
  • the processing server 110 may calculate a transaction reward value based on at least the transaction amount and at least one conversion rule.
  • the conversion rule may be based on the merchant 106, the consumer 102, the issuer 104, transaction data for the payment transaction, or any other suitable value.
  • the transaction reward value may be a representation of the value of rewards in the reward account required to fund the entire payment transaction via rewards. For example, a transaction reward value may be calculated to be 150 points for a $150 transaction.
  • the processing server 110 may also store, as discussed in more detail below, an account data entry corresponding to the consumer 102 in an account database 112.
  • the account data entry may include at least a reward balance for the reward account used by the consumer 102 to fund the payment transaction.
  • the processing server 110 may be associated with the issuer 104 and/or may receive account information (e.g., the reward balance) from the issuer 104.
  • the processing server 110 may identify a reduction amount for the account data entry, where the reduction amount is based on the lesser of the transaction reward value and the reward balance included in the account data entry. In such an instance, the reduction amount may account for scenarios where the reward balance exceeds the reward amount necessary to fund the payment transaction or where the reward balance does not exceed the reward amount and may only be used to partially fund the payment transaction.
  • the processing server 110 may then update the reward balance in the account data entry associated with the consumer 102 based on the reduction amount.
  • the processing server 110 may also calculate a rebate amount for a rebate to be processed on the reward account for the payment transaction based on the reduction amount and the at least one conversion rule.
  • the processing server 110 may then submit a rebate request to the payment network 108 for the rebate amount to be paid to the issuer 104 for the reward account based on the redeemed rewards.
  • the payment network 108 may process the rebate using systems and methods that will be apparent to persons having skill in the relevant art.
  • the processing server 110 may transmit a notification to the consumer 102 indicating the successful transmission of the rebate request to the payment network 108.
  • the notification may be transmitted to the consumer 102 via short message service (SMS) message, multimedia service message, e-mail, traditional mail, telephone, a website, an application program, or any other suitable method as will be apparent to persons having skill in the relevant art, which may be transmitted to the consumer 102 or a computing device associated with the consumer 102.
  • SMS short message service
  • multimedia service message multimedia service message
  • e-mail traditional mail
  • telephone telephone
  • a website an application program, or any other suitable method as will be apparent to persons having skill in the relevant art, which may be transmitted to the consumer 102 or a computing device associated with the consumer 102.
  • the processing server 110 may transmit another notification, in addition, or alternative to, the notification indicating successful transmission of the rebate request, indicating the successful processing of the rebate request.
  • the processing server 110 may also transmit a notification to the issuer 104, such as to provide an update as to the reward balance of the reward account based on the calculated updated reward balance.
  • the processing server 110 may request permission from the consumer 102 to submit a rebate request for a payment transaction where the reward balance for the account data entry associated with the consumer 102 is less than the transaction reward value.
  • the processing server 110 may submit a request to the consumer 102 (e.g., to a computing device associated with the consumer 102, such as a mobile computing device or a point-of-sale device where the payment transaction was conducted).
  • the consumer 102 may respond to the request, which may be received by the processing server 110 and processed accordingly.
  • the processing server 110 may submit a rebate request as discussed above if the consumer 102 wishes to use their reward balance, or may not submit any request if the consumer 102 does not wish to use their reward balance.
  • the processing server 110 may be configured to submit rebate requests based on partial use of a reward balance.
  • the systems and methods discussed herein may provide for a number of improvements over traditional systems and methods for enabling a consumer 102 to fund a payment transaction using rewards for a reward account. Because the processing server 110 may utilize a reward balance for funding of a payment transaction without requiring the consumer 102 to use a second payment card or to perform any actions prior to conducting the transaction, the processing server 110 may provide for faster and more efficient funding of payment transaction via rewards. As a result, the system 100 may potentially be more acceptable by consumers, which may, in turn, result in a higher rate of use, which may provide benefits to both consumers 102 and issuers 104.
  • the payment transaction itself may be conducted traditionally without modification to existing payment systems.
  • the rebate request may be transmitted as a clearing record following the payment transaction, which may result in very fast processing of the rebate request.
  • the initial authorization request submitted to the payment network 108 from the merchant 106 may be submitted traditionally, without interruption or intervention by the processing server 110, which may result in the maintaining of traditional processing speeds, which, when combined with the speed of clearing of the rebate request, may result in the processing of a rebate for a payment transaction using rewards with unnoticeable delay to the consumer 102.
  • FIG. 2 illustrates an embodiment of the processing server 110 of the system 100. It will be apparent to persons having skill in the relevant art that the embodiment of the processing server 110 illustrated in FIG. 2 is provided as illustration only and may not be exhaustive to all possible configurations of the processing server 110 suitable for performing the functions as discussed herein.
  • the computer system 600 illustrated in FIG. 6 and discussed in more detail below may be a suitable configuration of the processing server 110.
  • the processing server 110 may include a receiving unit 202.
  • the receiving unit 202 may be configured to receive data over one or more networks via one or more network protocols.
  • the receiving unit 202 may be configured to receive an authorization request from the payment network 108 corresponding to a payment transaction funded by a reward account, wherein the authorization request includes at least a transaction amount and payment information.
  • the payment information may include an account identifier or other suitable information, as will be apparent to persons having skill in the relevant art, which may be used to identify the reward account used to fund the payment transaction.
  • the processing server 110 may further include a processing unit 204.
  • the processing unit 204 may 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 (e.g., of the associated reward account), username, e-mail address, phone number, etc.
  • the reward balance may be a balance of the rewards earned by the consumer 102 for the associated reward account. In some instances, the reward balance may be received by the processing server 110 (e.g., via the receiving unit 202) from the issuer 104.
  • the processing unit 204 may be further configured to calculate a transaction reward value based on at least the transaction amount and one or more conversion rules, which may be stored in a memory 210.
  • the transaction reward value may be further based on at least one of: the consumer 102 (e.g., an account level for the consumer 102), the issuer 104 (e.g., issuer preferences, issuer category, etc.), the merchant 106 (e.g., merchant preferences, merchant category, merchant industry, etc.), transaction data included in the authorization request (e.g., product data, transaction time and/or date, geographic location, etc.), and more as will be apparent to persons having skill in the relevant art.
  • the consumer 102 e.g., an account level for the consumer 102
  • the issuer 104 e.g., issuer preferences, issuer category, etc.
  • the merchant 106 e.g., merchant preferences, merchant category, merchant industry, etc.
  • transaction data included in the authorization request e.g., product data, transaction time and/
  • the processing unit 204 may also be configured to identify a reduction amount, which 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 may then update the reward balance included in the identified account data entry 208 based on the current reward balance and the reduction amount, and may calculate a rebate amount based on the identified reduction amount and the at least one conversion rule. The processing unit 204 may generate a rebate request for the calculated rebate amount.
  • 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. The processing unit 204 may accordingly identify a reduction amount of 75 points, which may update the reward balance to be zero points, and may result in a calculated rebate amount of $75. The processing unit 204 may then generate a rebate request for $75 to the reward account.
  • the processing server 110 may also include a transmitting unit 206.
  • the transmitting unit 206 may be configured to transmit data over one or more networks via one or more network protocols.
  • the transmitting unit 206 may be configured to transmit the generated rebate request to the payment network 108 for processing.
  • the transmitting unit 206 may also be configured to transmit notifications to the consumer 102 and/or the issuer 104 indicating the successful transmitting of the rebate request.
  • the receiving unit 202 may receive a notification from the payment network 108 upon the successful processing of the rebate request.
  • the transmitting unit 206 may be further configured to transmit a notification to the consumer 102 and/or the issuer 104 indicating the successful processing.
  • the notification may be transmitted in addition, or alternative to, a prior notification indicating successful transmission of the rebate request.
  • the transmitting unit 206 may be configured to transmit a request for approval of the consumer 102 to proceed to the consumer 102.
  • the request may be transmitted to the consumer 102 via any suitable method as will be apparent to persons having skill in the relevant art, such as via a computing device associated with the consumer 102 or a point-of-sale device used to conduct the payment transaction (e.g., as indicated in the authorization request).
  • the receiving unit 202 may be configured to receive a response from the consumer 102 indicating to process the rebate request for the partial amount of the transaction amount or to withhold a rebate request.
  • the processing unit 204 may identify the indication included in the response and may act accordingly as discussed above.
  • the account data entry 208 may indicate if the processing unit 204 is to generate a rebate request if the reward balance is less than the calculated transaction reward value.
  • FIG. 3 illustrates a process for the processing of a payment transaction funded using a reward account and the subsequent processing of a rebate request using rewards earned on the reward account.
  • the consumer 102 may initiate a payment transaction with the merchant 106 for the purchase of goods or services using a reward account.
  • the consumer 102 may provide the merchant 106 with an account number for the reward account (e.g., via a payment card or other suitable method).
  • the merchant 106 e.g., or an acquirer associated with the merchant 106
  • the payment network 108 may forward the authorization request to the issuer 104 of the reward account.
  • the issuer 104 may approve the payment transaction (e.g., based on adequate funding in the reward account), in step 308, and may transmit an authorization response indicating approval back to the payment network 108, in step 310.
  • step 312 the payment network 108 may forward the authorization response to the merchant 106 indicating the approval of the payment transaction. It will be apparent to persons having skill in the relevant art that steps 304 through 312 are illustrative of the processing of a payment transaction using traditional systems and methods and that additional steps and/or additional entities may be included.
  • step 314 the merchant 106 may furnish a receipt and/or transacted for goods or services to the consumer 102.
  • step 316 the payment network 108 may transmit a copy of the
  • the processing server 110 may identify an account data entry 208 associated with the reward account used to fund the payment transaction and may further identify the potential for the use of rewards to fund the payment transaction based on a reward balance included in the identified account data entry 208 and a transaction reward value calculated based on the transaction amount and at least one conversion rule, and possibly based on a preference as described below.
  • a preference e.g., a reward preference
  • the processing server 110 may submit an approval request to the consumer 102, in step 320.
  • the consumer 102 may approve the use of points via a computing device (e.g., a mobile computing device, a point-of-sale device at the merchant 106, etc.) or other suitable method.
  • An approval response indicating the consumer's approval may be transmitted to the processing server 110, in step 324.
  • the processing server 110 may then generate a rebate request for a rebate amount based on the reduction amount and the at least one conversion rule, and potentially based on approval or preferences.
  • the processing server 110 may transmit the rebate request to the payment network 108.
  • the payment network 108 may process the rebate request using methods and systems that will be apparent to persons having skill in the relevant art.
  • the rebate may be processed from an account associated with the merchant 106 to the reward account associated with the consumer 102.
  • the payment network 108 may transmit a rebate response indicating the successful processing of the rebate for the rebate amount to the reward account.
  • the processing server 110 may transmit a notification to the consumer 102 indicating the successful processing of the rebate. In some instances, the notification may further include an updated reward amount and other suitable information as will be apparent to persons having skill in the relevant art.
  • FIG. 4 illustrates a method for the generating and processing thereof of a rebate reward request for a rebate for a payment transaction funded using a reward account as executed via the processing server 110 of the system 100.
  • the reward account may include the selection of a consumer's preferences in the use of a reward balance, and may include program preferences for the use of the reward balance as selected by an issuer 104, payment network provider, merchant 106 and/or acquirer.
  • 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 may include at least payment information and a transaction amount.
  • the processing unit 204 may determine if the payment transaction is a valid transaction for the full or partial funding of the payment transaction using rewards.
  • Step 404 may include the identification of an 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, then the transaction may not be considered valid, and the process may be ended.
  • the processing server 110 determines whether the payment transaction is eligible for a rebate reward request, based on one or more consumer and/or program preferences (e.g., reward preferences).
  • Each account data entry 208 in the account database 112 may include a consumer preference associated with a reward account.
  • the consumer preference may be indicative of when a reward rebate should be requested for purchase made at a point-of-sale terminal (physical or virtual), and conversely, when the purchase should not be eligible for a reward rebate request.
  • the consumer preference may be received from a computing device associated with the consumer 102, such as a mobile computing device or even a point-of-sale device where the payment transaction was conducted with the consumer 102 present.
  • the consumer 102 will select or provide, through the consumer computing device, a reward preference before arriving at the merchant 106, which is received by the processing server 110 and stored in the account data entry 208.
  • the consumer 102 may select a reward preference from a mobile computing device or a point-of-sale device at the merchant 106, while shopping, just prior to a payment purchase, or as part of a payment transaction.
  • the consumer preferences (e.g., consumer reward preferences) may include a variety of different indications of when a reward rebate should or should not be requested for a purchase.
  • consumer preference options may include disabling use of the reward rebate requests for payment transactions, using reward rebate requests for all payment transactions, using reward rebate requests for only the next payment transaction, etc. This allows the consumer 102 to decide when they would like to have a reward rebate requested for a payment transaction. If the reward balance is relatively small, or if the consumer 102 would like to build the reward balance up to a larger amount for a more significant purchase in the future, for example, the consumer 102 may, in some examples, turn off rewards usage for the time being. Alternatively, if the consumer 102 has built up a large reward balance in the reward account, or would like to use rewards as soon as possible, for example, the consumer 102 may select to use reward rebate requests for all payment transactions.
  • the consumer 102 may select to use a reward rebate request only for the next purchase.
  • the consumer 102 may, for example, select this reward preference at the merchant 106 while shopping, where the consumer 102 has decided to purchase a product, which he/she desires to use a reward rebate request. After the next purchase is made the consumer preference is automatically changed back to disabled. The consumer 102 is then able to change the preference later in order to have reward rebate requests used for subsequent payment transactions.
  • a consumer preference may include a particular merchant (or merchants), such that reward rebate requests should only be used for payment transactions at the particular merchant(s).
  • the processing server 110 and/or the consumer 102 may select minimum criteria, which must be met for the reward rebate to be requested for a payment transaction.
  • the consumer may select a minimum purchase amount of $20, such that reward rebate requests will only be used for payment transactions involving at least $20.
  • the consumer 102 may select this minimum purchase amount, for example, so that the consumer can pay for smaller purchases using normal payment account methods (e.g., charging/debiting reward account, etc.), while saving the reward balance to be used for larger, more significant purchases.
  • the consumer preference may include a maximum purchase amount.
  • Each of the above exemplary consumer preferences, and other consumer preferences may be received, via an interface at the consumer's computing device, or through other interaction between the consumer 102 and the processing server 110 (directly or indirectly), whereby the processing server 110 subsequently receives the consumer's preferences.
  • FIG. 5 illustrates an interface 450 suitable to be displayed at a consumer's mobile computing device.
  • the interface 450 includes an account number entry field 452, which may receive an account number (e.g., account identifier) associated with the consumer's reward account from the consumer 102.
  • the interface 450 further includes a passcode field 454, which may receive a passcode associated with the reward account, to prevent others from accessing and/or altering preferences of the consumer's reward account.
  • the interface 450 includes a radio button to select a minimum purchase amount 456, as described above, which may cause a rebate request to only be requested when payment transactions is at or above a minimum purchase amount entered by the consumer 102 in an amount field 458.
  • the interface 450 further includes radio buttons 460 associated with preferences for all transactions, no transactions, and a next transaction only, consistent with the preferences described above with reference to FIG. 4.
  • the consumer 102 submits the preferences to the processing server 110, by actuating a submit button 462.
  • the processing server 110 receives the preferences and stores the associated account data entry 208.
  • any number of different preferences from the consumer may be included and/or selected from an interface, such as interface 450.
  • the consumer preference allows the consumer 102 to predefine how the reward balance should be used, i.e., via one or more reward preferences, and then simply use the payment card associated with the reward account in a normal fashion without having to perform any additional actions and/or activities to utilize the reward balance, resulting in easier reward account usage for the consumer 102.
  • the issuer 104 of the reward account may set a minimum purchase amount for the reward account, such that reward rebates will only be requested for payment transactions involving at least that amount.
  • Program preferences may further limit the number of reward rebate requests in a certain period, limit the merchants 106 at which rewards may be used, and/or various other options, which may preserve breakage in a rewards program (not allow a consumer to cash out all of their points), create rewards program level variables, reduce the amount of processed reward redemptions, reduce the amount of reward redemption fees, etc. Any criteria established by the issuer 104, a merchant 106, a payment network provider, or an acquirer may be considered program preferences (e.g., program reward preferences).
  • step 405 the processing server 110 determines whether the payment transaction is eligible for a rebate request, based on one or more consumer and/or reward program preferences, including those described above.
  • step 405 may be located at other points in the method (e.g., after step 406, after step 408, etc.), or may be absent from the method.
  • Step 406 the processing unit 204 may determine if there is an adequate reward balance in the account for the full funding of the payment transaction.
  • Step 406 may include the calculation of a transaction reward value based on the transaction amount for the payment transaction and one or more conversion rules, and identification if a reward balance included in the identified account data entry 208 meets or exceeds the calculated transaction reward value.
  • the processing unit 204 may determine if there is default approval from the consumer, consumer preferences and/or program preferences associated with the reward account for partial funding of the payment transaction, such as based on data included in the identified account data entry 208.
  • the default approval may be indicated by a consumer preference and/or a program preference.
  • an issuer 104 may choose to only allow reward rebate requests when the reward balance is sufficient to fund the full amount of a transaction (i.e., fully funded). The issuer 104 may select this requirement in order to avoid processing separate payment methods (i.e., with rewards points and with normal payment account operations) for a single payment transaction, to reduce fees associated with reward point redemption, etc.
  • a reward rebate request will not be generated unless the reward balance is greater than or equal to the transaction amount (or transaction reward value).
  • the cash equivalent of the consumer's current reward point balance must be greater than the transaction amount.
  • a program preference may indicate that partial reward balance usage is allowed. If a consumer preference indicates partial payment is provided by default, a reward rebate request may be generated even if the reward balance is only sufficient to fund a portion of the payment transaction amount. The reward balance will be used even if the reward balance cash equivalent is less than the transaction amount.
  • the transmitting unit 206 of the processing server 110 may transmit an approval request to the consumer 102.
  • the method of communication of the approval request may be included in the identified account data entry 208.
  • the receiving unit 202 may receive a response from the consumer 102 indicating the approval or denial of the usage of rewards to partially fund the payment transaction.
  • the processing unit 204 may identify in the consumer response if usage of rewards is approved. If usage is not approved, then the process may be completed.
  • points may be redeemed in pre-defined increments according to a preference. For example, if a consumer 102 has 10,400 rewards points, and each point is worth $.01, the consumer has a cash equivalent balance of $104, through use of a conversion rule. If the program increment is set to $5, and the consumer attempts to make a purchase of $136.23, $100 would be redeemed. The consumer 102 would be left with 400 points, which amount to $4. The consumer 102 would be unable to use rewards points again until the consumer 102 accrued at least 500 points. Further, if a program minimum is $10, the consumer 102 would be unable to use rewards points until the consumer accrued at least 1,000 points.
  • the processing unit 204 may deduct the corresponding reward amount from the reward balance in the identified account data entry 208.
  • the processing unit 204 may then, in step 418, process the rebate for the payment transaction. Processing the rebate may occur upon calculating a rebate amount, which may be based on the transaction reward value, reward reduction amount, and at least one conversion rule, generating a rebate request for the calculated rebate amount, and transmitting thereof, by the transmitting unit 206, to the payment network 108 for processing.
  • the transmitting unit 206 may transmit a notification to the consumer 102 indicating the processing of the rebate.
  • the notification may include at least one of: the reduction amount, the rebate amount, and the updated reward balance.
  • FIG. 6 illustrates a method 500 for the initiating of a rebate for a payment transaction funded using a reward account.
  • a plurality of account data entries may be stored in a database (e.g., the account database 112), wherein each account data entry 208 includes data related to a consumer reward account including at least an account identifier and a reward balance.
  • an authorization request for a payment transaction involving a merchant e.g., the merchant 106
  • a receiving device e.g., the receiving unit 202
  • the authorization request includes at least payment information and a transaction amount.
  • a transaction reward value may be calculated, by a processing device (e.g., the processing unit 204), based on at least the transaction amount and at least one conversion rule.
  • the at least one conversion rule is associated with at least one of: the merchant 106, the transaction amount, an account level, and a merchant category.
  • a reduction amount may be identified, by the processing device 204, wherein the reduction amount is a lesser of the transaction reward value and the reward balance included in a specific account data entry 208 in the database 112 where the included account identifier corresponds to the payment information.
  • each account data entry 208 may further include an indication of whether the corresponding reward balance is to be used if the reward balance is less than the calculated transaction reward value.
  • the payment information included in the authorization request may include the account identifier included in the specific account data entry 208.
  • step 510 the reward balance included in the specific account data entry 208 may be updated, in the database 112, based on the identified reduction amount.
  • a rebate amount may be calculated, by the processing device 204, based on the transaction reward value and the identified reduction amount, and the at least one conversion rule.
  • step 514 a rebate request for the calculated rebate amount from a payment account associated with the merchant 106 to a payment account corresponding to the payment information included in the authorization request may be transmitted, by a transmitting device (e.g., the transmitting unit 206).
  • the rebate request may be transmitted to a payment network (e.g., the payment network 108).
  • the method 500 may further include: transmitting, by the transmitting device 206, a notification to a consumer (e.g., the consumer 102) associated with the specific account data entry 208 indicating successful transmission of the rebate request.
  • the method 500 may further include: receiving, by the receiving device 202, an indication of successful processing of a rebate in response to the transmitted rebate request; and transmitting, by the transmitting device 206, a notification to the consumer 102 associated with the specific account data entry indicating the successful processing of the rebate.
  • the method 500 may further include receiving, by the receiving device 202, an indication to proceed with transmitting the rebate request prior to the transmitting of the rebate request when the reward balance is less than the transaction reward value.
  • the indication to proceed may be received in response to transmitting, by the transmitting device 206, a request to proceed to a computing device associated with the specific account data entry 208.
  • the request to proceed may include at least the reward balance included in the specific account data entry 208 and may be transmitted via at least one of: short message service message, multimedia message service message, e-mail, and transmission to a point-of-sale device associated with the payment transaction.
  • a reward balance related to a reward account may be stored by a third party (e.g., airlines, retailers, etc.).
  • the reward account may include a third party indicator, indicative of a reward balance associated with the reward account being stored by a third party.
  • the third party may be a points bank that holds the rewards point balance of the consumer 102.
  • a processing server 110 may be configured to transmit a transaction reward value to the third party, based on a transaction amount of a payment transaction involving a reward account having a reward balance stored by the third party.
  • the transaction reward value may indicate an amount of reward balance (e.g., amount of reward points, cash equivalency, etc.) needed to fund the payment transaction.
  • the transaction reward value can be based on a rewards program, third party and/or consumer configuration. For example, any of the payment service provider, third party, consumer, etc., may set criteria for calculating the transaction reward value. If the payment transaction is deemed eligible, based on the criteria (e.g., consumer preference, program preference, etc.), the transaction reward value is transmitted to the third party.
  • criteria e.g., consumer preference, program preference, etc.
  • the processing server 110 may also transmit payment transaction information to the third party, which may include, without limitation, a transaction location, local currency amount, settlement currency amount, merchant location, etc.
  • the processing server 110 may also transmit a scoring rule used to calculate the amount of points required, which may include a cost per point (e.g., 100 basis points, each point being worth $.01, etc.).
  • the third party processor may then determine if the consumer 102 has enough reward balance to complete the redemption. If the consumer has enough reward balance, the third party processor may send a message indicating that points have been deducted, and a statement credit may be given to the consumer.
  • the third party may transmit a rebate request to an issuer of the reward account, a payment network provider, merchant and/or acquirer.
  • FIG. 7 illustrates an example system for processing a payment transaction involving a reward account having a reward balance stored with a third party, according to another example embodiment of the present disclosure.
  • a consumer 550 e.g., a MasterCard® consumer
  • POS point-of-sale
  • a payment transaction authorization is transmitted to an acquirer 554, and then to a payment network 556.
  • the payment network 556 may be linked to, or include, a system for transmitting and receiving information between banks (e.g., BankNet ASA).
  • the authorization request is then be transmitted to an issuer 558.
  • the transaction authorization is added to a queue, which is read by a real time rewards (RTR) engine 560.
  • the RTR engine 560 may be part of the payment network 556, and may be implemented by a processing server.
  • the RTR engine 560 applies applicable filtering logic (including consumer eligibility) and determines how many points are needed to cover the full transaction amount, or details on how to process a partial transaction amount.
  • the RTR engine 560 may apply any consumer and/or program preferences, including those described herein, to determine whether the transaction authorization is eligible for a rebate request.
  • the RTR engine 560 then generates a transaction reward value (i.e., scored transaction result), which may be calculated as described herein (e.g., based on at least one conversion rule, etc.).
  • the RTR engine 560 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 may include generating a rebate request as described herein (e.g., calculating a rebate amount based on the reward transaction value, etc.).
  • the RTR engine 560 transmits the transaction reward value to the third party (or a 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 the payment network 556.
  • the third party transaction processor calls an application programming interface (API) of the issuer 558 associated with the reward account to determine if the transaction should result in a statement credit (i.e., the reward balance should be applied to the transaction), and whether necessary points should be deducted. If the reward balance should be applied to the transaction, a rebate is sent to a rebate service 564, which may be part of the payment network 556.
  • the rebate service 564 saves the rebate redemption in a database, such as the MasterCard® rewards system (MRS) database.
  • the rebate may then be settled, such as being sent via batch to the MasterCard® global clearing management system (GCMS).
  • the rebate may also be reported to the issuer 558 of the reward account, for the issuer 558 to apply the rebate to the reward account.
  • the third party may then reduce the reward balance related to the reward account, based on the amount of the rebate request.
  • FIG. 8 illustrates an example method flow for processing a payment transaction according to the system illustrated in FIG. 7.
  • the method flow is broken into regions that designate actions at the consumer 550, at a payment network e.g., a merchant, an acquirer 554, a payment network 556, which may include BankNet, MRS and GCMS, and at the issuer 558.
  • a payment network e.g., a merchant
  • an acquirer 554 e.g., a payment network
  • 556 which may include BankNet, MRS and GCMS, and at the issuer 558.
  • the consumer 550 first signs up for the pay with rewards-real time rewards (PWR-RTR) service, at 566, at which point the payment network 556 enrolls the consumer into the service (e.g., by creating a new reward account, associating a reward balance and account identifier with an existing account, etc.).
  • PWR-RTR rewards-real time rewards
  • a transaction authorization request is received by the payment network 556, and may be stored in a queue (e.g., a transaction authorization request copy is provided by BankNet to MRS, then MRS acknowledges receipt of the transaction to BankNet, and stores the authorization transaction).
  • the payment network 556 determines whether the transaction passes validations, at 568, which may include consumer preferences, program preferences, etc. If the transaction does not pass validations, the transaction is complete. If the transaction passes validations, the payment network 556 calculates points for redemption based on the transaction amount (e.g., by calculating a transaction reward value based on at least one conversion rule).
  • the payment network 556 next checks to see if the reward account is associated with a third party bank, at 570. If the reward account is stored with a third party bank, the payment network 556 transmits an external fire-and-forget message to the third party (e.g., a message transmitted to the third party such that the third party, and not the payment network 556, handles further reward balance usage determination, reward balance updating, rebate request generation, etc.) and the process is complete.
  • the transmitted message may include the transaction reward value, and other transaction and/or reward account information.
  • the payment network 556 determines, at 572, whether the reward balance of the consumer's reward account can cover at least a portion of the transaction (e.g., whether the consumer's reward account has enough points to pay for at least a portion of the transaction). If the consumer reward balance doesn't have enough points, an optional message (e.g., short message service (SMS), email, etc.) may be sent to the consumer indicating the lack of reward points.
  • SMS short message service
  • the redemption cash back process is initiated.
  • a rebate request file is generated for the transaction, based on a schedule.
  • the rebate request file is then processed (e.g., by submitting the file to the GCMS).
  • the payment transaction may then be processed by the payment network 556, and settlement of the payment transaction occurs with the issuer 558 of the reward account.
  • Redemption fees are calculated (which may be based on the amount of the rebate request) and transmitted to the 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 illustrates an example method flow for processing a payment transaction involving a reward account associated with a third party, according to the system illustrated in FIG. 7.
  • the illustrated method flow is broken down into actions at the third party actions, the payment network 556 (including MRS services, MRS, and GCMS) and actions at the issuer 558.
  • the third party first processes rewards points redemption at 574 (e.g., in response to receiving a message from the payment network 556 indicating a consumer would like to use a reward balance of the consumer's reward account to fund a payment transaction).
  • the third party then transmits a rebate request to the payment network 556 (e.g., by initiating an MRS rebate redemption request).
  • the payment network 556 then processes the rebate request at 576 (e.g., MRS services then initiates redemption following a cash back process in which no points may be required).
  • the payment network transmits a message to the third party, which may indicate whether the rebate request was successful. If the rebate request was indicated as successful, the third party process is complete (and the third party may update the reward balance accordingly). If the rebate request was not successful, the third party may repeat the step of transmitting a rebate request to the payment network.
  • the payment network may create a rebate file based on a schedule, at 578.
  • the rebate file is then processed (e.g., by submitting the file to GCMS).
  • the payment transaction may then be processed by the payment network 556, and settlement of the payment transaction occurs with the issuer 558 of the reward account.
  • Redemption fees are calculated and sent to the issuer 558 associated with the reward account.
  • An optional redemption notification may be sent to the consumer 550.
  • FIGS. 8 and 9 Further details of the steps of FIGS. 8 and 9 are described in the blocks of the flow diagrams of FIGS. 8 and 9, but should not be considered as limiting the example processes illustrated in FIGS. 8 and 9. As should be apparent, in other example embodiments the order of the steps may vary, some steps may be absent, and some additional steps may be added, without departing from the scope of the present disclosure.
  • FIG. 10 illustrates a computer system 600 in which embodiments of the present disclosure, or portions thereof, may be implemented as computer-readable code.
  • the processing server 110 of FIG. 1 may be implemented in the computer system 600 using hardware, software, firmware, non-transitory computer readable media having executable instructions stored thereon, or a combination thereof and may be implemented in one or more computer systems or other processing systems.
  • Hardware, software, or any combination thereof may embody modules and components used to implement the methods of FIGS. 3-5.
  • programmable logic may execute on a commercially available processing platform or a special purpose device.
  • a person having ordinary skill in the art may appreciate that embodiments of the disclosed subject matter can be practiced with various computer system configurations, including multi-core multiprocessor systems, minicomputers, mainframe computers, computers linked or clustered with distributed functions, as well as pervasive or miniature computers that may be embedded into virtually any device.
  • processor device and a memory may be used to implement the above described embodiments.
  • a processor unit or device as discussed herein may be a single processor, a plurality of processors, or combinations thereof. Processor devices 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 used to generally refer to tangible media such as a removable storage unit 618, a removable storage unit 622, and a hard disk installed in hard disk drive 612.
  • Processor device 604 may be a special purpose or a general purpose processor device.
  • the processor device 604 may be connected to a communications infrastructure 606, such as a bus, message queue, network, multi-core message- passing scheme, etc.
  • the network may be any network suitable for performing the functions as disclosed herein and may include a local area network (LAN), a wide area network (WAN), a wireless network (e.g., WiFi), a mobile communication network, a satellite network, the Internet, fiber optic, coaxial cable, infrared, radio frequency (RF), or any combination thereof.
  • LAN local area network
  • WAN wide area network
  • WiFi wireless network
  • mobile communication network e.g., a mobile communication network
  • satellite network such as the Internet
  • RF radio frequency
  • the computer system 600 may also include a main memory 608 (e.g., random access memory, read-only memory, etc.), and may also include a secondary memory 610.
  • the secondary memory 610 may include the hard disk drive 612 and a removable storage drive 614, such as a floppy disk drive, a magnetic tape drive, an optical disk drive, a flash memory, etc.
  • the removable storage drive 614 may read from and/or write to the removable storage unit 618 in a well-known manner.
  • the removable storage unit 618 may include a removable storage media that may be read by and written to by the removable storage drive 614.
  • the removable storage drive 614 is a floppy disk drive
  • the removable storage unit 618 may be a floppy disk.
  • the removable storage unit 618 may be non- transitory computer readable recording media.
  • the secondary memory 610 may include alternative means for allowing computer programs or other executable instructions to be loaded into the computer system 600, for example, the removable storage unit 622 and an interface 620.
  • Examples of such means may include a program cartridge and cartridge interface (e.g., as found in video game systems), a removable memory chip (e.g., EEPROM, PROM, etc.) and associated socket, and other removable storage units 622 and interfaces 620 as will be apparent to persons having skill in the relevant art.
  • a program cartridge and cartridge interface e.g., as found in video game systems
  • a removable memory chip e.g., EEPROM, PROM, etc.
  • associated socket e.g., EEPROM, PROM, etc.
  • Data stored in the computer system 600 may be stored on any type of suitable computer readable media, such as optical storage (e.g., a compact disc, digital versatile disc, Blu-ray disc, etc.) or magnetic tape storage (e.g., a hard disk drive).
  • the data may be configured in any type of suitable database configuration, such as a relational database, a structured query language (SQL) database, a distributed database, an object database, etc. Suitable configurations and storage types will be apparent to persons having skill in the relevant art.
  • the computer system 600 may also include a communications interface 624.
  • the communications interface 624 may be configured to allow software and data to be transferred between the computer system 600 and external devices.
  • Exemplary communications interfaces 624 may include a modem, a network interface (e.g., an Ethernet card), a
  • Signals may be electronic, electromagnetic, optical, or other signals as will be apparent to persons having skill in the relevant art.
  • the signals may travel via a communications path 626, which may be configured to carry the signals and may be implemented using wire, cable, fiber optics, a phone line, a cellular phone link, a radio frequency link, etc.
  • Computer program medium and computer usable medium may refer to memories, such as the main memory 608 and secondary memory 610, which may be memory semiconductors (e.g., DRAMs, etc.). These computer program products may be means for providing software to the computer system 600.
  • Computer programs e.g., computer control logic
  • Computer programs may be stored in the main memory 608 and/or the secondary memory 610. Computer programs may also be received via the communications interface 624. Such computer programs, when executed, may enable computer system 600 to implement the present methods as discussed herein.
  • the computer programs, when executed may enable processor device 604 to implement the methods illustrated by FIGS. 3-4, 6, and 8-9, as discussed herein. Accordingly, such computer programs may represent controllers of the computer system 600.
  • the software may be stored in a computer program product and loaded into the computer system 600 using the removable storage drive 614, interface 620, and hard disk drive 612, or communications interface 624.
  • the above- described embodiments of the disclosure may be implemented using computer programming or engineering techniques including computer software, firmware, hardware or any combination or subset thereof, wherein the technical effect may be achieved by performing at least one of the following steps: (a) receiving an authorization request for a payment transaction involving the reward account, wherein the authorization request includes at least a transaction amount, (b) determining, based on the reward preference, whether the payment transaction is eligible for a reward rebate, (c) transmitting a request for the reward rebate when the payment transaction is eligible, (d) calculating a transaction reward value based on at least the transaction amount and at least one conversion rule, (e) calculating a rebate amount based on the lesser of the transaction reward value and the reward balance, (f) updating the reward balance based on the rebate amount, and (g) transmitting the transaction reward value and payment transaction information to a third party.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Computer Security & Cryptography (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Marketing (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

Selon la présente invention, des systèmes et des procédés permettant de traiter des transactions de paiement impliquant des comptes de récompense sont décrits. Un procédé, donné à titre d'exemple, comprend la réception d'une demande d'autorisation pour une transaction de paiement impliquant un compte de récompense. La demande d'autorisation comprend au moins un montant de transaction. Le procédé consiste également à déterminer, en fonction de la préférence de récompense, si la transaction de paiement est autorisée pour un rabais de récompense et à transmettre une demande pour le rabais de récompense lorsque la transaction de paiement est autorisée.
PCT/US2015/045887 2014-08-21 2015-08-19 Procédé et système de traitement d'un rabais en temps réel lors d'une autorisation de transaction WO2016028889A1 (fr)

Priority Applications (7)

Application Number Priority Date Filing Date Title
EP15833649.5A EP3192034A4 (fr) 2014-08-21 2015-08-19 Procédé et système de traitement d'un rabais en temps réel lors d'une autorisation de transaction
RU2017109095A RU2017109095A (ru) 2014-08-21 2015-08-19 Способ и система для обработки вычета в реальном времени при авторизации транзакции
AU2015305524A AU2015305524A1 (en) 2014-08-21 2015-08-19 Method and system for processing of a real-time rebate at transaction authorization
CA2958551A CA2958551A1 (fr) 2014-08-21 2015-08-19 Procede et systeme de traitement d'un rabais en temps reel lors d'une autorisation de transaction
BR112017003415A BR112017003415A2 (pt) 2014-08-21 2015-08-19 método e sistema para processamento de um reembolso em tempo real em autorização de transação
JP2017510295A JP2017528822A (ja) 2014-08-21 2015-08-19 取引認可においてリアルタイム割り戻しを処理するための方法及びシステム
CN201580057280.2A CN107077677A (zh) 2014-08-21 2015-08-19 用于在交易授权时处理实时返利的方法和系统

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US14/465,063 2014-08-21
US14/465,063 US20150112781A1 (en) 2013-10-21 2014-08-21 Method and System for Processing of a Real-Time Rebate at Transaction Authorization

Publications (1)

Publication Number Publication Date
WO2016028889A1 true WO2016028889A1 (fr) 2016-02-25

Family

ID=55351226

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/045887 WO2016028889A1 (fr) 2014-08-21 2015-08-19 Procédé et système de traitement d'un rabais en temps réel lors d'une autorisation de transaction

Country Status (8)

Country Link
EP (1) EP3192034A4 (fr)
JP (1) JP2017528822A (fr)
CN (1) CN107077677A (fr)
AU (1) AU2015305524A1 (fr)
BR (1) BR112017003415A2 (fr)
CA (1) CA2958551A1 (fr)
RU (1) RU2017109095A (fr)
WO (1) WO2016028889A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017176365A1 (fr) * 2016-04-06 2017-10-12 Mastercard International Incorporated Procédé et système de promotions en temps réel
WO2017176362A1 (fr) * 2016-04-06 2017-10-12 Mastercard International Incorporated Procédé et système d'application de remise en temps réel
US20230141912A1 (en) * 2020-07-06 2023-05-11 Block, Inc. Peer-to-peer transfer of a stored value

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107862541A (zh) * 2017-09-27 2018-03-30 天脉聚源（北京）科技有限公司 一种奖励反馈方法及装置
US10713677B2 (en) * 2017-12-13 2020-07-14 Mastercard Asia/Pacific Pte. Ltd. Method and system for social savings platform via blockchain
CN108280683B (zh) * 2018-01-18 2022-04-22 百度在线网络技术（北京）有限公司 基于广告投放平台的优惠券发放方法及装置
SG10201801787SA (en) * 2018-03-05 2019-10-30 Citibank Na Electronic payment systems and methods
US11301856B2 (en) * 2018-05-24 2022-04-12 Mastercard International Incorporated Method and system for transaction authorization via controlled blockchain
CN110245992A (zh) * 2019-06-20 2019-09-17 深圳前海微众银行股份有限公司 一种资源处理方法及装置
CN111681053B (zh) * 2020-06-09 2023-09-22 青岛有容信息科技有限公司 一种收付链构建方法、装置、计算机设备及可读存储介质
CN118379053A (zh) * 2024-06-25 2024-07-23 江西萌趣文化科技有限公司 一种基于多场景实体的数字红包发送方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080103968A1 (en) * 2006-10-31 2008-05-01 Discover Financial Services Llc Redemption of Credit Card Rewards at a Point of Sale
US20080133351A1 (en) * 2006-10-24 2008-06-05 Brigette White Method and apparatus for reward messaging, discounting and redemption at the point of interaction
US20130246273A1 (en) * 2012-03-16 2013-09-19 Visa International Service Association Systems and methods to generate a receipt for a transaction
US20140081733A1 (en) * 2012-09-16 2014-03-20 American Express Travel Related Services Company, Inc. System and method for rewarding in channel accomplishments
US20140156480A1 (en) * 2012-11-30 2014-06-05 Bank Of America Corporation Personal financial management payment allocation

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU4342300A (en) * 1999-04-13 2000-11-14 Shopexpert.Com, Inc. Method and apparatus for tracking consumers
CA2393735A1 (fr) * 1999-12-09 2001-06-14 Carlson Marketing Group, Inc. Systeme combine de rachat et de retribution interactifs memorises et en ligne, et procede y relatif
US8833645B2 (en) * 2005-06-24 2014-09-16 Visa U.S.A. Inc. System, apparatus and methods for automatically calculating discounts for purchases from merchants made using a reservation system
US9613361B2 (en) * 2006-07-18 2017-04-04 American Express Travel Related Services Company, Inc. System and method for E-mail based rewards
US8676642B1 (en) * 2007-07-05 2014-03-18 Jpmorgan Chase Bank, N.A. System and method for granting promotional rewards to financial account holders
CN101216920A (zh) * 2008-01-11 2008-07-09 侯万春 实现银行卡用户刷卡消费即获特惠的系统及方法
MX2011002436A (es) * 2008-09-04 2011-05-02 Mastercard International Inc Sistema y metodo para realizar una transaccion de reembolso en tiempo real por medio del apalancamiento de una red de pago.
US20100082420A1 (en) * 2008-09-25 2010-04-01 Greg Trifiletti System and method for benefit notification
CN101930573A (zh) * 2009-06-26 2010-12-29 海南新生信息技术有限公司 一种远程营销规则管理系统
US20110093387A1 (en) * 2009-10-16 2011-04-21 Zack Fuerstenberg System and method for non-credit card billers to accept credit card payments
WO2012097404A1 (fr) * 2011-01-17 2012-07-26 Independent Transaction Solutions Pty Ltd Système et procédé pour effectuer une récompense financée par un commerçant
US20120197801A1 (en) * 2011-01-27 2012-08-02 Day Jimenez Merchant payment system and method for mobile phones

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080133351A1 (en) * 2006-10-24 2008-06-05 Brigette White Method and apparatus for reward messaging, discounting and redemption at the point of interaction
US20080103968A1 (en) * 2006-10-31 2008-05-01 Discover Financial Services Llc Redemption of Credit Card Rewards at a Point of Sale
US20130246273A1 (en) * 2012-03-16 2013-09-19 Visa International Service Association Systems and methods to generate a receipt for a transaction
US20140081733A1 (en) * 2012-09-16 2014-03-20 American Express Travel Related Services Company, Inc. System and method for rewarding in channel accomplishments
US20140156480A1 (en) * 2012-11-30 2014-06-05 Bank Of America Corporation Personal financial management payment allocation

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3192034A4 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017176365A1 (fr) * 2016-04-06 2017-10-12 Mastercard International Incorporated Procédé et système de promotions en temps réel
WO2017176362A1 (fr) * 2016-04-06 2017-10-12 Mastercard International Incorporated Procédé et système d'application de remise en temps réel
US10943251B2 (en) 2016-04-06 2021-03-09 Mastercard International Incorporated Method and system for real-time rebate application
US20230141912A1 (en) * 2020-07-06 2023-05-11 Block, Inc. Peer-to-peer transfer of a stored value

Also Published As

Publication number Publication date
CA2958551A1 (fr) 2016-02-25
JP2017528822A (ja) 2017-09-28
AU2015305524A1 (en) 2017-03-16
BR112017003415A2 (pt) 2017-11-28
RU2017109095A3 (fr) 2018-09-21
EP3192034A1 (fr) 2017-07-19
RU2017109095A (ru) 2018-09-21
CN107077677A (zh) 2017-08-18
EP3192034A4 (fr) 2018-01-10

Similar Documents

Publication Publication Date Title
US20150112781A1 (en) Method and System for Processing of a Real-Time Rebate at Transaction Authorization
AU2019257460A1 (en) Method and system for processing of a real-time rebate at transaction authorization
WO2016028889A1 (fr) Procédé et système de traitement d'un rabais en temps réel lors d'une autorisation de transaction
US20140136309A1 (en) System and method for optimizing card usage in a payment transaction
US9218599B1 (en) Method and system for automatic chargeback reimbursement for product returns
US11263655B2 (en) Method and system for post authorization payment of transactions using loyalty points
US20190251542A1 (en) Method and system for instant credit issuance
US11023873B1 (en) Resources for peer-to-peer messaging
US20150294413A1 (en) Method and system for assuring currency exchange rates
US20160019572A1 (en) Method and system for efficiently distributing coupons
AU2018201269A1 (en) Method and system for allowing time-based, incremental point acceleration
US20170083897A1 (en) Mobile purchase rewards
US20150088643A1 (en) Method and system for linking social data instantaneously to purchase transactions
WO2019035821A1 (fr) Système, procédé et appareil permettant de fournir un compte de crédit plafonné associé à un compte de débit
US20150196845A1 (en) Method and system for providing social game use with financial card transactions
US20150310475A1 (en) Method and system for predicting coupon redemption
US11074602B2 (en) Method and system for card link filtering
US20220101331A1 (en) Systems and methods for executing parallel electronic transactions
US20140244376A1 (en) System and method for facilitating off-peak sales using a payment card network
AU2021236576A1 (en) Method and system for card link filtering
US20150242876A1 (en) Method and system for providing an investment fund for consumer rewards
AU2014337530A1 (en) Method and system for card link filtering

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15833649

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2958551

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2017510295

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015833649

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015833649

Country of ref document: EP

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112017003415

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2015305524

Country of ref document: AU

Date of ref document: 20150819

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: A201702504

Country of ref document: UA

ENP Entry into the national phase

Ref document number: 2017109095

Country of ref document: RU

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 112017003415

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20170221