This invention relates to magnetic cards and devices and associated payment systems.
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.
A card may be provided with a button in which the activation of the button causes a code to be communicated through a dynamic magnetic stripe communications device (e.g., after a read-head detector on the card detects a read-head of a magnetic stripe reader). The code may be indicative of a user pressing a particular button on a card or other device.
A card may be provided with two buttons. One button may, for example, be utilized for a user to communicate information through a card indicative of a user's desire to pay for a purchase with credit. In turn, the user may earn points proportional to the dollar amount of the purchase. Another button may be provided indicative of a user's desire to pay for a purchase with credit, but foregoing the earning of points. In exchange for foregoing points, the user may be provided with one, or more, chances to win one or more prizes. The number of chances earned, for example, may be proportional to the amount of the purchase. The chances to win may be provided at purchase authorization or purchase settlement. Prizes may be provided at purchase authorization or purchase settlement. Particularly, magnetic stripe information associated with a user's desire to forego points for chances to win prizes may be communicated via a magnetic stripe message (e.g., discretionary data in a magnetic stripe message). This discretionary data may be communicated at payment authorization or settlement to an entity (e.g., card issuer) with servers managing the chances to win and/or prizes.
An instant winner functionality may be provided on a card or other device (e.g., a mobile telephonic device). For example, a card may utilize read-head detectors to determine when the card is swiped by a user. An algorithm may reside on a card that provides the card with a chance to be an instant winner with every swipe. Such an algorithm may, for example, randomly pre-determine particular swipes that are instant winners. Alternatively, for example, such an algorithm may, for example, randomly determine, independently after each swipe, whether the card is an instant winner. An instant winner may be determined, for example, based on time. For example, an algorithm may provide an instant winner on the swipe after a particular period of time passes. A card may also, for example, determine if an instant winner has occurred based on the activation of a card (e.g., a user turning a card ON by pressing a button or entering a particular sequence of manual input into an array of buttons on the card).
An instant winner may, for example, display a winning code on a display of a card that may be entered, for example, on a website (e.g., an account page of the user). The code may correlate to a particular prize. Alternatively, for example, the code may be utilized to win a prize that is chosen randomly by the website.
A user may be provided with a code for entry into a card (or other device) with a purchase. Such a code may be provided via a printed, online, or emailed receipt. Accordingly, particular merchants may fund prize-based games and provide codes for use with such prize-based games. Accordingly, for example, a user may enter a code using buttons on a card. The card may, in turn, utilize the code with an instant winner algorithm. The algorithm may, for example, utilize the game code to randomly, independently, determine whether a card is an instant winner. The algorithm may, for example, utilize the game code to increase the count of received game codes (where an instant winner is triggered based on a pre-determined count). The algorithm may, for example, utilize the game code to translate the game code into a prize code (e.g., for entry onto an online website). Both the game code and the prize code may be utilized online, for example, to redeem a prize via a remote server (e.g., of a card issuer). A prize may take many forms such as, for example, gift certificates, particular amounts of points, plane tickets, statement credits, coupons, discounts, or hotel stays.
A remote server may keep count of the transactions processed for a card. An instant winner algorithm on a card may be similar to an instant winner algorithm on a remote server. Accordingly, such an instant winner algorithm may be tamper-proof for algorithms that, for example, determine a winner based on transactions. A card that is swiped more times than transactions occur may notify a user of an instant winner before the user is actually an instant winner. Accordingly, a remote server may include a range of transactions in which an instant winner code can be redeemed. Moreover, the remote server may notify a user that the instant winner code was redeemed earlier than expected by the remote server and may, therefore, deny the redemption until the appropriate number of transactions have been processed.
A user may associate a telephone number of his/her mobile telephonic device to a card on a remote server (e.g., the server of a card issuer). Accordingly, an instant winner message may be communicated (e.g., via an email or text message) to the mobile telephonic device at purchase authorization or settlement. Similarly, a user may associate an email address to a card on a remote server (e.g., the server of a card issuer). In doing so, for example, an instant winner message may be communicated to the email address. An instant winner message may include a description of the prize and instructions for redeeming the prize (e.g., a prize code).
An instant winner may be determined, for example, based at least in part on time. Particularly, a card may be programmed with a pre-determined set of time periods in which an instant win occurs. When an instant win occurs, for example, an instant winner code may be provided (e.g., via a display on a card). Alternatively, for example, no code may be provided. A remote server may be synched with the card, with respect to time, such that a user merely logs into his/her account webpage to receive information about the instant win. An instant win based on time (or any other instant win) may, for example, expire. For example, the instant win for a card may expire within 24, 48, or 72 hours. An instant win may be recognizable by a user by, for example, a particular screen on a display or the activation of one or more sources of light (e.g., LEDs). For example, a source of light may blink during the redemption period of an instant win. So long as, for example, the user goes online to his/her account webpage for the card within the redemption period, the user may obtain a prize associated with the instant win. The prize may be chosen randomly.
Prizes may be tiered and may be associated with, for example, the type of card a user carries (e.g., a card with a certain annual fee may have a different prize tier than a card with a different annual fee). Prizes may be tiered based on, for example, the amount of transaction volume associated with a card for a period of time (e.g., the preceding year). Users may also purchase higher tiers of prizes with points. The same prizes may be offered in all tiers, but the odds of winning higher value prizes may change with each tier. Prizes may also correlate to the transaction volume and/or the type of merchant for a particular purchase that triggered, for example, an instant win. For example, a $10 purchase at a gas station may provide a different prize than a $10 purchase at a fast food restaurant. Prizes may be proportional to the amount of a particular purchase and may be associated with a particular type of transaction. For example, a prize may be a particular percentage (e.g., approximately 5-25% such as approximately 10%) off the next purchase a user makes in the merchant category associated with the prize. A user may be notified of the type of prize at time of winning the prize or at a time after the prize is redeemed. If the user is aware that he/she has won a prize, but does not know what the prize is, the user may functionally receive a whimsical and festive benefit from the prize on two occasions (e.g., at winning and at redemption).
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:
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, one or more codes may be stored on memory 142 that is displayed based on an instant winner algorithm such that a user may redeem such codes for prizes. Such a code may be communicated, for example, in a magnetic stripe message, RFID message, and/or exposed chip message (e.g., EMV message) from a card. Memory 142 may also store types of actions that a user may select. Each type of action may be associated with a button. Or, for example, a user may scroll through a list of actions on a display on the front of the card (e.g., using buttons to scroll through the list). As per another example, a code may be stored indicative of a user's desire to pay with credit or forego points in an attempt to earn a prize. Such a code may be communicated, for example, in a magnetic stripe message, RFID message, and/or exposed chip message (e.g., EMV message) from a card.
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.
A card may randomly, based on time, indicate to a user that the user has won a prize. Such a feature may occur, for example, based on time. A user may have a period of time to make a purchase to claim the prize. For example, a user may have approximately, 24, 48, or 72 hours to claim a prize. Accordingly, a user may open his/her wallet or purse and see that the user has won a prize. The user may then make a purchase within a pre-determined amount of time by pressing a particular button (e.g. a “redeem prize” button). Information associated with this user selection may be communicate to a remote server (e.g., of a card issuer) via a magnetic stripe message from a dynamic magnetic stripe communications device, an RFID message from an RFID antenna, or a chip message from an exposed IC chip (e.g., an EMV chip). A card may allow for prizes, or chances to win prizes, to be earned in multiple ways. For example, any of the prize algorithms or prize chance algorithms discussed herein may be provided on a card. Accordingly, a card may provide a prize randomly based at least in part on time. The card may also allow a user to forego earning points for additional chances to win prizes.
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 website 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. Additionally, the card may receive wireless communications signals (e.g., WiFi signals) associated with the modifications and additions).
A light receiver may be utilized in a variety of ways. For example, a mobile telephonic phone may have an application that is associated to a user's card. After a user makes a purchase, data may be pushed to the application indicative of whether or not a user won a prize. The application may also be loaded by a user such that the application pulls information from remote servers indicative of any recent purchases and, for example, prizes associated with those purchases. A prize may include one or more chances to win a prize via a particular game. For example, an application on a mobile telephonic device may provide a person with chances to partake in a particular game on the phone, where the game is associated with the type of merchant associated with the purchase and the chances to win are associated with the amount of the purchase. For example, a $10 purchase at a gas station may cause the phone application to allow a user to partake in a race of virtual cars for prizes one time. A $100 purchase at an online store may allow a user to partake in a spin the wheel for reward point games ten times. Prizes may take the form, for example, of discounts or coupons. Such discounts and coupons can take the form of codes that may be redeemed online or barcodes that may be redeemed in a store via a barcode scanner by displaying the barcodes on the display of the mobile telephonic device. Such codes may be communicated to a card via light pulses that are provided by a mobile telephonic device's application to communicate information to one or more light sensors on a card.
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 then those described herein. All such modifications are within the scope of the present invention, which is limited only by the claims that follow.
This application claims the benefit of U.S. Provisional Patent Application No. 61/254,727, titled “Games, Prizes, and Entertainment for Powered Cards and Devices,” filed Oct. 25, 2009, which is hereby incorporated by reference herein in its entirety.
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 |
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 |
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 |
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 | Liu 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 |
7602904 | Juels et al. | Oct 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 |
7828207 | Cooper | Nov 2010 | B2 |
20010034702 | Mockett et al. | Oct 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 |
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 |
20040035942 | Silverman | Feb 2004 | A1 |
20040133787 | Doughty | Jul 2004 | A1 |
20040162732 | Rahim et al. | Aug 2004 | A1 |
20040172535 | Jakobsson | Sep 2004 | A1 |
20040177045 | Brown | Sep 2004 | A1 |
20050043997 | Sahota 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 |
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 |
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 |
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 |
20070192249 | Biffle et al. | Aug 2007 | A1 |
20070241183 | Brown et al. | Oct 2007 | A1 |
20070241201 | Brown et al. | Oct 2007 | A1 |
20070256123 | Duane et al. | Nov 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 |
20080028447 | O'Malley et al. | Jan 2008 | A1 |
20080040271 | Hammad et al. | Feb 2008 | A1 |
20080040276 | Hammad et al. | Feb 2008 | A1 |
20080058016 | Di Maggio et al. | Mar 2008 | A1 |
20080059379 | Ramaci et al. | 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 |
20080302877 | Musella et al. | Dec 2008 | A1 |
20080308627 | Sines 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 |
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 |
20110028184 | Cooper | Feb 2011 | A1 |
Number | Date | Country |
---|---|---|
05210770 | Aug 1993 | JP |
WO9852735 | Nov 1998 | WO |
WO0247019 | Jun 2002 | WO |
WO2006066322 | Jun 2006 | WO |
WO2006080929 | Aug 2006 | WO |
WO2006105092 | Oct 2006 | WO |
WO2006116772 | Nov 2006 | WO |
WO2008064403 | Jun 2008 | WO |
Entry |
---|
U.S. Appl. No. 60/594,300, Poidomani et al. |
U.S. Appl. No. 60/675,388, Poidomani et al. |
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. |
Number | Date | Country | |
---|---|---|---|
61254727 | Oct 2009 | US |