Advanced loyalty applications for powered cards and devices

Information

  • Patent Grant
  • 11003970
  • Patent Number
    11,003,970
  • Date Filed
    Friday, October 5, 2018
    5 years ago
  • Date Issued
    Tuesday, May 11, 2021
    3 years ago
Abstract
Advanced loyalty applications are provided to improve the functionality of cards and devices. For example, a user interface may be placed on a card (e.g., a physical button) or a telephonic device (e.g., a virtual button on a capacitive touch screen). Manual input provided to this user interface may, for example, cause a non-merchant product (e.g., insurance) to be purchased with a merchant purchase. The product can be paid for with debit, credit, gift card balance, or points. A code indicative of a user's desire to purchase the product may be communicated to a payment card reader (e.g., to a magnetic stripe reader via a magnetic stripe communications device). A display may be provided next to a button to allow a user to scroll, or toggle by pressing the button repeatedly, through different products (which may be merchant or non-merchant products).
Description
BACKGROUND OF THE INVENTION

This invention relates to magnetic cards and devices and associated payment systems.


SUMMARY OF THE INVENTION

A card may include a dynamic magnetic communications device. Such a dynamic magnetic communications device may take the form of a magnetic encoder or a magnetic emulator. A magnetic encoder may change the information located on a magnetic medium such that a magnetic stripe reader may read changed magnetic information from the magnetic medium. A magnetic emulator may generate electromagnetic fields that directly communicate data to a magnetic stripe reader. Such a magnetic emulator may communicate data serially to a read-head of the magnetic stripe reader.


All, or substantially all, of the front as well as the back of a card may be a display (e.g., bi-stable, non bi-stable, LCD, LED, or electrochromic display). Electrodes of a display may be coupled to one or more capacitive touch sensors such that a display may be provided as a touch-screen display. Any type of touch-screen display may be utilized. Such touch-screen displays may be operable of determining multiple points of touch. Accordingly, a barcode may be displayed across all, or substantially all, of a surface of a card. In doing so, computer vision equipment such as barcode readers may be less susceptible to errors in reading a displayed barcode.


A card may include a number of output devices to output dynamic information. For example, a card may include one or more RFIDs or IC chips to communicate to one or more RFID readers or IC chip readers, respectively. A card may include devices to receive information. For example, an RFID and IC chip may both receive information and communicate information to an RFID and IC chip reader, respectively. A device for receiving wireless information signals may be provided. A light sensing device or sound sensing device may be utilized to receive information wirelessly. A card may include a central processor that communicates data through one or more output devices simultaneously (e.g., an RFID, IC chip, and a dynamic magnetic stripe communications device). The central processor may receive information from one or more input devices simultaneously (e.g., an RFID, IC chip, dynamic magnetic stripe devices, light sensing device, and a sound sensing device). A processor may be coupled to surface contacts such that the processor may perform the processing capabilities of, for example, an EMV chip. The processor may be laminated over and not exposed such that such a processor is not exposed on the surface of the card.


Advanced loyalty features are provided on cards and devices such as payment cards. Such cards and devices may, for example, allow a user to purchase a product not sold by a merchant when the card is used at that merchant. For example, a card or device may include a user interface able to receive manual input to indicate that a user desires to purchase a product not sold by a merchant (or a particular merchant product). Such a card or device may send information indicative of such a user desire during a payment transaction at the merchant. For example, information may be communicated in a discretionary data field of one or more tracks of magnetic stripe data (e.g., via a dynamic magnetic stripe communications device). As per another example, information may be communicated via RFID communications to an RFID reader or IC chip (e.g., EMV chip) communications to an IC chip reader. The value of such a product chosen by a user may be subtracted from a user's cash account, available line of credit, or available point balance. A display may be included to display information indicative of a user's selection (e.g., to purchase a non-merchant product) such that a user may enter this information into a data entry field of an online store. Such products may include, for example, damage insurance and/or theft insurance. Multiple user payment accounts may be linked. For example, if a user desires to pay for an additional product with points and that user's point balance does not have enough points to cover the purchase price of the product, then a user's credit or debit account may be utilized to pay for the entire price of the product or the outstanding balance needed to purchase the product. An LED may indicate a particular user selection (e.g., via different colors). A display may be provided next to a button such that a user can see information representative of the product being purchased. The product displayed may be toggled from a list of products by, for example, pressing a button additional times. A confirmation button may also be provided such that a user presses a button first to activate a display and display a product name and then presses the confirmation button to confirm. A card may include a default method of payment (e.g., credit, debit, gift balance, or points) associated with a particular button (e.g., a button for purchasing a particular product). Limitations with such a default (e.g., a minimum point balance needed to utilize a product purchase with points) may be communicated to a user at card issue (e.g., via physical mail, email, or posting on a user's account page of a card issuer's website).


A user interface is provided on a card or device that allows a user to indicate a desire to top-up a purchase to the nearest dollar (or other monetary unit) and use the excess to purchase additional points. For example, a user may press a button on a card associated with $5 such that every purchase is rounded up to the nearest $5. In doing so, any excess amount between the price of a purchase and the round-up interval may be utilized to purchase points at a particular conversion rate. The conversion rate to buy points in this manner may be different (e.g., more points may be purchased for a particular monetary unit) than the conversion rate to buy points outside of a purchase transaction.


All or a portion of the purchase price of merchant items may be paid for at the merchant using points. A card or device may include buttons associated with monetary amounts (e.g., $1, $5, and $10). A user may press a button associated with the desired amount of money a user desires to pay for an item with points. A user may select an amount greater than the purchase price and the difference may be added to a user's credit balance or debit account at a point-to-cash conversion rate. Such a conversion rate may be different (e.g., more points needed for a monetary unit) than if a user selects a monetary amount that only pays for a portion of a purchase.


A user may earn points for different point accounts by providing different manual input for the different point accounts. Different buttons may be provided on a card or device. One, more than one, or all point accounts may be point pools. A point pool may be connected to different accounts—such as different cards. Such different accounts may be owned by different users (e.g., a husband and a wife). Accordingly, for example, points may be shared between multiple users. For example, a card may have a vacation pool. Every member of the family may have a card linked to such a vacation pool. In order to redeem points in a pool, for example, a particular user (e.g., a father), multiple users (e.g., a father and a mother), or all users (e.g., all members of a family) may need to agree to redeem the points for a particular award (e.g., a free vacation). Such users can do so, for example, on each user's account webpage of a main account. Multiple people may also share the same account (e.g., a husband and a wife) such that two cards are issued with the same account number and share the same point account. A cardholder may elect to contribute some or all of the points earned with a purchase to the account of a beneficiary (e.g., a child).


A card is provided that includes a user interface for receiving manual input indicative of a user's desire to forego earning points with a purchase in order to obtain an entry into a lottery. Alternatively, for example, an entry into a lottery may cost a particular number of points (e.g., over 1 point such as 50 points). Additionally, for example, an entry may only be able to be purchased while a user is purchasing an item or an entry may be able to be purchased at any time. Such a lottery may be held at least, for example, once a day, once a month, once a quarter, once every six months, or once a year. Multiple prizes and multiple winners may be included in each lottery. A winner of a lottery may win, for example, points (e.g., 1 million points), cash, and/or products. Non-point awards (e.g., plane tickets) may also be awarded in such a lottery.


A user interface may be provided on a card or button operable to receive manual input indicative of a user's desire to not earn points at a purchase from a merchant in order to obtain the ability to receive a particular point multiplier at the user's next purchase at that merchant so long as the purchase is transacted within a particular period of time (e.g., within a week or within a month). For example, a user may press a button on a card and associated information may be communicated in the discretionary data field of magnetic stripe data. Such a user may, for example, not earn any points with that purchase but may earn three times as many points with the next purchase at that merchant if the two purchases are made within a week of one another. The triple points may be, for example, limited to overlapping purchase value such that if the first purchase is $50 and the second purchase is $75 only $50 worth of purchase value obtains triple points. The remaining $25 of value may obtain no points or single points (regardless of the order of the $50 and $75 purchases). As per another example, the remaining $25 in value may receive double or triple points. Such a point bonus may be limited by a minimum purchase threshold for either a first or subsequent purchase (e.g., for qualifying purchases).


A card may be provided with an option (e.g., a manual user interface) for a user to select an opt-in marketing feature. Such a feature may send information to a merchant through, for example, magnetic stripe data communicated through a dynamic magnetic communications device. Such information may include, for example, demographic information or contact information (e.g., a user's email address). In turn, the merchant may fund a discount or additional points (e.g., a point multiplier such as double points) for the purchase. If a user has already used the opt-in feature at the merchant, the user may or may not be awarded the benefit associated with the user using the opt-in feature for the first time at a merchant. A merchant may send a user a communication (e.g., an email) as a result of receiving the user's email address in a communication to a payment card reader. The user may receive points from filling out such a survey.


Points may be utilized, for example, to purchase discounts for purchases. For example, a particular number of points may provide a 5%, 10%, 15%, or 20% discount on a purchase. A purchase limit for the discount may be provided (e.g., $100) or no purchase limit for the discount may be provided. If a limit is provided and the purchase is over the limit, the discount may only be applied to the limited amount (e.g., $100). Points may be utilized to purchase rebates (e.g., $5, $10, or $20) for a purchase. Such rebates or discounts may be, for example, open to all merchants or limited to qualifying purchases at participating merchants). Discounts and rebates may be processed by a card issuer by placing a credit on a credit statement having the value of the discount or rebate. In doing so, for example, rebates and discounts may be provided at any merchant without the knowledge of the merchant. Point levels required for purchase of a particular rebate or discount (or any other offering such as purchase insurance) may be communicated to a user via email, physical mail, or a user's account page on a card issuer's website. A product purchased with points via a button on a card may be, for example, an extended warranty associated with the products of a purchase as well as defect, damage, and/or theft protection. Other products purchased for points (or from other sources of payment) include, for example, product registration, expedited delivery, and ombudsman service.


Combinations of features may be provided on a card. For example, a card may be provided with a button associated with a feature that allows a user to earn a point multiplier at a second transaction within a period of time at a particular merchant. Another button may be provided on that card associated with a lottery feature. Yet another button may be provided on that card that allows a user to purchase a product at a purchase. Such a product may be associated with the purchase (e.g., purchase insurance for that product).





BRIEF DESCRIPTION OF THE DRAWINGS

The principles and advantages of the present invention can be more clearly understood from the following detailed description considered in conjunction with the following drawings, in which the same reference numerals denote the same structural elements throughout, and in which:



FIG. 1 is an illustration of cards constructed in accordance with the principles of the present invention;



FIG. 2 is an illustration of a card constructed in accordance with the principles of the present invention;



FIG. 3 is an illustration of a card constructed in accordance with the principles of the present invention;



FIG. 4 is an illustration of a card constructed in accordance with the principles of the present invention; and



FIG. 5 is an illustration of a mobile device constructed in accordance with the principles of the present invention.





DETAILED DESCRIPTION OF THE INVENTION


FIG. 1 shows card 100 that may include, for example, a dynamic number that may be entirely, or partially, displayed via display 112. A dynamic number may include a permanent portion such as, for example, permanent portion 111. Permanent portion 111 may be printed as well as embossed or laser etched on card 100. Multiple displays may be provided on a card. For example, display 113 may be utilized to display a dynamic code such as a dynamic security code. Display 125 may also be provided to display logos, barcodes, as well as multiple lines of information. A display may be a bi-stable display or non bi-stable display. Permanent information 120 may also be included and may include information such as information specific to a user (e.g., a user's name or username) or information specific to a card (e.g., a card issue date and/or a card expiration date). Card 100 may include one or more buttons such as buttons 130-134. Such buttons may be mechanical buttons, capacitive buttons, or a combination or mechanical and capacitive buttons. Card 100 may include button 199. Button 199 may be used, for example, to communicate information through dynamic magnetic stripe communications device 101 indicative of a user's intent to purchase a particular product with a purchase for points.


Architecture 150 may be utilized with any card. Architecture 150 may include processor 120. Processor 120 may have on-board memory for storing information (e.g., application code). Any number of components may communicate to processor 120 and/or receive communications from processor 120. For example, one or more displays (e.g., display 140) may be coupled to processor 120. Persons skilled in the art will appreciate that components may be placed between particular components and processor 120. For example, a display driver circuit may be coupled between display 140 and processor 120. Memory 142 may be coupled to processor 120. Memory 142 may include data that is unique to a particular card. For example, memory 142 may store discretionary data codes associated with buttons of card 150. Such codes may be recognized by remote servers to effect particular actions. For example, a code may be stored on memory 142 that causes a non-merchant product to be purchased with points during a merchant transaction. Memory 142 may store loyalty information such as identifying information for a points account (e.g., a points account number) and associated information (e.g., a default preference on how points are earned during a purchase, such as 50% of a purchase's points is given to the user and 50% of a purchaser's points is used to purchase lottery entries for a lottery that has at least one award of a particular number of points).


Any number of reader communication devices may be included in architecture 150. For example, IC chip 152 may be included to communicate information to an IC chip reader. IC chip 152 may be, for example, an EMV chip. As per another example, RFID 151 may be included to communicate information to an RFID reader. A magnetic stripe communications device may also be included to communicate information to a magnetic stripe reader. Such a magnetic stripe communications device may provide electromagnetic signals to a magnetic stripe reader. Different electromagnetic signals may be communicated to a magnetic stripe reader to provide different tracks of data. For example, electromagnetic field generators 170, 180, and 185 may be included to communicate separate tracks of information to a magnetic stripe reader. Such electromagnetic field generators may include a coil wrapped around one or more materials (e.g., a soft-magnetic material and a non-magnetic material). Each electromagnetic field generator may communicate information serially to a receiver of a magnetic stripe reader for particular magnetic stripe track. Read-head detectors 171 and 172 may be utilized to sense the presence of a magnetic stripe reader (e.g., a read-head housing of a magnetic stripe reader). This sensed information may be communicated to processor 120 to cause processor 120 to communicate information serially from electromagnetic generators 170, 180, and 185 to magnetic stripe track receivers in a read-head housing of a magnetic stripe reader. Accordingly, a magnetic stripe communications device may change the information communicated to a magnetic stripe reader at any time. Processor 120 may, for example, communicate user-specific and card-specific information through RFID 151, IC chip 152, and electromagnetic generators 170, 180, and 185 to card readers coupled to remote information processing servers (e.g., purchase authorization servers). Driving circuitry 141 may be utilized by processor 120, for example, to control electromagnetic generators 170, 180, and 185.



FIG. 2 shows card 200 that includes button 211 associated with display 215, button 212 associated with display 216, and button 213 associated with display 217. Each button may be associated with a feature displayed in display 210. A user may press a button in order to communicate data representative of the feature through a magnetic stripe communications device or other communications device (e.g., RFID or IC chip). A light emitting diode (or other source of light) may be associated with each button to indicate to a user what feature was selected by a user. A user may be able to select multiple features such that multiple feature codes are communicated in tracks of magnetic stripe data communicated by a magnetic stripe communications device. Such codes may be provided in discretionary data fields. Such codes may be repeated on each track of communicated magnetic stripe data (e.g., repeated on tracks 1 and 2 or repeated on tracks 1, 2, and 3). In doing so, a user may associate multiple features to a purchase. A user may purchase a financial service by, for example, pressing button 211 for a purchase transaction. A user may press button 212 to enter into a lottery. The cost of the entry may be that no points are earned during the transaction. Button 213 may allow a user to earn multiple points if a purchase is made at the same merchant within a particular time period (e.g., over a day such as within a week) for a cost. The cost may be that a user does not earn any points with the initial purchase or earns a reduced amount of points (e.g., 50% point reduction). Persons skilled in the art will appreciate that one or more remote servers may manage a point balance as well as authorize and settle transactions.


The features associated with each card may be pre-determined by a user. For example, a user may select features to place on a card when ordering a card. Additionally, a user may go to a card issuer's website and select attributes of features. For example, a user may visit a card issuer's website and select the particular offering that is to be purchased whenever a user selects the feature associated with button 211 and displayed on display 215. Information associated with a button may be displayed via a display or permanently printed, embossed, or laser engraved on a card. Card 200 may include a light sensing device to receive information via light pulses from a display (e.g., a television, mobile phone, or laptop display). A user may select to change the features or attributes of features from a card issuer's websites and may reconfigure a card accordingly. Alternatively, a card may be provided with buttons and no descriptive information. A user may change the features or attributes of features associated with one or more buttons via a card issuer's website and remote processing may perform the associated processing as a result of on-card button selections. Different codes may be communicated depending on the feature or attributes of features on a card. Such codes may be changed via a wireless communications signal (e.g., a light-based communications signal). In doing so, processing may occur off-card at a remote server without the need to determine what feature a user associated with a code. Persons skilled in the art will appreciate that a card issuer may monitor the frequency and number of times that a user utilizes a particular feature. A card issuer may cross-sell new products based on this information. For example, suppose a user's card allows a user to purchase insurance for that purchase with a particular number of points. If the user utilizes this option at a particular frequency or a particular number of times, then the user may be sent an offer to purchase the product on a periodic subscription basis (e.g., monthly) instead of an individual purchase. The offer may be communicated, for example, via physical mail, email, or a card issuer's website. In doing so, a card issuer may convert cardholders to subscription-based products the cardholder has tested in a per-purchase environment. If a user purchases a subscription for a product that was associated with a button on a card, the card issuer may change the product associated with that button and notify the user of the change (e.g., via email or a card issuer's website). Persons skilled in the art will appreciate that various types of insurance may be provided. For example, insurance may be associated with a purchase such that if a merchant fails to deliver a product, the insurance covers the incident. Insurance may also be provided, for example, for damage to a product during shipping. Insurance may cover multiple types of incidents. A card issuer may add or modify the attributes of a feature. For example, a card issuer may modify or add products in a list of products associated with a buy product for points feature. The addition or modification may be communicated via light information pulses. Additionally, a user may be provided with a code to enter into buttons on a card where the code represents the modifications or additions. Additionally, the card may receive wireless communications signals (e.g., WiFi signals) associated with the modifications and additions). In this manner, a merchant may change the information on a display associated with a lottery feature to read “win 1M points” during a first period of time and “win Olympic tickets” during a second period of time.


A card issuer may provide a reward network of participating merchants. Accordingly, merchant specific promotions may be provided and paid for with points. For example, a particular merchant may allow for free overnight shipping for a particular number of points while another merchant may allow for an extended warranty for a particular number of points. All such promotions may be associated to a single button (or more than one button). Permanent indicia associated to the single button may generically describe all such merchant-specific promotions (e.g., “merchant promotion”). A different point conversion rate (e.g., a discounted lower point conversion rate) may be provided when items are purchased at a merchant inside of the rewards network versus merchants outside of the rewards network. Such products may be merchant products or non-merchant products. For example, a user may purchase any merchant items using points (e.g., any DVD at a Best Buy) but may receive different conversion rates for the points depending on whether the merchant is within a card issuer's reward network as well as the level of membership within that issuer's reward network. Merchants (e.g., merchants that are part of a particular rewards network) may be provided with devices that offer on-the-spot promotions. Such devices may emit light pulses or other communication signals that are received and stored on a card or other device. A card may prompt a user to interact with a card (e.g., press a button) to confirm acceptance and desire to use a communicated promotion. A promotion may be paper based, but may interact with payment process that includes a card or other device. For example, a user may pick up a coupon that states “give this coupon to a friend and if that friend makes a purchase within 10 days, you will get double points.” The cashier may then scan the barcode of the coupon and a user may press a MERCHANT OFFER button on a card. The merchant system may similarly send the coupon code to a remote system. An associated code may be communicated with payment information (e.g., magnetic stripe data) to the remote system. The remote system may then associate the purchase with the coupon code. Upon a friend redeeming the coupon, the user associated with the original payment information may be provided with additional points (e.g., double points). As per another example, a merchant may pre-register with a card issuer the merchant's promotion. The promotion may be, for example, a cross-merchant promotion where a user that purchases an item at one merchant may receive double points and a 10% discount if a paper coupon is used within a particular number of days at a different merchant. To qualify, a user may be required to press a MERCHANT OFFER button. A card issuer may then retrieve the promotion for the merchant from a database to learn that the user has opted in for the cross-merchant promotion. Accordingly, the card issuer's processing system may periodically check during the promotional window (or at the end of the promotion) whether the user has made a purchase at the second merchant to receive the double points. The coupon may be utilized at the second merchant to receive the 10% discount. Alternatively, for example, the coupon may also be needed to obtain the double points in addition to the 10%.



FIG. 3 shows card 300 that may include dynamic magnetic stripe communications device 310, buttons 311-315, permanent information 320, display 350, data receiving device 370, and buttons 331-333. Button 331 may be associated with a first line of displayed information on display 350. Button 332 may be associated with a second line of displayed information on display 350. Button 333 may be associated with a third line of displayed information on display 350. Persons skilled in the art will appreciate that buttons 331-333 may actually be virtual buttons on display 350 and display 350 may be a capacitive touch screen. Data receiving device 370 may be a light or sound sensor for receiving information through received light or sound.



FIG. 4 shows card 400 that may include signature line 410 and display 420. Persons skilled in the art will appreciate that card 300 of FIG. 3 may depict the obverse side of a card and card 400 of FIG. 4 may depict the reverse side of a card. Individual components of card 300 of FIG. 3 or card 400 of FIG. 4 may be provided on either side of a card or both sides of a card. More than one instance of a component may be provided on any side of a card (e.g., the same side as a component or a different side as a component). Persons skilled in the art will appreciate that a user may communicate feature codes representative of a user's on-card selection via codes that may be displayed visually and entered into a webpage as part of an online payment. A display may display not only a code for an online payment, but also indicia representative of the feature. In doing so, the user can confirm that the right feature was selected. Persons skilled in the art will appreciate that different codes for the same feature may be displayed and communicated via a dynamic magnetic communications device. In doing so, the security of the card may be increased. Additionally, the same or different codes may be communicated on different tracks of data to represent the selection of a particular feature.



FIG. 5 shows mobile device 500, which may be a mobile telephonic device. Device 500 may include one or more physical buttons (e.g., button 540). Device 500 may include one or more display screens 510. Such a display screen may be touch sensitive such that virtual buttons (e.g., button 530 may be provided) on virtual card 520. Virtual card 520 may appear similar to a physical card described herein. A user may select different virtual cards by, for example, swiping his/her finger across a touch-sensitive display to scroll to the next virtual card. Mobile phone 502 may include a communications device operable to communicate data to a card reader. For example, mobile phone 502 may include an RFID antenna to communicate to an RFID reader, a pop-out IC chip panel operable to be fed into an IC chip reader, or a magnetic communications device having a magnetic emulator operable to communicate magnetic stripe data wirelessly to a read-head of a magnetic stripe reader.


Persons skilled in the art will also appreciate that the present invention is not limited to only the embodiments described. Instead, the present invention more generally involves dynamic information. Persons skilled in the art will also appreciate that the apparatus of the present invention may be implemented in other ways than those described herein. All such modifications are within the scope of the present invention, which is limited only by the claims that follow.

Claims
  • 1. A transaction device, comprising: a communication device operable to communicate transaction data as part of a purchase of a merchant product using a first currency, the transaction data including payment information associated with the purchase and second information; anda user interface operable to provide the second information in the transaction data, the second information indicative of a selection to pay a first monetary value in the first currency to obtain a second currency.
  • 2. The transaction device of claim 1, wherein the second currency is loyalty points.
  • 3. The transaction device of claim 1, wherein the first monetary value is the difference between a second monetary value and a cost of the merchant product.
  • 4. The transaction device of claim 1, wherein the second currency is loyalty points, and the first monetary value is the difference between a second monetary value and a cost of the merchant product.
  • 5. The transaction device of claim 1, wherein the second currency is loyalty points, and the first monetary value is a cost of the merchant product rounded up to a second monetary value.
  • 6. The transaction device of claim 1, wherein the second currency is loyalty points, and the first monetary value is a cost of the merchant product rounded up to the nearest five dollars.
  • 7. The transaction device of claim 1, wherein the transaction device is a mobile telephonic device.
  • 8. The transaction device of claim 1, wherein the transaction device is a powered card.
  • 9. The transaction device of claim 1, wherein the communication device is operable to communicate with a reader.
  • 10. The transaction device of claim 1, wherein the communication device is operable to communicate with a reader.
  • 11. The transaction device of claim 1, wherein the purchase is an online purchase.
CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No. 15/925,624, titled “Advanced Loyalty Applications For Powered Cards and Devices,” filed on Mar. 19, 2018, which is a continuation of U.S. patent application Ser. No. 13/944,455, titled “Advanced Loyalty Applications For Powered Cards and Devices,” filed on Nov. 16, 2017, which is a continuation of U.S. patent application Ser. No. 15/815,648, titled “Advanced Loyalty Applications For Powered Cards and Devices,” filed on Jul. 17, 2013, which is a continuation of U.S. patent application Ser. No. 12/857,766, titled “Advanced Loyalty Applications For Powered Cards and Devices,” filed on Aug. 17, 2010, which claims the benefit of U.S. Provisional Patent Application No. 61/234,583, titled “Advanced Loyalty Applications For Powered Cards and Devices,” filed Aug. 17, 2009, each of which is hereby incorporated by reference herein in their entirety.

US Referenced Citations (410)
Number Name Date Kind
4353064 Stamm Oct 1982 A
4394654 Hofmann-Cerfontaine Jul 1983 A
4614861 Pavlov et al. Sep 1986 A
4667087 Quintana May 1987 A
4701601 Francini et al. Oct 1987 A
4720860 Weiss Jan 1988 A
4786791 Hodama Nov 1988 A
4791283 Burkhardt Dec 1988 A
4797542 Hara Jan 1989 A
5038251 Sugiyama et al. Aug 1991 A
5168520 Weiss Dec 1992 A
5237614 Weiss Aug 1993 A
5276311 Hennige Jan 1994 A
5347580 Molva et al. Sep 1994 A
5361062 Weiss et al. Nov 1994 A
5412199 Finkelstein et al. May 1995 A
5434398 Goldberg Jul 1995 A
5434405 Finkelstein et al. Jul 1995 A
5478994 Rahman Dec 1995 A
5479512 Weiss Dec 1995 A
5484997 Haynes Jan 1996 A
5485519 Weiss Jan 1996 A
5585787 Wallerstein Dec 1996 A
5591949 Bernstein Jan 1997 A
5608203 Finkelstein et al. Mar 1997 A
5623552 Lane Apr 1997 A
5657388 Weiss Aug 1997 A
5834747 Cooper Nov 1998 A
5834756 Gutman et al. Nov 1998 A
5844230 Lalonde Dec 1998 A
5856661 Finkelstein et al. Jan 1999 A
5864623 Messina et al. Jan 1999 A
5907142 Kelsey May 1999 A
5913203 Wong et al. Jun 1999 A
5937394 Wong et al. Aug 1999 A
5955021 Tiffany, III Sep 1999 A
5956699 Wong et al. Sep 1999 A
6025054 Tiffany, III Feb 2000 A
6045043 Bashan et al. Apr 2000 A
6076163 Hoffstein et al. Jun 2000 A
6085320 Kaliski Jul 2000 A
6095416 Grant et al. Aug 2000 A
6130621 Weiss Oct 2000 A
6145079 Mitty et al. Nov 2000 A
6157920 Jakobsson et al. Dec 2000 A
6161181 Haynes, III et al. Dec 2000 A
6176430 Finkelstein et al. Jan 2001 B1
6182894 Hackett et al. Feb 2001 B1
6189098 Kaliski Feb 2001 B1
6199052 Mitty et al. Mar 2001 B1
6206293 Gutman et al. Mar 2001 B1
6240184 Huynh et al. May 2001 B1
6241153 Tiffany, III Jun 2001 B1
6256873 Tiffany, III Jul 2001 B1
6269163 Rivest et al. Jul 2001 B1
6286022 Kaliski et al. Sep 2001 B1
6308890 Cooper Oct 2001 B1
6313724 Osterweil Nov 2001 B1
6389442 Yin et al. May 2002 B1
6393447 Jakobsson et al. May 2002 B1
6411715 Liskov et al. Jun 2002 B1
6446052 Juels Sep 2002 B1
6460141 Olden Oct 2002 B1
6592044 Wong et al. Jul 2003 B1
6607127 Wong Aug 2003 B2
6609654 Anderson et al. Aug 2003 B1
6631849 Blossom Oct 2003 B2
6655585 Shinn Dec 2003 B2
6681988 Stack et al. Jan 2004 B2
6705520 Pitroda et al. Mar 2004 B1
6755341 Wong et al. Jun 2004 B1
6764005 Cooper Jul 2004 B2
6769618 Finkelstein Aug 2004 B1
6805288 Routhenstein et al. Oct 2004 B2
6811082 Wong Nov 2004 B2
6813354 Jakobsson et al. Nov 2004 B1
6817532 Finkelstein Nov 2004 B2
6873974 Schutzer Mar 2005 B1
6895386 Bachman May 2005 B1
6902116 Finkelstein Jun 2005 B2
6970070 Juels et al. Nov 2005 B2
6980969 Tuchler et al. Dec 2005 B1
6985583 Brainard et al. Jan 2006 B1
6991155 Burchette, Jr. Jan 2006 B2
7013030 Wong et al. Mar 2006 B2
7035443 Wong Apr 2006 B2
7039223 Wong May 2006 B2
7044394 Brown May 2006 B2
7051929 Li May 2006 B2
7083094 Cooper Aug 2006 B2
7090138 Rettenmyer et al. Aug 2006 B2
7100049 Gasparini et al. Aug 2006 B2
7100821 Rasti Sep 2006 B2
7111172 Duane et al. Sep 2006 B1
7114652 Moullette et al. Oct 2006 B2
7136514 Wong Nov 2006 B1
7140550 Ramachandran Nov 2006 B2
7163153 Blossom Jan 2007 B2
7195154 Routhenstein Mar 2007 B2
7197639 Juels et al. Mar 2007 B1
7219368 Juels et al. May 2007 B2
7225537 Reed Jun 2007 B2
7225994 Finkelstein Jun 2007 B2
7246752 Brown Jul 2007 B2
7298243 Juels et al. Nov 2007 B2
7334732 Cooper Feb 2008 B2
7337326 Palmer et al. Feb 2008 B2
7346775 Gasparini et al. Mar 2008 B2
7356696 Jakobsson et al. Apr 2008 B1
7357319 Lin et al. Apr 2008 B1
7359507 Kaliski Apr 2008 B2
7360688 Harris Apr 2008 B1
7363494 Brainard et al. Apr 2008 B2
7380710 Brown Jun 2008 B2
7398253 Pinnell Jul 2008 B1
7404087 Teunen Jul 2008 B2
7424570 D'Albore et al. Sep 2008 B2
7427033 Roskind Sep 2008 B1
7454349 Teunen et al. Nov 2008 B2
7461250 Duane et al. Dec 2008 B1
7461399 Juels et al. Dec 2008 B2
7472093 Juels Dec 2008 B2
7472829 Brown Jan 2009 B2
7494055 Fernandes et al. Feb 2009 B2
7502467 Brainard et al. Mar 2009 B2
7502933 Jakobsson et al. Mar 2009 B2
7503485 Routhenstein Mar 2009 B1
7516492 Nisbet et al. Apr 2009 B1
7523301 Nisbet et al. Apr 2009 B2
7530495 Cooper May 2009 B2
7532104 Juels May 2009 B2
7543739 Brown et al. Jun 2009 B2
7559464 Routhenstein Jul 2009 B2
7562221 Nystrom et al. Jul 2009 B2
7562222 Gasparini et al. Jul 2009 B2
7580898 Brown et al. Aug 2009 B2
7584153 Brown et al. Sep 2009 B2
7591426 Osterweil et al. Sep 2009 B2
7591427 Osterweil Sep 2009 B2
7594611 Arrington, III Sep 2009 B1
7602904 Juels et al. Oct 2009 B2
7611054 Bortolin et al. Nov 2009 B2
7631804 Brown Dec 2009 B2
7639537 Sepe et al. Dec 2009 B2
7641124 Brown et al. Jan 2010 B2
7660902 Graham et al. Feb 2010 B2
7784687 Mullen et al. Aug 2010 B2
7784692 Arrington, III Aug 2010 B1
7793851 Mullen Sep 2010 B2
7828207 Cooper Nov 2010 B2
7828220 Mullen Nov 2010 B2
7931195 Mullen Apr 2011 B2
7954705 Mullen Jun 2011 B2
8011577 Mullen et al. Sep 2011 B2
8020775 Mullen et al. Sep 2011 B2
8066191 Cloutier et al. Nov 2011 B1
8074877 Mullen et al. Dec 2011 B2
8121917 Insolia Feb 2012 B2
8172148 Cloutier et al. May 2012 B1
8282007 Cloutier et al. Oct 2012 B1
8286876 Mullen et al. Oct 2012 B2
8302872 Mullen Nov 2012 B2
8382000 Mullen et al. Feb 2013 B2
8393545 Mullen et al. Mar 2013 B1
8413892 Mullen et al. Apr 2013 B2
8424773 Mullen et al. Apr 2013 B2
8439274 Chenot May 2013 B2
8459548 Mullen et al. Jun 2013 B2
8459562 Field et al. Jun 2013 B1
8485437 Mullen et al. Jul 2013 B2
8511548 Mori et al. Aug 2013 B1
8511574 Yen et al. Aug 2013 B1
8517276 Mullen et al. Aug 2013 B2
8523059 Mullen et al. Sep 2013 B1
8579203 Lambeth et al. Nov 2013 B1
8590796 Cloutier et al. Nov 2013 B1
8608083 Mullen et al. Dec 2013 B2
8622309 Mullen et al. Jan 2014 B1
8668143 Mullen et al. Mar 2014 B2
8684265 McGhie Apr 2014 B1
8727219 Mullen May 2014 B1
8733638 Mullen et al. May 2014 B2
8757483 Mullen et al. Jun 2014 B1
8757499 Cloutier et al. Jun 2014 B2
8814050 Mullen et al. Aug 2014 B1
8875999 Mullen et al. Nov 2014 B2
8881989 Mullen et al. Nov 2014 B2
8931703 Mullen et al. Jan 2015 B1
8973824 Mullen et al. Mar 2015 B2
9004368 Mullen et al. Apr 2015 B2
9010630 Mullen et al. Apr 2015 B2
9064255 Mullen et al. Jun 2015 B1
9292843 Mullen et al. Mar 2016 B1
9329619 Cloutier May 2016 B1
9361569 Mullen et al. Jun 2016 B2
9384438 Mullen et al. Jul 2016 B2
9547816 Mullen et al. Jan 2017 B2
9639796 Mullen et al. May 2017 B2
9684861 Mullen et al. Jun 2017 B2
9697454 Mullen et al. Jul 2017 B2
9704088 Mullen et al. Jul 2017 B2
9704089 Mullen et al. Jul 2017 B2
9727813 Mullen et al. Aug 2017 B2
9805297 Mullen et al. Oct 2017 B2
9852368 Yen et al. Dec 2017 B1
9928456 Cloutier et al. Mar 2018 B1
9953255 Yen et al. Apr 2018 B1
10032100 Mullen et al. Jul 2018 B2
10095974 Mullen et al. Oct 2018 B1
10169692 Mullen et al. Jan 2019 B2
10176419 Cloutier et al. Jan 2019 B1
10181097 Mullen et al. Jan 2019 B1
10198687 Mullen et al. Feb 2019 B2
10223631 Mullen et al. Mar 2019 B2
10255545 Mullen et al. Apr 2019 B2
10325199 Mullen et al. Jun 2019 B2
10430704 Mullen et al. Oct 2019 B2
10467521 Mullen et al. Nov 2019 B2
10496918 Mullen et al. Dec 2019 B2
10579920 Mullen et al. Mar 2020 B2
10693263 Mullen et al. Jun 2020 B1
20010034702 Mockett et al. Oct 2001 A1
20010039511 Duckworth et al. Nov 2001 A1
20010047335 Arndt et al. Nov 2001 A1
20020059114 Cockrill et al. May 2002 A1
20020082989 Fife et al. Jun 2002 A1
20020096570 Wong et al. Jul 2002 A1
20020120583 Keresman, III et al. Aug 2002 A1
20030034388 Routhenstein et al. Feb 2003 A1
20030052168 Wong Mar 2003 A1
20030057278 Wong Mar 2003 A1
20030069846 Marcon Apr 2003 A1
20030116635 Taban Jun 2003 A1
20030152253 Wong Aug 2003 A1
20030163287 Vock et al. Aug 2003 A1
20030173409 Vogt et al. Sep 2003 A1
20030179909 Wong et al. Sep 2003 A1
20030179910 Wong Sep 2003 A1
20030226899 Finkelstein Dec 2003 A1
20040010462 Moon et al. Jan 2004 A1
20040035942 Silverman Feb 2004 A1
20040133787 Doughty Jul 2004 A1
20040162732 Rahim et al. Aug 2004 A1
20040172340 Bishop Sep 2004 A1
20040172535 Jakobsson Sep 2004 A1
20040177045 Brown Sep 2004 A1
20050021400 Postrel Jan 2005 A1
20050043997 Sohata et al. Feb 2005 A1
20050080747 Anderson et al. Apr 2005 A1
20050086160 Wong et al. Apr 2005 A1
20050086177 Anderson et al. Apr 2005 A1
20050116026 Burger et al. Jun 2005 A1
20050119940 Concilio et al. Jun 2005 A1
20050133590 Rettenmyer et al. Jun 2005 A1
20050154643 Doan et al. Jul 2005 A1
20050228959 D'Albore et al. Oct 2005 A1
20060000900 Fernandes et al. Jan 2006 A1
20060037073 Juels et al. Feb 2006 A1
20060041759 Kaliski et al. Feb 2006 A1
20060085328 Cohen et al. Apr 2006 A1
20060091223 Zellner May 2006 A1
20060161435 Atef et al. Jul 2006 A1
20060163353 Moulette et al. Jul 2006 A1
20060174104 Crichton et al. Aug 2006 A1
20060196931 Holtmanns et al. Sep 2006 A1
20060249575 Turner et al. Nov 2006 A1
20060256961 Brainard et al. Nov 2006 A1
20070034700 Poidomani et al. Feb 2007 A1
20070114274 Gibbs et al. May 2007 A1
20070124321 Szydlo May 2007 A1
20070129955 Dalmia Jun 2007 A1
20070152070 D'Albore Jul 2007 A1
20070152072 Frallicciardi et al. Jul 2007 A1
20070153487 Frallicciardi et al. Jul 2007 A1
20070174614 Duane et al. Jul 2007 A1
20070241183 Brown et al. Oct 2007 A1
20070241201 Brown et al. Oct 2007 A1
20070256123 Duane et al. Nov 2007 A1
20070265912 Belanger Nov 2007 A1
20070192249 Biffle et al. Dec 2007 A1
20070291753 Romano Dec 2007 A1
20080005510 Sepe et al. Jan 2008 A1
20080008315 Fontana et al. Jan 2008 A1
20080008322 Fontana et al. Jan 2008 A1
20080010675 Massascusa et al. Jan 2008 A1
20080016351 Fontana et al. Jan 2008 A1
20080019507 Fontana et al. Jan 2008 A1
20080021785 Hessburg Jan 2008 A1
20080028447 O'Malley et al. Jan 2008 A1
20080029607 Mullen Feb 2008 A1
20080035738 Mullen Feb 2008 A1
20080040271 Hammad et al. Feb 2008 A1
20080040276 Hammad et al. Feb 2008 A1
20080054068 Mullen Mar 2008 A1
20080054079 Mullen Mar 2008 A1
20080054081 Mullen Mar 2008 A1
20080058016 Di Maggio et al. Mar 2008 A1
20080059303 Fordyce Mar 2008 A1
20080059379 Ramaci et al. Mar 2008 A1
20080065555 Mullen Mar 2008 A1
20080096326 Reed Apr 2008 A1
20080116285 Shoemaker May 2008 A1
20080126398 Cimino May 2008 A1
20080128515 Di Iorio Jun 2008 A1
20080148394 Poidomani et al. Jun 2008 A1
20080201264 Brown et al. Aug 2008 A1
20080209550 Di Iorio Aug 2008 A1
20080288699 Chichierchia Nov 2008 A1
20080294930 Varone et al. Nov 2008 A1
20080302869 Mullen Dec 2008 A1
20080302876 Mullen Dec 2008 A1
20080302877 Musella et al. Dec 2008 A1
20090013122 Sepe et al. Jan 2009 A1
20090036147 Romano Feb 2009 A1
20090046522 Sepe et al. Feb 2009 A1
20090108064 Fernandes et al. Apr 2009 A1
20090150295 Hatch et al. Jun 2009 A1
20090152365 Li et al. Jun 2009 A1
20090159663 Mullen et al. Jun 2009 A1
20090159667 Mullen et al. Jun 2009 A1
20090159668 Mullen et al. Jun 2009 A1
20090159669 Mullen et al. Jun 2009 A1
20090159670 Mullen et al. Jun 2009 A1
20090159671 Mullen et al. Jun 2009 A1
20090159672 Mullen et al. Jun 2009 A1
20090159673 Mullen et al. Jun 2009 A1
20090159680 Mullen et al. Jun 2009 A1
20090159681 Mullen et al. Jun 2009 A1
20090159682 Mullen et al. Jun 2009 A1
20090159688 Mullen et al. Jun 2009 A1
20090159689 Mullen et al. Jun 2009 A1
20090159690 Mullen et al. Jun 2009 A1
20090159696 Mullen Jun 2009 A1
20090159697 Mullen et al. Jun 2009 A1
20090159698 Mullen et al. Jun 2009 A1
20090159699 Mullen et al. Jun 2009 A1
20090159700 Mullen et al. Jun 2009 A1
20090159701 Mullen et al. Jun 2009 A1
20090159702 Mullen Jun 2009 A1
20090159703 Mullen et al. Jun 2009 A1
20090159704 Mullen et al. Jun 2009 A1
20090159705 Mullen et al. Jun 2009 A1
20090159706 Mullen et al. Jun 2009 A1
20090159707 Mullen et al. Jun 2009 A1
20090159708 Mullen et al. Jun 2009 A1
20090159709 Mullen Jun 2009 A1
20090159710 Mullen et al. Jun 2009 A1
20090159711 Mullen et al. Jun 2009 A1
20090159712 Mullen et al. Jun 2009 A1
20090159713 Mullen et al. Jun 2009 A1
20090160617 Mullen et al. Jun 2009 A1
20090242648 Di Sirio et al. Oct 2009 A1
20090244858 Di Sirio et al. Oct 2009 A1
20090253460 Varone et al. Oct 2009 A1
20090255996 Brown et al. Oct 2009 A1
20090290704 Cimino Nov 2009 A1
20090303885 Longo Dec 2009 A1
20090308921 Mullen Dec 2009 A1
20100179870 Postrel Jul 2010 A1
20110028184 Cooper Feb 2011 A1
20110272465 Mullen et al. Nov 2011 A1
20110272466 Mullen et al. Nov 2011 A1
20110272467 Mullen et al. Nov 2011 A1
20110272471 Mullen Nov 2011 A1
20110272472 Mullen Nov 2011 A1
20110272473 Mullen et al. Nov 2011 A1
20110272474 Mullen et al. Nov 2011 A1
20110272475 Mullen et al. Nov 2011 A1
20110272476 Mullen et al. Nov 2011 A1
20110272477 Mullen et al. Nov 2011 A1
20110272478 Mullen Nov 2011 A1
20110272479 Mullen Nov 2011 A1
20110272480 Mullen et al. Nov 2011 A1
20110272481 Mullen et al. Nov 2011 A1
20110272482 Mullen et al. Nov 2011 A1
20110272483 Mullen et al. Nov 2011 A1
20110272484 Mullen et al. Nov 2011 A1
20110276380 Mullen et al. Nov 2011 A1
20110276381 Mullen et al. Nov 2011 A1
20110276416 Mullen et al. Nov 2011 A1
20110276424 Mullen Nov 2011 A1
20110276425 Mullen Nov 2011 A1
20110276436 Mullen et al. Nov 2011 A1
20110276437 Mullen et al. Nov 2011 A1
20110278364 Mullen et al. Nov 2011 A1
20110282753 Mullen et al. Nov 2011 A1
20120286037 Mullen et al. Nov 2012 A1
20120318871 Mullen et al. Dec 2012 A1
20120326013 Cloutier et al. Dec 2012 A1
20130020396 Mullen et al. Jan 2013 A1
20130282573 Mullen et al. Oct 2013 A1
20130282575 Mullen et al. Oct 2013 A1
20150186766 Mullen et al. Jul 2015 A1
20160180209 Mullen et al. Jun 2016 A1
20160239735 Mullen et al. Aug 2016 A1
20160283837 Mullen et al. Sep 2016 A1
20160307085 Mullen et al. Oct 2016 A1
20160335529 Mullen et al. Nov 2016 A1
20160342876 Mullen et al. Nov 2016 A1
20160342877 Mullen et al. Nov 2016 A1
20160342878 Mullen et al. Nov 2016 A1
20160342879 Mullen et al. Nov 2016 A1
20160342880 Mullen et al. Nov 2016 A1
20170286817 Mullen et al. Oct 2017 A1
20170300796 Mullen et al. Oct 2017 A1
20190042903 Cloutier et al. Feb 2019 A1
20190065928 Mullen et al. Feb 2019 A1
20190197387 Mullen et al. Jun 2019 A1
20190340484 Mullen et al. Nov 2019 A1
20200082383 Mullen et al. Mar 2020 A1
Foreign Referenced Citations (8)
Number Date Country
05210770 Aug 1993 JP
WO9852735 Nov 1998 WO
WO0247019 Jun 2002 WO
WO06066322 Jun 2006 WO
WO06080929 Aug 2006 WO
WO06105092 Oct 2006 WO
WO06116772 Nov 2006 WO
WO08064403 Jun 2008 WO
Non-Patent Literature Citations (4)
Entry
The Bank Credit Card Business. Second Edition, American Bankers Association, Washington, D.C., 1996.
A Day in the Life of a Flux Reversal. http://www.phrack/org/issues.html?issue=37&id=6#article. As viewed on Apr. 12, 2010.
Dynamic Virtual Credit Card Numbers. http://homes.cerias.purdue.edu/˜jtli/paper/fc07.pdf. As viewed on Apr. 12, 2010.
English translation of JP 05210770 A.
Provisional Applications (1)
Number Date Country
61234583 Aug 2009 US
Continuations (4)
Number Date Country
Parent 15925624 Mar 2018 US
Child 16153594 US
Parent 15815648 Nov 2017 US
Child 15925624 US
Parent 13944455 Jul 2013 US
Child 15815648 US
Parent 12857766 Aug 2010 US
Child 13944455 US