Cards and devices with multifunction magnetic emulators and methods for using same

Information

  • Patent Grant
  • 10997489
  • Patent Number
    10,997,489
  • Date Filed
    Monday, August 1, 2016
    8 years ago
  • Date Issued
    Tuesday, May 4, 2021
    3 years ago
Abstract
A payment card (e.g., credit and/or debit card) is provided with a magnetic emulator operable of communicating information to a magnetic stripe reader. Information used in validating a financial transaction is encrypted based on time such that a validating server requires receipt of the appropriate encrypted information for a period of time to validate a transaction for that period of time. Such dynamic information may be communicated using such an emulator such that a card may be swiped through a magnetic stripe reader—yet communicate different information based on time. An emulator may receive information as well as communicate information to a variety of receivers (e.g., an RFID receiver).
Description
BACKGROUND OF THE INVENTION

This invention relates to magnetic cards and payment systems.


SUMMARY OF THE INVENTION

A card is provided, such as a credit card or security card, that may transmit information to a magnetic stripe reader via a magnetic emulator. The magnetic emulator may be, for example, a circuit that emits electromagnetic fields operable to electrically couple with a read-head of a magnetic stripe reader such that data may be transmitted from the circuit to the magnetic stripe reader. The emulator may be operated serially such that information is transmitted serially to a magnetic stripe reader. Alternatively, for example, portions of a magnetic emulator may emit different electromagnetic fields at a particular instance such that the emulator is operated to provide physically parallel, instantaneous data. Alternatively still, a magnetic medium may be provided and a circuit may be provided to change the magnetic properties of the magnetic medium such that a magnetic stripe reader is operable to read information written on the magnetic medium.


A processor may be provided on a card, or other device, that controls a magnetic emulator. The processor may be configured to operate the emulator such that the emulator transmits serial or parallel information. Particularly, the processor may decouple portions of an emulator from one another such that different portions of the emulator may transmit different information (e.g., transmit data in a parallel operation). The processor may couple portions of an emulator together (or drive the portions together) such that all portions of the emulator transmits the same information (e.g., transmit data in a serial operation). Alternatively, the processor may drive a portion of the emulator to transmit data using one method (e.g., serially) while the processor drives another portion of the emulator using a different method (e.g., in parallel).


The processor may drive an emulator through a switching circuit. The switching circuit may control the direction and magnitude of current that flows through at least a portion of an emulator such that the switching circuit controls the direction and magnitude of the electromagnetic field created by at least that portion of the emulator. An electromagnetic field may be generated by the emulator such that the emulator is operable to electrically couple with a read-head from a magnetic stripe reader without making physical contact with the read-head. Particularly, for example, an emulator that is driven with increased current can be operable to couple with the read-head of a magnetic stripe reader even when placed outside and within the proximity of (e.g., 0.25 inches) the read-head.


A magnetic emulator may be operated to electrically couple, and transmit data to, devices other than a magnetic stripe reader. For example, a magnetic emulator may be operated to electrically couple, and transmit data to, a device using a Radio Frequency IDentification (RFID) protocol. Accordingly, a processor may drive the emulator at a frequency and magnitude in order to electrically couple with a read-head of a magnetic stripe reader and then drive the emulator at a different frequency and a different magnitude in order to electronically couple with an RFID reader.


A processor may receive information from a magnetic stripe reader detector and/or an RFID receiver detector. A processor may detect, for example, the presence of a read-head of a magnetic stripe reader by receiving signals from a magnetic stripe reader detector and, in response, the processor may drive a magnetic emulator in a manner that allows the emulator to couple with the magnetic stripe reader. The processor may also detect, for example, the presence of and RFID receiver by receiving signals from an RFID receiver detector and, in response, the processor may drive a magnetic emulator in a manner that allows the emulator to couple with the RFID receiver. More than one emulator may be provided on a card or other device and a processor may drive such emulators in a variety of different manners.


A circuit may be provided on a credit card that is operable to receive data from a magnetic stripe encoder and/or an RFID transmitter. Such a circuit may electrically couple with an RFID transmitter and/or magnetic stripe encoder and deliver information to a processor. In this manner, a card, or other device, may communicate bi-directionally with a device.


An emulator may communicate with a magnetic stripe reader outside of, for example, the housing of a magnetic stripe reader. Accordingly, for example, the emulator may be provided in devices other than cards sized to fit inside of the reading area of a magnetic stripe reader. In other words, for example, the emulator may be located in a device that is thicker than a card—yet the emulator can still communicate with one or more read-heads located in a magnetic stripe reader. Such a device may be, for example, a security token, a wireless communications device, a laptop, a Personal Digital Assistant (PDA), a physical lock key to a house and/or car, or any other device.


Dynamic information may be provided by a processor located on the card, or other device, and communicated through a magnetic emulator. Such dynamic information may, for example, change based on time. For example, the dynamic information may be periodically encrypted differently. One or more displays may be located on a card, or other device, such that the dynamic information may be displayed to a user through the display. Buttons may be provided to accept input from a user to, for example, control the operation of the card or other device.


Dynamic information may include, for example, a dynamic number that is used as, or part of, a number for a credit card number, debit card number, payment card number, and/or payment verification code. Dynamic information may also include, for example, a student identification number or medical identification number. Dynamic information may also, for example, include alphanumeric information such that a dynamic account name is provided.





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 cards constructed in accordance with the principles of the present invention;



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



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



FIG. 5 is an illustration of process flow charts constructed in accordance with the principles of the present invention;



FIG. 6 is an illustration of the electrical coupling between a card and a reader constructed in accordance with the principles of the present invention;



FIG. 7 is an illustration of the electrical coupling between a card and a reader constructed in accordance with the principles of the present invention;



FIG. 8 is an illustration of magnetic shielding in accordance with the principles of the present invention;



FIG. 9 is an illustration of process flow charts constructed in accordance with the principles of the present invention;



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



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



FIG. 12 is an illustration of a personal electronic device constructed in accordance with the principles of the present invention.





DETAILED DESCRIPTION OF THE INVENTION


FIG. 1 shows card 100 that includes printed information 111 and 120, displays 112 and 113, and buttons 130-134. Card 100 may be, for example, a payment card such as a credit card, debit card, and/or gift card. Payment information, such as a credit/debit card number may be provided as static information 111, dynamic information 112 and/or 113, or any combination thereof.


For example, a particular number of digits of a credit card number (e.g., the last 3 digits) may be provided as dynamic information. Such dynamic information may be changed periodically (e.g., once every hour). Information may be changed via, for example, encryption. Software may be provided at, for example, the payment verification servers that verifies the dynamic information for each period of time such that a payment can be validated and processed for a particular user. A user may be identifies using, for example, static information that is used to form a credit card number or other static information (e.g., information 120). Additionally, identification information may be derived (e.g., embedded) in dynamic information. Persons skilled in the art will appreciate that a credit card number may have, for example, a length of 15 or 16 digits. A credit card number may also have a length of up to 19 digits. A verification code may be used with some payment systems and such a verification code may be provided statically on the card or may be provided as dynamic information. Such a verification code may be provided on a second display located on, for example, the front or rear surface of card 100. Alternatively, a verification code may be displayed on the same display as other dynamic information (e.g., dynamic information 112). A display may be, for example, a flexible electronic ink display. Such a flexible electronic ink display may, for example, utilize power to change displayed information, but may not utilize power to display information after the information is changed.


Card 150 may be provided. Card 150 may include static magnetic stripe tracks 153 and 152. A magnetic emulator may be provided as device 151. Device 151 may be operable to electrically couple with a read-head of a magnetic stripe reader. Persons skilled in the art will appreciate that a read-head housing of a magnetic stripe reader may be provided with one, two, or three active read-heads that are operable to each couple with a separate magnetic track of information. A reader may also have more than one read-head housing and each read-head housing may be provided with one, two, or three active read-heads that are operable to each couple with a separate magnetic track of information. Such read-head housings may be provided different surfaces of a magnetic stripe reader. For example, the read-head housings may be provided on opposite walls of a trough sized to accept payment cards. Accordingly, the devices on the opposite sides of the trough may be able to read a credit card regardless of the direction that the credit card was swiped.


A magnetic emulator may be provided and may be positioned on card 150 such that when card 150 is swiped through a credit card reader, the magnetic emulator passes underneath, or in the proximity of, a read-head for a particular magnetic track. An emulator may be large enough to simultaneously pass beneath, or in the proximity of, multiple read-heads. Information may be transmitted, for example, serially to one or more read-heads. Information from different tracks of data may also be transmitted serially and the magnetic stripe reader may determine the different data received by utilize the starting and/or ending sentinels that define the information for each track. A magnetic emulator may also transmit a string of leading and/or ending zeros such that a magnetic reader may utilize such a string of zeros to provide self-clocking. In doing so, for example, information may be transmitted serially at high speeds to a magnetic stripe reader. For example, credit card information may be transmitted to a magnetic stripe reader at speeds up to, and greater than, 30 Khz).


Different emulators may be provided, and positioned, on card 150 to each couple with a different read-head and each emulator may provide different track information to those different read-heads. Read-head detectors may be utilized to detect when a read-head is over an emulator such that an emulator is controlled by a processor to operate when a read-head detector detects the appropriate presence of a read-head. In doing so, power may be saved. Additionally, the read-head detector may detect how many read-heads are reading the card and, accordingly, only communicate with the associated emulators. In doing so, additional power may be conserved. Accordingly, an emulator may be utilized to communicate dynamic information to a magnetic stripe reader. Such dynamic information may include, for example, dynamic payment card information that changes based on time.


A static magnetic stripe may be provide to transmit data for one or more tracks to a magnetic strip reader where dynamic information is not desired. Card 150, for example, may include static magnetic track 153 and static magnetic track 152. Information on static magnetic tracks 152 and 153 may be encoded via a magnetic stripe encoder. Device 151 may include an emulator such that dynamic information may be communicated through emulator 151. Any combination of emulators and static magnetic tracks may be utilized for a card or device.


One or more batteries, such as flexible lithium polymer, batteries may be utilized to form card 100. Such batteries may be electrically coupled in a serial combination to provide a source of power to the various components of card 100. Alternatively, separate batteries may provide power to different components of card 100. For example, a battery may provide power to a processor and/or display of card 100, while another battery provides a source of energy to one or more magnetic emulators of card 100. In doing so, for example, a processor may operate even after the battery that supplies power to an emulator completely discharges. Accordingly, the processor may provide information to another component of card 100. For example, the processor may display information on a display to indicate to a user that the magnetic emulator is not longer operational due to power exhaustion. Batteries may be, for example, rechargeable and contacts, or other devices, may be provided on card 100 such that the battery may be recharged.


Buttons (e.g., buttons 130-134) may be provided on a card. Such buttons may allow a user to manually provide information to a card. For example, a user may be provided with a personal identification code (e.g., a PIN) and such a personal identification code may be required to be manually inputted into a card using the buttons in order for the card to operate in a particular manner. For example, the use of a magnetic emulator or the use of a display may require a personal identification code.


By dynamically changing a portion of a user's credit card number, for example, credit card fraud is minimized. By allowing the dynamic information to displayed visually to a user, and changed magnetically on a card, user behavior change is minimized (with respect to a credit card with completely static information). By requiring the use of a personal identification code, the fraud associated with lost or stolen credit cards is minimized. Fraud associated with theft/loss is minimized as third party users do not know the personal identification code needed to operate particular aspects of a credit card with dynamic information.



FIG. 2 shows card 200. Card 200 may include, for example, static magnetic stripe track 203, static magnetic stripe track 201, and magnetic emulator 202 sandwiched between read-head detectors 204 and 205. A read-head detector may, for example, be provided as a circuit that detects, for example, changes in capacitance or mechanical coupling to a conductive material. Processor 220 may be provided to, for example, receive information from read-head detectors 204 and 205 and control emulator 202. Persons skilled in the art will appreciate that processor 220 may cause a current to flow through a coil of emulator 202 in a different direction to produce different electromagnetic fields. The transitions between the different electromagnetic fields may be sensed by a magnetic stripe reader as information. Accordingly, a magnetic emulator may transmit data serially while a read-head is electrically coupled with a magnetic reader.


RFID antenna 210 may be provided on card 200. Such an RFID antenna may be operable to transmit information provided by processor 220. In doing so, for example, processor 220 may communicate with an RFID device using RFID antenna 210 and may communicate with a magnetic stripe reader using magnetic emulator 204. Both RFID antenna 210 and magnetic emulator 204 may be utilized to communicate payment card information (e.g., credit card information) to a reader. Processor 240 may also be coupled to display 240 such that dynamic information can be displayed on display 240. Button array 230 may also be coupled to processor 220 such that the operation of card 200 may be controlled, at least in part, by manual input received by button array 230.


Card 250 may be provided and may include static magnetic track 253, magnetic emulators 251 and 252, and magnetic read-heads 254-257). Persons skilled in the art will appreciate that static magnetic track 253 may be a read-write track such that information may be written to magnetic track 253 from a magnetic stripe reader that includes a head operable to magnetically encode data onto a magnetic track. Information may be written to magnetic track 253 as part of a payment process (e.g., a credit card or debit card transaction). Persons skilled in the art will appreciate that a static magnetic track may include a magnetic material that includes ferromagnetic materials that provide for flux-reversals such that a magnetic stripe reader can read the flux-reversals from the static magnetic track. Persons skilled in the art will also appreciate that a magnetic emulator may communicate information that remains the same from payment card transaction to payment card transaction (e.g., static information) as well as information that changes between transactions (e.g., dynamic information).



FIG. 3 shows card 300 that may include magnetic encoders 302 and 302 without, for example, a static magnetic track. Read-head detectors 304-307 may also be provided. Persons skilled in the art will appreciate that a magnetic reader may include the ability to read two tracks of information (e.g., may include at least two read-heads). All of the information needed to perform a financial transaction (e.g., a credit/debit card transaction) may be included on two magnetic tracks. Alternatively, all of the information needed to perform a financial transaction (e.g., a gift card transaction) may be included on one magnetic track. Accordingly, particular cards, or other devices, may include the ability, for example, to only transmit data associated with the tracks that are needed to complete a particular financial transaction. Persons skilled in the art will appreciate that for systems with three tracks of information, the bottom two tracks may be utilized for credit card information. Persons skilled in the art will also appreciate that a secure credit card transaction may be provided by only changing, for example, one of two magnetic tracks utilized in a credit card transaction (for those transactions that utilize two tracks). Accordingly, one track may be a static magnetic track constructed from a magnetic material and the other track may be provided as a magnetic emulator. Persons skilled in the art will also appreciate that numerous additional fields of data may be provided on a magnetic track in addition to a credit card number (or a security code). Dynamic information may be provided in such additional fields in order to complete a particular financial transaction. For example, such additional dynamic information may be numbers (or characters), encrypted with time and synced to software, at a validating server, operable to validate the encrypted number for a particular period of time.


Card 350 includes processor 360. RFID field detector 353 may provide information to processor 350. Additionally, magnetic stripe detectors may provide information to processor 350. An RFID receiver may produce an electromagnetic field that an RFID antenna is operable to electrically couple with and communicate information to. An RFID receiver may act as a source of electrical power to an RFID antenna. Such a power may be harvested (e.g., via RFID 210 of FIG. 2) to charge a rechargeable battery of a card or other device. An RFID field detector may thus be provided to detect an RFID field.


Emulator 351 may be able to generate electromagnetic fields of different frequencies and magnitudes, and operate in different manners, depending on drive signals provided by processor 360. Accordingly, emulator 351 may be driven to electrically couple with an RFID receiver and emulator 351 may also be driven to electrically couple with a magnetic stripe reader. Accordingly, processor 360 may drive emulator 351 to communicate information (e.g., payment information that includes dynamic information) to an RFID receiver when an RFID field is present and to a magnetic stripe reader when a magnetic stripe is present. Accordingly, for example, a multi-purpose emulator is provided. In instances where, for example, both an RFID field and a magnetic stripe reader is detected, processor 360 may select a default communications methodology (e.g., an RFID or magnetic stripe methodology). Processor 360 may be operable to communicate at least two different drive signals to emulator 351 (e.g., signals 391 and 392).


Card 400 shows card 400 that may include processor 400, emulator 401, read-heads 402 and 403, and magnetic stripe encoding receiver 420. Magnetic stripe encoding receiver 420 may be a coil such that a current is induced in the coil when a magnetic stripe encoder attempts to provide a signal that would encode a static magnetic track. Accordingly, receiver 420 may receive information via an encoder such that bi-directional communication can be established with a magnetic stripe reader that includes an encoding capability. Persons skilled in the art will appreciate that a magnetic emulator may be provided that can both transmit data to a read-head of a magnetic stripe reader as well as receive data from an encoding-head of a magnetic stripe reader.


Card 450 includes emulator 451 that includes active region 454 operable to communicate data serially to a magnetic stripe reader. Similarly, for example, emulator 451 may receive information for a magnetic stripe encoder. Persons skilled in the art will appreciate that emulator 451 includes a tail that is spread-out. Such a tail may include the return lines of emulator 451 and may be spaced such that a magnetic reader is not able to pick up the electromagnetic fields generated by such a tail. Accordingly, active region 454 may be spaced close together such that a magnetic stripe reader is able to pick up the cumulative electromagnetic field generated by such an active region. Processor 453 may drive emulator 451 via switching circuitry 452. Switching circuitry 452 may include, for example, one or more transistors that may be utilized to control the direction of current via emulator 451 (e.g., the polarity of voltage(s) across a drive resistor).



FIG. 5 shows flow chart 510 that may includes steps 511-513. Step 511 may be utilized to determine, of example, whether an RFID or a magnetic stripe reader is within the proximity of a card (or other device). Step 512 may be utilized to run an emulator as an RFID or magnetic stripe in response to step 511. Step 513 may be utilized to determine an RFID and magnetic stripe reader such that the process may be repeated.


Process 520 may be included and may include step 521 to detect a read-head. Step 522 may be included to transmit information using an emulator in a transmitting mode. Step 523 may be utilized to receive information from an emulator (or receiving coil) in a receiving mode. Persons skilled in the art will appreciate that an emulator may be operating in a receiving mode and a transmitting mode at the same time.


Process 530 may be included and may include step 531 to encode data into static magnetic tracks fabricated from a magnetic material. Step 532 may be provided to program data into a processor to be utilized in a subsequent step (e.g., step 533). Step 533 may be utilized to emulate data using an emulator driven by the data programmed in the processor.



FIG. 6 shows environment 600 that may include magnetic stripe reader 610, read-head housing 640, card 620, and magnetic emulator 630. Read-head housing 640 may include any number of read-head's such as, for example, one, two, or three read-heads. Each read-head may independently receive magnetic fields from magnetic emulator 630 (or a magnetic stripe, such as a magnetic stripe encoded on-card by card 620). Emulator 630 may be positioned to be adjacent to any one or more read-heads of read-head housing 640 or may be positioned to communicate information to any one or more read-heads of read-head housing 640. Persons skilled in the art will appreciate that emulators with longer lengths may be located within the proximity of one or more read-heads for a longer duration of time when a card is swiped. In doing so, for example, more information may be transmitted from an emulator to a read-head when a card is being swiped.



FIG. 7 includes environment 700 that may include cards 720 and 730 as well as magnetic stripe reader 710. Read-head housing 711 may be included on a wall of a trough of magnetic stripe reader 710. The trough may be sized to accept cards (e.g., credit cards).


Card 720 may include emulator 721. Emulator 721 may provide electromagnetic field 791 that may transmit through a portion of the housing of magnetic stripe reader 710 (e.g., through a wall of a trough to get to read-head housing 711). Accordingly, card 720 may be located outside of a reader—yet still be operable to communicate information to a magnetic stripe reader. A reader may be provided with an outer wall, for example, with a thickness of a quarter of an inch or more. Emulator 721 can provide electromagnetic field 791 over a distance of, for example, a quarter of an inch or more.


Persons skilled in the art will appreciate that card 720 may be coupled to a device via a permanent or removable cable. Such a device may provide power to card 720 as well as control information—such as control information for emulator 730. An external source of power may be utilized, for example, to provide a larger amount of electrical energy to emulator 721 than from a source of power located within card 720. Persons skilled in the art will appreciate that a car having an internal battery may still be able to receive a cable from a device having its own source of electrical energy.


Card 730 may be provided with emulator 731 and may electrically couple with a read-head of magnetic stripe reader 710. Any number of emulators may be provided in card 730 in any number of orientations such that the appropriate electromagnetic field may couple with a read head of read-head housing 711 regardless of the orientation of card 720 with respect to read-head 711. More particularly, for example, additional read-head housings may be provided in magnetic stripe reader 710 at different locations about the reader to electrically couple with a emulators in a number of different configurations. A sticker and/or guide-structures may be provided on a magnetic stripe reader to, for example, direct a user on how to position his/her card (or other device) for contactless transmission of data (e.g., credit card data) to a read-head housing without using the trough that includes that read-head housing.


Persons skilled in the art will appreciate that a magnetic stripe reader may include a trough that includes two (or more) read-head housings 711 located in approximately the same vertical position on a card-swiping trough, but at different horizontal locations on opposite walls of the trough. In doing so, for example, a magnetic stripe may be read regardless of the direction that a card having the magnetic stripe is facing when the card is swiped. Magnetic emulator 721 may, for example, communicate magnetic fields outside both the front and read surfaces of a card. Accordingly, a single emulator 721 may, for example, couple with a single read-head regardless of the direction the card was facing when swiped. In doing so, for example, the costs of readers may be reduced as only a single read-head may be need to receive information regardless of the direction a card is facing when swiped. Accordingly, magnetic readers do not need stickers and/or indicia to show a user the correct orientation to swipe a card through a magnetic stripe reader. An adapter may be provided that coupled directly to a read-head that allows a device not operable to fit in a trough to electrically couple with a read-head.


An dynamic magnetic communications device, such as a emulator, may be positioned about a surface of a card (or other device), beneath a surface of a device, or centered within a card. The orientation of a magnetic emulator in a card may provide different magnetic fields (e.g., different strength's of magnetic fields) outside different surfaces of a card. Persons skilled in the art will appreciate that a magnetic emulator may be printed via PCB printing. A card may include multiple flexible PCB layers (e.g., FR4 layers) and may be laminated to form a card. Portions of an electronic ink display may also be fabricated on a layer during a PCB printing process.


Magnetic shielding may be provided to limit an electromagnetic field of an emulator. For example, layer 810 may include magnetic shielding 811 (which may be a magnetic material). Magnetic shielding may block magnetic fields from emulator 851 on layer 820. Accordingly, for example, a card may not interact with read-heads blocked from emulator 851 from magnetic shielding 811. In doing so, for example, a magnetic stripe reader may receive information from a single read-head housing at any given time. Layer 830 may be provided, for example, with magnetic shielding 831 that includes an active-region space 832. Accordingly, layer 830 may block magnetic fields from emulator 851 except for those fields generated by active portion 854 (e.g., if space 832 is aligned with active portion 854).



FIG. 9 shows processes 900 that may include flow chart 910. Flow chart 910 may include step 911, in which a first layer of magnetic shielding may be provided (e.g., printed). Step 912 may be provided such that, for example, an emulator is provided (e.g., printed). Step 913 may be included such that, for example, a second layer of shielding may be provided (e.g., printed).


Flow chart 920 may be included. Step 921 may be included in flow chart 920. A read-head may be detected in step 921, a first level of current may be provided through an emulator in step 922, and the direction of the current through the emulator may be switched in step 923 in order to transmit data.


Flow chart 930 may be included. Step 931 may be included in flow chart 930. A button press may be detected in step 931, a second level of current may be provided through an emulator in step 932, and the direction of the current through the emulator may be switched in step 933 in order to transmit data. Flow chart 921 and 931 may be utilized together, for example, to provide a multi-function emulator. For example, an emulator may provide a magnetic-stripe signal to a magnetic stripe reader in flow chart 920 and may provide an RFID signal to an RFID receiver in flow chart 930.


Persons skilled in the art will appreciate that a number does not need to, for example, change with time. Information can change, for example, based on manual input (e.g., a button press or combination of button presses). Additionally, a credit card number may be a static display number and may be wholly or partially displayed by a display. Such a static credit card number may result in the reduction of fraud if, for example, a personal identification code is required to be entered on a manual input entry system to activate the display. Additionally, fraud associated with card cloning may be minimized with the use of a magnetic emulator activated by the correct entry on a manual input entry system.


Person skilled in the art will also appreciate that a card may be cloned by a thief, for example, when the thief puts a illegitimate credit card reader before a legitimate credit card reader and disguising the illegitimate credit card reader. Thus, a read-head detector may detect a read-head housing and then, if a second read-head housing is detected on the same side of the credit card, the reader may transmit information to the second read-head that signifies that two read-head housings were detected. In doing so, for example, a bank, or the police, may be notified of the possibility of the presence of a disguised cloning device. The information representative of multiple read-heads may be included with information that would allow a credit card number to be validated. As such, a server may keep track of the number of read-head housings at each reader and, if more read-head housings are detected than expected, the server may contact an administrator (or the police). The server may also cause the credit card transaction to process or may reject the credit card transaction. If the number of read-head housings (or read-heads) is the number expected by the server, the server can validate the payment transaction.


A payment system using dynamic numbers may, for example, be operable with numbers that are stored outside of the period in which those numbers would otherwise be valid. A server may be included, for example, that accepts a dynamic credit card number, information representative of a past credit card number, and the merchant that is requesting payment. The server may register that merchant for that saved number. The number may be decrypted (or otherwise validated) for that past period of time. Accordingly, the credit card transaction may be validated. Additionally, the merchant identification information may be linked to the stored dynamic credit card number for that past period of time. If the server receives a transaction from a different merchant with that same dynamic credit card number for that same period of time, the server may reject the transaction. In doing so, a merchant may be protected from having credit card numbers stolen from its various storage devices. If a thief steals a number from a merchant's server that is associated with a past period of time, that number cannot be used, for example, anywhere else. Furthermore, such a topology may, for example, allow merchants to provide a one-click shopping, periodic billing, or any other type of feature that may utilize dynamic numbers that are stored and used outside of the period in which the dynamic numbers were generated.


Persons skilled in the art will appreciate that different emulators may be controlled by different switching circuitry (e.g., different transistors). Opto-isolators may be included to protect the processor from any voltage swings driving a magnetic emulator.


Persons skilled in the art will appreciate that multiple buttons may be coupled together to form a single-bit bus. If any button is pressed, the bus may change states and signal to the processor to utilize different ports to determine what button was pressed. In this manner, buttons may be coupled to non-triggerable ports of a processor. Each button (or a subset of buttons) may be coupled to one or more triggerable ports of a processor. A port on a microprocessor may be utilized to drive an emulator in addition to, for example, receiving information from a button. For example, once an appropriate personal identification code is received by a processor, the processor may utilize one or more ports that receive information from one or more buttons to drive an emulator (e.g., for a period of time). Alternatively, for example, a magnetic emulator may be coupled to its own triggerable or non-triggerable processor port. A card may also include a voltage regulator to, for example, regulate power received from an internal or external source of power.


Persons skilled in the art will appreciate that any type of device may be utilized to provide dynamic magnetic information on a card to a magnetic stripe reader. As discussed above, a magnetic encoder may be provided that can change information on a magnetic medium where the changed information can be detected by a magnetic stripe reader.



FIG. 10 shows card 1000 that may include, for example, one or more IC chips 1030 (e.g., EMV chips), RFID antennas 1020, processors 1040, displays 1050, dynamic magnetic communications devices 1010 (e.g., magnetic encoders and/or magnetic emulators), batteries 1060, and buttons 1051 and 1052. Additional circuitry 1098 may be provided which may be, for example, one or more oscillators or emulator driving circuits. Persons skilled in the art will appreciate that button 1051 may, for example, be utilized by a user to select one encryption algorithm for a number displayed on display 1050 while button 1052 may be utilized by a user to select a different encryption algorithm. Persons skilled in the art will appreciate that the components of card 1000 may be provided on either surface of a card (e.g., a front or rear surface of the card) or inside of a card. A logo (e.g., of a card issuer) and logo may be provided on either surface of a card.


A button, such as button 1051, may be utilized, for example, to display a number. Such a number may be, for example, encrypted from a secure number based on time or use. For example, one-time use numbers (e.g., a payment number or code) may be retrieved from a list of numbers on memory each time button 1051 is pressed and displayed on display 1050. A processor may only go through each number once on a list. A registration process may be provided in which a user may be requested to enter in a sequence of numbers such that a remote server may validate the card and learn where in a sequence of a list a card currently resides. Numbers may be repeated on a list or may only occur once on a list. All of the numbers available by the length of the number may be utilized by the list or only a portion of the numbers available by the length of the number may be provided by the list. A secret number may be encrypted on a card and a verification server may also have knowledge of this secret number. Accordingly, the remote server may perform the same encryption function as the card on the secret number and verify that the resultant encrypted number is the same as the resultant encrypted number on a card. Alternatively, for example, the remote server may decrypt the received encrypted number to determine the authenticity of the encrypted number and validate an activity (e.g., validate a security access request or a purchase transaction).


Persons skilled in the art will appreciate, for example, that a card may include an IC chip (e.g., EMV chip), RFID, and a dynamic magnetic communications device (e.g., a magnetic emulator or encoder). The same information may be communicated through, for example, any number of such devices (e.g., a dynamic magnetic communications device, RFID, and an EMV chip). A central processor may cause each device to communicate the information (in the same format or a different format). Each component may have its own processor or driving circuitry. Such individual processors or driving circuitry may be coupled to a central processor. An EMV chip may be utilized, for example, to provide control signals to other devices (e.g., circuitry driving a display as well as a dynamic magnetic communications device). Such an EMV chip may receive signals provided by one or more buttons to determine, for example, that a particular button, or sequence of buttons, was pressed by a user.


Persons skilled in the art will appreciate that a read-head housing may include, for example, multiple read-heads. A read-head detector may, more generally, detect a read-head housing and, in doing so, detect a read-head.



FIG. 11 shows card 1100 that may include, for example, signature area 1140 that may include a material operable to receive marks from a pen (e.g., a signature). Card 1100 may also include, for example, displays 1120 and 1130. Display 1120 may, for example, display a payment number while display 1130 displays a security code (e.g., for online purchase authentication). Display 1120 as well as display 1130 may be utilized on the same side as, for example, dynamic magnetic communications device 1110.



FIG. 12 shows personal electronic device 1200 which may be, for example, a portable telephonic device, portable media player, or any type of electronic device. Persons skilled in the art will appreciate that the functionality of a card may be provided on a personal device and displayed through a graphical user interface. Personal electronic device 1200 may include, for example, user inputs 1240 and display 1210. Virtual card 1220 may be displayed on display 1220. Display 1220 may be a touch-sensitive display such that, for example, virtual button 1230 may be provided on virtual card 1220. Persons skilled in the art will appreciate that cards may be provided as virtual cards and a user may interact with such virtual cards in order to provide a variety of functions. Personal electronic device 1200 may communicate to a card reader such as, for example, an RFID reader.


A display may be bi-stable or non bi-stable. A bi-stable display may consume electrical energy to change the information displayed on the bi-stable display but may not consume electrical energy to maintain the display of that information. A non bi-stable display may consume electrical energy to both change and maintain information on the non bi-stable display. A display driving circuit may be provided, for example, for a bi-stable display (or a non bi-stable display). Such a display driving circuit may step-up a supply voltage (e.g., 1-5 volts) to a larger voltage (e.g., 6-15 volts) such that a bi-stable display may change displayed information. A controller (e.g., a processor) may be utilized to control such a display driving circuit. Persons skilled in the art will appreciate that a display may be configured to display numerical data or alphanumerical data. A display may also be configured to display other indicia (e.g., the image of a battery and its remaining life).


A magnetic stripe reader may, for example, determine information on a magnetic stripe by detecting the frequency of changes in magnetic fields (e.g., flux transversals). A particular frequency of flux transversals may correlate to, for example, a particular information state (e.g., a logic “1” or a logic “0”). Accordingly, for example, a magnetic emulator may change the direction of an electromagnetic field at particular frequencies in order to communicate a different state of information (e.g., a logic “1” or a logic “0”).


Persons skilled in the art will appreciate that a magnetic emulator may electromagnetically communicate information serially by changing the magnitude of an electromagnetic field with respect to time. As such, for example, a current in a single direction may be provided through a magnetic emulator in order for that magnetic emulator to generate an electromagnetic field of a single direction and a particular magnitude. The current may then be removed from the magnetic emulator such that, for example, the electromagnetic field is removed. The creation of a presence of an electromagnetic field, and the removal of that electromagnetic field, may be utilized to communicate information to, for example, a magnetic stripe reader. A magnetic stripe reader may be configured to read, for example, the change in flux versus time and may associate an increase in an electromagnetic field (e.g., creation of a field) as one flux transversal and a decrease (e.g., removal of a field) as another transversal. In doing so, for example, driving circuitry (not shown) may be provided which, in turn, controls when current is provided to a magnetic emulator. The timing of magnetic flux transversals, as determined by a magnetic stripe reader, may be utilized by that reader to determine whether a logic one (“1”) or logic zero (“0”) was communicated. Accordingly, a driving circuit may change the frequency of when current is supplied and removed from a magnetic emulator in order to communicate a logic one (“1”) or a logic zero (“0”).


A driving circuit may, for example, change the direction of current supplied to a magnetic emulator to increase the amount of change in an electromagnetic field magnitude for a period of time. In doing so, for example, a magnetic stripe reader may more easily be able to discern overall changes in an electromagnetic field and, as such, may more easily be able to discern information. As such, for example, a driving circuit may increase the magnitude of an electromagnetic field by providing negative current, decrease the amount of negative current until no current is provided and provide an increasing positive current in order to provide a large swing in the magnitude of an electromagnetic field. Similarly, a driving circuit may switch from providing one amount of negative current (or positive current) to one amount of positive current (or negative current).


Persons skilled in the art will appreciate that a string of a particular bit of data (e.g., a string of logic zeros “0s”) may be communicated before as well as after information is communicated through a magnetic emulator. A magnetic stripe reader may utilize such data, for example, to determine base timing information such that the magnetic stripe reader has a timing reference that the reader can utilize to assist in determining timing changes of perceived flux transverals. Accordingly, for example, a magnetic emulator may send data at different overall frequencies and a magnetic stripe reader may be able to reconfigure itself to receive data at such overall frequencies. Information may be encoded using, for example, Frequency/Double Frequency (F2F) encoding such that magnetic stripe readers may perform, F2F decoding.


A processor may control one or more emulators by, for example, controlling the direction of the current supplied through one or more segments of an emulator. By changing the direction of current through a region, for example, the direction of an electromagnetic field may be changed. Similarly, a processor may control one or more emulators by, for example, controlling the change in magnitude of current supplied through one or more segments of an emulator. As such, for example, a processor may increase the magnitude of current as well as decrease the magnitude of current supplied through an emulator. A processor may control the timing of such increases and decreases in current such that a magnetic emulator may, for example, communicate F2F encoded information.


Persons skilled in the art will appreciate that a dynamic magnetic communications device (e.g., a magnetic emulator or magnetic encoder) may be fabricated, either completely or partially, in silicon and provided as a silicon-based chip. Other circuitry (e.g., driving circuitry) may also be fabricated on such a silicon-based chip. A processor, such as a processor for controlling a magnetic communications device, may be, for example, a programmable processor having on-board programmable non-volatile memory (e.g., FLASH memory), volatile memory (e.g., RAM), as well as a cache. Firmware as well as payment information (e.g., dynamic numbers) may be, for example, communicated from a programming device to a processor's on-board programmable non-volatile memory (e.g., a FLASH memory) such that a card may provide a variety of functionalities. Such a processor may also have one or more power-saving operating modes, in which each operating mode turns OFF a different set of circuitry to provide different levels of power consumption. One or more power-savings modes may turn OFF, for example, one or more clocking circuitry provided on a processor. An Application-Specific Integrated Circuit (ASIC) may also be included in a card or other device to provide, for example, processing, dynamic magnetic communications, as well as driving capabilities.


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.

Claims
  • 1. A device comprising: a magnetic emulator operable to electrically couple to and communicate data to a read-head of a magnetic stripe reader; anda processor for controlling the magnetic emulator;wherein the magnetic emulator is operable to electrically couple to and communicate the data to the read-head when the device is located outside and within proximity of the magnetic stripe reader.
  • 2. The device of claim 1, wherein the device is thicker than a credit card.
  • 3. The device of claim 1, wherein the device is a wireless communication device.
  • 4. The device of claim 1, wherein the magnetic emulator is operable to electrically couple to and communicate the data to the read-head when the device is located at least a quarter of an inch away from the read-head.
  • 5. The device of claim 1, wherein the magnetic emulator is operable to electrically couple to and communicate the data to the read-head when the read-head is further from the device than the thickness of a housing of the magnetic stripe reader.
  • 6. The device of claim 1, wherein the device is a portable telephonic device.
  • 7. The device of claim 1, wherein the device is a portable media player.
  • 8. The device of claim 1, further comprising a display operable to display a virtual card.
  • 9. The device of claim 1, further comprising a touch-sensitive display operable to display a virtual card.
  • 10. The device of claim 1, wherein the magnetic emulator is operable to communicate the data using RFID protocol.
  • 11. The device of claim 1, wherein the magnetic emulator is operable to communicate the data using frequency/double frequency (F2F) encoding.
  • 12. The device of claim 1, further comprising a display operable to display a virtual payment card, wherein said display is operable to display alphanumeric data.
  • 13. The device of claim 1, wherein the device is a portable telephonic device, and the device further comprising an RFID antenna operable to transmit RFID data in response to the processor detecting the presence of an RFID antenna.
  • 14. The device of claim 13, further comprising a touch screen graphical user interface.
  • 15. The device of claim 1, wherein the device is a card.
  • 16. The device of claim 15, further comprising an electronic ink display operable to display graphical information.
  • 17. The device of claim 16, wherein the magnetic emulator is further operable to transmit at least one of a string of leading zeros and trailing zeros.
  • 18. The device of claim 17, further comprising magnetic shielding.
  • 19. The device of claim 18, wherein the magnetic shielding is adjacent to the magnetic emulator.
  • 20. The device of claim 19, wherein the processor is operable to detect a presence of at least one of an RFID antenna and a magnetic stripe reader.
  • 21. The device of claim 20, further comprising an RFID antenna operable to transmit RFID data in response to the processor detecting the presence of an RFID antenna.
  • 22. The device of claim 21, further comprising memory.
  • 23. The device of claim 22, wherein the memory is operable to store payment information.
  • 24. The device of claim 23, wherein the processor comprises the memory.
  • 25. The device of claim 22, wherein the processor comprises the memory.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 13/557,525, filed on Jul. 25, 2012, which claims the benefit of U.S. Pat. No. 8,517,276, filed on Dec. 19, 2008, which claims the benefit of U.S. Provisional Patent Application Nos. 61/016,491 filed on Dec. 24, 2007, 61/026,846 filed on Feb. 7, 2008, 61/027,807 filed on Feb. 11, 2008, 61/081,003 filed on Jul. 15, 2008, 61/086,239 filed on Aug. 5, 2008, 61/090,423 filed on Aug. 20, 2008, 61/097,401 filed Sep. 16, 2008, 61/112,766 filed on Nov. 9, 2008, 61/117,186 filed on Nov. 23, 2008, 61/119,366 filed on Dec. 2, 2008, and 61/120,813 filed on Dec. 8, 2008, all of which are hereby incorporated by reference herein in their entirety.

US Referenced Citations (430)
Number Name Date Kind
4297735 Eppich Oct 1981 A
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
4789776 Inoue Dec 1988 A
4791283 Burkhardt Dec 1988 A
4797542 Hara Jan 1989 A
4902146 Ishikawa Feb 1990 A
5038251 Sugiyama et al. Aug 1991 A
5166774 Banerji et al. Nov 1992 A
5168520 Weiss Dec 1992 A
5237614 Weiss Aug 1993 A
5254843 Hynes et al. Oct 1993 A
5276311 Hennige Jan 1994 A
5291068 Rammel Mar 1994 A
5347580 Molva et al. Sep 1994 A
5361062 Weiss et al. Nov 1994 A
5412192 Hoss May 1995 A
5412199 Finkelstein et al. May 1995 A
5434398 Goldberg Jul 1995 A
5434400 Scherzer Jul 1995 A
5434405 Finkelstein et al. Jul 1995 A
5477038 Levine et al. Dec 1995 A
5478994 Rahman et al. Dec 1995 A
5479512 Weiss Dec 1995 A
5484997 Haynes Jan 1996 A
5485519 Weiss Jan 1996 A
5521831 May May 1996 A
5535078 Warwick Jul 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
5748737 Daggar May 1998 A
5834747 Cooper Nov 1998 A
5834756 Gutman et al. Nov 1998 A
5838549 Nagata et al. Nov 1998 A
5856661 Finkelstein et al. Jan 1999 A
5864623 Messina et al. Jan 1999 A
5866949 Scheuller Feb 1999 A
5886874 Onoda et al. Mar 1999 A
5907142 Kelsey May 1999 A
5907350 Nemirofsky May 1999 A
5913203 Wong et al. Jun 1999 A
5937394 Wong et al. Aug 1999 A
5941375 Kamens et al. Aug 1999 A
5955021 Tiffany, III Sep 1999 A
5955961 Wallerstein Sep 1999 A
5956699 Wong et al. Sep 1999 A
6005691 Grot Dec 1999 A
6012636 Smith Jan 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
6129274 Suzuki Oct 2000 A
6129277 Grant et al. Oct 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, Jr. et al. Sep 2001 B1
6308890 Cooper Oct 2001 B1
6313724 Osterweil Nov 2001 B1
6422462 Cohen Apr 2002 B1
6389442 Yin et al. May 2002 B1
6393447 Jakobsson et al. May 2002 B1
6402029 Gangi Jun 2002 B1
6411715 Liskov et al. Jun 2002 B1
6425960 Yoshizawa Jul 2002 B1
6446052 Juels Sep 2002 B1
6460141 Olden Oct 2002 B1
6574058 Aruga et al. Jun 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
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
6883714 Keogh Apr 2005 B2
6902116 Finkelstein Jun 2005 B2
6929550 Hisada Aug 2005 B2
6934664 Webb et al. Aug 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
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
7195160 Ison et al. 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
7306144 Moore Dec 2007 B2
7334732 Cooper Feb 2008 B2
7337326 Palmer et al. Feb 2008 B2
7346775 Gasparinl 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
7364092 Narendra et al. Apr 2008 B2
7370805 Smith et al. May 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
7441709 Chan et al. Oct 2008 B2
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
7516883 Hardesty Apr 2009 B2
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 Nyström 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
7591416 Blossom 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
7715593 Adams et al. May 2010 B1
7828207 Cooper Nov 2010 B2
7851517 Holmes Dec 2010 B2
7946501 Borracci May 2011 B2
7954708 Blossom Jun 2011 B2
7996318 Marcon Aug 2011 B2
8313037 Humphrey Oct 2012 B1
8517276 Mullen et al. Aug 2013 B2
8763916 Foo Jul 2014 B1
8931703 Mullen et al. Jan 2015 B1
9547816 Mullen et al. Jan 2017 B2
9704088 Mullen et al. Jul 2017 B2
9704089 Mullen et al. Jul 2017 B2
9727813 Mullen et al. Aug 2017 B2
9734345 Spodak et al. Aug 2017 B2
20010034702 Mockett et al. Oct 2001 A1
20010047335 Arndt et al. Nov 2001 A1
20020032657 Singh Mar 2002 A1
20020043566 Goodman et al. Apr 2002 A1
20020059114 Cockrill et al. May 2002 A1
20020070976 Tanner et al. Jun 2002 A1
20020073042 Maritzen Jun 2002 A1
20020082989 Fife et al. Jun 2002 A1
20020096570 Wong et al. Jul 2002 A1
20020108066 Masui Aug 2002 A1
20020120583 Keresman, III et al. Aug 2002 A1
20020134837 Kishon Sep 2002 A1
20020153424 Chuan Oct 2002 A1
20030030935 Yamamoto Feb 2003 A1
20030034388 Routhenstein et al. Feb 2003 A1
20030052168 Wong Mar 2003 A1
20030057278 Wong Mar 2003 A1
20030069846 Marcon Apr 2003 A1
20030085286 Kelley et al. May 2003 A1
20030098780 Taylor et al. May 2003 A1
20030111527 Blossom Jun 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
20030209608 Blossom Nov 2003 A1
20030218066 Fernandes et al. Nov 2003 A1
20030226899 Finkelstein Dec 2003 A1
20040011877 Reppermund Jan 2004 A1
20040035942 Silverman Feb 2004 A1
20040055770 Babb Mar 2004 A1
20040097054 Abe May 2004 A1
20040117514 Nelms Jun 2004 A1
20040127256 Goldwaithe Jul 2004 A1
20040128256 Krouse et al. Jul 2004 A1
20040133787 Doughty Jul 2004 A1
20040159700 Khan et al. Aug 2004 A1
20040162732 Rahim et al. Aug 2004 A1
20040172535 Jakobsson et al. Sep 2004 A1
20040177045 Brown Sep 2004 A1
20040179718 Chou Sep 2004 A1
20040212017 Mizuno et al. Oct 2004 A1
20040251303 Cooper Dec 2004 A1
20050001711 Doughty et al. Jan 2005 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
20050092830 Blossom May 2005 A1
20050116026 Burger et al. Jun 2005 A1
20050119940 Concilio et al. Jun 2005 A1
20050133590 Rettenmyer et al. Jun 2005 A1
20050133606 Brown Jun 2005 A1
20050154643 Doan et al. Jul 2005 A1
20050194452 Nordentoft et al. Sep 2005 A1
20050194453 Conner et al. Sep 2005 A1
20050219728 Durbin et al. Oct 2005 A1
20050228959 D'Albore et al. Oct 2005 A1
20050230788 Kato et al. Oct 2005 A1
20050274803 Lee Dec 2005 A1
20060000900 Fernandes et al. Jan 2006 A1
20060017570 Moskowitz et al. Jan 2006 A1
20060037073 Juels et al. Feb 2006 A1
20060041759 Kaliski et al. Feb 2006 A1
20060054699 Osterweil Mar 2006 A1
20060083931 Wadle et al. Apr 2006 A1
20060085043 Stevenson Apr 2006 A1
20060085328 Cohen et al. Apr 2006 A1
20060091223 Zellner et al. May 2006 A1
20060124748 Osborn et al. Jun 2006 A1
20060161435 Atef et al. Jul 2006 A1
20060161789 Doughty et al. Jul 2006 A1
20060163353 Moulette et al. Jul 2006 A1
20060174104 Crichton et al. Aug 2006 A1
20060186209 Narendra et al. Aug 2006 A1
20060196931 Holtmanns et al. Sep 2006 A1
20060217792 Hussein et al. Sep 2006 A1
20060227523 Pennaz et al. Oct 2006 A1
20060231611 Chakiris Oct 2006 A1
20060241236 Kuznetsov et al. Oct 2006 A1
20060249574 Brown et al. Nov 2006 A1
20060256961 Brainard et al. Nov 2006 A1
20060262585 Lenssen Nov 2006 A1
20060262655 Persson Nov 2006 A1
20060283940 Kuo Dec 2006 A1
20060283958 Osterweil Dec 2006 A1
20060289632 Walker Dec 2006 A1
20070023532 Narendra et al. Feb 2007 A1
20070029110 Matsumoto et al. Feb 2007 A1
20070034700 Poidomani et al. Feb 2007 A1
20070040030 Kranzley et al. Feb 2007 A1
20070052517 Bishop et al. Mar 2007 A1
20070063776 Okuda Mar 2007 A1
20070063804 Watanabe Mar 2007 A1
20070114274 Gibbs et al. May 2007 A1
20070124321 Szydlo May 2007 A1
20070131759 Cox Jun 2007 A1
20070136211 Brown et al. Jun 2007 A1
20070152052 Sines Jul 2007 A1
20070152070 D'Albore Jul 2007 A1
20070152072 Frallicciardi et al. Jul 2007 A1
20070153487 Frallicciardi et al. Jul 2007 A1
20070158439 Conner et al. Jul 2007 A1
20070174614 Duane et al. Jul 2007 A1
20070189591 Lu et al. Aug 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
20070263596 Charrat Nov 2007 A1
20070267503 Dewan Nov 2007 A1
20070285246 Koyoma 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
20080028447 O'Malley et al. Jan 2008 A1
20080029598 Fernandes et al. Feb 2008 A1
20080040271 Hammad et al. Feb 2008 A1
20080040276 Hammad et al. Feb 2008 A1
20080058016 DiMaggio et al. Mar 2008 A1
20080059379 Ramaci et al. Mar 2008 A1
20080093467 Narendra et al. Apr 2008 A1
20080096326 Reed Apr 2008 A1
20080116283 Newbrough May 2008 A1
20080116285 Shoemaker May 2008 A1
20080121726 Brady et al. May 2008 A1
20080126260 Cox et al. May 2008 A1
20080126262 Brady et al. May 2008 A1
20080126398 Cimino May 2008 A1
20080128515 Di Iorio Jun 2008 A1
20080140536 Ruiz Jun 2008 A1
20080148059 Shapiro Jun 2008 A1
20080148393 Wendt Jun 2008 A1
20080148394 Poidomani et al. Jun 2008 A1
20080150123 Li et al. Jun 2008 A1
20080201264 Brown et al. Aug 2008 A1
20080209550 Di Iorio Aug 2008 A1
20080217396 Boalt Sep 2008 A1
20080223937 Preta et al. Sep 2008 A1
20080238610 Rosenberg Oct 2008 A1
20080259551 Gavenda et al. Oct 2008 A1
20080262825 Haid et al. Oct 2008 A1
20080288699 Chichierchia Nov 2008 A1
20080290166 von Mueller Nov 2008 A1
20080294930 Varone et al. Nov 2008 A1
20080302877 Musella et al. Dec 2008 A1
20090006262 Brown et al. Jan 2009 A1
20090013122 Sepe et al. Jan 2009 A1
20090023476 Saarisalo et al. Jan 2009 A1
20090036147 Romano Feb 2009 A1
20090037275 Pollio Feb 2009 A1
20090046522 Sepe et al. Feb 2009 A1
20090048971 Hathaway et al. Feb 2009 A1
20090055893 Manessis et al. Feb 2009 A1
20090076921 Nelson et al. Mar 2009 A1
20090078761 Sines Mar 2009 A1
20090089041 Irving et al. Apr 2009 A1
20090090783 Killian et al. Apr 2009 A1
20090108064 Fernandes et al. Apr 2009 A1
20090134218 Yuzon et al. May 2009 A1
20090136211 Kikukawa et al. May 2009 A1
20090143104 Loh Jun 2009 A1
20090150295 Hatch et al. Jun 2009 A1
20090152365 Li et al. Jun 2009 A1
20090159663 Mullen Jun 2009 A1
20090159673 Mullen Jun 2009 A1
20090159689 Mullen Jun 2009 A1
20090164380 Brown Jun 2009 A1
20090166435 Blythe Jul 2009 A1
20090170432 Lortz Jul 2009 A1
20090191811 Griffin Jul 2009 A1
20090200367 Arnouse Aug 2009 A1
20090206165 Laackmann et al. Aug 2009 A1
20090210308 Toomer Aug 2009 A1
20090222349 Burger et al. Sep 2009 A1
20090222383 Tato Sep 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
20090261161 Blossom Oct 2009 A1
20090261166 Lawson et al. Oct 2009 A1
20090288012 Hertel Nov 2009 A1
20090290704 Cimino Nov 2009 A1
20090303885 Longo Dec 2009 A1
20100019033 Jolivet Jan 2010 A1
20100023449 Skowronek Jan 2010 A1
20100045627 Kennedy Feb 2010 A1
20100066701 Ningrat Mar 2010 A1
20100078472 Lin et al. Apr 2010 A1
20100108771 Wong May 2010 A1
20100117794 Adams et al. May 2010 A1
20100127830 Nielsen et al. May 2010 A1
20100153269 McCabe Jun 2010 A1
20100224684 Bonnin et al. Sep 2010 A1
20100230793 Kudose Sep 2010 A1
20100265617 Isuyama Oct 2010 A1
20100270373 Poidomani et al. Oct 2010 A1
20100275259 Adams et al. Oct 2010 A1
20100304670 Shuo Dec 2010 A1
20100304796 Stohr et al. Dec 2010 A1
20110028184 Cooper Feb 2011 A1
20110050164 Partovi et al. Mar 2011 A1
20110066550 Shank Mar 2011 A1
20110084149 Faith et al. Apr 2011 A1
20110117838 Bosquet et al. May 2011 A1
20110140538 Jung et al. Jun 2011 A1
20110140841 Bona et al. Jun 2011 A1
20110174874 Poznansky et al. Jul 2011 A1
20110178924 Briscoe et al. Jul 2011 A1
20110218911 Spodak Sep 2011 A1
20110240748 Doughty et al. Oct 2011 A1
20110272465 Mullen et al. Nov 2011 A1
20110272475 Mullen et al. Nov 2011 A1
20120074232 Spodak et al. Mar 2012 A1
20120280048 Kim Nov 2012 A1
20130020396 Mullen et al. Jan 2013 A1
20130200999 Spodak et al. Aug 2013 A1
20130344804 Chen et al. Dec 2013 A1
20140152417 Ebeid et al. Jun 2014 A1
20140339315 Ko Nov 2014 A1
20160239735 Mullen et al. Aug 2016 A1
20160292669 Tunnell et al. Oct 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
20180114036 Spodak et al. Apr 2018 A1
20180129923 Olson et al. May 2018 A1
Foreign Referenced Citations (33)
Number Date Country
102008060513 Jun 2010 DE
0203683 Dec 1986 EP
2259815 Mar 1993 GB
2420098 May 2006 GB
S63155188 Jun 1988 JP
05210770 Aug 1993 JP
05210770 Aug 1993 JP
H06150078 May 1994 JP
11087989 Mar 1999 JP
2005010964 Jan 2005 JP
2005056540 Mar 2005 JP
2005190363 Jul 2005 JP
2004165400 Dec 2005 JP
2006195925 Jul 2006 JP
2006252160 Sep 2006 JP
2007172214 Jul 2007 JP
2008225626 Sep 2008 JP
2009037495 Feb 2009 JP
2010044730 Feb 2010 JP
2010086026 Apr 2010 JP
2011134298 Jul 2011 JP
200287641 Aug 2002 KR
WO1989001672 Feb 1989 WO
WO9852735 Nov 1998 WO
WO0247019 Jun 2002 WO
WO06066322 Jun 2006 WO
WO2006078910 Jul 2006 WO
WO06080929 Aug 2006 WO
WO06105092 Oct 2006 WO
WO06116772 Nov 2006 WO
WO07141779 Dec 2007 WO
WO08064403 Jun 2008 WO
WO2008066806 Jun 2008 WO
Non-Patent Literature Citations (94)
Entry
U.S. Appl. No. 60/594,300, Poidomani et al.
Dynamic Virtual Credit Card Numbers. http://homes.cerias.purdue.edu/˜jtli/paper/fc07.pdf.
English translation of JP 05210770 A.
U.S. Appl. No. 60/494,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.
USPTO, International Search Report, dated Apr. 28, 2009.
English translation of JP 05210770.
EPO, Extended European Search Report, dated Jan. 26, 2012.
Translation of KR200287641Y1.
Translation of JP2005056540A.
Examination Report dated Nov. 9, 2016, received from Australian Patent Office for Australian Patent Application No. 2011218216.
Examination Report dated Sep. 19, 2017, received from Australian Patent Office for Australian Patent Application No. 2016259296.
Examination Report dated Feb. 17, 2016, received from Australian Patent Office for Australian Patent Application No. 2011255568.
Examination Report dated Feb. 13, 2017, received from Australian Patent Office for Australian Patent Application No. 2011255568.
Examination Report dated Oct. 30, 2017, received from Australian Patent Office for Australian Patent Application No. 2017201100.
Examination Report dated Feb. 23, 2016, received from Australian Patent Office for Australian Patent Application No. 2011283665.
Examination Report dated Feb. 23, 2017, received from Australian Patent Office for Australian Patent Application No. 2011283665.
Examination Report dated Aug. 25, 2016, received from Australian Patent Office for Australian Patent Application No. 2012240353.
Examination Report dated Feb. 17, 2016, received from Australian Patent Office for Australian Patent Application No. 2017219095.
Examination Report dated Jun. 14, 2016, received from Australian Patent Office for Australian Patent Application No. 2012235439.
Examination Report dated May 12, 2017, received from Australian Patent Office for Australian Patent Application No. 2012235439.
Examination Report dated Jun. 13, 2017, received from Australian Patent Office for Australian Patent Application No. 2012235439.
Examination Report dated Mar. 29, 2018, received from Australian Patent Office for Australian Patent Application No. 2017204011.
Examination Report dated Oct. 11, 2012, received from Australian Patent Office for Australian Patent Application No. 2008340226.
Examination Report dated Oct. 11, 2016, received from Australian Patent Office for Australian Patent Application No. 2008340226.
Examiner's Requisition dated Mar. 29, 2016, received from Canadian Patent Office for Canadian Patent Application No. 2,789,461.
Examiner's Requisition dated Mar. 8, 2017, received from Canadian Patent Office for Canadian Patent Application No. 2,798,984.
Examiner's Requisition dated Feb. 22, 2018, received from Canadian Patent Office for Canadian Patent Application No. 2,805,310.
Examiner's Requisition dated Dec. 10, 2018, received from Canadian Patent Office for Canadian Patent Application No. 2,831,459.
Examiner's Requisition dated Jan. 18, 2018, received from Canadian Patent Office for Canadian Patent Application No. 2,831,464.
Examiner's Requisition dated Dec. 13, 2018, received from Canadian Patent Office for Canadian Patent Application No. 2,831,464.
Office Action dated Dec. 6, 2018, received from Indian Patent Office for Indian Patent Application No. Dec. 6, 2018.
Office Action dated Dec. 12, 2017, received from South Korean Patent Office for Korean Patent Application No. 20137029089.
English translation of Office Action dated Dec. 12, 2017, received from South Korean Patent Office for Korean Patent Application No. 2013-7029089.
Office Action dated May 28, 2018, received from South Korean Patent Office for Korean Patent Application No. 2013-7029089.
English translation of Office Action dated May 28, 2018, received from South Korean Patent Office for Korean Patent Application No. 2013-7029089.
Office Action dated Sep. 13, 2018, received from South Korean Patent Office for Korean Patent Application No. 2013-7029089.
English translation of Office Action dated Sep. 13, 2018, received from South Korean Patent Office for Korean Patent Application No. 2013-7029089.
Office Action dated Nov. 14, 2018, received from Japanese Patent Office for Japanese Patent Application No. 2017195295.
English translation of Office Action dated Nov. 14, 2018, received from Japanese Patent Office for Japanese Patent Application No. 2017195295.
Office Action dated Jun. 27, 2018, received from Japanese Patent Office for Japanese Patent Application No. 2016210782.
English translation of Office Action dated Jun. 27, 2018, received from Japanese Patent Office for Japanese Patent Application No. 2016210782.
Office Action dated Oct. 30, 2017, received from Japanese Patent Office for Japanese Patent Application No. 2016210782.
English translation of Office Action dated Oct. 30, 2017, received from Japanese Patent Office for Japanese Patent Application No. 2016210782.
Office Action dated Aug. 29, 2018, received from Japanese Patent Office for Japanese Patent Application No. 2016153360.
English translation of Office Action dated Aug. 29, 2018, received from Japanese Patent Office for Japanese Patent Application No. 2016153360.
Office Action dated Oct. 12, 2017, received from Japanese Patent Office for Japanese Patent Application No. 2016153360.
English translation of Office Action dated Oct. 12, 2017, received from Japanese Patent Office for Japanese Patent Application No. 2016153360.
Office Action dated Jun. 5, 2016, received from Japanese Patent Office for Japanese Patent Application No. 2016000177.
English translation of Office Action dated Jun. 5, 2016, received from Japanese Patent Office for Japanese Patent Application No. 2016000177.
Office Action dated Nov. 9, 2016, received from Japanese Patent Office for Japanese Patent Application No. 2016000177.
English translation of Office Action dated Nov. 9, 2016, received from Japanese Patent Office for Japanese Patent Application No. 2016000177.
Office Action dated Jun. 27, 2016, received from Japanese Patent Office for Japanese Patent Application No. 2013522010.
English translation of Office Action dated Jun. 27, 2016, received from Japanese Patent Office for Japanese Patent Application No. 2013522010.
Office Action dated Jul. 29, 2017, received from Japanese Patent Office for Japanese Patent Application No. 2013522010.
English translation of Office Action dated Jul. 29, 2017, received from Japanese Patent Office for Japanese Patent Application No. 2013522010.
Office Action dated Apr. 4, 2016, received from Japanese Patent Office for Japanese Patent Application No. 2013533532.
English translation of Office Action dated Apr. 4, 2016, received from Japanese Patent Office for Japanese Patent Application No. 2013533532.
Office Action dated Mar. 18, 2015, received from Japanese Patent Office for Japanese Patent Application No. 2013533532.
English translation of Office Action dated Mar. 18, 2015, received from Japanese Patent Office for Japanese Patent Application No. 2013533532.
Office Action dated Dec. 2, 2015, received from Japanese Patent Office for Japanese Patent Application No. 2012553989.
English translation of Office Action dated Dec. 2, 2015, received from Japanese Patent Office for Japanese Patent Application No. 2012553989.
Office Action dated Nov. 4, 2014, received from Japanese Patent Office for Japanese Patent Application No. 2012553989.
English translation of Office Action dated Nov. 4, 2014, received from Japanese Patent Office for Japanese Patent Application No. 2012553989.
Summons to attend oral proceedings dated Sep. 18, 2013, received from European Patent Office for European Patent Application No. 08865573.3.
European Search Report dated Jan. 25, 2012, received from European Patent Office for European Patent Application No. 08865573.3.
European Search Report dated May 2, 2013, received from European Patent Office for European Patent Application No. 08865573.3.
Decision on Appeal dated May 5, 2014, received from European Patent Office for European Patent Application No. 08865573.3.
European Search Report dated Sep. 23, 2015, received from European Patent Office for European Patent Application No. 13752216.5.
Summons to attend oral proceedings dated Jul. 4, 2018, received from European Patent Office for European Patent Application No. 12783038.8.
European Search Report dated Feb. 27, 2015, received from European Patent Office for European Patent Application No. 12783038.8.
European Search Report dated Apr. 8, 2016, received from European Patent Office for European Patent Application No. 12783038.8.
European Search Report dated Oct. 19, 2017, received from European Patent Office for European Patent Application No. 17173592.1.
Summons to attend oral proceedings dated Sep. 19, 2016, received from European Patent Office for European Patent Application No. 12767357.2.
European Search Report dated Aug. 22, 2014, received from European Patent Office for European Patent Application No. 12767357.2.
European Search Report dated Aug. 18, 2015, received from European Patent Office for European Patent Application No. 12767357.2.
Decision on Appeal dated Mar. 30, 2017, received from European Patent Office for European Patent Application No. 12767357.2.
European Search Report dated Feb. 12, 2018, received from European Patent Office for European Patent Application No. 17182452.7.
Summons to attend oral proceedings dated Oct. 19, 2016, received from European Patent Office for European Patent Application No. 11813282.8.
European Search Report dated Jul. 22, 2014, received from European Patent Office for European Patent Application No. 11813282.8.
European Search Report dated Aug. 24, 2015, received from European Patent Office for European Patent Application No. 11813282.8.
Decision on Appeal dated Oct. 5, 2017, received from European Patent Office for European Patent Application No. 11813282.8.
European Search Report dated Oct. 7, 2016, received from European Patent Office for European Patent Application No. 16172188.1.
European Search Report dated Jun. 15, 2015, received from European Patent Office for European Patent Application No. 11784196.5.
European Search Report dated Nov. 10, 2015, received from European Patent Office for European Patent Application No. 11784196.5.
European Search Report dated Aug. 15, 2018, received from European Patent Office for European Patent Application No. 11784196.5.
European Search Report dated Dec. 18, 2017, received from European Patent Office for European Patent Application No. 11784196.5.
European Search Report dated Feb. 7, 2014, received from European Patent Office for European Patent Application No. 11745157.5.
European Search Report dated Oct. 29, 2018, received from European Patent Office for European Patent Application No. 11745157.5.
European Search Report dated Jun. 20, 2017, received from European Patent Office for European Patent Application No. 11745157.5.
European Search Report dated Jul. 7, 2016, received from European Patent Office for European Patent Application No. 11745157.5.
Related Publications (1)
Number Date Country
20160342877 A1 Nov 2016 US
Provisional Applications (11)
Number Date Country
61016491 Dec 2007 US
61026846 Feb 2008 US
61027807 Feb 2008 US
61081003 Jul 2008 US
61086239 Aug 2008 US
61090423 Aug 2008 US
61097401 Sep 2008 US
61112766 Nov 2008 US
61117186 Nov 2008 US
61119366 Dec 2008 US
61120813 Dec 2008 US
Continuations (2)
Number Date Country
Parent 13557525 Jul 2012 US
Child 15225095 US
Parent 12339045 Dec 2008 US
Child 13557525 US