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 include one or more light transmitters and light receivers. The light transmitters and receivers may be the same, or different, devices. A light transmitter may be able to transmit visible, infrared, or visible and infrared light. A light transmitter may be able to transmit additional types of light (e.g., ultraviolet light). A light receiver may be able to receive visible, infrared, or visible and infrared light. A light receiver may be able to transmit additional types of light (e.g., ultraviolet light). A light transmitter may take the form of, for example, an LED. A light receiver may take the form of, for example, a photo-transistor, photo-diode, or photo-resistor.
A card may include a light transmitter (e.g., an infrared transmitter) about one end of that card and a light receiver (e.g., an infrared receiver) about the opposite end of that card. In doing so, the light transmitter and receiver may be located at a distance from one another (e.g., greater than half an inch, one inch, one-half an inch, two inches, or two and a half inches away from one another) such that the light receiver cannot pick up transmissions from the light transmitter. For example, a light receiver may be located along about a top edge of a card at a particular distance from one side edge (e.g., 1.067 inches from one side edge). A light transmitter may also be located about the top edge at that same particular distance from the other side edge (e.g., 1.067 inches from the other side edge). Accordingly, a programming fixture may include a light transmitter spaced similarly from a light receiver such that the light receiver of the programming fixture may communicate with the light transmitter of the card and the light transmitter of the programming fixture may communicate with the light receiver of that same card. In this manner, cards may be moved through the programming fixture and stopped in front of the programming fixture for programming. A programming module may be included with multiple programming fixtures such that multiple programming fixtures may simultaneously program cards.
A personalization machine may include multiple modules (e.g., multiple programming modules) such that cards may be personalized utilizing the personalization machine. For example, a personalization machine may include one or more modules for embossing a card, modules for printing indicia on a card, modules for writing to a static magnetic stripe of a card, modules for reading from a static magnetic stripe of a card, modules for reading and/or writing information to an IC chip (e.g., EMV chip) of a card, modules for reading and/or writing information to a Radio-Frequency Identification Tag of a card, modules for laser engraving to a card, modules for flex-testing a card, modules for placing holograms onto a card, modules for placing protective coatings on a card, modules for optically reading physical information on a card (e.g., a credit card number), and modules for placing a material operable to receive an ink-based signature/mark on a card.
The personalization machine may be able to communicate with a remote server to, for example, download information to be programmed into a card. The personalization machine may be able to communicate with a remote server to, for example, upload information confirming data programmed into a card.
A card may include a universal identification number. In this manner, multiple card accounts may be programmed into a card. A universal identification number may be supplied by a card (e.g., via a light transmitter) during programming to identify a universal card number. Such information may be communicated to a remote server, in which one or more multiple card account information (e.g., magnetic stripe data for multiple card accounts), may be communicated to the personalization machine and then communicated to a card via a light transmitter.
The magnetic stripe data may be stored in a memory of a card during programming. Application code may be pre-programmed into the card before programming by the personalization machine such that the application code is not programmed when the magnetic stripe data is programmed into the card. Particular magnetic stripe data may then be emulated, for example, through a magnetic emulator located on a card in accordance with the previously programmed application code. Additional data may be stored during programming of magnetic stripe data. For example, information utilized by application code other than magnetic stripe data may be programmed. For example, a particular one or more security codes for a particular universal identification number may be programmed into a card. The remote server may keep track of the one or more security codes programmed into a particular card (e.g., using a universal identification number or a payment card account number such as a credit card number).
Numerous types of light may be utilized to program a card. For example, infrared light of a particular frequency may be utilized. All cards programmed by a particular module may be programmed, for example, utilizing the same frequency of infrared light. Alternatively, for example, different cards may be programmed utilizing different frequencies of light. In doing so, multiple cards may be programmed in close proximity to one another and different frequencies of communication for each card may protect against infrared cross-talk within the programming module.
A card may include an identification number (e.g., a universal identification number or a payment card account number such as a credit card account number) that is optically read by a module of a personalization machine. A remote database may store a pre-programmed infrared communications frequency for that card. Accordingly, the personalization machine may receive the frequency from the remote database, such that the card and IR programming module of the personalization machine may each know the frequency of communication without the need of, for example, directly communicating with one another.
A card's processor may be able to perform functionalities as soon as, for example, a battery is coupled to the processor. The card's processor may include application code on a memory located internal to the card's processor or, for example, may be coupled to a memory device located external to the card's processor. This internal or external memory may, for example, include a particular amount of free space for personalization information (e.g., magnetic stripe data).
The application code may instruct the processor to enter a pre-programming mode. In this mode, all external communication devices (e.g., IC chip, RFID, and dynamic magnetic stripe communications device) may be ignored by the processor other than, for example, the light transmitter(s) and light receiver(s) utilized for programming. In the pre-programming mode, the card may be placed in a sleep mode by the processor until an appropriate light-based signal is received from a programming device to put the card into a programming mode. Such a light-based signal may cause an interrupt to the processor to awaken the processor from the sleep mode. The card may then be programmed during the programming mode. During the programming mode, the card may receive and store personal data. Other functions (e.g., ability to utilize buttons, dynamic magnetic stripe communications device, RFID, or IC chip) may be inactive. After programming is complete, the card may be placed into a post-programming mode. Here, for example, the card may be able to be operated manually by a user in accordance with the application code.
A messaging protocol may be provided such that a card may communicate with a programming fixture of a programming module of a personalization machine. Such a messaging protocol may be utilized to authenticate messages sent between a card and a programming module (e.g., asynchronous serial messages). A programming module may initiate a handshaking process by sending a message to a card. In turn, a card may respond. The identity of the programming module may be included in the message sent by the module.
Similarly, the programming module may include a security key for the particular card. The identity of the card may be known by the programming module because, for example, the programming module may optically read an identification number on the front of the card. Accordingly, the programming module may optically determine an identity of a card, retrieve a security key from a remote server based on the determined identity, and then transmit the security key (or a module-specific key based off the security key) to the card. The card may, in turn, respond by sending a proper response key after the card has confirmed the receipt of the appropriate security key. The programming module may confirm the response key by, for example, retrieving the appropriate response key from a remote server and comparing the response key received from the card to the response key obtained from the remote server.
A message between a card and a programming module may also be utilized, for example, to communicate information to another card. A message may include a portion that includes information regarding the function of a message (e.g., header message, synchronization message) as well as a portion that includes content associated with that function.
One messaging protocol is provided where the card does not provide a response to a programming module. Messages and protocols may include, for example, error checking (e.g., a checksum or CRC), password verification, and byte count matches. Messages may be communicated, for example, in an encrypted form such that the receiving device decrypts the encrypted message.
A programming module may capture cards and place them in specific orientations with respect to programming fixtures such that the communication ports (e.g., IR transmitters and/or receivers) of each card are placed in the proximity of the communication ports (e.g., IR transmitters and/or receivers) of each programming fixture. A global IR transmitter may be, for example, utilized to program more than one card. Particularly, such a global IR transmitter may transmit information to the IR receivers of multiple cards.
Multiple types of data may be communicated to a card. For example, one or more account numbers, expiration dates, user names, and other data (e.g., magnetic stripe track data) may be loaded into a card using communication ports on the card (e.g., IR transmitters and/or receivers). A programming module may timeout after a particular time (e.g., more than two seconds) and retry sending a message if, for example, an acknowledgement was expected by the programming module, but not received by the programming module.
After data has been transferred, the IR receiver interrupts to the processor may be disabled. In doing so, for example, the IR receiver may no longer be utilized such that the IR receiver cannot provide instructions to change data stored on a card or other device. A card may include firmware and this firmware may be programmed into the card before programming (e.g., at a different facility such as an assembling facility). Personal data may be placed in an area of memory (or a separate memory) for personal data. Such memory may be erased, and confirmed to be erased, as well as properly formatted when the firmware for the card is programmed. A processor may erase the programming routines on a card after personal data is programmed to ensure that personal data may not be entered into a card via the IR receiver after programming has occurred.
Asynchronous serial formats may be utilized in messages of particular protocols. Such a format may have a particular baud rate or bit rate that may be observed by both the transmitter and receiver. Accordingly, a clocking device (e.g., a clocking device having a crystal) may be included to provide accurate synchronization. Synchronization characters may be provided in messages (e.g., in particular locations of messages) to allow for adjustments to provide a synchronized programmer and card. A preamble sequence of equal length bits may be provided in messages such that a card, or programming module may detect and synchronize to the desired baud rate. An IR receiver interrupt service routine may be provided to measure, for example, a preamble of a message and calculate a particular baud rate compatible with a programmer.
The performance of a card may be evaluated by a personalization machine. For example, a personalization machine may test a dynamic magnetic stripe communications device located on a card programmed with personal data to confirm the dynamic magnetic stripe communications device is working and that the correct magnetic stripe data was programmed into the card. Additional tests may include verifying that buttons on a card are not shorted and operate properly and that light emitting diodes are capable of emitting light. A display of a card may also be cycled, for example, to determine proper operation of a display. An optical system may be utilized, for example, to determine that the display of a card is operating properly.
A serial number may be programmed into each card. A personalization process may include a customer approved function to properly format a portion of memory (e.g., flash memory) utilized for personalization data. In providing a particular format, for example, the security of a personalization protocol and the security to protect against attempts to reprogram a card may be increased.
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:
Card 100 may include one or more buttons such as buttons 130-134. Such buttons may be mechanical buttons, capacitive buttons, or a combination of mechanical and capacitive buttons. Card 100 may include button 199. Button 199 may be used, for example, to place card 100 into a programming mode to receive programming (e.g., programming of a user's personal payment card data). A button (e.g., button 199) may be utilized in a variety of ways (e.g., to communicate information through a dynamic magnetic communications device indicative of a user's intent to purchase a particular product with points instead of credit).
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 to define programming rules for a card). 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 purchaser'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).
Memory 142 may be partially implemented as non-volatile memory. Accordingly, memory 142 may be pre-programmed with, for example, a programming protocol that may define how data (e.g. IR data) may be received by data input 153 and how data (e.g., IR data) may be transmitted by data output 154.
Memory 142 may receive data as received from data input 153 (e.g., an IR receiver). For example, data may be received by memory 142 that may be indicative of a universal identification number associated with card 100. Such a universal identification number may, for example, uniquely identify card 100. Memory 142 may receive data via data input 153 that may represent a security code that may be associated with the universal identification number of card 100.
Memory 142 may provide data, such as a universal identification number associated with card 100, to data output 154. Accordingly, data output 154 (e.g., an IR transmitter) may transmit such a universal identification number to, for example, a personalization machine. The personalization machine may relay the universal identification number to a remote server, which in turn, may respond with personalization data that may be associated with the universal identification number of card 100.
Memory 142 may receive data from data input 153 (e.g., an IR receiver) that may be associated with a universal identification number of card 100. For example, one or more account numbers, user names, discretionary data, and expiration dates may be stored within memory 142. Such data may be provided by card 100, for example, as one or more tracks of magnetic stripe data during a transaction (e.g., a purchase transaction).
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 magnetic material and/or a non-magnetic material).
Each electromagnetic field generator may communicate information serially to a receiver of a magnetic stripe reader for a 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). The 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.
For example, card 210 is provided that includes transmitter 211 (or a receiver) on the left side of a face of card 210 within the proximity of one end of card 210 and receiver 212 (or a transmitter) on the right side of the same face of card 210 within the proximity of the other end of card 210. Such components may be provided to communicate information from the side that a dynamic magnetic communications device communicates from (e.g., for a dynamic magnetic communications device that communicates from one side of a card) or the opposite side. For example, such components may be provided to communicate information from a side of a card that includes a payment account number (e.g., a printed or etched credit card number), expiration date, association hologram, and customer name. A receiver and transmitter may be provided that is operable to communicate information from both sides of a card as well as along the edges of a card.
Card 220 includes transmitter 221 and receiver 222 located on opposite longitudal sides of a card within the proximity of a center line of card 220. Similarly, card 230 includes transmitter 231 and receiver 232 located on the top and bottom of a card within proximity of a longitudal center line. Card 240 includes transmitter and receiver 241 that may, for example, both transmit and receive information.
Persons skilled in the art will appreciate that changing the locations of such components may provide advantageous benefits. For example, one or more transmitters and/or receivers may be placed above a magnetic stripe or dynamic magnetic communications device such that the transmitters and/or receivers are located in space between the stripe/device and the edge of a card (e.g., in the approximately 0.223 inches space shown in card 210). Such placement may occur on a printed circuit board including, for example, a processor, buttons, and display and may be provided on the side of the printed circuit board facing displayed personal data such as payment card number, customer name, and expiration date. In doing so, for example, components, such as displays and buttons, may be more easily moved around interior areas of a card without having to move such transmitters and receivers.
Persons skilled in the art will appreciate that programming receivers and transmitters may be utilized to provide just the functionality of programming personal data into a card and/or for additional functions. For example, application code may be programmed utilizing such receivers and/or transmitters. Additionally, cards may communicate with other cards using such receivers and/or transmitters. Furthermore, for example, a card may receive information using a receiver from a display (e.g., a blinking virtual object communicating information via light pulses from a display of a mobile telephonic device or a laptop computer display screen). Similarly, a card may communicate information via light to a camera of a computing device. For example, a video camera may receive information via light pulses from a card. A camera may receive information from a photograph taken of a card depending on, for example, the color of light and/or intensity of light.
Accordingly, cards 210-240 may include a light sensing device (e.g., a programming receiver) 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.
Process 410 may include, for example, step 411, in which a batch of cards may be moved into a programming module for programming. Step 412 may include programming cards individually. Step 413 may include verifying that all cards in a batch have been programmed. Step 414 may include moving the programmed batch of cards out of the programming module so that a new batch of cards may be moved into the programming module in step 415.
Process 420 may be provided, in which information printed on a card may be optically read in step 421 (e.g., via a barcode or optical imaging of printed alphanumerics such as a printed number). Step 422 includes retrieving personal data (e.g., from a remote server) to program into a particular card (e.g., based on the optically read information). Step 423 may include communicating information (e.g., retrieved personal data) via a communications channel (e.g., light) to a card. Additional data may be programmed into card in step 424.
Persons skilled in the art will appreciate that the card may include application code indicative of information used by the card so that the card may request, for example, additional information (e.g., to be retrieved from a remote server and transferred to a card). Additional code may include, for example, security keys, encryption algorithms, and updated application code if available based on the version number of code stored on the card. The card may be packaged for delivery and mailed in step 425.
Process 430 may include placing a card in programming mode in step 431. Step 432 may include receiving data by a card. Such data may be stored in step 433. A processor may turn OFF communications ports (e.g., ignore the ports) in step 434. Accordingly, the card may not be able to program additional data on the card after step 434, for example, is reached. The card may enter an application mode in step 435.
A card may include processor 751. Resistor 752 and photo-transistor 755 may form, for example, a receiving circuit. Resistor 757 and photo-diode 758 may form, for example, a transmitting circuit. Such receiving circuits and transmitting circuits may be coupled to a processor as well as ground 759. Persons skilled in the art will appreciate that one or more port of a processor may be utilized to sample photo-transistor 755. For example, lines 753 and 754 may be utilized to sample photo-transistor 755. A dynamic magnetic stripe communications device may be positioned to extend across the length of a card, but have gaps near the ends of the card. A receiver may be positioned in one of these gaps. A transmitter may be positioned in the other one of these gaps.
Persons skilled in the art will appreciate that a card may communicate, via a transmitter, a card identification number and/or an application code identifier. A personalization machine may then access a remote server and utilize this card identification number and/or application code identifier to determine what type of information is to be programmed into the card. Such a remote server may then retrieve (e.g., from other, remote servers) the information to be programmed.
Cards 810 through 818 may be cards that have completed a first stage of assembly, for example, whereby all electronics (e.g., processors, input and/or output devices, dynamic magnetic communications devices, batteries, buttons, displays, and LEDs) have been installed. Such cards may also employ non-volatile memory (e.g., electrically-erasable read-only memory EE-PROM) that may have been pre-loaded with a communications protocol. Such a communications protocol may be employed to define a set of messages that may be exchanged between each card and its respective programming module.
In addition, each of cards 810-818 may have been laminated such that both sides of each card are protected from scratching, moisture, etc. Such lamination nevertheless allows information (e.g., infrared information) to be exchanged between a card and a programming module despite the laminated surfaces of the cards.
Once a card is manufactured and a battery is first installed, cardholder information may not exist within a card. Furthermore, functionality that may be associated with input and/or output devices of the card may be inactivated. For example, buttons may be ignored, LEDs may not light, displays may remain blank, and any dynamic magnetic communications devices on the card may remain inactive. Until cardholder information is downloaded into the card, the card may remain in a low-power (e.g., sleep-mode) of operation. Once a signal (e.g., an IR signal) is received by a card, a card may awaken from a low-power mode of operation and may transition into a programming mode of operation.
For example, a processor of each card may be programmed to be interrupted from a low-power mode of operation upon receipt of a signal (e.g., an IR signal). In particular, an IR signal may be received at an IR port of the card, which may be generated by a corresponding IR port of a programming module.
Once awakened, a processor of a card may operate in accordance with a personalization protocol. For example, a first operation of such a personalization protocol may include interrogation of a memory block of a card by a processor of a card. Such an interrogation may insure that the memory block has been properly formatted in accordance with certain personalization protocol rules. For example, the memory block may be pre-loaded with a particular data pattern before any personalization programming may occur. In so doing, a card may protect against any unauthorized personalization by first validating that a proper data pattern exists in the memory block. Any unauthorized erasure of the memory block may be detected by the absence of such a proper data pattern in the memory block, which may then preclude any further personalization programming sequences that may occur.
A personalization protocol may further query each card for a unique identification number that may be associated with each card. For example, once awakened from a low-power mode of operation, a programming module may query the awakened card for its unique identification number. A programming module, for example, may then transmit the card's response to remove server 820 for verification.
The card's response to such a query may not provide a legitimate identification number. Accordingly, remote server 820 may revoke, via API 802, programming privileges for the illegitimately responding card. In so doing, further programming sequences may be precluded by the programming module that is communicating with the illegitimately responding card. Such procedures may be enforced by the programming protocol, for example, to insure that unauthorized access to unprogrammed cards may be precluded.
A personalization protocol may further provide features to assist in the production of the card by, for example, providing performance verification for quality control purposes. For example, test fixture 822 may be provided by a production facility that may interface with API 802. API 802 may, for example, provide JTAG functionality such that test fixture 822 may conduct boundary scan testing of cards 810-818.
For example, debug functionality may be implemented within test fixture 822, such that test operations (e.g., single-stepping and break-pointing) may be conducted via the processors within cards 810-818. In so doing, for example, a test sequence integrated (e.g., stored within non-volatile memory) within each processor of cards 810-818 may be single-stepped and/or break-point driven to ascertain proper operation of each card's electronics (e.g., single-step operation to sequentially activate LEDs, displays, and dynamic magnetic communications devices).
Programming modules may further include wireless (e.g., optical and electromagnetic) receivers. Accordingly, as each card is being tested, the programming modules may verify proper operation, for example, of LEDs, displays, and dynamic magnetic communications devices and may relay such verifications onto test fixture 822.
In step 913, for example, a card may determine if a response is necessary. For example, if a received message is properly authenticated, a response may be transmitted (e.g., as in step 914) by the card to the programming module as a simple acknowledgment. A response may alternately convey additional information per protocol requirements. If a received message is not properly authenticated, a card may not transmit a response at all. Furthermore, a card may not provide any indication that a message has been received if the message does not conform to protocol requirements. If a response is not received by the programming module, the programming module may re-send the message after a predetermined timeout period.
A programming protocol may be installed within a card, for example, as in step 921 of sequence 920. During an assembly process of a card, for example, a programming protocol may be installed within a memory space (e.g., a non-volatile memory space) of a card. A card may enter a low-power mode of operation in step 922, for example, once a battery is installed within the card. Such a low-power mode of operation may include instructions to allow a processor of the card to be interrupted from the low-power mode of operation upon detection of programming signals (e.g., IR programming signals as in step 923) that may be present at an IR port of the card.
Once awakened, a processor of a card may determine proper initial conditions of the card (e.g., as in step 924). For example, a processor of a card may first determine whether a personalization memory of the card is properly formatted to receive personalization data. For example, a processor of a card may first require a particular data pattern to exist within the personalization memory of the card before allowing a personalization programming sequence to complete (e.g., as in step 925). In so doing, a card may protect itself from unauthorized programming once a card is personalized a first time. A processor may further erase (e.g., electronically erase) a memory space of the card that was initially programmed with a programming protocol to further protect against unauthorized programming once a card is personalized a first time.
Step 931 of sequence 930 may conclude the personalization of a card. Additional functionality may be provided within a programming module to further assist in production of the card and verification of a card's performance. For example, a test fixture either existing within the programming module or external to the programming module may perform verification tests (e.g., boundary-scan tests) to verify proper operation of the card (e.g., as in step 932). Such boundary-scan operations may serve only to verify proper operation of each card and may not alter the personalized programming of each card.
In so doing, such verification tests (e.g., as in step 933) may verify, for example, that buttons on a card are not shorted and operate properly, that LEDs and displays illuminate properly, and that a dynamic magnetic communications device properly generates signals (e.g., electromagnetic signals). A test report for each card tested may be generated (e.g., as in step 934) and metrics may be collected (e.g., as in step 935). Accordingly, test metrics (e.g., production yield statistics) may be utilized to identify and correct any failure modes that may exist.
Persons skilled in the art will 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/249,692, titled “Programming with Light for Powered Cards and Devices,” filed Oct. 8, 2009 and U.S. Provisional Patent Application No. 61/287,366, titled “Programming Protocols for Powered Cards and Devices,” filed Dec. 17, 2009, which are hereby incorporated by reference herein in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
3710106 | Loucheur et al. | Jan 1973 | A |
3728521 | Borough | Apr 1973 | A |
3858032 | Scantlin | Dec 1974 | A |
4013894 | Foote | Mar 1977 | A |
4025760 | Trenkamp | May 1977 | A |
4106062 | Foote | Aug 1978 | A |
4202491 | Suzuki | May 1980 | A |
4353064 | Stamm | Oct 1982 | A |
4362930 | Ehrat | Dec 1982 | A |
4387639 | Brown | Jun 1983 | A |
4394654 | Hofmann-Cerfontaine | Jul 1983 | A |
4500777 | Drexler | Feb 1985 | A |
4544184 | Freund et al. | Oct 1985 | A |
4585220 | Zemke | Apr 1986 | A |
4614861 | Pavlov et al. | Sep 1986 | A |
4626669 | Davis | Dec 1986 | A |
4663518 | Borror | May 1987 | A |
4667087 | Quintana | May 1987 | A |
4673626 | Takeda | Jun 1987 | A |
4694148 | Diekemper | Sep 1987 | A |
4701601 | Francini et al. | Oct 1987 | A |
4720860 | Weiss | Jan 1988 | A |
4742573 | Popovic | May 1988 | A |
4745267 | Davis | May 1988 | A |
4752554 | Sato | Jun 1988 | A |
4772782 | Nonat | Sep 1988 | A |
4783823 | Tasaki | Nov 1988 | A |
4786791 | Hodama | Nov 1988 | A |
4791283 | Burkhardt | Dec 1988 | A |
4797542 | Hara | Jan 1989 | A |
4814594 | Drexler | Mar 1989 | A |
4820913 | Haddock | Apr 1989 | A |
4827425 | Linden | May 1989 | A |
4877713 | Fujita | Oct 1989 | A |
4918415 | Hashimoto et al. | Apr 1990 | A |
4956215 | Fujita | Sep 1990 | A |
4978840 | Anegawa | Dec 1990 | A |
4985920 | Seki | Jan 1991 | A |
5012073 | Hewitt | Apr 1991 | A |
5012407 | Finn | Apr 1991 | A |
5038251 | Sugiyama et al. | Aug 1991 | A |
5041826 | Milheiser | Aug 1991 | A |
5067154 | Hosobuchi | Nov 1991 | A |
5083301 | Matoba et al. | Jan 1992 | A |
5085925 | Hiraoka | Feb 1992 | A |
5168520 | Weiss | Dec 1992 | A |
5196682 | Englehardt | Mar 1993 | A |
5237614 | Weiss | Aug 1993 | A |
5272688 | Horiguchi | Dec 1993 | A |
5276311 | Hennige | Jan 1994 | A |
5287692 | Matsubayashi | Feb 1994 | A |
5292616 | Fujita | Mar 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 |
5533606 | Yuyama | Jul 1996 | A |
5557679 | Julin et al. | Sep 1996 | A |
5585787 | Wallerstein | Dec 1996 | A |
5591949 | Bernstein | Jan 1997 | A |
5608203 | Finkelstein et al. | Mar 1997 | A |
5615381 | Iijima | Mar 1997 | A |
5623552 | Lane | Apr 1997 | A |
5657388 | Weiss | Aug 1997 | A |
5663900 | Bhandari et al. | Sep 1997 | A |
5729697 | Schkolnick et al. | Mar 1998 | A |
5736727 | Nakata | Apr 1998 | A |
5768143 | Fujimoto | Jun 1998 | A |
5777307 | Yamazaki | Jul 1998 | A |
5789733 | Jachimowicz et al. | Aug 1998 | A |
5815252 | Price-Francis | Sep 1998 | 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 |
5889941 | Tushie et al. | Mar 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 |
5984181 | Kreft | Nov 1999 | A |
6016962 | Nakata | Jan 2000 | A |
6021393 | Honda et al. | Feb 2000 | 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 |
6098891 | Guthery et al. | Aug 2000 | A |
6130621 | Weiss | Oct 2000 | A |
6145079 | Mitty et al. | Nov 2000 | A |
6145742 | Drexler | 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 |
6193156 | Han | Feb 2001 | B1 |
6196459 | Goman | Mar 2001 | B1 |
6199052 | Mitty et al. | Mar 2001 | B1 |
6206293 | Gutman et al. | Mar 2001 | B1 |
6218942 | Vega et al. | Apr 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 |
6283368 | Ormerod | Sep 2001 | B1 |
6286022 | Kaliski et al. | Sep 2001 | B1 |
6308890 | Cooper | Oct 2001 | B1 |
6313724 | Osterweil | Nov 2001 | B1 |
6325285 | Baratelli | Dec 2001 | B1 |
6328209 | O'Boyle | Dec 2001 | B1 |
6371375 | Ackley et al. | Apr 2002 | 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 |
6452786 | Ogata | Sep 2002 | B1 |
6460141 | Olden | Oct 2002 | B1 |
6527173 | Narusawa | Mar 2003 | 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 |
6722989 | Hayashi | Apr 2004 | B1 |
6732936 | Kiekhaefer | May 2004 | B1 |
6755341 | Wong et al. | Jun 2004 | B1 |
6764005 | Cooper | Jul 2004 | B2 |
6769618 | Finkelstein | Aug 2004 | B1 |
6769622 | Tournemille et al. | 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 |
6859650 | Ritter | Feb 2005 | B1 |
6873974 | Schutzer | Mar 2005 | B1 |
6902116 | Finkelstein | Jun 2005 | B2 |
6938244 | Perlin et al. | Aug 2005 | B1 |
6946951 | Cole et al. | Sep 2005 | B2 |
6958677 | Carter | Oct 2005 | B1 |
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 |
7081905 | Raghunath | Jul 2006 | B1 |
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 |
7349885 | Gangi | 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 |
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 | Mockett et al. | Feb 2010 | B2 |
7828207 | Cooper | Nov 2010 | B2 |
8041030 | Somers et al. | Oct 2011 | B2 |
8162229 | Huse | Apr 2012 | B1 |
8397988 | Zuili | Mar 2013 | B1 |
8561894 | Mullen | Oct 2013 | B1 |
8590796 | Cloutier | Nov 2013 | B1 |
8827153 | Rhoades | Sep 2014 | B1 |
9306666 | Zhang | Apr 2016 | B1 |
9727816 | Strater, Jr. | Aug 2017 | B1 |
10726681 | Durieux | Jul 2020 | B1 |
11409971 | Rhoades | Aug 2022 | B1 |
20010007333 | Goman | Jul 2001 | A1 |
20010034702 | Mockett et al. | Oct 2001 | A1 |
20010047335 | Arndt et al. | Nov 2001 | A1 |
20010053947 | Lenz | Dec 2001 | A1 |
20020059114 | Cockrill et al. | May 2002 | A1 |
20020082989 | Fife et al. | Jun 2002 | A1 |
20020096570 | Wong et al. | Jul 2002 | A1 |
20020101498 | Vuong et al. | Aug 2002 | A1 |
20020120583 | Keresman, III et al. | Aug 2002 | A1 |
20020143518 | Abrahamson | Oct 2002 | A1 |
20020145050 | Jayaratne | Oct 2002 | A1 |
20020162885 | Himmel et al. | Nov 2002 | A1 |
20020179702 | Fischbacher | Dec 2002 | A1 |
20020194137 | Park | Dec 2002 | A1 |
20020198731 | Barnes | Dec 2002 | A1 |
20030034388 | Routhenstein et al. | Feb 2003 | A1 |
20030052168 | Wong | Mar 2003 | A1 |
20030057278 | Wong | Mar 2003 | A1 |
20030116635 | Taban | Jun 2003 | A1 |
20030139994 | Jones | Jul 2003 | A1 |
20030152253 | Wong | Aug 2003 | A1 |
20030155419 | Bretl | Aug 2003 | A1 |
20030157983 | Kobayashi | 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 |
20030201317 | Shay | Oct 2003 | A1 |
20030222137 | Nishimura | Dec 2003 | A1 |
20030226899 | Finkelstein | Dec 2003 | A1 |
20040011865 | Morgavi | Jan 2004 | A1 |
20040035942 | Silverman | Feb 2004 | A1 |
20040042641 | Jakubowski | Mar 2004 | A1 |
20040060989 | Bove | Apr 2004 | A1 |
20040069845 | Goldstein | Apr 2004 | A1 |
20040077367 | Sama | Apr 2004 | A1 |
20040099730 | Tuchler | May 2004 | A1 |
20040118930 | Berardi | Jun 2004 | A1 |
20040129788 | Takahashi | Jul 2004 | A1 |
20040133787 | Doughty | Jul 2004 | A1 |
20040155103 | Klinefelter | Aug 2004 | A1 |
20040162732 | Rahim et al. | Aug 2004 | A1 |
20040166942 | Muir | Aug 2004 | A1 |
20040172535 | Jakobsson | Sep 2004 | A1 |
20040177045 | Brown | Sep 2004 | A1 |
20040222305 | Leaming | Nov 2004 | A1 |
20040245346 | Haddock | Dec 2004 | A1 |
20050043997 | Sohata et al. | Feb 2005 | A1 |
20050068161 | Ichinose et al. | Mar 2005 | A1 |
20050080747 | Anderson et al. | Apr 2005 | A1 |
20050086160 | Wong et al. | Apr 2005 | A1 |
20050086177 | Anderson et al. | Apr 2005 | A1 |
20050110641 | Mendolia et al. | May 2005 | A1 |
20050116026 | Burger et al. | Jun 2005 | A1 |
20050119940 | Concilio et al. | Jun 2005 | A1 |
20050154643 | Doan et al. | Jul 2005 | A1 |
20050218212 | Berthe | Oct 2005 | A1 |
20050228959 | D'Albore et al. | Oct 2005 | A1 |
20050269410 | Wilson | Dec 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 |
20070040022 | Lovegreen et al. | Feb 2007 | A1 |
20070075132 | Kean | Apr 2007 | A1 |
20070100754 | Brown | May 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 |
20070228158 | Brown | Oct 2007 | A1 |
20070241183 | Brown et al. | Oct 2007 | A1 |
20070241201 | Brown et al. | Oct 2007 | A1 |
20070246526 | Elgar | Oct 2007 | A1 |
20070254587 | Schadler et al. | Nov 2007 | A1 |
20070256123 | Duane et al. | Nov 2007 | A1 |
20070192249 | Biffle et al. | Dec 2007 | A1 |
20070279311 | Kai et al. | Dec 2007 | A1 |
20070291753 | Romano | Dec 2007 | A1 |
20070299632 | Bryant | 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 |
20080011836 | Adema 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 |
20080042653 | Bryant | Feb 2008 | A1 |
20080058016 | Di Maggio et al. | Mar 2008 | A1 |
20080059379 | Ramaci et al. | Mar 2008 | A1 |
20080068267 | Huseth | Mar 2008 | A1 |
20080096326 | Reed | Apr 2008 | A1 |
20080126398 | Cimino | May 2008 | A1 |
20080128515 | Di Iorio | Jun 2008 | A1 |
20080148394 | Poidomani et al. | Jun 2008 | A1 |
20080165951 | Somers et al. | Jul 2008 | A1 |
20080201264 | Brown et al. | Aug 2008 | A1 |
20080209550 | Di Iorio | Aug 2008 | A1 |
20080223921 | Salazar et al. | Sep 2008 | A1 |
20080223938 | Faith | Sep 2008 | A1 |
20080265509 | Gatzios | Oct 2008 | A1 |
20080288699 | Chichierchia | Nov 2008 | A1 |
20080294930 | Varone et al. | Nov 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 |
20090127337 | Kargl | May 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 |
20100071831 | Peters | Mar 2010 | A1 |
20100237999 | Hilgers | Sep 2010 | A1 |
20110025569 | Payne | Feb 2011 | A1 |
20110028184 | Cooper | Feb 2011 | A1 |
20110095866 | Karr | Apr 2011 | A1 |
20120024961 | Yisraelian et al. | Feb 2012 | A1 |
20120154290 | Yang | Jun 2012 | A1 |
20120166018 | Larschan et al. | Jun 2012 | A1 |
20120191513 | Ocher | Jul 2012 | A1 |
20120286464 | Takei | Nov 2012 | A1 |
20130026218 | Miller | Jan 2013 | A1 |
20130140359 | Xie et al. | Jun 2013 | A1 |
20130173484 | Wesby | Jul 2013 | A1 |
20140001269 | Hartwick | Jan 2014 | A1 |
20140117084 | Wooldridge | May 2014 | A1 |
20160012465 | Sharp | Jan 2016 | A1 |
20180350180 | Onischuk | Dec 2018 | A1 |
20210129133 | Ohta | May 2021 | A1 |
Number | Date | Country |
---|---|---|
05210770 | Aug 1993 | JP |
11212923 | Aug 1999 | 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 |
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 | |
---|---|---|---|
61287366 | Dec 2009 | US | |
61249692 | Oct 2009 | US |