Patent Grant
9842344
At least certain embodiments of the invention disclosed herein relate generally to financial services transactions, and more particularly to a stock-based value added services system and method for payment card transactions.
There are several marketing efforts related to offering incentives to promote certain customer spending behaviors. For example, a merchant may offer a loyalty program to provide rewards, such as a discount, rebate, or gift, to encourage customers to purchase from the merchant. A credit or debit card account issuer may offer a loyalty program to encourage cardholders to use the credit card from the issuer. Merchants may also integrate their own loyalty programs with a credit or debit card issuer to cooperate to offer loyalty programs to promote their respective services and products. For example, some payment card issuers have allowed or promoted the consolidation of rewards earned through customer relationships, such as hotels, airlines, oil companies, etc. These rewards are typically limited to purchases made using the payment cards from the respective account issuers. The amounts of the rewards are calculated based on the total purchase price charged to the payment card accounts. To consolidate rewards, payment card issuers or their associated merchant partners in the loyalty program may exchange information about the rewards.
Loyalty programs generally maintain an account for each customer to accumulate benefits earned by the customer in connection with activities related to the loyalty program. For instance, rewards are credited to a reward account of a consumer after the consumer performs certain actions that satisfy the rules of the loyalty program, such as by making a purchase using a particular payment credit or debit card from the account issuer providing the loyalty program or by making a purchase from a specific merchant or group of merchants sponsoring the loyalty program. Rewards can be quantified in various units, such as actual cash value, points, miles, stars, digital cash, etc.
A shareholder investment system and method is provided. At least certain embodiments relate to processing of loyalty rewards such as rewards generated via the use of credit cards, debit cards, prepaid cards, etc. A payment processing system for financial transactions is enhanced to support reward transactions. The reward communications can be processed over the payment processing system together with payment transactions. Consumer's can accumulate monetary value associated with the rewards in a rewards account. The rewards are based on awards provided by conducting transactions using a rewards account associated with a shareholder rewards program or by conducting transactions with particular merchants participating in the rewards program. The accumulated monetary value can then be used for purchase of shares of stock of participating merchants.
For a better understanding of at least certain embodiments, reference will be made to the following Detailed Description, which is to be read in conjunction with the accompanying drawings, wherein:
Throughout the description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent to one skilled in the art, however, that the present invention may be practiced without some of these specific details. In other instances, well-known structures and devices are shown in block diagram form to avoid obscuring the underlying principles of embodiments of the invention. The embodiments described herein include a method and system for shareholder investment.
Provided below is a description of an example system in which embodiments provided herein may be implemented. Although certain of the entities may be depicted as separate components, in some instances one or more of the components may be combined into a single device or system. Similarly, although certain functionality may be described as being performed by a single entity or component within the system, the functionality may, in some instances, be performed by multiple components or entities acting in a coordinated fashion. Communications between entities and components may comprise the exchange of data or information using electronic messages on any suitable electronic communication medium as understood by persons of skill in the art.
In the most common case, a POS device is used. A POS device is generally an electronic device where a transaction is completed and any suitable terminal may be used. It is the point at which a consumer 30 makes a payment to the merchant in exchange for goods or services. At the POS the merchant device 22 calculates the total amount owed by the consumer and provides options for payment. The merchant will also normally issue a receipt for the transaction. In many cases, POS devices 22 include card readers. Card readers may include any suitable contact or contactless mode of operation. For example, card readers may include magnetic stripe readers, RF antennas, NFC readers, etc. Alternatively, the access device 22 may interact with the consumer 30 remotely in an online purchase over a network such as the Internet.
In addition, POS devices in various industries may include customized hardware and software. Retailers may utilize weighing scales, scanners, electronic and manual cash registers, EFTPOS terminals, touch screens, or any other of a wide variety of hardware and software available for use with POS devices. For example, a grocery or candy store may use a scale at the point of sale, while bars and restaurants may use software to customize the item or service sold when a customer has a special meal or drink request. Modern POS devices may include advanced features to cater to different functionality, such as inventory management, CRM, financials, warehousing, etc., all built into the POS software.
The payment processing system 26 may include any data processing subsystems, networks, or operations used to support and deliver payment authorization services, exception file services, and/or clearing and settlement services. Exemplary payment processors include systems capable of processing credit card transactions, debit card transactions, and other types of commercial transactions, as well as performing clearing and settlement services. A clearing process is a process of exchanging financial details between an acquirer system and an account issuer to facilitate posting the transaction to the consumer's account and reconciliation of the consumer's settlement position. Clearing denotes all activities from the time a commitment is made for a transaction until the transaction is settled. Clearing payments is necessary to the promise of payment into the actual movement of money from one bank to another. Clearing and settlement can occur simultaneously.
The payment processing system 26 may include a server computer as is well known in the art. A server computer is typically a powerful computer or cluster of computers. For example, the server computer can be a large mainframe, a minicomputer cluster, or a group of servers functioning in cooperation as a unit. In one example, the server computer may be a database server coupled to a web server. The payment processing system 26 may use any suitable wired or wireless network, including the Internet. For the purposes of the proposed methods, the acquirer system 24, payment processing system 26, and issuer system 28 can each individually act as a service provider. They can also act as a single service provider by working together in any combination. The consumer 30 may be an individual or an organization such as a business that is capable of purchasing goods or services.
In a typical purchase transaction, the consumer 30 purchases a good or service at the merchant access device 22 using a consumer payment device. The consumer's payment device can interact with an access device 22 such as a POS terminal 22 at the merchant. An “authorization request message” is then generated at the merchant access device 22 and forwarded to the acquirer system 24. As used herein the term “authorization request message” refers to any electronic message that is sent over a payment processing network or to an account issuer to request authorization for a particular transaction. An authorization request message according to some embodiments may comply with an International Organization for Standardization (“ISO”). For example, an authorization request message may comply with ISO 8583, which is a standard message format for systems that exchange electronic transaction information associated with a payment using a payment device or payment account. The authorization request message may include an issuer account number (or other account identifier) that may be associated with the consumer's payment device. An authorization request message may also include additional data elements of identification information including, by way of example, a service code, a card verification value (“CVV”), an expiration date, etc. An authorization request message may also include any information associated with a current transaction, such as the amount, merchant identifier, merchant location, etc., as well as any other information that may be utilized in determining whether to identify or authorize the transaction.
After receiving the authorization request message, the authorization request message is then sent to the payment processing system 26, which then forwards it to the account issuer system 28 of the consumer payment device for authorization. In such an embodiment, the consumer's account information is stored at the account issuer 28 and is checked for authorization. In other embodiments, the payment processor 26 may also have access to the consumer's account information locally and can authorize transactions on behalf of the account issuer system 28.
After the issuer system 28 receives the authorization request message, the issuer 28 sends an “authorization response message” back to the payment processing system 26 to indicate whether or not the current transaction is authorized. An “authorization response message” may be any electronic reply message to an authorization request message generated by an issuing financial institution or payment processing network. The authorization response message may include, for example, one or more of the following: (1) transaction approved; (2) transaction declined; or (3) response pending more information. The authorization response message may also include an authorization code, which may be a code that a credit card issuing bank returns in response to an authorization request message (either directly or through the payment processing network) to a merchant's access device 22 that indicates approval or disapproval of the transaction. The code may serve as proof of authorization. In some embodiments, the payment processing network may generate or forward the authorization response message to the merchant.
The transaction processing system 26 then forwards the authorization response message back to the acquirer system 24, which then forwards the response message back to the merchant access device 22. After the merchant 22 receives the authorization response message, the access device 22 at the merchant may then provide the authorization response message for the consumer 30. The response message may be displayed by the POS terminal, or may be printed out on a receipt, etc. At the end of the day, a normal clearing and settlement process can be conducted by the payment processing system 26.
Acquirer system 24 can communicate with the merchant access device 22 and payment processing system 26 over the one or more secure financial networks 110. Further, payment processing system 26 can communicate with the account issuer system 28 and a brokerage system 30 over one or more secure financial networks 120. As described in detail below, system 200 can be used to facilitate transactions and can implement a shareholder rewards program according to the embodiments described herein. At least certain embodiments relate to processing of loyalty rewards such as rewards generated via the use of credit cards, debit cards, prepaid cards, etc. A payment processing system 26 for financial transactions is enhanced to support reward transactions. The reward communications can be processed over the payment processing system 26 together with payment transactions. Consumer's 30 can accumulate monetary value associated with the rewards in a rewards account. The rewards are based on awards provided by conducting transactions using a rewards account associated with a shareholder rewards program or by conducting transactions with particular merchants 22 participating in the rewards program. The accumulated monetary value can then be used for purchase of shares of stock of participating merchants 22.
In the illustrated embodiment, payment processing server 301 includes a network interface (I/F) unit 202 in communication with one or more secure financial networks. Payment processing server 301 is shown as including a processor 210 and a system memory 211 (which may comprise any combination of volatile or non-volatile memory such as RAM, DRAM, ROM, flash, or any other suitable memory). In addition, payment processing server is shown as including one or more units or modules 206, 207, 208, and 209. These units may be disposed within one or more of the components of the system memory 211, or may be externally located. They may be implemented in hardware, software, or any combination of hardware and software elements. The processing unit 210 and system memory 211 may be used in conjunction with all or any number of these units as described below to provide the desired functionality. Moreover although many of the data processing functions and features of some embodiments may be physically located in the payment processing server 301, it should be understood that such functions and features could be present in other components such as the issuer system 28, and need not be specifically located in the payment processing server 26.
Payment processing server 301 includes a database unit 209 configured to communicate and manage a database 217. As shown in the illustrated embodiment, database 217 includes consumer account information 214, consumer rewards account information 215, and participating merchant information 216. Consumer account information 214 for accounts issued by issuer system 28 can be stored locally in database 217 and used to implement the techniques described herein. Further, the rewards account information 215 associated with each consumer's shareholder rewards account can be stored in database 217. Participating merchant information 216 can also be stored in database 217. Merchants that agree to participate in the shareholder rewards program can register with the service. Accounts can be created for these merchants that contain certain information specific to the merchant. For example, the name of the merchant, and type of goods or services the merchant provides can be included in the merchant information 216. In addition, the details of the merchant's participation can also be stored in 216. For instance, when a merchant accepts a payment card transaction, the merchant will typically pay a transaction fee to the payment processor for providing this service. The merchant participating in the shareholder rewards program may pay an additional percentage of the transaction fee for participating in the shareholder rewards program. Alternatively, the merchant may elect to offer to pay a higher percentage of the transaction fee as part of a sales incentive for attracting program participants to shop at the merchant's stores or to receive services offered by the merchant.
In one embodiment, database is a remote database in communication with the payment processing server 301 over one or more networks. In other embodiments, database 217 can be a local database integrated with the payment processing server 310. In yet other embodiments, this information is stored in system memory 211 of the payment processing server 301 and no database is used or necessary.
Payment processing server 301 further includes a shareholder rewards unit 208. Shareholder rewards unit 208 may be implemented in dedicated computer hardware, software, or any combination of computer hardware and software elements. In at least certain embodiments, the shareholder rewards unit 208 is configured to implement embodiments of the shareholder investment method and system described herein. Consumers can register for the shareholders rewards account offered in a shareholder rewards program for payment transactions as described herein. Registered users' account information can then be associated with a corresponding shareholder rewards account. When a transaction is performed by a consumer using a payment device (e.g., credit or debit card or mobile device) that is associated with a registered rewards account, the shareholder rewards unit 208 can be configured to capture the consumer's payment account information in the authorization request message and to identify the consumer's account 214 as being associated with a shareholders rewards account 215. The shareholders rewards unit 208 is configured to then credit a shareholder fee (“SF”) to the consumer's shareholder rewards account 215 based on the transaction conducted by the consumer as described in detail below.
Process 400 continues at operation 405 where the merchant with whom the consumer is conducting the transaction is identified as participating in the shareholder rewards program. In one embodiment, this is accomplished by accessing a database containing participating merchant information as described above. Once the consumer's account is identified as being associated with a shareholder rewards account and the merchant is identified as participating in the shareholder rewards program, the merchant can be charged a merchant transaction fee associated with the transaction (operation 407) and at least a percentage of the merchant transaction fee can be credited to the consumer's shareholder rewards account as a shareholder fee (“SF”) at operation 409. The SF may be assigned a monetary value and this value will accumulate in the consumer's shareholder rewards account over time (operation 411).
In one embodiment, the percentage of the transaction fee credited to the consumer's shareholder rewards account is set by the issuer of the account associated with the payment card used in the transaction. In another embodiment, the merchant can set the percentage of the transaction fee credited to the consumer's shareholder rewards account. For instance, the merchant may want to set a percentage of a transaction fee to be paid to a consumer's rewards account based on the total sale price of the transaction or based on a sale or other incentive offered by the merchant to encourage consumer's to conduct business with the merchant. Merchants may also increase the SFs paid as long as the value of those SFs is only used for purchasing shares of stock of the merchant. Groups of merchants may also do this so that consumers are incentivized to conduct business with that group of merchants or service providers. Some merchants may offer the SFs as a cash back award in the form of SFs that can be used for the purchase of any shares of stock from any merchant using the consumer's brokerage account. Other merchants may require their SF awards only be used for purchasing stock of that merchant or group of merchants. Further, yet other merchants may offer larger cash back awards in the form of SFs for marketing like any sale, or for purchase of that merchant's stock, or any combination of these.
To accomplish this, in one embodiment, separate merchant accounts can be provided for each participating merchant in the consumer's shareholder rewards account such that purchase transactions conducted with that merchant are credited solely to the merchant's separate account. This incentivizes merchants to participate in the program since any rewards paid to consumers will ultimately be used to purchase company stock of the merchant. Separate accounts can also be provided for pools of merchants in the same way.
The embodiments described herein have several advantages. First, the embodiments are advantageous for consumers because consumers can invest in shares of stock in various companies just by using their shareholder rewards card. In addition, the embodiments are advantageous for payment card account issuers to use the program because it encourages consumers to utilize their payment cards for conducting transactions. Finally, the embodiments are advantageous to merchants because consumers are encouraged to transact business with merchants or service providers who are participants in the shareholder rewards program. In addition, when consumers use their SF reward value to purchase stock of the merchants, the merchants ultimately benefit from that long term by increasing the total volume of investors in their stock offerings. Merchants can set the percentage of cash back (SFs) based on the total sale price or a set rate. Receipts can also be issued to consumers at the point of sale saying “you earned $10 cash back towards the purchase of shares of X stock.”
The embodiments of the invention described herein relate to an enhancement of current payment card transactions as a new card account to reward consumers with automatic cash back in the form of SFs to be applied toward the purchase of shares of stock in publicly held corporations. SF can be charged to the merchant's account at a suggested automatic rate of, for example ¼ to 1% of the total purchase price or a fixed amount per transaction can be charged. As an additional incentive to the merchant to increase sales, the merchant can choose to increase the SF rate to an even higher rate and advertise this rate to consumers. Much like having a sale, the higher the SF rate of reward, the more likely the consumer will go out of their way to shop at that merchants POS. The SF rewards are paid back to the consumer's shareholder rewards account and can be transferred to the consumer's brokerage account to be invested at a later date. The consumer may also add any additional amount to the consumer's account toward the purchase of shares of stock. Further, merchants choosing to decline accepting payment cards implemented according to the systems and methods described herein can still accept a standard Visa/MasterCard payment portion of the card.
In addition, unincorporated merchants may apply for business relayed funding under the card, Main Street Banking, based on the total volume of unincorporated SFs. In addition, the U.S. Government Tax Revenues will benefit by the increased number of investors' profits to tax.
Embodiments of the present invention may be practiced with various computer system configurations including hand-held devices, microprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers and the like. The embodiments can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a wire-based or wireless network.
As shown in
RAM 505 can be implemented as dynamic RAM (“DRAM”), which requires power continually in order to refresh or maintain the data in the memory. The other nonvolatile memory 506 can be a magnetic hard drive, magnetic optical drive, optical drive, DVD RAM, or other type of memory system that maintains data after power is removed from the system. While
With these embodiments in mind, it will be apparent from this description that aspects of the described techniques may be embodied, at least in part, in software, hardware, firmware, or any combination thereof. It should also be understood that embodiments could employ various computer-implemented functions involving data stored in a computer system. The techniques may be carried out in a computer system or other data processing system in response executing sequences of instructions stored in memory. In various embodiments, hardwired circuitry may be used independently or in combination with software instructions to implement these techniques. For instance, the described functionality may be performed by specific hardware components containing hardwired logic for performing operations, or by any combination of custom hardware components and programmed computer components. The techniques described herein are not limited to any specific combination of hardware circuitry and software.
Embodiments herein may also be implemented in computer-readable instructions stored on an article of manufacture referred to as a computer-readable medium, which is adapted to store data that can thereafter be read and processed by a computer. Computer-readable media is adapted to store these computer instructions, which when executed by a computer or other data processing system such as data processing system 500, are adapted to cause the system to perform operations according to the techniques described herein. Computer-readable media can include any mechanism that stores information in a form accessible by a data processing device such as a computer, network device, tablet, smartphone, or any device having similar functionality.
Examples of computer-readable media include any type of tangible article of manufacture capable of storing information thereon including floppy disks, hard drive disks (“HDDs”), solid-state devices (“SSDs”) or other flash memory, optical disks, digital video disks (“DVDs”), CD-ROMs, magnetic-optical disks, ROMs, RAMs, erasable programmable read only memory (“EPROMs”), electrically erasable programmable read only memory (“EEPROMs”), magnetic or optical cards, or any other type of media suitable for storing instructions in an electronic format. Computer-readable media can also be distributed over a network-coupled computer system stored and executed in a distributed fashion.
It should be understood that the various data processing devices and systems are provided for illustrative purposes only, and are not intended to represent any particular architecture or manner of interconnecting components, as such details are not germane to the techniques described herein. It will be appreciated that network computers and other data processing systems, which have fewer components or perhaps more components, may also be used. For instance, these embodiments may be practiced with a wide range of computer system configurations including any device that can interact with the Internet via a web browser or an application such as hand-held devices, microprocessor systems, workstations, personal computers (“PCs”), Macintosh computers, programmable consumer electronics, minicomputers, mainframe computers, or any mobile communications device including an iPhone, iPad, Android, or Blackberry device, or any device having similar functionality. These embodiments can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a wire-based or wireless network.
Throughout the foregoing description, for the purposes of explanation, numerous specific details were set forth in order to provide a thorough understanding of the invention. It will be apparent, however, to persons skilled in the art that these embodiments may be practiced without some of these specific details. Accordingly, the scope and spirit of the invention should be judged in terms of the claims that follow as well as the legal equivalents thereof.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6631358 | Ogilvie | Oct 2003 | B1 |
| 8131590 | Armstrong | Mar 2012 | B1 |
| 20010047295 | Tenembaum | Nov 2001 | A1 |
| 20020052818 | Loveland | May 2002 | A1 |
| 20030004803 | Glover | Jan 2003 | A1 |
| 20030004809 | Palcic | Jan 2003 | A1 |
| 20040210505 | Pourhamid | Oct 2004 | A1 |
| 20040254873 | Loveland | Dec 2004 | A1 |
| 20050055272 | Ryan | Mar 2005 | A1 |
| 20050209916 | Longman | Sep 2005 | A1 |
| 20070106581 | Mitchell | May 2007 | A1 |
| 20070192198 | Schwarz | Aug 2007 | A1 |
| 20070208624 | Gallagher | Sep 2007 | A1 |
| 20070265950 | Reuss | Nov 2007 | A1 |
| 20080033816 | Miller | Feb 2008 | A1 |
| 20080201230 | Hardison | Aug 2008 | A1 |
| 20090265263 | Williams | Oct 2009 | A1 |
| 20100106578 | Allio | Apr 2010 | A1 |
| 20110087532 | Garner | Apr 2011 | A1 |
| 20120203608 | Lele | Aug 2012 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20160098739 A1 | Apr 2016 | US |
