WO2021101438A1 - Un système de rabais pour générer une valeur de rabais et un procédé associé - Google Patents

Un système de rabais pour générer une valeur de rabais et un procédé associé Download PDF

Info

Publication number
WO2021101438A1
WO2021101438A1 PCT/SG2020/050594 SG2020050594W WO2021101438A1 WO 2021101438 A1 WO2021101438 A1 WO 2021101438A1 SG 2020050594 W SG2020050594 W SG 2020050594W WO 2021101438 A1 WO2021101438 A1 WO 2021101438A1
Authority
WO
WIPO (PCT)
Prior art keywords
rebate
value
app
consumer
stored
Prior art date
Application number
PCT/SG2020/050594
Other languages
English (en)
Inventor
Maojie FOO
Original Assignee
Whalesave Pte. Ltd.
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
Application filed by Whalesave Pte. Ltd. filed Critical Whalesave Pte. Ltd.
Publication of WO2021101438A1 publication Critical patent/WO2021101438A1/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
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems
    • G06Q20/208—Input by product or record sensing, e.g. weighing or scanner processing
    • 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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/326—Payment applications installed on the mobile devices
    • G06Q20/3267—In-app payments
    • 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

Definitions

  • the present invention relates to a rebate system for generating a rebate value and a method thereof.
  • In-app purchasing refers to the buying of goods and services from inside the app.
  • a game app may offer the user the ability to skip a particularly difficult level for a fee or the owner may provide consumers with the ability to view premium content that is behind a pay- wall.
  • Consumers making purchases through an app may stay within the app to make the purchase or may be directed to another platform, which can be an app or a website, to complete the transaction for the purchase.
  • the app may offer a rebate on the product or service purchased.
  • a rebate is an amount paid to the consumer by way of a reduction, return, or refund of what has already been paid or contributed. It is common for businesses to use rebates primarily as incentives or supplements to product sales. However, most apps do not provide a form of rebate for in-app purchases. One of the reasons is that most of these purchases are one-off transactions and rebates received within one app is not transferable for use on another app. Most businesses and developers of applications therefore do not consider rebate as a form of marketing tool to attract consumers.
  • the present invention provides to a method for generating a rebate value by a rebate system when purchasing an in-app product in one of a plurality of applications hosted by one or more merchant servers in communication with the rebate system, the method includes receiving a consumer identifier from a consumer device, receiving an application identifier of the one of the plurality of applications, obtaining a product identifier of the in-app product, retrieving the rebate value from the rebate system based on the product identifier, associating the rebate value to the consumer identifier, and storing the rebate value in the rebate system as a stored rebate value.
  • the method may further include receiving a purchase value of another in-app product in any one of the plurality of applications and offsetting the stored rebate value from the purchase value of the another in-app product.
  • associating the rebate value to the consumer identifier may include retrieving a rebate e-wallet based on the consumer identifier, and such that the storing the rebate value in the rebate system may include storing the stored rebate value in the rebate e -wallet.
  • the method may further include converting the rebate value to a currency and storing the rebate value in the currency.
  • the method may further include converting the stored rebate value in the currency to a local currency used by one of the plurality of applications before offsetting the stored rebate value from a purchase value of the in-app product.
  • the present invention provides a rebate system for generating a rebate value
  • the rebate system is configured to communicate with a plurality of merchant servers, each hosting a plurality of applications, such that each of the plurality of application has a plurality of in-app products
  • rebate system comprising a processor, and a memory in communication with the processor for storing instructions executable by the process, such that the processor is configured to receive a consumer identifier from a consumer device, receive an application identifier of the one of the plurality of applications, obtain a product identifier of an in-app product, retrieve the rebate value from the rebate system based on the product identifier, associate the rebate value to the consumer identifier, and store the rebate value in the rebate system as a stored rebate value.
  • the processor may be configured to receive a purchase value of another in-app product in any one of the plurality of applications and offset the stored rebate value from the purchase value of the another in-app product.
  • the processor may be configured to retrieve a rebate e-wallet based on the consumer identifier, and store the stored rebate value in the rebate e-wallet.
  • the processor may be configured to convert the rebate value to a currency, such that the rebate value is stored in the currency.
  • the processor may be configured to convert the stored rebate value in the currency to a local currency used by one of the plurality of applications before offsetting the stored rebate value from a purchase value of the in-app product.
  • a non-transitory computer readable storage medium comprising instructions, such that the instructions, when executed by a processor in a rebate system, cause the rebate system to generate a rebate value, such that the rebate system is configured to communicate with a plurality of merchant servers, each hosting a plurality of applications, wherein each of the plurality of application has a plurality of in-app products, and such that the processor is configured to receive a consumer identifier from a consumer device, receive an application identifier of the one of the plurality of applications, obtain a product identifier of an in-app product, retrieve the rebate value from the rebate system based on the product identifier, associate the rebate value to the consumer identifier, and store the rebate value in the rebate system as a stored rebate value.
  • Fig. 1 shows an exemplary embodiment of a rebate system for generating a rebate value.
  • Fig. 2 shows an exemplary embodiment of a purchase interface in the rebate app for purchasing the in-app product.
  • FIG. 3 shows a flow diagram of an exemplary method for generating a rebate value.
  • Fig. 4A and Fig. 4B shows a flow diagram of an exemplary method of generating a rebate value.
  • Fig. 1 shows an exemplary embodiment of a rebate system 10 for generating a rebate value.
  • Rebate system 10 may include a rebate server 100 operated and maintained by a rebate service provider.
  • Rebate server 100 may be configured to communicate with a merchant server 200 or a plurality of merchant servers 200 operated by one or more merchants to provide goods and/or services.
  • Merchant server 200 is configured to host a merchant application (“app”) that provides the goods and/or services.
  • a consumer may view the product (“in -app product”) using the merchant app downloaded onto a consumer device 300, e.g. a mobile phone, tablet, laptop, which may be configured to communicate with the merchant server 200.
  • Rebate server 100 may be configured to host a rebate app, which may be downloaded onto the consumer device 300.
  • Consumer device 300 may be configured to communicate with the rebate server 100 directly. Consumer device 300 may access the merchant app via the rebate app.
  • Rebate server 100 may be configured to communicate with a rebate database to retrieve and store data, e.g. consumer identifier, consumer details, rebate value of in-app products, stored rebate value, etc.
  • Merchant server 200 may be configured to communicate with a merchant database to retrieve and store data, e.g. consumer identifier, consumer details, in-app product identifiers, purchase value of in-app product, etc.
  • Rebate server 100, the merchant server 200 and the consumer device 300 may communicate with each other via a payment network 12.
  • the consumer may see and like an in- app product in the merchant app. Instead of purchasing the in-app product directly in the merchant app, the consumer may purchase the in-app product via the rebate app to obtain the rebate value. Consumer may access the rebate app to search for merchant app. Upon finding the merchant app via the rebate app, the consumer may search for and purchase the in-app product.
  • Rebate server 100 may be configured to receive payment from the consumer, e.g. to top up wallet value, to pay for the in-app product. Rebate server 100 may be configured to notify the merchant server 200 when the purchase is successful so that the merchant server 200 may disburse the in-app product to the consumer.
  • a merchant app may include a game app, a shopping app, etc.
  • Rebate server 100 may generate the rebate value based on the purchase value of the in-app product and store the rebate value in the rebate database.
  • Rebate value may be a percentage of the purchase value as pre-arranged with the merchant.
  • Rebate server may include a consumer’s electronic wallet (“e-wallet”) and rebate e-wallet stored in the rebate server.
  • Fig. 2 shows an exemplary embodiment of a purchase interface 320 in the rebate app for purchasing the in-app product.
  • Consumer may enter his/her consumer identifier, e.g. username, email address, user ID in the username box 322.
  • Consumer server 100 may verify the consumer identifier to validate that the consumer to be a user of the rebate app.
  • Consumer may pre-register as a user of the rebate app to provide consumer identifier, i.e. customer ID, and other data, e.g. financial data.
  • Purchase interface 320 may include a product selection section 324 where a plurality of in-app product buttons 324B representing the plurality of in- app products are being displayed for the consumer to view and select.
  • the purchase value of the in-app product is displayed in purchase value section 324P and the rebate amount or a rebate percentage of the purchase value of the in-app product is displayed in a rebate section 324R.
  • the consumer Before the consumer decides to purchase an in-app product, the consumer is able to know about the purchase value of the in-app product and the rebate value that can be received when purchasing the in-app product.
  • the consumer may tap on the in-app product button 324B of the in-app product to select it.
  • Rebate app may indicate that the in-app product button 324B has been selected. For example, the colour of the in-app product button may change as shown in Fig. 2 or a sign may be displayed on or adjacent thereto.
  • Purchase interface 320 may include a total purchase value section 324TP to show the consumer the total purchase value of in-app product selected.
  • the purchase interface 320 may include a total rebate section 324TR.
  • the rebate app may be configured to calculate the total purchase value and the total rebate value of the selected in-app products and the total purchase value and the total rebate value may be shown in the total purchase value section 324TP and the total rebate section 324TR respectively.
  • Purchase interface 320 may include a stored rebate value section 324W to display a stored rebate value that the consumer has in his/her rebate e-wallet. Consumer may view the stored rebate value that he/she has in the stored rebate value section 324W.
  • Rebate e-wallet stores the stored rebate value of the consumer.
  • Purchase interface 320 may display a prompt to ask the consumer if he/she wishes to use the stored rebate value for the purchase.
  • Purchase interface 320 may include a rebate usage selection box 324S configured to accept a rebate instruction from the consumer whether to use the stored rebate value for the purchase. Consumer may choose whether to use the stored rebate value for the purchase by selecting his/her choice in the rebate usage selection box 324S.
  • Rebate usage selection box 324S may include a yes/no option box, a switch, a dialog box, etc.
  • Purchase interface 320 may display the final total purchase value in a final total purchase value section 324F.
  • the consumer may view the final total purchase value to be paid for the in-app purchase taking into consideration the use of the stored rebate value for the purchase. If the consumer indicates that the stored rebate value is to be used for the purchase, the rebate app may calculate the final total purchase value by deducting the stored rebate value from the total purchase value. Otherwise, the rebate app may display the final total purchase value as is.
  • Purchase interface 320 may include a purchase button 324U configured to accept a purchase instruction to purchase the in-app product. Consumer may proceed to purchase the in-app purchase by tapping on the purchase button 324U.
  • the rebate server 100 may be configured deduct the final total purchase value from the consumer’s e-wallet stored in the rebate server 100. E-wallet stores the wallet value of the consumer. Once the deduction is completed, the rebate server 100 may instruct the merchant server 200 to disburse the in-app product to the consumer and the total rebate value may be stored into the consumer’s rebate e-wallet in the rebate server 100.
  • the consumer may access the merchant app directly to purchase the in-app product.
  • a similar purchase interface 320 may be shown in the merchant app.
  • the consumer may enter his/her consumer identifier, e.g. username, email address, user ID in the merchant app.
  • Merchant server 200 may verify the consumer identifier to validate that the consumer to be a user of the merchant app.
  • Consumer may browse the plurality of in-app products in the merchant app and select one or more of the plurality of in-app products.
  • the merchant app is configured to display the availability and the purchase value of each of the plurality of in-app products.
  • the merchant app is configured to retrieve from the rebate server 100 and display the rebate value available for each of the plurality of in-app products.
  • Merchant app may also be configured to calculate and display the total purchase value of the selected in-app products.
  • Merchant app may be configured to retrieve the stored rebate value and display it on the consumer device 300. Once the one or more of the in-app products is selected, the merchant app may display the total purchase value and the total rebate value of the selected in-app products. Similarly, the merchant app may be configured to display a prompt to ask the consumer if he/she wishes to use the stored rebate value for the purchase. Depending on the decision of the consumer, the merchant app may be configured to display the final total purchase value, which includes the deduction of the stored rebate value. Merchant app may be configured to display the purchase button 324U.
  • the merchant server 200 may transmit the purchase data, e.g. a purchase instruction, product identifier of the in-app product, rebate instruction, etc, to the rebate server 100.
  • Rebate server 100 may, if instructed, deduct the stored rebate value from the total purchase value and deduct the total purchase value from the wallet value.
  • the rebate server 100 may be configured to transmit a payment confirmation to the merchant server 200 so that the in-app product may be disbursed to the consumer.
  • the stored rebate value may be deducted from the e-wallet and the total rebate value may be stored into the consumer’s rebate e -wallet in the rebate database.
  • Method 1000 may be carried out by the rebate system 10 when the consumer purchases an in-app product in one of the plurality of applications hosted by one or more merchant servers 200 in communication with the rebate system 10.
  • Method may include receiving a consumer identifier from a consumer device 300 in block 1100, receiving an application identifier of the one of the plurality of applications in block 1200, obtaining a product identifier of the in-app product in block 1300, retrieving the rebate value from the rebate system 10 based on the product identifier in block 1400, associating the rebate value to the consumer identifier in block 1500, and storing the rebate value in the rebate system 10 as a stored rebate value in block 1600.
  • the rebate value is applicable to the purchase of an in-app product in any one of the plurality of applications.
  • Rebate system 10 is able to consolidate and store a consumer’s rebate value to be offset for future purchases of in- app products across the plurality of merchant applications.
  • the stored rebate value received from one merchant application may be “transferred” to another merchant application.
  • the rebate system 10 is able to provide an easy way for consumers to review the rebates they have accumulated from various merchant applications. For the merchants, they are able to market and promote their products in the merchant apps while using the rebates as incentives and are able to manage the rebate separately from the merchant applications.
  • Fig. 4A and Fig. 4B shows a flow diagram of an exemplary method 2000 of generating a rebate value.
  • Method may be carried out at the merchant server 200.
  • the merchant server 200 may receive a consumer identifier via the purchase interface 320 in the merchant app on the consumer device 300.
  • Merchant server 200 may be configured to verify, based on the consumer identifier, if the consumer is an existing user in block 2110.
  • Merchant server 200 may be configured to notify the consumer via the consumer device 300 if the consumer identifier is not found in the merchant server 200 in block 2120.
  • Merchant server 200 may direct the consumer to a registration page to register as a user of the merchant app.
  • Merchant server 200 may be configured to receive an application identifier of the merchant app to identify the merchant app that the consumer has accessed. Merchant server 200 may be configured to receive the product identifier in block 2130 via the merchant app. Upon receiving the product identifier, the merchant server 200 may verify the product database if the product identifier exists in the product database in block 2140. If the product identifier does not exist, it means that the in-app product is not available, and the merchant server 200 may notify the consumer accordingly via the merchant app in block 2150. If the product identifier exists, the merchant server 200 may retrieve the rebate value of the in-app product of the product identifier from the rebate server 100 in block 2160.
  • the merchant server 200 may transmit the product identifier to the rebate server 100 to retrieve the rebate value.
  • Rebate server 100 upon receiving the product identifier may retrieve the rebate value associated to the product identifier in block 2160 and transmit the rebate value to the merchant server 200.
  • the rebate server 100 may retrieve the consumer rebate e-wallet and the stored rebate value associated to the consumer from the rebate database at block 2170 and transmit the stored rebate value to the merchant server 200.
  • Merchant server 200 may receive the stored rebate value.
  • Merchant server 200 may retrieve the purchase value of the in-app product and display it on the purchase interface 320.
  • the merchant server 200 may receive the wallet value from the rebate server 100 and display it in the purchase interface 320.
  • Merchant server 200 may determine if the consumer rebate e-wallet has a stored rebate value in block 2200. If there is a stored rebate value, the merchant server 200 may prompt the consumer whether to use the stored rebate value in block 2210. Merchant server 200 may receive a rebate instruction from the merchant app on the consumer device 300 whether the consumer uses the stored rebate value in block 2220. If the consumer does not choose to use the stored rebate value, the merchant server 200 may receive a rebate instruction not to use the stored rebate value. Consequently, the merchant server 200 may calculate the final total purchase value of the in-app product(s) in block 2230.
  • the merchant server 200 may generate the final total purchase value without deducting the stored rebate value if the rebate instruction is not to use the stored rebate value. If the consumer chooses to use the stored rebate value, the merchant server 200 may receive a rebate instruction to use the stored rebate value. Consequently, the merchant server 200 may calculate the final total purchase value after deducting the stored rebate value from the total purchase value in block 2240. Merchant server 200 may determine if there is sufficient wallet value or stored rebate value for the purchase. Merchant server 200 may determine if the stored rebate value is more than the purchase value. If the stored rebate value is not more than the final total purchase value, the merchant server 200 may verify the wallet value to determine if the wallet value is equal or more than the final total purchase value, i.e. after deducting any stored rebate value. If the wallet value is lower than the total final purchase value, the merchant server 200 may prompt the consumer to top up the wallet value.
  • Merchant server 200 may activate the rebate app on the consumer device 300 for the top up or activate the top up via the rebate server 100.
  • Rebate server 100 may verify the IP address on the consumer device 300 for the top up. If the IP address does not match the stored IP address of the consumer, the rebate server 100 may transmit a verification notification, e.g. an email, to the consumer’s registered email address to request the consumer to verify the new IP address. If the consumer verifies the new IP address, the rebate server 100 allows the top up of the wallet value with the amount as chosen by the consumer. Otherwise, the rebate server 100 denies the top up and notifies the consumer via the consumer device 300. The above process may be carried out on the merchant app as well.
  • the merchant server 200 may proceed to process the payment in block 2250. If the payment is not possible due to insufficient wallet value or stored value, the merchant server 200 may notify the consumer via the merchant app in block 2270. If payment is successful, the merchant server 200 may transmit total rebate value to the rebate server 100 to be stored in the consumer’s rebate e- wallet in the rebate server 100 in block 2280. Rebate server 100 may associate the rebate value to the consumer identifier. Rebate server 100 may retrieve the rebate e-wallet based on the consumer identifier and store the rebate value in the rebate e-wallet as stored rebate value.
  • the merchant server 200 may disburse the product to the consumer by discharging the product identifier to the merchant app of the consumer device 300 in block 2290.
  • the merchant server 200 may transmit the final total purchase value to the rebate server 100 so that the rebate server 100 may deduct the wallet value or the stored rebate value from the consumer wallet or rebate wallet respectively.
  • the consumer may access the rebate system 10 via the rebate app on the consumer device 300.
  • the method for generating the rebate value carried out at the rebate server 100 is similar to method 2000 described above.
  • the rebate server 100 may transmit the consumer identifier to the merchant server 200 to be verified at block 2110. If the consumer identifier does not exist, the rebate server 100 may receive a notification from the merchant server 200 and the rebate server 100 may transmit the notification to the consumer. If the rebate server 100 receives a notification that the consumer identifier exists, the rebate server 100 may be configured to transmit an application identifier of the merchant app to identify the merchant app that the consumer has accessed.
  • the rebate server 100 may transmit the product identifier to the merchant server 200 to be verified at block 2140. If the product identifier does not exist in the product database, the rebate server 100 may receive a notification from the merchant server 200 and the rebate server 100 may transmit the information to the consumer to inform the consumer that the product does not exist. If the product identifier exists, the rebate server 100 may receive the confirmation from the merchant server 200 and retrieve the rebate value based on the product identifier from the rebate database. Rebate server 100 may display the rebate value of the in-app product in the purchase interface 320. Rebate server 100 may also retrieve the stored rebate value and the wallet value from the rebate database based on the consumer identifier.
  • Rebate server 100 may receive the purchase value of the in-app product from the merchant server 200 and display it on the consumer device 300. Rebate server 100 may determine if the rebate e-wallet has stored rebate value. If there is stored rebate value, the merchant server 200 may prompt the consumer whether to use the stored rebate value in purchase interface 320 on the rebate app. If the consumer chooses not to use the stored rebate value, the rebate server 100 may receive a rebate instruction from the rebate app and calculate the final total purchase value of the in-app product(s) without deducting the stored rebate value. If the consumer chooses to use the stored rebate value, the rebate server 100 may receive a rebate instruction to use the stored rebate value and calculate the final total purchase value after deducting the stored rebate value from the total purchase value.
  • Rebate server 100 may determine if there is sufficient wallet value or stored rebate value for the purchase as described above and prompt the consumer to top up the wallet value if it is insufficient. Similarly, the rebate server 100 may verify the purchase of the in-app product as described above. Once the rebate server 100 determines that there is sufficient wallet value or stored rebate value, the rebate server 100 may proceed to process the payment. If the payment is not possible due to insufficient wallet value or stored value, the rebate server 100 may notify the consumer via the rebate app. If payment is successful, the rebate server 100 may store the total rebate value to the rebate database in the consumer’s rebate e-wallet.
  • the rebate server 100 may transmit the payment confirmation to the merchant server 200 for the merchant server 200 to disburse the product to the consumer by discharging the product identifier to the merchant app of the consumer device 300 in block 2290.
  • the rebate server 100 may deduct the wallet value or the stored rebate value from the consumer wallet or rebate wallet respectively. Once the purchase is successful, the rebate server 100 may transfer a percentage of the final total purchase value to the merchant server 200.
  • Rebate server 100 may withhold the stored rebate value from being stored in the consumer’s rebate e-wallet.
  • Rebate server 100 may be configured to verify that a plurality of conditions are met by the merchant server 200 before the total rebate value may be stored in the rebate e-wallet of the consumer.
  • Rebate server 100 may be configured to validate the purchase.
  • the rebate server 100 may store the total rebate value into the consumer’s rebate e-wallet.
  • the merchant may have cancellation, return, and exchange policies and allows the purchase of the in-app product to be cancelled, the in-app product to be returned or exchanged with another in-app product of a different purchase value.
  • the rebate server 100 may only store the total rebate value to the rebate e-wallet after the expiry of such period or time, e.g. 60 days, 75 days, etc.
  • the rebate server 100 may be configured to withhold the total rebate value to be credited until the payment is cleared by the credit card system.
  • Rebate system 10 may be configured to allow the stored rebate value to be converted to a cashback credit, or a credit amount that may be encashed into money. Rebate system 10 may allow the conversion after a pre-determined period of time, e.g. 60 days.
  • the rebate system 10 may store the rebate value in a single currency that is commonly used, e.g. US dollar.
  • the rebate system 10 may convert the rebate value to the common currency to be stored in the rebate e-wallet based on current exchange rates at the time of storage.
  • the rebate system 10 may convert the stored rebate value in the common currency to the local currency before the deduction. In this way, the rebate value may be used across the plurality of merchant apps of varying currencies.
  • the consumer may use the stored rebate value to offset the purchase value of the another in-app product.
  • Merchant server 200 upon receiving the product identifier, may receive the purchase value of the another in-app product and, if the consumer chooses, offset the stored rebate value from the purchase value.
  • Merchant server 200 may convert the stored rebate value in the common currency to a local currency used by one of the plurality of merchant apps before offsetting the stored rebate value from the purchase value of the in-app product.
  • Rebate server 100 may be configured to authenticate the plurality of merchant servers 200 when sending data to the plurality of merchant servers 200.
  • Rebate server 100 may generate a secret key.
  • Rebate server 100 may receive a link from one of the plurality of merchant servers 200 to send the data.
  • the link may include a webhook URL from the merchant server 200.
  • Rebate server 100 may be configured to transmit the secret key together with the data via the link so that the merchant server 200 knows that the data is transmitted from the rebate server 100.
  • Merchant server 200 may revoke the secret key and re-generate a new secret key to be transmitted to the rebate server 100 so that the rebate server 100 may transmit the new secret key with the data to the merchant server 200.
  • the present invention relates to a rebate system for generating a rebate value and a method thereof generally as herein described, with reference to and/or illustrated in the accompanying drawings.

Abstract

La présente invention concerne un système de rabais destiné à générer une valeur de rabais, le système de rabais étant configuré pour communiquer avec une pluralité de serveurs de commerçant, chacun hébergeant une pluralité d'applications, de sorte que chacune de la pluralité d'applications comporte une pluralité de produits in-app, et le système de rabais comprenant un processeur et une mémoire en communication avec le processeur pour stocker des instructions exécutables par le processeur, de sorte que le processeur est configuré pour recevoir un identificateur de consommateur provenant d'un dispositif de consommateur, recevoir un identificateur d'application provenant de l'une de la pluralité d'applications, obtenir un identificateur de produit d'un produit in-app, récupérer la valeur de rabais du système de rabais sur la base de l'identificateur de produit, associer la valeur de rabais à l'identificateur de consommateur, et stocker la valeur de rabais dans le système de rabais en tant que valeur de rabais stockée.
PCT/SG2020/050594 2019-11-21 2020-10-16 Un système de rabais pour générer une valeur de rabais et un procédé associé WO2021101438A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
SG10201910996P 2019-11-21
SG10201910996P 2019-11-21

Publications (1)

Publication Number Publication Date
WO2021101438A1 true WO2021101438A1 (fr) 2021-05-27

Family

ID=75981752

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SG2020/050594 WO2021101438A1 (fr) 2019-11-21 2020-10-16 Un système de rabais pour générer une valeur de rabais et un procédé associé

Country Status (1)

Country Link
WO (1) WO2021101438A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120265595A1 (en) * 2011-04-14 2012-10-18 Fiksu, Inc. Mobile digital media download incentive management through multiple user action tracking
US20150324829A1 (en) * 2014-05-09 2015-11-12 Yvolver, Inc. Systems and methods for operating a loyalty platform for games and internet-connected applications
US20160210626A1 (en) * 2015-01-19 2016-07-21 Royal Bank Of Canada Secure processing of electronic payments
CN106203881A (zh) * 2016-07-20 2016-12-07 武汉斗鱼网络科技有限公司 一种应用内购买的订单处理系统及方法
US20170017977A1 (en) * 2014-03-07 2017-01-19 White Shoe Media, Inc. Dynamic content and pricing

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120265595A1 (en) * 2011-04-14 2012-10-18 Fiksu, Inc. Mobile digital media download incentive management through multiple user action tracking
US20170017977A1 (en) * 2014-03-07 2017-01-19 White Shoe Media, Inc. Dynamic content and pricing
US20150324829A1 (en) * 2014-05-09 2015-11-12 Yvolver, Inc. Systems and methods for operating a loyalty platform for games and internet-connected applications
US20160210626A1 (en) * 2015-01-19 2016-07-21 Royal Bank Of Canada Secure processing of electronic payments
CN106203881A (zh) * 2016-07-20 2016-12-07 武汉斗鱼网络科技有限公司 一种应用内购买的订单处理系统及方法

Similar Documents

Publication Publication Date Title
US10825016B2 (en) Electronic bearer bond online transaction and card system and method thereof
AU2013277468B2 (en) Prepaid wallet for merchants
US11182758B2 (en) Rapid checkout after payment
US20130080321A1 (en) Method for Recipient Orientated Financial Services
US20140032412A1 (en) Payment system and method for vending machine using mobile terminal and storage medium storing program for implementing the method
US20130159077A1 (en) Local affiliate marketing
KR20170142374A (ko) 가상화폐를 이용한 송금 시스템 및 방법
KR102094101B1 (ko) 연동형 디지털화폐 시스템 및 그 방법, 전용 디지털화폐와 연동되는 전자지갑 간 결제 시스템 및 그 방법
KR101781408B1 (ko) 택스 리펀드 통합 관리 방법 및 그 시스템
EP2817778A1 (fr) Exécution sélective de transactions de commerce électronique basées sur de l'argent liquide
CN116171450A (zh) 使用数字资产的电子金融交易系统及该系统的支付方法
KR20000077102A (ko) 선불카드를 이용한 전자 상거래 시스템
JP2018133107A (ja) 購買支援装置、購買支援システム、購買支援方法、購買支援プログラム
US7103571B2 (en) Electronic settlement system using prepaid type electronic money
US10242354B2 (en) Selectively providing cash-based e-commerce transactions
JP6556335B2 (ja) デジタルコンテンツを提供する方法、サーバ及びシステム
KR100897498B1 (ko) 유비쿼터스 환경에서의 통합형 금융 서비스 시스템
WO2021101438A1 (fr) Un système de rabais pour générer une valeur de rabais et un procédé associé
US10558995B2 (en) Value management system
KR20090120129A (ko) 가상지갑의 충전 및 결제시스템 및 그 방법
KR20120137534A (ko) 쿠폰 판매 관리 시스템 및 방법
JP2022032781A (ja) プログラム、電子的価値管理装置及び電子的価値管理方法
WO2013040696A1 (fr) Procédé de prestation de services financiers ciblant le destinataire
KR20070040182A (ko) 은행에서 발행하는 상품권 운용 시스템과 이를 위한 상품권운용 장치 및 기록매체
KR20090013247A (ko) 보안결제 서비스에서의 선 할인 서비스 제공 시스템 및 그 제공 방법

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: 20889251

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 31/08/2022)

122 Ep: pct application non-entry in european phase

Ref document number: 20889251

Country of ref document: EP

Kind code of ref document: A1