Patent Application
20170132653
This application is a U.S. National Stage filing under 35 U.S.C. §119, based on and claiming benefit of and priority to SG Patent Application No. 10201509121Q filed Nov. 5, 2015.
The following discloses a method and system for accumulating and redeeming rewards using digital wallets.
A digital wallet is a software component that allows a customer to make an electronic payment with a financial instrument such as a credit card or a bank account. A server-side digital wallet is one that the digital wallet service provider creates and maintains for a customer on its servers. These types of digital wallets are gaining popularity among customers due to the security and convenience they provide. As all the required information such as shipping address, billing address, payment methods (including credit card numbers, expiry dates, and security numbers) are already stored in the organization's server, the customer is relieved of the mundane and sometimes arduous task of keying in this information when making payment, thereby enhancing the overall purchasing experience.
It is commonplace for credit cards to have rewards and redemption schemes. These schemes are in place to incentivize customers to use the credit cards to make payment, and in return be awarded rewards points that can be redeemed for a monetary value. A digital wallet is usually associated with multiple credit cards or other electronic payment instruments such as debit cards, prepaid cards and store loyalty cards. Usually, the payment cards in a digital wallet are issued by a single issuer such as a bank (e.g. Citibank) or a financial services company (e.g. American Express Company). Therefore, to take advantage of the various incentives across different banks, financial services companies and merchants, a customer would normally have multiple digital wallets, each digital wallet being associated with payment cards issued by a single issuer.
However, the drawback is that as the rewards points system for each payment card in a digital wallet is bank-specific or even payment card-specific, customers are unable to utilize the rewards points issued by a particular bank, for a purchase with a payment card issued by another bank. The result is that a customer ends up with rewards points across many credit cards, but is unable to consolidate the disparate rewards points for redemption in a coherent manner.
Thus, there is a want for a method and system which standardizes and aggregates disparate rewards points accumulated for various digital wallets into a single rewards points system. The points in this single rewards points system can be redeemed with a purchase with any one of the customer's digital wallets and with any participating merchant. Furthermore, other desirable features and characteristics will become apparent from the subsequent detailed description and the appended claims, taken in conjunction with the accompanying drawings and this background of the disclosure.
According to a first aspect of the invention, a computer-implemented method for accumulating rewards for redemption is described, the method comprising the steps of storing at a server, a first digital wallet, the first digital wallet associated with a first standard rewards value and storing at least one payment card number for a payment card issued by a first issuer, the first issuer having a first issuer server; receiving at the server, a rewards value from the first issuer server; applying with the server, a normalizing algorithm to the rewards value from the first issuer server to obtain a first normalized rewards value; and updating with the server, the first standard rewards value by adding the first normalized rewards value to the first standard rewards value.
Preferably, the computer-implemented method further comprises the steps of receiving at the server, instructions that payment is to be made with the first digital wallet; sending from the sever, the first standard rewards value to a customer device for display; receiving at the server, instructions from the customer device that a portion or an entirety of the first standard rewards value has been selected; and providing from the server, the selected portion or the selected entirety of the first standard rewards value to a merchant server for redemption.
Preferably, the computer-implemented method further comprises the steps of storing at the server, a second digital wallet, the second digital wallet associated with a second standard rewards value and storing at least one payment card number for a payment card issued by a second issuer, the second issuer having a second issuer server; receiving at the server, a rewards value from the second issuer server; applying with the server, the normalizing algorithm to the rewards value from the second issuer server to obtain a second normalized rewards value; updating with the server, the second standard rewards value by adding the second normalized rewards value to the second standard rewards value; and adding with the server, the first standard rewards value and the second standard rewards value to obtain a consolidated standard rewards value.
Preferably, the computer implemented method further comprises the steps of sending from the server, the consolidated standard rewards value to the customer device for display; receiving at the server, instructions from the customer device that a portion or an entirety of the consolidated standard rewards value has been selected; and providing from the server, the selected portion or the selected entirety of the consolidated standard rewards value to the merchant server for redemption.
Preferably, the step of applying the normalizing algorithm comprises scaling the rewards value from the first issuer server or the rewards value from the second issuer server by a predetermined factor, wherein the predetermined factor is correlated to a ratio between the dollar value of the rewards value from the first issuer server and the dollar value of the rewards value from the second issuer server.
Preferably, the step of receiving the rewards value from the first issuer server is via an application programming interface (API).
Preferably, the step of receiving the rewards value from the second issuer server is via another API.
Preferably, the first standard rewards value is stored in the first digital wallet and the second standard rewards value is stored in the second digital wallet.
Preferably, the merchant server is associated with a merchant category code such that the selected portion or the selected entirety of the first standard rewards value or the selected portion or the selected entirety of the consolidated standard rewards value can be redeemed.
According to a second aspect of the invention, a system for accumulating rewards for redemption is described, the system for accumulating rewards for redemption comprising at least one server configured to store a first digital wallet, the first digital wallet associated with a first standard rewards value, and storing at least one payment card number for a payment card issued by a first issuer, the first issuer having a first issuer server; receive a rewards value from the first issuer server; apply a normalizing algorithm to the rewards value from the first issuer server to obtain a first normalized rewards value; and update the first standard rewards value by adding the first normalized rewards value to the first standard rewards value.
Preferably, the at least one server is further configured to receive instructions that payment is to be made with the first digital wallet; send the first standard rewards value to a customer device for display; receive instructions from the customer device that a portion or an entirety of the first standard rewards value has been selected; and provide the selected portion or the selected entirety of the first standard rewards value to a merchant server for redemption.
Preferably, the at least one server is further configured to store a second digital wallet, the second digital wallet associated with a second standard rewards value, and storing at least one payment card number for a payment card issued by a second issuer, the second issuer having a second issuer server; receive a rewards value from the second issuer server; apply the normalizing algorithm to the rewards value from the second issuer server to obtain a second normalized rewards value; update the second standard rewards value by adding the second normalized rewards value to the second standard rewards value; and add the first standard rewards value and the second standard rewards value to obtain a consolidated standard rewards value.
Preferably, the at least one server is further configured to send the consolidated standard rewards value to the customer device for display; receive instructions from the customer device that a portion or an entirety of the consolidated standard rewards value has been selected; and provide the selected portion or the selected entirety of the consolidated standard rewards value to the merchant server for redemption.
Preferably, the normalizing algorithm comprises scaling the rewards value from the first issuer server or the rewards value from the second issuer server by a predetermined factor, wherein the predetermined factor is correlated to a ratio between the dollar value of the rewards value from the first issuer server and the dollar value of the rewards value from the second issuer server.
Preferably, the at least one server is further configured to receive the rewards value from the first issuer server via an application programming interface (API).
Preferably, the at least one server is further configured to receive the rewards value from the second issuer server via another API.
Preferably, the first standard rewards value is stored in the first digital wallet and the second standard rewards value is stored in the second digital wallet.
Preferably, the merchant server is associated with a merchant category code such that the selected portion or the selected entirety of the first standard rewards value or the selected portion or the selected entirety of the consolidated standard rewards value can be redeemed.
According to a third aspect of the invention, a computer program product for accumulating rewards for redemption is described, the computer program product embodied on a non-transitory computer readable storage medium comprising executable computer readable program code configured to, when executed on at least one processor, cause an apparatus or system to store a first digital wallet, the first digital wallet associated with a first standard rewards value, and storing at least one payment card number for a payment card issued by a first issuer, the first issuer having a first issuer server; receive a rewards value from the first issuer server; apply a normalizing algorithm to the rewards value from the first issuer server to obtain a first normalized rewards value; and update the first standard rewards value by adding the first normalized rewards value to the first standard rewards value.
Preferably, the computer readable program code is further configured to, when executed on at least one processor, cause an apparatus or system to receive instructions that payment is to be made with the first digital wallet; send the first standard rewards value to a customer device for display; receive instructions from the customer device that a portion or an entirety of the first standard rewards value has been selected; and provide the selected portion or the selected entirety of the first standard rewards value to a merchant server for redemption.
Preferably, the computer readable program code is further configured to, when executed on at least one processor, cause an apparatus or system to store a second digital wallet, the second digital wallet associated with a second standard rewards value, and storing at least one payment card number for a payment card issued by a second issuer, the second issuer having a second issuer server; receive a rewards value from the second issuer server; apply the normalizing algorithm to the rewards value from the second issuer server to obtain a second normalized rewards value; update the second standard rewards value by adding the second normalized rewards value to the second standard rewards value; and add the first standard rewards value and the second standard rewards value to obtain a consolidated standard rewards value.
Preferably, the computer readable program code is further configured to, when executed on at least one processor, cause an apparatus or system to send the consolidated standard rewards value to the customer device for display; receive instructions from the customer device that a portion or an entirety of the consolidated standard rewards value has been selected; and provide the selected portion or the selected entirety of the consolidated standard rewards value to the merchant server for redemption.
Preferably, the computer readable program code is further configured to, when executed on at least one processor, cause an apparatus or system to apply the normalizing algorithm by scaling the rewards value from the first issuer server or the rewards value from the second issuer server by a predetermined factor, wherein the predetermined factor is correlated to a ratio between the dollar value of the rewards value from the first issuer server and the dollar value of the rewards value from the second issuer server.
The accompanying figures, where like reference numerals refer to identical or functionally similar elements throughout the separate views and which together with the detailed description below are incorporated in and form part of the specification, serve to illustrate various embodiments, by way of example only, and to explain various principles and advantages in accordance with a present embodiment.
Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been depicted to scale. For example, the dimensions of some of the elements in the block diagrams or steps in the flowcharts may be exaggerated with respect to other elements to help improve understanding of the present embodiment.
The following detailed description is merely exemplary in nature and is not intended to limit the invention or the application and uses of the invention. Furthermore, there is no intention to be bound by any theory presented in the preceding background of the invention or the following detailed description. It is the intent of the preferred embodiments to disclose a method and system for standardizing and consolidating disparate rewards points accumulated for various financial instruments into a single rewards points system.
Currently, there exists no mechanism that allows customers to standardize and consolidate their rewards points accumulated for their various financial instruments. This results in customers being unable to utilize their rewards points freely.
Certain embodiments of the present invention seek to address the above challenges by disclosing a method and system that standardizes and aggregates disparate rewards points accumulated for various digital wallets into a single rewards points system. The points in this single rewards points system can be redeemed with a purchase from any of the customer's digital wallets and with any participating merchant. This is also known as an “open-loop points standard” in which the standardized points can be used across various issuers and merchants.
Certain embodiments of the present invention also seek to provide a secure ecosystem for rewards points to be passed from the issuer to the customer, and then onto the merchant for redemption. This is achieved by a server being placed intermediate between the issuers and merchants, the server implementing an open Application Programming Interface (API) based secure communication channel.
Also in system 100 is issuer 1 server 114, issuer 2 server 115, issuer 3 server 116 and issuer 4 server 117. Issuer 1 server 114 provides payment card 1134 to the customer. Issuer 2 server 115 provides payment card 2135 and payment card 3145 to the customer. Issuer 3 server 116 provides payment card 4136 to the customer. Issuer 4 server 117 provides payment card 5137 to the customer. Issuer 1 server 114 is managed by issuer 1, issuer 2 server 115 is managed by issuer 2, issuer 3 server 116 is managed by issuer 3 and issuer 4 server 117 is managed by issuer 4. Issuer 1, issuer 2, issuer 3 and issuer 4 can be any bank or financial services company. Service provider server 103 communicates with issuer 1 server 114 via an application programming interface (API) 1124. Service provider server 103 communicates with issuer 2 server 115 via an application programming interface (API) 2125. Service provider server 103 communicates with issuer 3 server 116 via an application programming interface (API) 3126. Service provider server 103 communicates with issuer 4 server 117 via an application programming interface (API) 4127.
Digital wallet 1104 is associated with payment card 1134, which may be a credit card, debit card or prepaid card, for example. In other words, payment card 1134 is provisioned onto digital wallet 1104. Payment card 1134 is issued by issuer 1. Digital wallet 1104 can store the card number (e.g. the primary account number or PAN) of payment card 1134. Digital wallet 2105 is associated with payment card 2135 and payment card 3145. In other words, payment card 2135 and payment card 3145 are provisioned onto digital wallet 2105. Payment card 2135 and payment card 3145 are issued by issuer 2. Digital wallet 2105 can store the card number of payment card 2135 and the card number of payment card 3145. Digital wallet 3106 is associated with payment card 4136 and payment card 5137. In other words, payment card 4136 and payment card 5137 are provisioned onto digital wallet 3106. Payment card 4136 is issued by issuer 3 while payment card 5137 is issued by issuer 4. Despite the fact that payment card 4136 and payment card 5137 are issued by different issuers, payment card 4136 and payment card 5137 can still be provisioned on the same digital wallet i.e. digital wallet 3106. This is because digital wallet 3106 can be an open wallet. Digital wallet 3106 can store the card number of payment card 4136 and the card number of payment card 5137. Although it is shown in this instance that a digital wallet is associated with one or two payment cards, this is for illustration purposes only and there no restriction on the number of payment cards a digital wallet can be associated with.
Digital wallet 1104 is associated with standard rewards value 107. Preferably, standard rewards value 107 is stored in digital wallet 1104. Alternatively, standard rewards value 107 can be stored in a customer account in service provider server 103 which digital wallet 1104 has access to. Digital wallet 2105 is associated with standard rewards value 108. Preferably, standard rewards value 108 is stored in digital wallet 2105. Alternatively, standard rewards value 108 can be stored in a customer account in service provider server 103 in which digital wallet 2105 has access to. Digital wallet 3106 is associated with standard rewards value 109. Preferably, standard rewards value 109 is stored in digital wallet 3106. Alternatively, standard rewards value 109 can be stored in a customer account in service provider server 103 in which digital wallet 3106 has access to. Service provider server 103 can read, and write to update standard rewards value 107, standard rewards value 108 and standard rewards value 109. Standard rewards value 107, standard rewards value 108 and standard rewards value 109 can be a whole number.
The following description of service provider server 103 is provided by way of example only and is not intended to be limiting. Service provider server 103 may be a server or comprise a plurality of servers. As shown in
The secondary memory 210 may include, for example, a storage drive 212, which may be a hard disk drive, a solid state drive or a hybrid drive and/or a removable storage drive 214, which may include a magnetic tape drive, an optical disk drive, a solid state storage drive (such as a USB flash drive, a flash memory device, a solid state drive or a memory card), or the like. The removable storage drive 214 reads from and/or writes to a removable storage medium 244 in a well-known manner. The removable storage medium 244 may include magnetic tape, optical disk, non-volatile memory storage medium, or the like, which is read by and written to by removable storage drive 214. As will be appreciated by persons skilled in the relevant art(s), the removable storage medium 244 includes a computer readable storage medium having stored therein computer executable program code instructions and/or data. In an alternative implementation, the secondary memory 210 may additionally or alternatively include other similar means for allowing computer programs or other instructions to be loaded into service provider server 103. Such means can include, for example, a removable storage unit 222. Examples of a removable storage unit 222 include a program cartridge and cartridge interface (such as that found in video game console devices), a removable memory chip (such as an EPROM or PROM) and associated socket, a removable solid state storage drive (such as a USB flash drive, a flash memory device, a solid state drive or a memory card), and other removable storage units 222 which allow software and data to be transferred from the removable storage unit 222 to service provider server 103.
Service provider server 103 also includes at least one communication interface 224. The communication interface 224 allows software and data to be transferred between service provider server 103 and external devices via a communication path 226. For example, data can be transferred between service provider server 103 and customer device 102 via communication interface 224. In various embodiments of the inventions, the communication interface 224 permits data to be transferred between service provider server 103 and a data communication network, such as a public data or private data communication network. Examples of a communication interface 224 can include a modem, a network interface (such as an Ethernet card), a communication port (such as a serial, parallel, printer, GPIB, IEEE 1394, RJ45, USB), an antenna with associated circuitry and the like. The communication interface 224 may be wired or may be wireless. Software and data transferred via the communication interface 224 are in the form of signals which can be electronic, electromagnetic, optical or other signals capable of being received by communication interface 224. These signals are provided to the communication interface via the communication path 226.
Software may be stored in a computer program product and loaded into service provider server 103 using the removable storage drive 214, the storage drive 212, or the interface 240. Alternatively, the computer program product may be downloaded to service provider server 103 over the communications path 226. The software, when executed by the processor 204, causes service provider server 103 to perform functions of embodiments described herein. It is to be understood that the embodiment of
As used herein, the term “computer program product” may refer, in part, to removable storage medium 244, removable storage unit 222, a hard disk installed in storage drive 212, or a carrier wave carrying software over communication path 226 (wireless link or cable) to communication interface 224. Computer readable storage media or medium refers to any non-transitory, non-volatile tangible storage medium that provides recorded instructions and/or data to service provider server 103 for execution and/or processing. Examples of such storage media include magnetic tape, CD-ROM, DVD, Blu-ray™ Disc, a hard disk drive, a ROM or integrated circuit, a solid state storage drive (such as a USB flash drive, a flash memory device, a solid state drive or a memory card), a hybrid drive, a magneto-optical disk, or a computer readable card such as a PCMCIA card and the like, whether or not such devices are internal or external of service provider server 103. Examples of transitory or non-tangible computer readable transmission media that may also participate in the provision of software, application programs, instructions and/or data to service provider server 103 include radio or infra-red transmission channels as well as a network connection to another computer or networked device, and the Internet or Intranets including e-mail transmissions and information recorded on Websites and the like.
Keypad 302 and touch-screen display 304 are controlled by application processor 318. Power and audio controller 320 is provided to supply power from battery 322 to the communication subsystem, application processor 318, and the other hardware. Power and audio controller 320 also controls input from microphone 338, and audio output via speaker 308. Also provided is global positioning system (GPS) antenna and associated receiver element 324 which is controlled by application processor 318 and is capable of receiving a GPS signal for use with a satellite navigation functionality of customer device 102.
In order for the application processor 318 to operate, various different types of memory are provided. Firstly, customer device 102 includes Random Access Memory (RAM) 326 connected to application processor 318 into which data and program code can be written and read from at will. Code placed anywhere in RAM 326 can be executed by application processor 318 from RAM 326. RAM 326 represents a volatile memory of customer device 102. Secondly, customer device 102 is provided with long-term storage 328 connected to application processor 318. Long-term storage 328 comprises three partitions, an operating system (OS) partition 330, system partition 332 and user partition 334. Long-term storage 328 represents a non-volatile memory of customer device 102.
In the present example, OS partition 330 contains the firmware of customer device 102 which includes an operating system. Other computer programs may also be stored on long-term storage 328, such as application programs, and the like. In particular, application programs which are mandatory to customer device 102, such as, in the case of a smartphone, communications applications and the like are typically stored in system partition 332. The application programs stored on system partition 332 would typically be those which are bundled with customer device 102 by the device manufacturer when customer device 102 is first sold. Application programs which are added to customer device 102 by the customer would usually be stored in user partition 334. For example, digital wallet application 101 can be stored in user partition 334. As stated, the representation of
In step 401, the customer accesses digital wallet 1104 with digital wallet application 101, selects payment card 1134 and initiates a transaction with a merchant terminal. The transaction could be initiated by the customer tapping customer device 102 against the NFC (Near field communication)-enabled merchant terminal.
In step 402, service provider server 103 communicates the card number of payment card 1134 to merchant terminal which then triggers a chain of events among the merchant bank server, issuer 1 server 114 and a payment network, which culminates in merchant terminal responding to customer device 102 that the transaction has been approved. The merchant bank server is the server of a bank which processes the merchant-related transactions. An example of the payment network is the MasterCard® payment network.
In step 403, issuer 1 server 114 issues the rewards points for payment card 1134, and forwards data indicative of these card-specific rewards points to service provider server 103 via API 1124.
In step 404, service provider server 103 converts the card-specific rewards points into standard rewards points by applying a normalizing algorithm. This step is important as the rewards points for different rewards issuers and merchants have differing weights and values. For example, the rewards points for buying a coffee drink with a payment card from a particular rewards issuer may be in the double digits. On the other hand, the rewards points for buying the same coffee drink with a payment card from another rewards issuer may be in the thousands. Therefore, it is crucial to normalize the disparate rewards points in order to obtain a standardized rewards points system or an “open-loop points standard” so that the standard points can be used across various rewards issuers and merchants.
The normalizing algorithm can involve scaling rewards points by a predetermined factor. This predetermined factor can be correlated to a ratio between the dollar value of the rewards points of the different rewards issuers. For example, if rewards issuer 1 offers 1000 rewards points for a $1 spend while rewards issuer 2 offers 10 rewards points for a $1 spend, then the ratio between the dollar value of the rewards points of rewards issuer 1 and the rewards points of issuer 2 could be 100 is to 1, or 100:1. The predetermined factor would then be 100. In this scenario, the normalizing algorithm would scale the rewards points of rewards issuer 2 by the predetermined factor of 100 so as to normalize the rewards points of issuer 2 with the rewards points of rewards issuer 1. The determination of the ratio between the dollar value of the rewards points of the different rewards issuers is essentially a business decision which requires an agreement between the different rewards issuers.
In step 405, service provider server 103 updates standard rewards value 107 of digital wallet 1104 with the acquired standard rewards points. This update procedure could be an addition of the acquired standard rewards points to standard rewards value 107.
In step 406, the updated standard rewards value 107 is displayed on digital wallet application 101 to the customer.
In step 501, the customer accesses digital wallet 2105 with digital wallet application 101, selects payment card 2135 and initiates a transaction with a merchant terminal. The transaction could be initiated by the customer tapping customer device 102 against the NFC (Near field communication)-enabled merchant terminal. As digital wallet 2105 is provisioned with both payment card 2135 and payment card 3145, the customer can choose to make payment with payment card 3145 instead of payment card 2135.
In step 502, service provider server 103 communicates the card number of payment card 2135 to merchant terminal which then triggers a chain of events among the merchant bank server, issuer 2 server 115 and the payment network, which culminates in the merchant terminal responding to customer device 102 that the transaction has been approved.
In step 503, issuer 2 server 115 issues the appropriate card-specific rewards points, and forwards the card-specific rewards points to service provider server 103 via API 2125.
In step 504, service provider server 103 converts the card-specific rewards points into standard rewards points by applying a normalizing algorithm. This step is similar to step 404 as described above.
In step 505, service provider server 103 updates standard rewards value 108 of digital wallet 2105 with the acquired standard rewards points. This update procedure could be an addition of the acquired standard rewards points to standard rewards value 108.
In step 506, the updated standard rewards value 108 is displayed on digital wallet application 101 to the customer.
The method in which digital wallet 3106 accumulates rewards points and in which standard rewards value 109 is updated is similar to the above described methods for digital wallet 1104 and digital wallet 2105. To avoid being repetitive, the method in which digital wallet 3106 accumulates rewards points and in which standard rewards value 109 is updated is not explicitly illustrated in this document.
Digital wallet 1104 is associated with payment card 1134 i.e. payment card 1134 is provisioned onto digital wallet 1104. Digital wallet 2105 is associated with payment card 2135 and payment card 3145 i.e. payment card 2135 and payment card 3145 are provisioned onto digital wallet 2105. Digital wallet 3106 is associated with payment card 4136 and payment card 5137 i.e. payment card 4136 and payment card 5137 are provisioned onto digital wallet 3106. Issuer 1 server 114 provides payment card 1134 to the customer. Issuer 2 server 115 provides payment card 2135 and payment card 3145 to the customer. Issuer 3 server 116 provides payment card 4136 to the customer. Issuer 4 server 117 provides payment card 5137 to the customer.
In step 701, the customer accesses digital wallet 1104 with digital wallet application 101, selects payment card 1134 and initiates a transaction with merchant POS terminal 601. The transaction could be initiated by the customer tapping customer device 102 against the NFC-enabled merchant POS terminal 601.
In step 702 service provider server 103 receives a merchant category code from merchant POS terminal 601 and determines that the rewards points can be utilized in this transaction.
In step 703, service provider server 103 sums up standard rewards value 107, standard rewards value 108 and standard rewards value 109 to obtain a consolidated standard rewards value, and presents the consolidated standard rewards value to digital wallet application 101. This allows the customer the opportunity to utilize the consolidated rewards points accumulated in digital wallet 1104, digital wallet 2105 and digital wallet 3106 in offsetting partially or fully the purchase price.
In step 704, customer selects via digital wallet application 101 the amount of standard rewards points to use in the payment. The customer may decide to use a portion of the consolidated standard rewards value or all of it.
In step 705, service provider server 103 communicates the selected standard rewards points to merchant bank server 602.
In step 706, merchant bank server 602 applies the appropriate discount to the purchase price based on the selected standard rewards points and computes the outstanding payment balance.
In step 707, merchant POS terminal 601 displays the outstanding payment balance.
In step 708, customer uses digital wallet application 101 to initiate the payment of the outstanding payment balance.
In step 709, service provider server 103 communicates the card number of payment card 1134 to merchant POS terminal 601 which then triggers a chain of events among the merchant bank server 602, issuer 1 server 114 and a payment network, which culminates in merchant POS terminal 601 responding to customer device 102 that the transaction has been approved. An example of the payment network is the MasterCard® payment network.
In step 710, service provider server 103 debits the selected standard rewards points from standard rewards value 107, standard rewards value 108 and standard rewards value 109.
Therefore, what has been disclosed is a method and system that standardizes and aggregates disparate rewards points accumulated for various digital wallets into a single rewards points system. The points in this single rewards points system can be redeemed with a purchase from any of the customer's digital wallets and with any participating merchant. This allows customers to fully utilize their accumulated rewards points, enhancing the overall customer's experience. This may even incentivize customers to perform even more transactions with their digital wallets, with the knowledge that their accumulated rewards points across their various digital wallets can be consolidated and utilized with any participating merchant. Another benefit is that certain embodiments of the invention discloses a secure ecosystem for rewards points to be passed from the issuer to the customer, and then onto the merchant for redemption. This is achieved by service provider server 103 being placed intermediate between the issuer servers and merchant bank servers, and service provider server 103 implementing an open Application Programming Interface (API) based secure communication channel.
In the application, unless specified otherwise, the terms “comprising”, “comprise”, and grammatical variants thereof, intended to represent “open” or “inclusive” language such that they include recited elements but also permit inclusion of additional, non-explicitly recited elements. The invention illustratively described herein may suitably be practiced in the absence of any element or elements, limitation or limitations, not specifically disclosed herein. Thus, for example, the terms “comprising”, “including”, “containing”, etc. shall be read expansively and without limitation. Additionally, the terms and expressions employed herein have been used as terms of description and not of limitation, and there is no intention in the use of such terms and expressions of excluding any equivalents of the features shown and described or portions thereof, but it is recognized that various modifications are possible within the scope of the invention claimed. Thus, it should be understood that although the present invention has been specifically disclosed by preferred embodiments and optional features, modification and variation of the inventions embodied therein herein disclosed may be resorted to by those skilled in the art, and that such modifications and variations are considered to be within the scope of this invention.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10201509121Q | Nov 2015 | SG | national |
