Cards and devices with magnetic emulators with zoning control and advanced interiors

Information

  • Patent Grant
  • 11494606
  • Patent Number
    11,494,606
  • Date Filed
    Monday, May 1, 2017
    7 years ago
  • Date Issued
    Tuesday, November 8, 2022
    2 years ago
Abstract
A payment card (e.g., credit and/or debit card) is provided with a magnetic emulator operable to act as a magnetic stripe read-head detector and a data transmitter. A multiple layer flexible PCB may be fabricated to include multiple magnetic emulators. An emulator may include a coil that includes magnetic, ferromagnetic, or ferromagnetic, material in the coil's interior. Coils may be associated with zones. As a read-head is detected to move from zone-to-zone, coils may be activated to transmit information in those zones.
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 or more) the read-head.


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. 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 device, such as a magnetic stripe. 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.


Magnetic emulation circuits may be provided that generate electromagnetic fields. The emulation circuits may have active regions operable to be read by a read-head of a magnetic stripe reader. The emulation circuits may also have, for example, non-active regions that are not operable to be read by a read-head of a magnetic stripe reader. Multiple emulation circuits may be provided on different layers such that the active regions of multiple emulation circuits provide a read-head of a magnetic stripe reader continuous visibility to active regions while a card is swiped. A coil may include return paths that may be able to, for example, transmit information to a read-head but may communicate information using electromagnetic fields in an opposite direction than the primary paths (e.g., active regions) of a coil such that a reader may not be able discern a set of when the reader picks up part of the information from a return path followed by part of the information from a primary path (or vice versa).


Magnetic emulation circuits may extend across multiple tracks. However, the areas of such magnetic emulation circuits that extended to undesired tracks may be configured to be invisible to the read-heads for those tracks. For example, a magnetic emulator may produce magnetic fields that are not oriented properly to be picked up by unintended read-head(s) but that are oriented properly to be picked up by intended read-head(s).


Read-head detectors may be provided to determine, for example, when a card is being swiped and/or when a read-head is located over a particular portion of a card (e.g., a magnetic emulation circuit). A magnetic emulation circuit may be provided as, for example, a coil. Portions of such a coil may be utilized to detect a read-head while in other portions of the coil may be utilized to communicate information electromagnetically to a read-head. Accordingly, a coil may be utilized to detect a read-head and, after a read-head is detected, the coil may be utilized to, for example, serially transmit information to a magnetic stripe reader.


A read-head detector, or an array of read-head detectors, may be able to, for example, determine the type of reader that the card entered into. For example, a read-head detector array may determine, for example, when a motorized reader was utilized, an insertion reader was utilized, or a user-swipe reader was utilized. Such information may be stored and communicated to a remote storage device (e.g., a remote database). This stored information may be utilized to combat, for example, card cloning. For example, if a particular number of cards (e.g., 10 more) that made consecutive purchases from a machine (e.g., an ATM) detected more than one reader, then, for example, the system may make an autonomous determination that an illegal cloning device was located on front of that ATM machine. If, for example, multiple cards use a restaurant point-of-sale terminal and determine that multiple readers were used then, for example, a computer can make an autonomous determination that cloning may have occurred at the restaurant.


Cards may be swiped through the same reader multiple times for a number of reasons (e.g., mis-swipes). However, over a number of cards (e.g., 100), instances of cloning may become apparent. Additionally, for example, information about swipes that happened outside of a transaction (e.g., the period from which the card is active after an appropriate unlocking code is entered) may be transmitted to detect instances where a magnetic emulator was turned ON and read by a reader, but no transaction was received by a processing/authorization facility. Such information may be utilized to, for example, provide an alert that the user may have encountered, and tried to use, a fake ATM machine.


Multiple magnetic emulators may be coupled in series. Multiple magnetic emulators, or arrays of magnetic emulators, may be controlled independently. Emulators may be assigned zones and may be utilized to communicate information on a zone-by-zone basis. In doing so, for example, emulators that include coils with return paths may place those return paths in other zones. Accordingly, the primary paths for an emulator may be included in a zone to communicate information when that zone is activated. When other zones are activates, the return paths of the emulator may not interfere with the primary paths of other emulators that are attempting to communicate information. Read-head detectors may be utilized, for example, to provide information to a processor so that the processor may make a determination as to what zone, or zones, should be activated to communicate information at any given time.


Magnetic emulators, such as magnetic emulators that include coils, may be fabricated on multiple layers of either flexible or rigid printed circuit board. Accordingly, a coil may be fabricated over multiple layers. Materials may be placed in the interior of these coils to assist the coil in communicating information to a read-head. For example, two PCB layers may be utilized. The top layer may be utilized for one set of paths (e.g., primary paths) and the bottom layer may be utilize for another set of paths (e.g., return paths).


A material may be sandwiched between the two layers to assist in reducing the effect of the electromagnetic fields from one set of coil segments on the side of the material opposite that set of coil segments. Such an interior material may be insulated such that the material does not short the coil segments. Additionally, such an interior material may be chosen, for example, such that the material does not saturate when the coil is conducting current. The coil and material may run, for example, along the location of a track of magnetic data for a payment card.


A material may be placed and/or printed on a PCB layer and sandwiched between two other PCB layers. These two other layers may each include coil segments and vias. The middle layer may also include vias such that the material is fabricated to be located in the center of the coil. The material may take a cylindrical, rectangular, square, or any type of shape. Four layers may also be utilized, where the coil segments are printed on a surface of the exterior layers and one or more materials are printed and/or placed on/between the interior layers. A material may be a magnetic material, ferromagnetic material, ferrimagnetic material, or any type of material. For example, copper may be printed on a PCB layer and plated with a material (e.g., nickel, iron, chrome, tin, gold, platinum, cobalt, zinc, alloys). A material, for example, may have a relative permeability multiple times greater than the permeability of a vacuum. A material, for example, may have a permeability of 2 to 25,000 N/A^2. A material may include, for example, a permalloy, iron, steel, ferrite, nickel or any other material. A material may be an alloy such as a nickel-iron alloy. Such a nickel-iron alloy may include, for example, nickel (e.g., 75-85%), iron, copper, molybdenum and may be placed through one or more annealing processes. Annealing may occur before and/or after the material is placed/printed on a layer of material (e.g., a PCB layer or other layer). A similar and/or different material may be placed either above and/or below a portion, or the entire, set of paths on a layer for a coil. Accordingly, for example, a material may be placed in the interior of a coil as well as along a side of the coil.





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



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



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



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



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



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



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



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



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



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



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



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



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



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



FIG. 17 is an illustration of a card 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 or any other type of card (e.g., security access or identification 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 server 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 identified 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. Magnetic emulator 151 may be included and 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 provided 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. Emulator 151 may be included such that dynamic information may be communicated to a magnetic stripe reader, for example, without a magnetic stripe via an electromagnetic signal transmitted directly from emulator 151 to a read-head of a magnetic stripe reader. Any combination of emulators and static magnetic tracks may be utilized for a card or device (e.g., two magnetic emulators without any magnetic stripes).


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 202. Both RFID antenna 210 and magnetic emulator 202 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. A smart-card chip may, for example, be included on card 200 in lieu of, or in addition to, RFID 210.


Persons skilled in the art will appreciate that a static magnetic track may be a read-write track such that information may be written to a magnetic track from a magnetic stripe reader that includes a head operable to magnetically encode data onto a magnetic track. Information may be written to a magnetic track 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).


A card may include magnetic emulators without, for example, including a static magnetic track. Read-head detectors 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 250 includes emulator 251 that includes a coil operable to communicate data serially to a magnetic stripe reader. Similarly, for example, emulator 251 may receive information for a magnetic stripe encoder. Persons skilled in the art will appreciate that a coil may run across the length of a card such that a read-head moves along the length of the coil and can receive information transmitted serially from the coil. The coil may extend into multiple tracks such that multiple read-heads receive information from the coil. Track information can be sent serially (e.g., track 1 information followed by track 2 information). Multiple coils may be driven separately and placed in different zones such that a single read-head moves from coil-to-coil (e.g., zone-to-zone) and power is conserves as only coils in a particular zone (or zones) may be utilized to communicate information any particular time. Separate coils may be utilized for separate tracks. Materials may be placed in the interior of each coil to assist with manipulating the electromagnetic field produced by the coils. Material may be placed above or below a coil to further manipulate the electromagnetic field produced by the coil. Switching circuitry 252 may include, for example, one or more transistors that may be utilized to control the direction of current via emulator 251 (e.g., the polarity of voltage(s) across a drive resistor). For example, a coil may be utilized to transmit a string of information to a particular read-head. Different coils may transmit information at different speeds (or at the same speed). Different coils may transmit different amounts of information. For example, three coils may be provided. The coil closest to the bottom of the long-end of a card may transmit at least 79 characters. The coil next closest to the bottom of the long-end of a card may transmit at least 40 characters of information. The coil next closest to the bottom of the long-end of the card may transmit at least 107 characters. One or more coils may have different character sets (e.g., a 6-bit character set or a 7-bit character set). The last bit in a character may include, for example, a parity bit. Additional synching information may be transmitted before and after the data information to assist with synching a magnetic stripe reader. For example, a string of zeros may be communicated before and after communicating primary data. Characters may be included in the data information for other purposes such as an LRC character.



FIG. 3 shows fabrication process 300, in which layer 310, 320, and 330 are attached together. Layer 310 may include a set of coil segments that are coupled to a set of coil segments on layer 330 to form a coil. Layer 320 may include material 354 to assist in manipulating the electromagnetic field generated by the coil. Vias may be placed on layer 320 such that the coil segments from layer 310 may be coupled to the coil segments from layer 330. Layers may be, for example, layers of a flexible or rigid material such as an FR4 epoxy dielectric. Coil 390 may be formed from such a process that may include top view 391 and cross-sectional view 392.



FIG. 4 shows environment 400 that may include magnetic stripe reader 410, read-head housing 440, card 420, and magnetic emulator 430. Read-head housing 440 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 430 (or a magnetic stripe, such as a magnetic stripe encoded on-card by card 420). Emulator 430 may be positioned to be adjacent to any one or more read-heads of read-head housing 440 or may be positioned to communicate information to any one or more read-heads of read-head housing 440. 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. 5 includes environment 500 that may include cards 520 and 530 as well as magnetic stripe reader 510. Read-head housing 511 may be included on a wall of a trough of magnetic stripe reader 510. The trough may be sized to accept cards (e.g., credit cards).


Card 520 may include emulator 521. Emulator 521 may provide electromagnetic field 591 that may transmit through a portion of the housing of magnetic stripe reader 510 (e.g., through a wall of a trough to get to read-head housing 511). Accordingly, card 520 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 521 can provide electromagnetic field 591 over a distance of, for example, a quarter of an inch or more.


Persons skilled in the art will appreciate that card 520 may be coupled to a device via a permanent or removable cable. Such a device may provide power to card 520 as well as control information—such as control information for emulator 530. An external source of power may be utilized, for example, to provide a larger amount of electrical energy to emulator 521 than from a source of power located within card 520. 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 530 may be provided with emulator 531 and may electrically couple with a read-head of magnetic stripe reader 510. Any number of emulators may be provided in card 530 in any number of orientations such that the appropriate electromagnetic field may couple with a read head of read-head housing 511 regardless of the orientation of card 720 with respect to read-head 511. More particularly, for example, additional read-head housings may be provided in magnetic stripe reader 510 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 511 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 521 may, for example, communicate magnetic fields outside both the front and read surfaces of a card. Accordingly, a single emulator 521 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 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 and may be laminated to form a card using, for example, a hot and/or cold lamination. Portions of an electronic ink display may also be fabricated on a layer during a PCB printing process.


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).


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. 6 includes topology 600 that may be utilized to communicate information to a read-head. Topology 600 may include magnetic emulators 610, 620, 630, 640, 650, 660, 670, and 680. Each of these magnetic emulators may be provided on a different layer and aligned such that the primary paths are seen, from the perspective of a read-head as one set of paths. The return paths may be aligned to minimize the amount of time a read-head is located above the return paths of the magnetic emulators. The magnetic emulators may be coupled in series or operated independently. Additional layers may be included to include additional routing between the magnetic emulators. A magnetic emulator may be, for example, a flat coil placed on a single layer of material. Current may be provided through a magnetic emulator such that the magnetic emulator generates an electromagnetic signal. A primary path of a coil may include a dense section of coil segments where current runs through those coil segments in the same direction. Accordingly, the electromagnetic field is intensified in active region compared to the area of the coil with coil segments that are widely spaced or not configured in an orientation where the magnetic fields from these coil segments can be read. Accordingly, a current may be placed through the coil such that a magnetic stripe reader is operable to receive information from active region 651 but not the region outside active region 651. Persons skilled in the art will appreciate that the direction of current through magnetic circuit 650 may be changed and controlled in a pattern that is representative of magnetic stripe data. Particularly, a processor may, for example, transmit information through a coil by changing the direction of the electromagnetic field generated from emulator circuit at particular times. A change in the frequency of field reversals may be representative of, for example, a particular bit of information (e.g., “1” or “0”). Magnetic emulation circuit 650 may include a dense active region and a less dense return paths. A magnetic emulation circuit may include return paths that also can transmit information to a read-head, but that provides an electromagnetic field in an opposite direction to that of a primary path. Accordingly, read-head sensors may be placed, for example, such that no current is provided through a magnetic emulator while a read-head is over a return path, but the emulator is utilized to communicate information when the read-head (or read-heads are located over the primary path). Additionally, a processor may change how an emulator is controlled in order to accommodate the different electromagnetic fields produced by the two regions such that a portion of a set of data can be transmitted by a return path and a portion of the set of data can be transmitted by a primary path. If zones, for example, are implemented, the return path may be utilized to communicate a portion of information when that zone associated with the return path is utilized and primary paths may be utilized to communicate another portion of information the zone associated with the primary path is activated. Accordingly, return paths may be staggered in order to increase their total visibility to a read-head. Magnetic emulators 610, 620, 630, 640, 650, 660, 670, 680, and 680 may be sized to fit, for example, within the footprint of a track of data for a payment card. The primary paths of these magnetic emulators may be staggered such that, from above, a continuous set of primary path segments is seen. Accordingly, the emulators may be controlled in the same way such that, for example, a continuous electromagnetic field is produced and can be controlled. Accordingly, data can be communicated serially through this continuous electromagnetic field to a magnetic stripe reader. An instance of topology 600 may, for example, be provided for each track of information on a magnetic card. Different magnetic emulator topologies may be utilized for different tracks. Different magnetic emulators in a magnetic emulator topology may be provided different amounts of current such that emulators at different depths can provide a sufficient electromagnetic field at the surface of topology 600.



FIG. 7 shows topology 700 where the primary paths of multiple emulators are provided on a layer of material and the return paths for the coils that are included in those emulators are provided on different layers. Accordingly, for example, each emulator may be provided with the same amount of current to produce a sufficient electromagnetic field. Such coils may be, for example, flat coils that are bent onto multiple layers (e.g., utilizing vias).


Topology 700 may include coil 711 with two portions of return paths and one portion of primary paths that may be, for example, visualized as return portion 712, primary portion 713, and return portion 714. The primary portion may be viewed from an eagle-eye perspective as portion 715. Multiple emulator design 730 is included that may include multiple emulators with primary paths located adjacent to one another to provide a continuous electromagnetic field. The emulators may be controlled independently such that different emulators are utilized to communicate information at different times. Accordingly, emulators may be utilized from left-to-right as a reader passes over the emulators from left-to-right. For example, read-head detector 761 of circuit 750 may detect the presence of a read-head (e.g., a housing that stores a read-head) and may signal the processor to communicate with emulators 751 and 752. When read-head detector 762 detects the presence of the read-head, read-head detector 762 may signal the processor to communicate with emulators 752, 754, and 755. Read-head detectors 761 and 762 may be, for example, contacts coupled to a capacitive sensing circuit or different capacitive sensing circuits.



FIG. 8 shows topology 800 that may include, for example, zones 810, 820, 830, 840, 850, and 860. Topology 800 may be a cross-sectional perspective of a multiple layer card. Primary paths 891 and 892 may, for example, be located in zone 810 and primary paths 892, 893, and 894 may be located in zone 820. Primary path 892 may be utilized, for example, to produce a transitional electromagnetic field between zones 810 and 820. Read-head detector 899, for example, may be utilized to signal the processor to change from operating zone 810 to operating zone 820 to communicate data. Primary portions may be divided into more than one primary portion and placed in different zones such that an emulator that includes a coil having two primary portion may cover more than one zone as well as non-adjacent zones. Similarly, return paths portions may be utilized to communicate data and primary portions may not be utilized (e.g., using a zone-based control methodology).



FIG. 9 shows circuit 900 that may include primary paths on one layer, but that may place a different return path on different vertical layers such that the return paths are vertically stacked. In doing so, the area of the return paths (as viewed by a read-head) may be minimized. In a zone-based control topology, minimizing the read-head visibility to the return paths may, for example, allow for a layer margin of error when detecting the location of a read-head. Circuit 900 may include return paths 910, 920, and 930.



FIG. 10 includes circuit 1000 that may include, for example, a return portion that forms a triangle such that a return path includes two segments that are angled from one another. Each segment may be at a 45 degree angle from a path (e.g., a path it is vertically aligned with) and the two may be, for example, at a 90 degree angle from one another. One or more materials may be placed between the primary paths and the return paths either from the perspective of going into the page or spanning the length of the page (e.g., threading through the open loop created by the primary and return paths). Circuit 1000 may include return paths 1010, 1020, and 1030.



FIG. 11 includes circuit 1110 that may be, for example, a coil. Circuit 1120 may be included that includes two angled return path segments that are located in area 1222, which is outside track footprint 1121. Area 1122 may correspond to an area, for example, that is outside of where a read-head (or read-head housing) passes.



FIG. 1200 shows coil 111 that may include interior material 1210. Multiple pieces of interior material 1210 may be provided inside of coil 1211. Interior material 1210 may be, for example, a magnetic, ferromagnetic, and/or a ferromagnetic material. A powder may be utilized. An alloy may be utilized. An interior material may extend various distances outside of a coil. An interior material may end at the last coil segment of a coil. Coil 1221 includes interior segment 1220.


A coil may be wrapped around interior materials of different shapes and sizes. A gap between a coil may be provided having various distances. A material may be provided between the interior material and the coil such that the interior material does not, for example, short the coil. An interior material may be, for example, rectangular (e.g., material 1230), square (e.g., material 1240), or cylindrical (e.g., material 1250).



FIG. 13 shows card 1300 that may include, for example, processor 1320, display 1340, switching circuitry 1330, read-head detectors 1350 and 1360, and coils 1370, 1380, and 1385. Coils 1370, 1380, and 1385 may span the length of a track and may communicate information serially. Coils 1370, 1380, and 1385 may be spaced and controlled such that the electromagnetic field from one coil does not introduce interference in a read-head attempting to read information from another track (e.g., an adjacent track). An interior material may be provided to assist in manipulating the profile of the electromagnetic field provided by a coil.


A read head detector may include a cluster of read-head detectors such as cluster 1390. Cluster 1390 may include read-head detectors 1391-1399. Each read-head detector may be, for example, a capacitive sensor. The read-head detectors may thus, for example, be conductive areas coupled to a capacitive sensing circuit. Cluster 1390 may be coupled to a multi-channel capacitive sensing circuit. Each of the contacts of a cluster may be coupled to their own capacitive sensing circuit. A microprocessor may be utilized in capacitive sensing. Any type of read-head detector may be utilized in cluster 1390. For example, a read-head detector may include a physical contact, proximity, optical, or other detector. A cluster may include multiple different types of read-head detectors. Cluster 1390 may be utilized to discern, for example, between different objects. For example, a processor may determine that a user swiped the card through a reader if, for example, 1) only read-head detector 1396 detects an object; 2) after read-head detector 1396 detects an object, only read-head detector 1395 detects an object; and 3) after read-head detector 1395 detects an object, only read-head detector 1394 detects an object. Accordingly, different detection profiles can be associated with readers such that if other types of objects are detected, the processor can discern between these objects and read-heads. Different profiles may be associated with different readers (e.g., motorized, insertion-swipe, and user-swipe). Such different profiles may be utilized to better combat card cloning as, for example, a fake reader overlaid on top of a legitimate ATM machine may have a different profile.


Persons skilled in the art will appreciate that a magnetic emulation circuit may act as a read-head detector as well as a magnetic information transmitter. For example, a magnetic emulator may be driven according to a process that includes a step in which a correct Personal Identification Code (e.g., a PIN) is determined to have been entered on a card. Accordingly, another step may activate, in which a coil is driven such that its return paths act as a read-head detector. This may be done in numerous ways. For example, the current providing an electromagnetic field may undergo a phase-shift when a magnetic and/or conductive material is placed in the electromagnetic field. Accordingly, a phase-shift may be determined. When such a phase-shift is determined, a step may initiate and a magnetic emulation circuit may be driven to communicate data serially. Accordingly, some region(s) may be utilized to detect a read-head and other region(s) 1220 may be utilized to communicate information to that read-head. Persons skilled in the art will appreciate that a magnetic emulation circuit may not be supplied current until an appropriate Personal Identification Code (PIC) is entered into manual interfaces located on the card. Such a scheme, for example, provides for power savings as well as prevents card cloning. Accordingly, a magnetic emulator may be driven into a read-head detector mode upon receiving an appropriate manual input and then into a data transmission mode after determining the presence of a read-head.



FIG. 14 shows card 1400 that may include display 1440, processor 1420, display 1450, switching circuitry 1430, emulators 1470 and 1480, and read-head detector 1460. Read-head detector 1460 may be located such that emulators are located between read-head detector 1460 and an edge of the card. Accordingly, for example, a read-head detector may be triggered when a read-head is in the middle of the card such that a single read-head detector can be utilized. Data may be communicated quickly such that all data is transmitted serially before a read-head (or read-heads) travel past emulators 470 and 480. Additionally, a capacitive sensing circuit may be coupled to detector 1460 without having the interconnection fall within the path of a moving read-head. In doing so, capacitive changes in the interconnection due to a read-head moving over an interconnection may not mis-trigger a capacitive sensing circuit.


Persons skilled in the art will appreciate that a user's payment card number (e.g., credit card or debit card number) does not have to change. A display may hide this payment card number until an appropriate unlocking code is entered into buttons of the card. Similarly, a magnetic emulator may not be provided current until the proper unlocking code is entered—thus keeping magnetic information private and not allowing undesirable readers to read a card. A security code may be displayed on the same or a different display. A button may be provided representative of an online purchase (or a user may utilize buttons to instruct the processor that an online purchase is desirable). For such an online purchase, the credit card number and the security code may be displayed—but the magnetic emulator may not be activated. In doing so, the level of security of the card is increased. Furthermore, for example, a button may be provided representative of in-store purchases (or a user may utilize buttons to instruct the processor that an in-store purchase is desirable). Accordingly, a processor may be signaled that an in-store purchase is desired. A different operation may be associated with different types of purchases (e.g., online or in-store). Accordingly, for example, magnetic emulators may be activated for an in-store environment—but not the displays. Accordingly, for example, a restaurant cashier may not be able to read the credit card number from the card, but may still be able to swipe the card. If a reader is down or a cashier requires reading particular information (e.g., a security code or credit card number information) then controls may be utilized to communicate this information. A record of the types of transactions may be stored and may be communicated in discretionary fields of data within a transmitted data track. Such record information may be utilized, for example, to further increase security and/or introduce a variety of additional functionality.


Different types of cards may be provided on a card. For example, a security ID number and a credit card number may both be provided on the same card. A button may be utilized to allow a user to provide instruction to a processor such that the processor can display (e.g., visually and/or magnetically) the desired information. For example, a user may determine to use one of a variety of payment accounts (e.g., credit and/or debit) for a purchase. An entire payment number (e.g., credit or debit) may be changed and/or hidden visually and/or magnetically. A portion of a payment card number (e.g., credit or debit) may be changed and/or hidden visually and/or magnetically.


Persons skilled in the art will appreciate that a display on the card may display a credit card number that does not change with time. Additionally, for example, a magnetic emulator (or multiple magnetic emulators) may magnetically communicate financial data that does not change with time. Such a card may reduce, for example, the effects of physical card theft and card cloning.


One or more light generation devices, such as a Light Emitting Diode (LED), may be provided as part of a card (or other device). Such an LED may produce light, for example, upon a manual input such as a button press, the correct entry of a PIC such as a PIN, and/or the incorrect entry of a PIC. A light emitting device may be operable to produce different colors of light. For example, the incorrect entry of a PIC may produce a red light and the correct entry of a PIC may produce a green light. A PIC may take any form such as a numerical code or a code that include alphabet letters and/or symbols. For example, a PIC may be “A-B-B-B-A” and an “A” button may be provided on a card in addition to a “B” button (as well as other buttons such as a “C,” “D,” and/or “E” buttons).


Persons skilled in the art will appreciate that any numbers of a credit card number may remain static and/or change either with time or based off a transaction (e.g., by sensing a read-head “swipe”). Additionally, any static and/or dynamic numbers may be displayed via a display or printed on a card. For example, a middle 6 digits of a credit/debit card number may be static and may be displayed on a display. Such a middle 6 digits may be displayed, for example, upon the entry of a correct PIC. Similarly, a magnetic emulator may not communicate information until a correct PIC has been entered by a user. Doing so may, for example, reduce fraud associated with card cloning. Additionally, a receipt may be provided that includes masked credit card numbers except for the last few digits of credit card numbers. Accordingly, displaying a static middle 6 digits of credit card numbers may allow for such a receipt to be provided while still reducing credit card fraud from hiding numbers that are not displayed on such a receipt. Any amount of numbers and/or characters may be displayed through a display. For example, nineteen digits may be displayed as part of a credit/debit numbers and these numbers may also be communicated through one or more magnetic emulation circuits. The entry of particular PICs may provide different results. For example, a first PIC may only display a string of alphanumeric characters. A second PIC may only activate a magnetic emulation circuit to transmit information including that string of alphanumeric characters (or a different string). A third PIC may activate a magnetic emulation circuit and a display. A display and/or magnetic emulation circuit may be turned OFF, for example, upon entry of an incorrect PIC and/or after a period of time has passed since the entry of the PIC and/or after the detection of a particular number of swipes by a read-head detector (e.g., one or two).


Persons skilled in the art will appreciate that a credit/debit card number (or any other information) may remain static until an event occurs and then may become dynamic (e.g., change based on swipes and/or time). For example, a particular PIC may change from a static to a dynamic topology and/or a topology may be changed from static to dynamic after a pre-determined period of time. Additionally a card and/or device may include a wireless receiver and a topology may be changed from a static to a dynamic topology upon, for example, receiving an appropriate signal from the wireless receiver. Accordingly, a validation process may change at a validation server depending upon whether a card is utilizing a static and/or dynamic topology at any given time. Additionally, a static credit/debit card number may be printed on the face of a card and information (e.g., a security code) may be displayed via a display and remain static over time (or with use) or be provided dynamically.


A card or other device (e.g., a mobile telephone) may accept a pre-determined number of consecutive incorrect PICs before locking the card for a period of time or until an appropriate secondary PIC is entered. Accordingly, a user may enter in an incorrect PIC a number of times and then, after a card becomes locked, call a support center for a secondary one-time use PIC. A card may cycle through unlocking PICs based, for example, on time or the number of previous unlock attempts.


A website may be provided where a user enters in his/her credit card number, pays a fee, and a new card is programmed and sent to the user. The new card may include a display to display a portion of the users credit/debit card number in a static form upon entry of an appropriate PIC. Such a card may also include one or more magnetic emulation circuits to transmit the information to a reader. Such a card may or may not, for example, include a portion of a magnetic stripe. For example, three tracks of magnetic stripe data may be communicated via three different emulation circuits, more than three different emulation circuits, one emulation circuits (e.g., tracks communicated serially to all read-heads), or one or more tracks may be represented by magnetic stripe(s) while one or more other tracks may be represented by a magnetic emulation circuit. A track of data may also be partially represented by a magnetic emulation circuit and partially represented by a magnetic stripe.



FIG. 15 shows card 1500 that may include, for example, one or more IC chips 1530 (e.g., EMV chips), RFID antennas 1520, processors 1540, displays 1550, dynamic magnetic communications devices 1510 (e.g., magnetic encoders and/or magnetic emulators), batteries 1560, and buttons 1551 and 1552. Additional circuitry 1598 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 1551 may, for example, be utilized by a user to select one encryption algorithm for a number displayed on display 1550 while button 1552 may be utilized by a user to select a different encryption algorithm. Persons skilled in the art will appreciate that the components of card 1500 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 1551, 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 1551 is pressed and displayed on display 1550. 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. 16 shows card 1600 that may include, for example, signature area 1640 that may include a material operable to receive marks from a pen (e.g., a signature). Card 1600 may also include, for example, displays 1620 and 1630. Display 1620 may, for example, display a payment number while display 1930 displays a security code (e.g., for online purchase authentication). Display 1620 as well as display 1630 may be utilized on the same side as, for example, dynamic magnetic communications device 1610.



FIG. 17 shows personal electronic device 1700 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 1700 may include, for example, user inputs 1740 and display 1710. Virtual card 1720 may be displayed on display 1720. Display 1720 may be a touch-sensitive display such that, for example, virtual button 1230 may be provided on virtual card 1720. 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 1700 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 transversals. 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 first and a second zone;a first and a second read-head detector each operable to detect a read-head of a magnetic stripe reader; anda magnetic emulator operable to couple with and wirelessly communicate with the read-head of the magnetic stripe reader comprising a first and a second portion;wherein the first portion and the first read-head detector are located in the first zone and the second portion and the second read-head detector are located in the second zone.
  • 2. The device of claim 1, further comprising a processor wherein said processor utilizes a signal from the first read-head detector to communicate data using the first portion.
  • 3. The device of claim 1, further comprising a processor wherein: the processor utilizes a signal from the first read-head detector to communicate data using the first portion, andthe processor utilizes a signal from the second read-head detector to communicate data using the second portion.
  • 4. The device of claim 1, further comprising a processor wherein: the magnetic emulator further comprises a third portion;the third portion is located in the first and second zone; andthe processor utilizes a signal from the first and second read-head detector to communicate data using the third portion.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims is a continuation of U.S. patent application Ser. No. 12/339,048, 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 (713)
Number Name Date Kind
3613101 Leonard et al. Oct 1971 A
4013894 Foote et al. Mar 1977 A
4077242 Sedley Mar 1978 A
4296315 Weimer et al. Oct 1981 A
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
4880963 Yamashita Nov 1989 A
4902146 Ishikawa Feb 1990 A
4937436 Eglise et al. Jun 1990 A
4977040 Yano et al. Dec 1990 A
5038251 Sugiyama et al. Aug 1991 A
5131089 Cole Jul 1992 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
5281799 McIntire et al. Jan 1994 A
5288942 Godfrey Feb 1994 A
5291068 Rammel Mar 1994 A
5347580 Molva et al. Sep 1994 A
5359183 Skodlar Oct 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
5671271 Henderson et al. Sep 1997 A
5679945 Renner et al. Oct 1997 A
5748737 Daggar May 1998 A
5763868 Kubota et al. Jun 1998 A
5834747 Cooper Nov 1998 A
5834756 Gutman et al. Nov 1998 A
5838549 Nagata et al. Nov 1998 A
5844230 Lalonde Dec 1998 A
5856661 Finkelstein et al. Jan 1999 A
5864623 Messina et al. Jan 1999 A
5866949 Scheuller Feb 1999 A
5883377 Chapin, Jr. Mar 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
5999624 Hopkins Dec 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, Jr. 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, Jr. Feb 2001 B1
6199052 Mitty et al. Mar 2001 B1
6202926 Ito et al. Mar 2001 B1
6206293 Gutman et al. Mar 2001 B1
6223984 Renner et al. May 2001 B1
6240184 Huynh et al. May 2001 B1
6241149 Baitz et al. Jun 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
6398115 Krause Jun 2002 B2
6402029 Gangi Jun 2002 B1
6410923 Crewe Jun 2002 B1
6411715 Liskov et al. Jun 2002 B1
6425061 Kaise et al. Jul 2002 B1
6425960 Yoshizawa Jul 2002 B1
6446052 Juels Sep 2002 B1
6460141 Olden Oct 2002 B1
6549912 Chen Apr 2003 B1
6552869 Takahashi et al. Apr 2003 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
6769607 Pitroda et al. Aug 2004 B1
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
6920611 Spaeth Jul 2005 B1
6929550 Hisada Aug 2005 B2
6934664 Webb et al. Aug 2005 B1
6970070 Juels et al. Nov 2005 B2
6975205 French et al. Dec 2005 B1
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
7039221 Tumey et al. May 2006 B1
7039223 Wong May 2006 B2
7044394 Brown May 2006 B2
7051929 Li May 2006 B2
7073721 Kano et al. Jul 2006 B2
7083094 Cooper Aug 2006 B2
7093757 Boucher et al. Aug 2006 B2
7097108 Zellner et al. Aug 2006 B2
7100049 Gasparini et al. Aug 2006 B2
7100821 Rasti Sep 2006 B2
7111172 Duane et al. Sep 2006 B1
7114652 Moullette et al. Oct 2006 B2
7136514 Wong Nov 2006 B1
7140550 Ramachandran Nov 2006 B2
7163153 Blossom Jan 2007 B2
7195154 Routhenstein Mar 2007 B2
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 Apr 2008 B2
7370805 Smith et al. May 2008 B2
7375631 Moskowitz 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
7461788 Iwamura Dec 2008 B2
7472093 Juels Dec 2008 B2
7472829 Brown Jan 2009 B2
7494055 Fernandes et al. Feb 2009 B2
7500603 McCaskey et al. Mar 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 Nystrom et al. Jul 2009 B2
7562222 Gasparini et al. Jul 2009 B2
7580898 Brown et al. Aug 2009 B2
7581678 Narendra et al. Sep 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
7599192 Pennaz et al. Oct 2009 B2
7602904 Juels et al. Oct 2009 B2
7621458 Zellner et al. Nov 2009 B2
7631804 Brown Dec 2009 B2
7639537 Sepe et al. Dec 2009 B2
7641124 Brown et al. Jan 2010 B2
7660902 Graham et al. Feb 2010 B2
7681232 Nordentoft et al. Mar 2010 B2
7715593 Adams et al. May 2010 B1
7784687 Mullen et al. Aug 2010 B2
7793851 Mullen Sep 2010 B2
7828207 Cooper Nov 2010 B2
7828220 Mullen Nov 2010 B2
7851517 Holmes Dec 2010 B2
7900845 Stagg Mar 2011 B2
7931195 Mullen Apr 2011 B2
7946501 Borracci May 2011 B2
7954705 Mullen Jun 2011 B2
7954708 Blossom Jun 2011 B2
7954724 Poidomani et al. Jun 2011 B2
7954725 Blythe Jun 2011 B2
7996318 Marcon Aug 2011 B2
8011577 Mullen et al. Sep 2011 B2
8020775 Mullen et al. Sep 2011 B2
8074877 Mullen et al. Dec 2011 B2
8103881 Doughty et al. Jan 2012 B2
8181874 Wan May 2012 B1
8245923 Merrill, Jr et al. Aug 2012 B1
8286876 Mullen et al. Oct 2012 B2
8302872 Mullen Nov 2012 B2
8313037 Humphrey Nov 2012 B1
8317103 Foo et al. Nov 2012 B1
8382000 Mullen et al. Feb 2013 B2
8413892 Mullen et al. Apr 2013 B2
8424773 Mullen et al. Apr 2013 B2
8459548 Mullen et al. Jun 2013 B2
8485437 Mullen et al. Jul 2013 B2
8485446 Mullen et al. Jul 2013 B1
8517276 Mullen et al. Aug 2013 B2
8608083 Mullen et al. Dec 2013 B2
8651386 Hepner et al. Feb 2014 B2
8668143 Mullen et al. Mar 2014 B2
8733638 Mullen et al. May 2014 B2
8763916 Foo Jul 2014 B1
8875999 Mullen et al. Nov 2014 B2
8881989 Mullen et al. Nov 2014 B2
8931703 Mullen et al. Jan 2015 B1
8973824 Mullen et al. Mar 2015 B2
9004368 Mullen et al. Apr 2015 B2
9010630 Mullen et al. Apr 2015 B2
9331585 Lin et al. May 2016 B1
9361569 Mullen et al. Jun 2016 B2
9384438 Mullen et al. Jul 2016 B2
9547816 Mullen et al. Jan 2017 B2
9639796 Mullen et al. May 2017 B2
9684861 Mullen et al. Jun 2017 B2
9697454 Mullen et al. Jul 2017 B2
9704088 Mullen et al. Jul 2017 B2
9704089 Mullen et al. Jul 2017 B2
9727813 Mullen et al. Aug 2017 B2
9734345 Spodak et al. Aug 2017 B2
9805297 Mullen et al. Oct 2017 B2
10032100 Mullen et al. Jul 2018 B2
10095974 Mullen et al. Oct 2018 B1
10169692 Mullen et al. Jan 2019 B2
10198687 Mullen et al. Feb 2019 B2
10223631 Mullen et al. Mar 2019 B2
10255545 Mullen et al. Apr 2019 B2
10325199 Mullen et al. Jun 2019 B2
10430704 Mullen et al. Oct 2019 B2
10467521 Mullen et al. Nov 2019 B2
10496918 Mullen et al. Dec 2019 B2
10579920 Mullen et al. Mar 2020 B2
10997489 Mullen et al. May 2021 B2
11062195 Mullen Jul 2021 B2
20010009485 Furuya Jul 2001 A1
20010034702 Mockett et al. Oct 2001 A1
20010047335 Arndt et al. Nov 2001 A1
20010050247 Myer, Sr. Dec 2001 A1
20020003169 Cooper Jan 2002 A1
20020017559 Mos et al. Feb 2002 A1
20020032657 Singh Mar 2002 A1
20020043566 Goodman Apr 2002 A1
20020059114 Cockrill et al. May 2002 A1
20020062249 Iannacci May 2002 A1
20020070976 Tanner et al. Jun 2002 A1
20020073025 Tanner et al. Jun 2002 A1
20020073042 Maritzen et al. Jun 2002 A1
20020082989 Fife et al. Jun 2002 A1
20020092914 Pentz et al. Jul 2002 A1
20020096570 Wong et al. Jul 2002 A1
20020108066 Masui Aug 2002 A1
20020120583 Keresman, III et al. Aug 2002 A1
20020123967 Wang Sep 2002 A1
20020134837 Kishon Sep 2002 A1
20020153424 Li Oct 2002 A1
20020170959 Madani Nov 2002 A1
20020185543 Pentz et al. Dec 2002 A1
20020188505 Burrus, IV Dec 2002 A1
20030030935 Yamamoto Feb 2003 A1
20030034388 Routhenstein et al. Feb 2003 A1
20030042316 Teraura Mar 2003 A1
20030043488 Fernandez et al. Mar 2003 A1
20030052168 Wong Mar 2003 A1
20030057278 Wong Mar 2003 A1
20030069846 Marcon Apr 2003 A1
20030071120 Orii 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
20030145205 Sarcanin Jul 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
20040052034 Senba et al. Mar 2004 A1
20040055770 Babb Mar 2004 A1
20040064302 Cunin Apr 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 et al. Jul 2004 A1
20040143451 McIntyre et al. Jul 2004 A1
20040150091 Stobbs Aug 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
20040189700 Mandavilli et al. Sep 2004 A1
20040205273 Mowery et al. Oct 2004 A1
20040212017 Mizuno et al. Oct 2004 A1
20040212831 Imai et al. Oct 2004 A1
20040251303 Cooper Dec 2004 A1
20050001711 Doughty et al. Jan 2005 A1
20050006482 Kano et al. Jan 2005 A1
20050039027 Shapiro Feb 2005 A1
20050043997 Sahota et al. Feb 2005 A1
20050068868 Hasegawa Mar 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
20050144076 Cimino Jun 2005 A1
20050154643 Doan et al. Jul 2005 A1
20050178827 Shatford Aug 2005 A1
20050178835 Akiho et al. Aug 2005 A1
20050194452 Nordentoft et al. Sep 2005 A1
20050194453 Conner et al. Sep 2005 A1
20050205665 Lasch et al. Sep 2005 A1
20050218229 Morley et al. Oct 2005 A1
20050219728 Durbin et al. Oct 2005 A1
20050228959 D'Albore et al. Oct 2005 A1
20050230788 Kato et al. Oct 2005 A1
20050247787 Von Mueller Nov 2005 A1
20050274803 Lee Dec 2005 A1
20060000900 Fernandes et al. Jan 2006 A1
20060017570 Moskowitz et al. Jan 2006 A1
20060017571 Arnold et al. Jan 2006 A1
20060032906 Sines Feb 2006 A1
20060037073 Juels et al. Feb 2006 A1
20060041759 Kaliski et al. Feb 2006 A1
20060043180 Ison Mar 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
20060131396 Blossom Jun 2006 A1
20060161435 Atef et al. Jul 2006 A1
20060161789 Doughty et al. Jul 2006 A1
20060163353 Moulette et al. Jul 2006 A1
20060169768 Gangi Aug 2006 A1
20060174104 Crichton et al. Aug 2006 A1
20060175398 Hilton et al. Aug 2006 A1
20060186209 Narendra et al. Aug 2006 A1
20060187055 Colby Aug 2006 A1
20060196931 Holtmanns et al. Sep 2006 A1
20060198291 Teguri Sep 2006 A1
20060213973 Chan et al. Sep 2006 A1
20060214866 Araki et al. Sep 2006 A1
20060217792 Hussein et al. Sep 2006 A1
20060227523 Pennaz et al. Oct 2006 A1
20060241236 Kuznetsov et al. Oct 2006 A1
20060249574 Brown et al. Nov 2006 A1
20060249575 Turner et al. Nov 2006 A1
20060256961 Brainard et al. Nov 2006 A1
20060261174 Zellner et al. Nov 2006 A1
20060262585 Lenssen Nov 2006 A1
20060262655 Persson Nov 2006 A1
20060278696 Watson Dec 2006 A1
20060278698 Lovett Dec 2006 A1
20060283940 Kuo Dec 2006 A1
20060283958 Osterweil Dec 2006 A1
20060287964 Brown Dec 2006 A1
20060289632 Walker Dec 2006 A1
20070005685 Chau et al. Jan 2007 A1
20070017975 Lewis et al. Jan 2007 A1
20070023532 Narendra et al. Feb 2007 A1
20070029110 Matsumoto et al. Feb 2007 A1
20070034700 Poidomani Feb 2007 A1
20070040030 Kranzley et al. Feb 2007 A1
20070052517 Bishop et al. Mar 2007 A1
20070063025 Blossom Mar 2007 A1
20070063776 Okuda Mar 2007 A1
20070063804 Watanabe Mar 2007 A1
20070100754 Brown May 2007 A1
20070114274 Gibbs et al. May 2007 A1
20070124321 Szydlo May 2007 A1
20070131759 Cox et al. Jun 2007 A1
20070136211 Brown et al. Jun 2007 A1
20070138299 Mitra Jun 2007 A1
20070152052 Sines Jul 2007 A1
20070152070 D'Albore Jul 2007 A1
20070152072 Frallicciardi et al. Jul 2007 A1
20070152829 Lindsay 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
20070208671 Brown et al. Sep 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
20070290049 Ratcliffe 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
20080010190 Rackley III et al. Jan 2008 A1
20080010675 Massascusa et al. Jan 2008 A1
20080016351 Fontana et al. Jan 2008 A1
20080017721 Zehnacker 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
20080029607 Mullen Feb 2008 A1
20080035738 Mullen Feb 2008 A1
20080040271 Hammad et al. Feb 2008 A1
20080040276 Hammad et al. Feb 2008 A1
20080054068 Mullen Mar 2008 A1
20080054079 Mullen Mar 2008 A1
20080054081 Mullen Mar 2008 A1
20080058016 Di Maggio et al. Mar 2008 A1
20080059374 Gangi Mar 2008 A1
20080059379 Ramaci et al. Mar 2008 A1
20080065555 Mullen Mar 2008 A1
20080093467 Narendra et al. Apr 2008 A1
20080096326 Reed Apr 2008 A1
20080099556 Park May 2008 A1
20080105751 Landau May 2008 A1
20080110983 Ashfield May 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
20080148394 Poidomani et al. Jun 2008 A1
20080150123 Li et al. Jun 2008 A1
20080197201 Manessis et al. Aug 2008 A1
20080197533 Tsao et al. Aug 2008 A1
20080201264 Brown et al. Aug 2008 A1
20080209550 Di Iorio Aug 2008 A1
20080210754 Lovett Sep 2008 A1
20080217396 Boalt Sep 2008 A1
20080223937 Preta et al. Sep 2008 A1
20080227437 Lewis Sep 2008 A1
20080238610 Rosenberg Oct 2008 A1
20080245851 Kowalski 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
20080302869 Mullen Dec 2008 A1
20080302876 Mullen Dec 2008 A1
20080302877 Musella et al. Dec 2008 A1
20080308629 Roskind Dec 2008 A1
20090006262 Brown et al. Jan 2009 A1
20090011821 Griswold et al. Jan 2009 A1
20090013122 Sepe et al. Jan 2009 A1
20090023474 Luo et al. Jan 2009 A1
20090023476 Saarisalo et al. Jan 2009 A1
20090026277 Phillips 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
20090143104 Loh Jun 2009 A1
20090150295 Hatch et al. Jun 2009 A1
20090152365 Li et al. Jun 2009 A1
20090153297 Gardner Jun 2009 A1
20090159663 Mullen et al. Jun 2009 A1
20090159667 Mullen et al. Jun 2009 A1
20090159668 Mullen et al. Jun 2009 A1
20090159669 Mullen et al. Jun 2009 A1
20090159670 Mullen et al. Jun 2009 A1
20090159671 Mullen et al. Jun 2009 A1
20090159672 Mullen et al. Jun 2009 A1
20090159673 Mullen et al. Jun 2009 A1
20090159680 Mullen et al. Jun 2009 A1
20090159681 Mullen et al. Jun 2009 A1
20090159682 Mullen et al. Jun 2009 A1
20090159688 Mullen et al. Jun 2009 A1
20090159689 Mullen et al. Jun 2009 A1
20090159690 Mullen et al. Jun 2009 A1
20090159696 Mullen Jun 2009 A1
20090159697 Mullen et al. Jun 2009 A1
20090159698 Mullen et al. Jun 2009 A1
20090159699 Mullen et al. Jun 2009 A1
20090159700 Mullen et al. Jun 2009 A1
20090159701 Mullen et al. Jun 2009 A1
20090159702 Mullen Jun 2009 A1
20090159703 Mullen et al. Jun 2009 A1
20090159704 Mullen et al. Jun 2009 A1
20090159705 Mullen et al. Jun 2009 A1
20090159706 Mullen et al. Jun 2009 A1
20090159707 Mullen et al. Jun 2009 A1
20090159708 Mullen et al. Jun 2009 A1
20090159709 Mullen Jun 2009 A1
20090159710 Mullen et al. Jun 2009 A1
20090159711 Mullen et al. Jun 2009 A1
20090159712 Mullen et al. Jun 2009 A1
20090159713 Mullen et al. Jun 2009 A1
20090160617 Mullen et al. Jun 2009 A1
20090164380 Brown Jun 2009 A1
20090164381 Brown Jun 2009 A1
20090166435 Blythe Jul 2009 A1
20090170432 Lortz Jul 2009 A1
20090173785 Cooper Jul 2009 A1
20090187507 Brown 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
20090261167 Iwayama Oct 2009 A1
20090288012 Hertel Nov 2009 A1
20090290704 Cimino Nov 2009 A1
20130311363 Ramaci et al. Nov 2009 A1
20090296605 Lewis Dec 2009 A1
20090303885 Longo Dec 2009 A1
20090308921 Mullen Dec 2009 A1
20100019033 Jolivet Jan 2010 A1
20100023449 Skowronek Jan 2010 A1
20100045627 Kennedy Feb 2010 A1
20100057580 Raghunathan Mar 2010 A1
20100066701 Rat Mar 2010 A1
20100078472 Lin et al. Apr 2010 A1
20100084476 Zellner et al. Apr 2010 A1
20100108771 Wong May 2010 A1
20100117794 Adams et al. May 2010 A1
20100127083 Brown 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
20100265037 Domsten et al. Oct 2010 A1
20100265617 Isuyama Oct 2010 A1
20100270373 Poidomani Oct 2010 A1
20100275259 Adams et al. Oct 2010 A1
20100287039 Telles Nov 2010 A1
20100304670 Shuo Dec 2010 A1
20100304796 Stohr et al. Dec 2010 A1
20110006122 Chenot Jan 2011 A1
20110028184 Cooper Feb 2011 A1
20110050164 Partovi et al. Mar 2011 A1
20110062239 Lau et al. Mar 2011 A1
20110066550 Shank Mar 2011 A1
20110084149 Faith et al. Apr 2011 A1
20110108626 Hepner et al. May 2011 A1
20110112717 Resner May 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
20110220726 Narendra et al. Sep 2011 A1
20110240748 Doughty et al. Oct 2011 A1
20110272465 Mullen et al. Nov 2011 A1
20110272466 Mullen et al. Nov 2011 A1
20110272467 Mullen et al. Nov 2011 A1
20110272471 Mullen Nov 2011 A1
20110272472 Mullen Nov 2011 A1
20110272473 Mullen et al. Nov 2011 A1
20110272474 Mullen et al. Nov 2011 A1
20110272475 Mullen et al. Nov 2011 A1
20110272476 Mullen et al. Nov 2011 A1
20110272477 Mullen et al. Nov 2011 A1
20110272478 Mullen Nov 2011 A1
20110272479 Mullen Nov 2011 A1
20110272480 Mullen et al. Nov 2011 A1
20110272481 Mullen et al. Nov 2011 A1
20110272482 Mullen et al. Nov 2011 A1
20110272483 Mullen et al. Nov 2011 A1
20110272484 Mullen et al. Nov 2011 A1
20110276380 Mullen et al. Nov 2011 A1
20110276381 Mullen et al. Nov 2011 A1
20110276416 Mullen et al. Nov 2011 A1
20110276424 Mullen Nov 2011 A1
20110276425 Mullen Nov 2011 A1
20110276436 Mullen et al. Nov 2011 A1
20110276437 Mullen et al. Nov 2011 A1
20110278364 Mullen et al. Nov 2011 A1
20110282753 Mullen et al. Nov 2011 A1
20110284640 Mullen et al. Nov 2011 A1
20120071205 Narendra et al. Mar 2012 A1
20120074232 Spodak et al. Mar 2012 A1
20120101882 Todd Apr 2012 A1
20120123937 Spodak May 2012 A1
20120191612 Spodak et al. Jul 2012 A1
20120196530 Moosavi et al. Aug 2012 A1
20120205451 Poidomani et al. Aug 2012 A1
20120234927 Poidomani Sep 2012 A1
20120235797 Poidomani et al. Sep 2012 A1
20120241524 Blot et al. Sep 2012 A1
20120270528 Goodman Oct 2012 A1
20120280035 Liu et al. Nov 2012 A1
20120280048 Kim Nov 2012 A1
20120286037 Mullen et al. Nov 2012 A1
20120286936 Mullen et al. Nov 2012 A1
20120310826 Chatterjee Dec 2012 A1
20120318871 Mullen et al. Dec 2012 A1
20130020396 Mullen et al. Jan 2013 A1
20130024372 Spodak et al. Jan 2013 A1
20130083787 Restiau et al. Apr 2013 A1
20130140360 Graylin Jun 2013 A1
20130146661 Melbrod et al. Jun 2013 A1
20130200999 Spodak et al. Aug 2013 A1
20130214044 Sperduti et al. Aug 2013 A1
20130248591 Look et al. Sep 2013 A1
20130282573 Mullen et al. Oct 2013 A1
20130282575 Mullen et al. Oct 2013 A1
20130320080 Olson et al. Dec 2013 A1
20130320081 Olson et al. Dec 2013 A1
20130344804 Chen et al. Dec 2013 A1
20130346167 Telles Dec 2013 A1
20140138447 Goldman et al. May 2014 A1
20140138449 Goldman et al. May 2014 A1
20140144984 Olson et al. May 2014 A1
20140152417 Ebeid et al. Jun 2014 A1
20140183258 DiMuro Jul 2014 A1
20140263385 Martin Sep 2014 A1
20140293980 Shibata Oct 2014 A1
20140339315 Ko Nov 2014 A1
20150069126 Leon Mar 2015 A1
20150073983 Bartenstein et al. Mar 2015 A1
20150134513 Olson et al. May 2015 A1
20150186766 Mullen et al. Jul 2015 A1
20150304291 Cook Oct 2015 A1
20150324792 Guise et al. Nov 2015 A1
20160180209 Mullen et al. Jun 2016 A1
20160239735 Mullen et al. Aug 2016 A1
20160283837 Mullen et al. Sep 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
20170286817 Mullen et al. Oct 2017 A1
20170300796 Mullen et al. Oct 2017 A1
20180114036 Spodak et al. Apr 2018 A1
20180129923 Olson et al. May 2018 A1
20190065928 Mullen et al. Feb 2019 A1
20190197387 Mullen et al. Jun 2019 A1
20190340484 Mullen et al. Nov 2019 A1
Foreign Referenced Citations (35)
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 1995 JP
01194392 Jul 2001 JP
01194392 Jul 2001 JP
2004165400 Dec 2001 JP
2005010964 Jan 2005 JP
2005056540 Mar 2005 JP
2005190363 Jul 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 (98)
Entry
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.
English translation of JP 05210770 A.
Patent Examination Report No. 1, Australian Patent Application No. 2008340226, dated Oct. 11, 2012.
Article 94(3) EPC communication in European Patent Application No. 08865573.3-2221, dated Feb. 5, 2013.
Magnetic stripe card, Mindmatrix (this document is presented by the European Patent Office without a link).
Summons to Oral Proceedings in European Patent Application No. 08865573.3-2221, dated Sep. 18, 2013.
Digital Transactions Trends in the Electronic Exchange of Value. Samsung Pay's Mag-Stripe Emulation Advantage might be Short Lived.
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. 2013-7029089.
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.
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 om 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.
Related Publications (1)
Number Date Country
20170286817 A1 Oct 2017 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 (1)
Number Date Country
Parent 12339048 Dec 2008 US
Child 15583356 US