Patent Grant
9224142
All of the above-identified applications are fully incorporated by reference.
1. Field of the Invention
The present invention relates generally to card readers configured to be coupled to mobile devices to conduct financial transactions, and more particularly to card readers with power supplies and wake-up circuits configured to be coupled to mobile devices.
2. Description of the Related Art
Plastic cards having a magnetic stripe embedded on one side of the card are prevalent in everyday commerce. These cards are used in various transactions such as to pay for purchases by using a credit card, a debit card, or a gasoline charge card. A charge card or a debit card may also be used to transact business with a bank through use of an automated teller machine (ATM). The magnetic stripe card is capable of storing data by modifying the magnetism of magnetic particles embedded in the stripe. The data stored on the magnetic stripe may be sensed or read by swiping the stripe past a read head. The analog waveform obtained by sensing the magnetic stripe must undergo a process known as decoding to obtain the digital information stored in the magnetic stripe of the card.
Currently, there are hundreds of magnetic stripe readers/swipers on the market, all of them are at least as long as the credit card itself. These existing readers/swipers can be classified as either platform card readers or plunge card readers. Platform card readers are traditional card swipers with single rails, which allow a card to be held against the base of the reader by the user and moved across the read head of the reader. Plunge swipers guide a card by two sets of rails and a backstop. Once the user has inserted the card against the backstop, the card is read as it is removed from the plunge swipers. Plunge swipers are common on ATMs and other self-pay devices because they are less prone to hacking.
Magnetic stripe cards having standard specifications can typically be read by point-of-sale devices at a merchant's location. When the card is swiped through an electronic card reader, such as a platform card reader, at the checkout counter at a merchant's store, the reader will usually use its built-in modem to dial the number of a company that handles credit authentication requests. Once the account is verified and an approval signal will be sent back to the merchant to complete a transaction.
Although magnetic stripe cards are universally used by merchants, there is no way for an individual to take advantage of the card to receive a payment from another individual (who is not a merchant) by swiping the card through a simple reader attached to his/her mobile device. For a non-limiting example, one person may owe another person money for a debt, and the conventional way to pay the debt is to provide cash or a check. It would be convenient to be able to use a credit card or a debit card to pay off the debt. In addition, it is advantageous for an individual to make payment to another individual or merchant by swiping his magnetic stripe card through a reader connected to a mobile device.
There is a need for improved card readers that are configured to be coupled to mobile devices for conducting financial transactions. There is a further need for cost effective card readers configured to be coupled to mobile devices for the conduct of financial transactions. Yet there is a further need for card readers with power supplies and wake-up circuits configured to be coupled to mobile devices for conducting financial transactions.
An object of the present invention is to provide card readers for financial transactions using mobile devices.
Another object of the present invention is to provide card readers for conducting financial transactions using portable electronic devices, such devices including software, firmware, hardware, or a combination thereof that is capable of at least receiving a signal.
A further object of the present invention is to provide secure card readers for financial transactions using mobile devices.
A further object of the present invention is to provide card readers with increased efficiency for financial transactions using mobile devices.
Yet another object of the present is to provide card readers that have cost efficient architectures for payments using mobile devices.
Another object of the present is to provide low power consumption card readers for conducting financial transactions using mobile devices.
These and other objects of the present invention are achieved in a card reader with a read head positioned in a housing. The read head is configured to be coupled to a mobile device and has a slot for swiping a magnetic stripe of a card. The read head reads data on the magnetic stripe and produces a raw magnetic signal indicative of data stored on the magnetic stripe. A power supply is coupled to wake-up electronics and a microcontroller. An output jack is adapted to be inserted in a port of the mobile device and deliver an output jack signal to the mobile device.
a)-(b) depict examples of actual card reader with miniaturized design.
a)-(b) depict examples of alignment between read head of the card reader and magnetic stripe of card being swiped.
a)-(c) depict examples of internal structures of a miniaturized card reader.
a)-(b) depict examples of waveforms of data read from one track of the magnetic stripe by read head when the card is swiped through the slot of the card reader in the forward and reverse directions, respectively.
a)-(f) depict screenshots of an example of a financial transaction between a purchaser and a merchant through a miniaturized card reader connected to a mobile device.
The approach is illustrated by way of example and not by way of limitation in the figures of the accompanying drawings in which like references indicate similar elements. It should be noted that references to “an” or “one” or “some” embodiment(s) in this disclosure are not necessarily to the same embodiment, and such references mean at least one.
In the example of
As used herein, the term engine refers to software, firmware, hardware, or other component that is used to effectuate a purpose. The engine will typically include software instructions that are stored in non-volatile memory (also referred to as secondary memory). When the software instructions are executed, at least a subset of the software instructions is loaded into memory (also referred to as primary memory) by a processor. The processor then executes the software instructions in memory. The processor may be a shared processor, a dedicated processor, or a combination of shared or dedicated processors. A typical program will include calls to hardware components (such as I/O devices), which typically requires the execution of drivers. The drivers may or may not be considered part of the engine, but the distinction is not critical.
As used herein, the term database is used broadly to include any known or convenient means for storing data, whether centralized or distributed, relational or otherwise.
In the example of
In one embodiment of the present invention a system is provided with transaction engine 130 running on mobile device 100. In response to a financial transaction between a buyer and a seller, the mobile device 100 accepts information selected including but not limited to information from financial transaction or information pertaining to financial transaction card used by the buyer in the transaction. Additionally, a financial transaction device can be utilized. Non-limiting examples of financial transaction devices include but are not limited to a, wristband, RFID chip, cell phone, biometric marker and the like. At least a portion of this information is communicated with a third party financial institution or payment network to authorize the transaction. The buyer receives confirmation of the payment. Payment confirmation can be in real time by a payment service.
Payment confirmation can be made with a communication channel of the buyer's choice. As non-limiting examples, confirmation of payment can be an electronic notification in the form selected from at least one of, email, SMS message, tweet (message delivered via Twitter), instant message, communication within a social network and the like.
In response to the transaction, a confirmation is made that the buyer is authorized to use the financial transaction card in order to prevent fraud. There can also be a confirmation that there are sufficient funds for the purchase made by the buyer.
In one embodiment, it is determined that that the buyer, authorized to use the financial transaction card, is present with the seller at the time of the financial transaction.
Miniaturized Card Reader
In the example of
The size of card reader 10 is miniaturized to be portable for connection with mobile device 100. For a non-limiting example, the size of card reader 10 can be miniaturized to an overall length of less than 1.5″. In addition, the miniaturized card reader 10 is also designed to reliably read the card with minimum error via a single swipe by counteracting vendor specific filtering done by mobile device 100. Note that this broad overview is meant to be non-limiting as components to this process are represented in different embodiments. For instance the decoding engine 110 can be embedded in the card reader 10 as shown in
In the example of
a) depicts an example of an actual card reader with miniaturized design and
The card reader 10 includes the slot 14 and is miniaturized relative to the size of the mobile device 100. In some embodiments, the housing 12 is not included.
In one embodiment, the slot 14 is configured to maintain contact between the read head 16, and the magnetic stripe of the financial transaction card during a swipe. The signal is decoded in the mobile device 100. The decoding includes determining pulses in the signal and converting at least some of the pulses to characters. In one embodiment, the slot 14 has a width of no greater than 1 mm. The width of the slot 14 is sufficient to enable a successful swiping of the financial transaction card, while producing the signal. It is sized to enable the successful swipe without creating sufficient torque between the signal plug 18 or output jack and the read head 16 or at the mobile device 100 to cause damage due to excessive torque. If the slot 14 is too wide, then it is more difficult to achieve a successful swipe that produce the signal. If there is a miss, or insufficient data is generated, then the resulting signal is not competent. If the slot 14 is too narrow, then the financial transaction card can not be swiped. The size of the slot 14 is selected to reduce torque as discussed above. Additionally, in one embodiment, the output jack 18 is at least partially if not fully rotatable relative to the port it is coupled to in the mobile device 100. The decoding includes error checking. In one embodiment, the decoding includes detecting that data in the signal is from the financial transaction card, seeing the beginning and ending sentinels and reconstructing data in the signal from a pattern of pulses.
In one embodiment of the present invention, the mobile device 100 has an audio input port, a line input port a USB port and others. In one embodiment, a sampling rate of the signal at the audio input port or a line input port of the mobile device is at least 15 kHZ. In various other embodiments, the sample rate of the signal at the audio input port or line import port can be, least 20 kHz; at least 25 kHz, at least 30 kHz, at least 35 kHz or at least 40 kHz.
In one embodiment, the slot 14 is oriented and sized to reduce torque applied on the read head 10 when the financial transaction card is swiped through the slot 14 in order to maintain accuracy and reliability of the data read by the read head 10.
In the example of
In the example of
To correctly read the data on the magnetic stripe of the card, the read head 16 must maintain contact with the stripe as the card moves past slot 14. If the card rocks during the swipe, the alignment of the head 12 with the stripe may be compromised. As the length of the slot 14, i.e., the card path through which the card swiped though slot 14, is shortened, rocking and head alignment may become significant issues. As shown in
In some embodiments, the base 15 of slot 14 can be changed from flat to a curved base with a radius in order to increase contact between the read head 16 and the magnetic stripe to address the rocking problem. As shown in
In some embodiments, signal plug 18 may be retractable within the housing 12. In some embodiments, signal plug 18 is configured to extend beyond housing 12 of the reader in order to accommodate connection with mobile devices 100 having cases or having a recessed plug-in socket, wherein the socket can be but is not limited to a microphone input socket or a line in audio input of the mobile device.
In some embodiments, housing 12 of card reader 10 is made of non-conductive material such as plastic so that the reader will not interfere with the function of mobile device 100 it is connected with. Such choice of material is important since the outer case of certain mobile devices, such as iPhone 4, is conductive and serves as an antenna for the device, which function could potentially be interfered with if the metal case of the device gets in touch with the housing of a card reader made of conductive material.
a) depicts an example of an internal structural diagram of a miniaturized card reader. Although the diagrams depict components as functionally separate, such depiction is merely for illustrative purposes. It will be apparent that the components portrayed in this figure can be arbitrarily combined or divided into separate software, firmware and/or hardware components.
In the example of
In the example of
In some embodiments, read head 16 in card reader is capable of reading only one track of data (either track 1 or 2, but not both) from the magnetic stripe in order to reduce the size and structural complexity of compact read head 16 as only one pin needs to be included in the read head.
In some embodiments, the size or thickness of the housing 12 of card reader 10 is configured to be narrow enough to accommodate only a single read head 16. Such design is intended to be tampering-proof so that even if the housing 12 is tampered with, no additional circuitry can be added to the card reader 10 and such tampering will render the card reader non-functional.
In the example of
In the example of
Passive ID Circuit
In some embodiments, housing 12 of card reader 10 may further encapsulate a passive ID circuitry 22 powered by the mobile device 100 through signal plug 18, wherein passive ID circuitry 22 delivers an unique ID of the card reader to mobile device 100 only once upon the card reader being connected to (and powered up by) the mobile device. Although both are integrated in the same housing 12, passive ID circuitry 22 functions independently and separately from read head 18 without interfering with the read head's card swiping functions described above.
In the example of
In the example of
In standard operation the pathway subsystem 30 is configured to direct the mobile device's 100 bias voltage to the power subsystem 28. After the power subsystem converts the bias voltage to a system voltage, the control unit 32 is able to operate. Control unit 32 configures the pathway subsystem 30 to allow the communication subsystem 26 access to the mobile device 100. The communication subsystem 26 relays the unique ID from the unique ID storage 24. The control unit 32 then configures the pathway subsystem 30 to allow the card reader circuit 16 access to the mobile device 100.
In the example of
In the example of
In some embodiments, passive ID circuitry 22 may further include additional encryption and/or decryption systems as shown in
Signal Decoding
Once card reader 10 provides the set waveform to the attached mobile device 100, the incoming signals (waveform) may be amplified, sampled, and converted to a stream of digital values or samples by decoding engine 110 running via a microprocessor inside the mobile device. Here, decoding engine 110 may comprise a pipeline of software decoding processes (decoders) to decode and process the incoming signals as described below, where each software process in this pipeline can be swapped out and replaced to accommodate various densities of track data read in order to reduce card swipe error rate. The incoming signals may be of low quality due to one or more of: low quality of data read from a single and/or low density track of a magnetic stripe of the card, sampling speed limitations of the microphone input socket of the mobile device, and noise introduced into the mobile device 100 from card reader 10.
In the example of
Take one system buffer of audio signal and compute the DC offset of this buffer.
Save the computed DC offset.
Compute the average of the last three DC offsets.
Compute the variance of the current DC offset from the average computed in step 3.
The following values presented were found to be optimum for performance in the decoding system. In the spirit of full disclosure they have been provided here to allow someone trained in the arts to be able to replicate this process. It is fully realized that many other values can be used here and depending on hardware implementation. The values here are meant to be non-limiting. If the variance computed in step 4 is less than the variance threshold, 0.06% of full scale or less than the offset percentage, 10% of the offset average computed in step 3, and the DC offset computed in step 1 is less than the noise ceiling, 3% of full scale, of the mobile device 100. After initialization is complete, decoding engine 110 can proceed to process the incoming signals to detect the swipe of the card. Otherwise, Steps 1-4 need to be repeated.
The flowchart 1400 continues to block 1404 where decoding engine 110 detects the card swipe once the incoming signals are in a steady state. This signal detection phase processes the incoming signals in steady state in order to detect the presence of a swipe of a card through the card reader. The signal detection phase is a light-weight procedure that operates at near real time. It parses the incoming signals quickly and stitches multiple system buffers of signals together to form a signal of interest. In some embodiments, the signal detection process goes through at least the following steps:
Apply a software upscale of system buffers of the incoming signals.
Begin taking buffers of incoming signals and look for points that exceed a minimum signal amplitude threshold, which is a hardware-based parameterization found empirically.
Set a flag that triggers the detection of a swipe once a single point that exceeds the threshold is detected.
Once the flag triggered, the incoming signal is appended to a larger buffer until the signal drops below a minimum signal amplitude threshold for a certain period of time, e.g., 10 ms.
Trim the last 10 ms of data to reduce the amount of signal data to be processed later.
Check to see if at least a certain number of samples have been collected in the buffer to make sure that there are enough information for later decoding. This number is parameterized based on the hardware of the mobile device used.
Alternatively, a hardware independent swipe detection process can be utilized to capture the signal of interest via Fast Fourier Transform (FFT), while trimming the front and back of the signal. Such process would include at least the following steps:
Retrieve system buffers of incoming signals and keep a certain number of buffers of history of the signals.
Compute the frequency distribution of the signal history kept via FFT.
Locate two maxima in the histogram and check if one maximum is located at 2× the frequency of the other maximum. If this condition is satisfied, continue to add on buffers of history that exhibit such behavior.
Once such behavior has stopped, begin removing signals from the beginning and ending of the signals in the buffers until SNR is maximized, wherein SNR is defined to be the two maxima's amplitudes that are greatest from the next maximum.
The flowchart 1400 continues to block 1406 once a card swipe is detected to be present where decoding engine 110 identifies peaks in the incoming signals. Peak detection is the most complex portion of decoding of incoming signals from credit card swipes, and credit card swipe decodes have traditionally not been done on heavily filtered signals like the signal that enters through the TRS plug, since most mobile device manufacturers assume the incoming signal is audio based. This results in a wide variety of signal filtering that peak detection must account for. Different peak detection approaches discussed below can be utilized by the microprocessor to perform peak detection in the incoming signals in different ways, all applying a basic, moving average low-pass filter to smooth out some of the high frequency noise in order to overcome the low quality data read, sampling speed limitations of the mobile device, and the noise introduced into the mobile device.
Reactive Peak Detection
Reactive peak detection is a heuristics based approach for peak detection, which is well suited for situations where the incoming signals from the card swipe is not excessively distorted by the mobile device's filter circuitry. This approach utilizes at least the following steps to detect signal peaks:
Seed an adaptive positive and adaptive negative threshold with an ambient noise value that is dependent on the hardware of the mobile device. These thresholds will be used for initial peak detection.
Begin processing through the sample buffer, and for each sample in the buffer:
Wait for the threshold to be crossed again when either the negative or positive threshold is crossed, except with a hysteresis factor applied to the threshold for the second crossing. The hysteresis factor is key in making this approach resistant to ringing in the incoming signals, which is associated with the active filter(s) of the platform hardware.
Begin looking for slope changes within this time frame once the two samples where the threshold is crossed have been established.
If more than one slope change is found, compute the midpoint of the two samples.
If only a single slope change is detected, then, pick the maximum point for the slope change.
Compare the peak's amplitude to the previously found peak's amplitude (if this has been established).
Skip the current peak and move on if its amplitude is greater than (([full scale]−[current peak amplitude])/([full scale]*100)+100)% of the previous peak's amplitude.
If the prior step did not result in skipping of the peak, check the peak's polarity against the previous peak's polarity.
If the peak's polarity is the same as the previous peak's polarity, then remove the previous peak and put the current peak in its place.
If the polarity of the current peak has changed, then simply add the current peak to the list of peaks. This step is another key component for making this approach resistant to ringing.
Upon the finding of a peak, update the adaptive threshold of the corresponding polarity as the polarity of the peak just found and the amplitude to be a percentage of this peak's amplitude. Here, the percentage is a parameter varied by the detection approach being used, since higher values more accurately detects peaks, but are not as resistant to noise, while lower values are more resistant to noise, but may pick up errant peaks associated with ringing.
Predictive Peak Detection
Predictive peak detection defers the heavy processing to the digitizing stage of decoding. Predictive peak detection is highly resistant to scratches in the card that could cause low quality or false peak information to manifest in the incoming signals. This approach is more memory intensive than the reactive peak detection approach since more peaks are stored. The approach utilizes at least the following steps to detect signal peaks:
Seed a positive and adaptive negative threshold with an ambient noise value that is dependent on the hardware of the mobile device.
Begin going through the sample buffer. For each sample in the buffer:
Begin waiting for the slope to change when either the positive of negative threshold is crossed.
When the slope changes, store the current sample as a peak.
Maxima Peak Detection
Maxima peak detection detects peaks by looking for local maxima and minima within a window of digital samples. If either of these is at the edges of the window of samples, then the approach skips the window and moves to the next window to look for local maxima and minima. These local maxima and minima are then stored into a list of peaks.
The flowchart 1400 continues to block 1408 where decoding engine 110 identifies the track from which data of the incoming signals are read through the swipe of the card via the card reader. Traditionally, track 1 and track 2 came off of different pins on the read head of a card reader, and so there was no need to guess which track is being read. Since read head 16 in card reader is capable of reading only one track of data from the magnetic stripe, track identification becomes an important issue. This track identification process is run by detection engine 110 after peaks are detected to guess and recognize the track (track 1 or track 2) from which the data is read by card reader by inferring a range of peaks to be expected for signals coming from each track. Since track 1 is known to be much denser in data than track 2, it is thus reasonable to expect more peaks to be identified in data coming from track 1. Although this process is not a definitive guess, it yields the correct track value 99.9% when coupled with the peak detection algorithms described herein in testing. Alternatively, track guessing can be based on the number of bits found in the digital signals after the digitizing stage of decoding. When a decoder fails due to guessing the wrong track (since track identification affects how the bits from the digital signals are framed and matched against character sets), the decoder may simply choose another track type, though this makes the card processing more processor intensive.
The flowchart 1400 continues to block 1410 where decoding engine 110 digitizes the identified peaks in the incoming signals into bits. The digitizing process takes the given peak information turns them into binary data and appends them to an array of digital bits. There are two types of digitizers: reactive digitizing and predictive digitizing.
Reactive Digitizing
Reactive digitizing takes the given peak information as fact, and attempts to convert them into 1s and 0s in the following steps:
Go through all peak information. For each peak:
Identify the distance between each pair of adjacent peaks.
If these distances are similar (e.g., based on a parameter for finding a series of peaks that are equidistant from each other), begin looking for 1s and 0s. The initial peaks always represent zeros, since the credit card is padded with zeros at the front and back of the signal.
Once equidistant peaks are found, identify the number of samples between peaks, which is the number of samples that roughly equate to a bit.
Examine the number of samples between the current peak and the next peak.
Examine the number of samples between the current peak and the peak after the next.
Compare the results from Steps 5 and 6 against the value from Step 4:
If the result from Step 5 is closer to the value from Step 4, then identify the bit found as a 0.
If the result from Step 6 is closer, then identify the bit found as a 1.
Tie breaking: if the distances are equal and the next two peak amplitudes are smaller than the current peak amplitude, then identify the bit found as a 1. Otherwise, identify the bit found as a 0.
Once the peak is determined, update the bit length based on the peak found: if the peak found was a 0, update with the value of Step 5; otherwise, use the value of step 6.
Predictive Digitizing
Predictive digitizing of detected peaks in the incoming signals does not treat the list of peaks as facts. It first finds bit length, and then seeks to a point in the peak list where the next relevant peak should be. Once it reaches this location, it then searches before and after the location for the nearest peak. The process then checks the polarity of this peak compared to the previous peak examined. If the polarities are the same, the bit found is identified as a 1. Otherwise, it is identified as a 0. This method of digitizing a peak list is effective in that it simply ignores any information that is likely irrelevant.
The flowchart 1400 ends at block 1412 where decoding engine 110 converts the array of digitized bits into words of card information. This converting process locates the bit sequence that is the start sentinel in the array. At that point, it takes frames of bits (e.g., 5 bits for track 2, 7 bits for track 1) and decodes them based on a symbol table. Along the way, the process constantly checks for parity and the LRC at the end to ensure the data is correct. If there are any errors in parity, LRC, or track length, blocks 1406-1412 may be repeated with a different set of parameters to get the correct signal data.
When a card swipe begins, decoding engine 110 can combine various peak detectors and digitizers discussed above in order to cover various ranges of degradation in quality of the analog input signal generated by card reader 10. In some embodiments, different process combinations and parameters can be chosen and optimized depending on the hardware platform of the mobile device. These combinations and parameter values can be pre-determined based on experimentation and testing and initialized upon starting of the decoding process. The decoding then runs through all processes specified and runs certain specific processes multiple times in order to get the correct signal. Such decoding process allows automatic scaling and adjustment during each run to account for different amounts of noise, sampling speed variations, signal ringing, and swipe direction.
Card Present Transaction without Information Sharing
In the example of
In some embodiments, other than the conventional keyboard, user interaction engine 120 may utilize a touch screen of mobile device 100 to enable the buyer and the merchant to input numbers, characters, and signatures by touching the screen via a stylus or a finger.
In some embodiments, in addition to the result of the transaction, user interaction engine 120 may also present products or services provided by the merchant to the buyer in combination of one or more of text, pictures, audio, and videos, and enable the buyer to browse through the products and services on the mobile device to choose the one he/she intended to purchase. Such product information can be stored and managed in product database 150.
In the example of
In the example of
In some embodiments, although transaction engine 130 does not share card information of the buyer to the merchant, it may present identity information of the buyer, such as a picture of the buyer on record in user database 140, with the merchant via user interaction engine 120 so that merchant can reliably confirm the identity of the buyer during the card-present transaction to prevent credit fraud.
In the example of
In the example of
Dynamic Receipt
In various embodiments, upon the completion of a financial transaction through, for a non-limiting example, card reader 10 connected to mobile device 100 associated with a merchant, transaction engine 130 running on the mobile device 100 can be configured to capture additional data associated with the transaction and incorporate the additional data into a dynamic receipt for the transaction, wherein in addition to transaction information typically included in a conventional receipt, the dynamic receipt may also include additional environmental information of the transaction. For non-limiting examples, the financial transaction can be an electronic transaction conducted over the Internet or a card present point-of-sale transaction where the buyer/payer makes the purchase at a store front, other “brick-and-mortar” location, or simply in presence of a merchant/payee.
In some embodiments, the additional environmental information included in the dynamic receipt may include information pertaining to the transaction environment. In one non-limiting example, a mobile device equipped with a Global Positioning System (GPS) receiver can be used to capture the coordinates/location of the transaction, and record it as a part of the information on the dynamic receipt. This way, the physical location of the point of sale (which may be different from the merchant/payee's registered address) can be recorded and used by transaction engine 120 to verify the transaction. In another non-limiting example, a mobile device equipped with a camera and/or audio and/or video recorder can be used to capture a photo and/or a video and/or an audio recording of the product or service involved in the transaction and incorporate such data or link/reference to such data into the dynamic receipt. In another non-limiting example, a mobile device with a biometric scanner can be used to scan the fingerprint or palm print of the buyer/payer and/or merchant/payee and includes at least a portion of such information in the dynamic receipt. In another non-limiting example, the mobile device can record certain information associated with the transaction in the dynamic receipt, wherein such information includes but is not limited to, how quickly the buyer swipes the card, the angle at which the card is swiped. In another non-limiting example, special characteristics of the card being swiped, also referred to as the magnetic fingerprint of the card, can be recorded and included in the dynamic receipt.
In some embodiments, the dynamic receipt can be in electronic form that can be accessed electronically or online and may also include link or reference pointing to multimedia information such as image, video or audio that are relevant to the transaction.
In some embodiments, transaction engine 130 can use the environmental information included in the dynamic receipt to assess risk associated with a transaction. For a non-limiting example, if the GPS information indicates that the transaction is taking place in a high crime/high risk area, the risk associated with the transaction is adjusted accordingly, and the buyer's bank may be notified accordingly. Alternatively, biometric information scanned and included in the dynamic receipt can be used for identity verification purposes to prevent identity theft and credit fraud.
In some embodiments, transaction engine 130 can use the dynamic receipt can be used as a non-intrusive way to communicate with the buyer and/or the merchant. For a non-limiting example, the additional information included in the dynamic receipt can be used to make offers to the buyer. If a dynamic receipt includes the GPS location of the point of sale of the transaction, coupons or other promotional offers made by vendors at nearby locations can be presented to the buyer when the buyer chooses to view the receipt electronically online. Alternatively, if a specific product involved the transaction can be identified by the transaction engine either directly through product description or indirectly by analyzing pictures or videos taken, offers of similar or complementary products can be made by a vendor to the merchant of the product.
In some embodiments, transaction engine 130 may notify buyer and/or the merchant of the receipt via an electronic message, which can be but is not limited to, an email message, a Short Message Service (SMS) message, Twitter, or other forms of electronic communication. The recipient of the electronic message may then retrieve a complete itemized dynamic receipt online at his/her convenience via a telephone number on his/her record in user database 140 to retrieve his/her electronic receipts stored in transaction database 160. In some embodiments, the electronic message may include an indication such as a code that the recipient can use to retrieve the electronic receipt online as an alternative or in combination with the telephone number.
In one embodiment, a longitudinal plane of the of the output jack 18 lies within the plane that the card travels in the slot 14 within 5 mm, and in another embodiment within 3 mm.
Referring now to
In another embodiment of the present invention, a method is provided for conducting a financial transaction with a financial transaction card using the integrated read head system 210.
In one embodiment of the present invention, as illustrated in
The first party's mobile device 100 is configured to communicate with the payment service. The first party views the names of the one or more qualified second parties with the first party's mobile device 100. The first party establishes the first party's financial account. The first party enters financial account information with a single initial entry to the payment service and additional entries of the financial account information to the payment service are not required for future financial transactions between the first party and any qualified second party when the same payment service is used.
The financial account is selected from at least one of, a bank account, credit card, debit card, pre-paid card, a second party financial account and the like. The financial account is selected by the first party by at least one of, use of a mobile device 100, from a bank terminal, done on-line and the like. The first party's financial account can be a financial transaction card, and the entering of the first party's financial card information is with a mobile device 100. Entering of the financial card information can be done by, swiping the financial transaction card through a slot of a card reader coupled to the mobile device 100, through a slot of the mobile device 100, by touch of the financial transaction card to the mobile device 100, by typing in information at the mobile device 100, with photos, by selecting a card from an application on a mobile device 100, from an on-line entity and the like. The mobile device 100 is a device as described above.
The qualified second party can see a list of first parties that have an association with the payment service. The qualified second party can view a list of first parties with open tabs. The list of first parties seen by the qualified second party has first party identifying information. The identifying information is anything that reliably identifies the first party and can include, but is not limited to, names, photos, cell number, social security number, e-mail address, other personal identifying information for a first party and the like.
In another embodiment, a method of paying a second party a first party views the names of one or more qualified second parties with a mobile device 100. Preferably, the mobile device 100 is the first party's mobile device 100. A tab is then opened by the first party as recited above that can be selected by the qualified second party at any geographic location of the first party's mobile device 100, but the qualified second party is only able to charge a first party's financial transaction card when the first party's mobile device 100 is within a defined geographic area. In one embodiment, the mobile device 100 is coupled to a card reader that includes an output jack adapted to be inserted at least one of the audio input port or microphone input port, USB port and the like of the mobile device 100 and delivers a signal to the mobile device 100. In various embodiments, the sampling rate of the signal at the audio input port or a line input port of the mobile device 100 is at least 15 kHZ, 20 kHz, 30 kHz, 40 kHz and the like.
Entering of the financial card information can be achieved by a variety of methods including but not limited to, swiping the financial transaction card through a slot of a card reader coupled to the mobile device 100, through a slot of the mobile device 100, with a touch of the financial transaction card to the mobile device 100, typing in information at the mobile device 100, with photos, selecting a card from an application on a mobile device 100 and from an on-line entity and the like.
A confirmation of payment can be made to the first party in response to a transfer of funds from the financial transaction card. In various embodiments, the financial transaction card is selected from at least one of, credit financial transaction card, debit financial transaction card, gift financial transaction card, fund transfer financial transaction card, other types of payment authenticating piece capable of carrying out a transfer of funds and the like, as set forth above.
In another embodiment of the present invention, illustrated in
In various embodiments, the first party's personal identifying information is entered by at least one of, use of a mobile device 100, from a bank terminal, done on-line and the like. For the transaction, the first party uses the first party's financial account. The first party enters financial account as recited above, which does not require re-entry with the payment service for future transactions with second parties that are also registered with the payment service.
In one embodiment, the first party uses the first party's financial transaction card for the transaction where the card information is entered to the payment service as recited above. Additionally, the first party enters it's personal identifying information with the payment service only once as recited above and need not re-enter for second party transactions.
In various embodiments, the on-line entity is any second party that can transact business with the payment service including but not limited to, merchants, peers and the like.
In one specific embodiment, the first party enters its personal identifying information, that is sent to the payment service, using the first party's mobile device 100. In this embodiment, the first party can use a first party financial card to complete the transaction. The first party's mobile device 100 is coupled to a card reader that includes an output jack adapted to be inserted at least one of the audio input port or microphone input port, USB port and the like, of the mobile device 100 and delivers a signal to the mobile device 100.
In another embodiment of the present invention, illustrated in
In another embodiment, funds are transferred from the first party's financial account to a second party using the payment service.
In one embodiment, the second party is already registered with the payment service or becomes registered with the payment service prior to the transfer of funds from the first party. In another embodiment, the second party is not registered with the payment service.
In one specific embodiment, funds are transferred to and/or from the first party's financial account using the payment service, e.g., to the first party or to a second party, where the financial account is a bank account, credit card, debit card, pre-paid card, a third party funding source and the like. In another specific embodiment.
In another embodiment, the first party's financial card is entered with a single initial entry to the payment service using a mobile device 100. Again, for future uses of the first party's financial transaction card to transfer funds using the payment service to a second party, the first party's financial transaction card information need not be entered again.
Again, the entering of the financial card information to the payment service can be achieved by, swiping the financial transaction card through a slot of a card reader coupled to the mobile device 100, through a slot of the mobile device 100, with a touch of the financial transaction card to the mobile device 100, typing in information at the mobile device 100, with photos, selecting a card from an application on a mobile device 100, from an on-line entity and the like.
In another embodiment of the present invention, a method of conducting a financial transaction includes the first party's financial account information being entered once, e.g, with a single initial entry to the payment service. For future uses of the first party's financial account to transfer funds using the payment service to a second party, the first party's financial account information need not be entered again with the payment service. The second party's personal identifying information is entered. Funds are transferred from the first party's financial account to an account of the second party with the use of the payment service.
In another embodiment, the first party's financial transaction card information is entered with a single initial entry to the payment service. Again, for future uses of the first party's financial transaction card to transfer funds using the payment service to a second party, the first party's financial account information need not be entered again with the payment service. The second party's personal identifying information is entered and funds are transferred from the first party's financial account to an account of the second party with the use of the payment service.
In various embodiments, (i) the second party has an association with the payment system, (ii) the first party and the second party each have an association with the payment system, (iii) the first party has an association with the payment system but the second party does not.
In one embodiment, the first party uses a send money mode of the first party's mobile device 100. In various embodiments, the second party is (i) anybody on the first party's phone list, (ii) not on the first party's phone list but is added to the first party's phone list in response to a transaction, (iii) the second party has an association with a payment system or is a database of the payment system, (iv) the second party does not have an association but then has one in response to a text message or equivalent sent to the second party, and the like. In response to the text message, the second party either accepts or rejects.
In another embodiment, the first party's financial transaction card information is entered with a single initial entry to the payment service. Again, for future uses of the first party's financial transaction card information to transfer funds using the payment service to a second party, the first party's financial account information need not be entered again with the payment service. The second party's mobile device 100 number is entered in the first party's mobile device 100. In response, funds are transferred from the first party to an account of the second party.
In one embodiment of the present invention, the read head 310 reads track 1 of the financial transaction card. Track 1 is 210 bytes per inch and is more difficult to decode than track 2. In one embodiment of reading track 1, the signal is interpreted and transferred at a constant rate 2400 baud.
In another embodiment, the read head 310 is configured to be positioned to provide for rotation of up to 10 degrees while still registering on a track to be read. The location of the read head 310 relative to the mobile device 312, and the microphone port of the mobile device 312, is off set from a center of track 1 in order to bias it to a bottom of track 1. As a non-limiting example, the offset can be 0.05 inches in the direction x and 0.040 inches in the y direction.
In another embodiment, illustrated in
In one embodiment, the mobile device 312 provides encryption and authentication. In this embodiment, each card reader 322 can have a unique key that can be included in the microprocessor 324 of the PCB 318. The financial transaction card is swiped and the signal interpreted. The microprocessor 324 than encrypts the data using a HWID and counter. The signal is encrypted when received at the mobile device 312 with an ID and counter. The signal sent to the back end 326 of the payment system where the identification of the read head 310 is determined and the signal is decrypted.
At the back end 326, the payment system can use HWID and decode the encrypted signal from the mobile device 312 using a hard function decode. Using HWID, encrypted hash function decode, the complete CC with CRC is reconstructed which is then sent to a payment gateway 328 as illustrated in
As illustrated in
Several fields of cardholder information are sent to the server at the back end 326 in either an encrypted or authenticated format. In one embodiment, the protocol has several fields: length of message, counter, hardware id, authenticated message length, issue type, last 4 digits of the financial transaction card, cardholder name, PAN number, expiration date, service code, and an authentication tag.
Referring to
Referring to
The read head 310 can include a power source 330 as illustrated in
In one embodiment, the read head 310 is a four piece plastic mold. The spring member 314 can be soldered onto the PCB 318 to form the sub-assembly 316.
As a non-limiting example, the read head housing 330 can be heat-staked onto the back side of the backbone 320. The battery 330 can be attached to the front side of the backbone 320 with PSA. With the front cover, it can be attached to the backbone 320 using ultrasonic welding. A TRS connector can be placed onto the back bone and the connection soldered to the PCB 318. The back cover can be attached to the backbone 320 to complete the assembly.
In various embodiments, the card reader 322 is coupled to various ports of the mobile device 312, including but not limited to the microphone port, the USB port, accessory port.
In another embodiment, the card reader is coupled to other ports of the mobile device 100, including but not limited to the USB port, accessory port and the like.
In one embodiment of the present invention, a method is provided of conducting a financial transaction with reduced likelihood of fraud. A financial transaction is entered into using a first party's financial transaction instrument to transfer funds. The first party's financial transaction instrument information is sent externally to the mobile device 100. The financial transaction instrument information is sent from the financial transaction instrument such as a mobile device 100 to a payment system. A determination is made to see if there is fraudulent use of the financial transaction instrument 100 prior to completion of the financial transaction. The mobile device 100 can be a merchant's mobile device 100. The determination of fraudulent use can be made either at the mobile device 100 or the payment system. In one embodiment, the first party's financial transaction instrument information is only sent once to the mobile device 100 and need not be done again for future purposes.
The financial transaction instrument 100 is selected from at least one of those listed above, as well as a person's financial account and the like.
In one embodiment, a location identifier is received from a position-sensing device indicating a location where the request is submitted or information that can lead to identification of the location where the request is submitted. The position-sensing device can be selected from a group of eligible devices. Information identifying the selected position-sensing device can be received by the request processor in advance of the request processor receiving the submitted request; and determining whether to service the request based at least in part on the received location identifier or information. The submission device can be embodied in an apparatus separate from an apparatus housing the position-sensing device. The submission device and the position-sensing device can be integrated in the mobile device 100.
In another embodiment, the first party's financial account information is entered using the first party's mobile device 100 with a single initial entry to a payment service. Funds are transferred to and/or from the first party's financial account using the payment service. The first party is registered with the payment service, or becomes registered prior to transferring funds to and/or from the financial account using the payment service. For future uses of the first party's financial account to transfer funds to and/or from the first party's financial account, the first party's financial account information need not be entered again with the payment service. In response to, (i) entering the first party's financial account information or (ii) using the first party's mobile device 100 for a financial transaction following the single initial entry to the payment service, a determination is made to see if a fraudulent attempt or fraudulent use of the first party's financial account information is committed.
In another embodiment, the first party's financial account information is entered using the first party's mobile device 100 with a single initial entry to a payment service. Funds are transferred from the first party's financial account to a second party using the payment service. The first party is either registered with the payment service, or becomes registered prior to transferring funds to and/or from the first party's financial account using the payment service. For future uses of the first party's financial account to transfer funds to and/or from the first party's financial account, the first party's financial account information need not be entered again with the payment service. In response to, (i) entering the first party's financial account information or (ii) using the first party's mobile device 100 for a financial transaction following the single initial entry to the payment service, a determination is made to see if a fraudulent attempt or fraudulent use of the first party's financial account information is committed.
In another embodiment, the first party's financial account information is entered using the first party's mobile device 100 with a single initial entry to the payment service. The first party's financial account is selected from at least one of, a bank account, credit card, debit card, pre-paid card and a third party funding source. Funds are transferred to and/or from the first party's financial account using the payment service. The first party is either registered with the payment service, or becomes registered prior to transferring funds to and/or from the financial account using the payment service. For future uses of the first party's financial account to transfer funds to and/or from the first party's financial account, the first party's financial account information need not be entered again with the payment service. In response to, (i) entering the first party's financial account information or (ii) using the first party's mobile device 100 for a financial transaction following the single initial entry to the payment service, a determination is made to see if a fraudulent attempt or fraudulent use of the first party's financial account information is committed.
In another embodiment, a first party's financial account information is entered using the first party's mobile device 100 with a single initial entry to a payment service. The first party's financial account is selected from at least one of, a bank account, credit card, debit card, pre-paid card and a third party funding source. Funds are transferred from the first party's financial account to a second party using the payment service. The first party is registered with the payment service, or becomes registered prior to transferring funds to and/or from the first party's financial account using the payment service. For future uses of the first party's financial account to transfer funds to and/or from the first party's financial account, the first party's financial information need not be entered again with the payment service. In response to, (i) entering the first party's financial account information or (ii) using the first party's mobile device 100 for a financial transaction following the single initial entry to the payment service, a determination is made to see if a fraudulent attempt or fraudulent use of the first party's financial account information is committed.
In another embodiment, a first party's financial transaction card information is entered using the first party's mobile device 100 with a single initial entry to a payment service. For future uses of the first party's financial transaction card to transfer funds to and/or from the first party's financial transaction card, the first party's financial transaction card information need not be entered again with the payment service. In response to, (i) entering the first party's financial transaction card information or (ii) using the first party's mobile device 100 for a financial transaction following the single initial entry to the payment service, a determination is made to see if a fraudulent attempt or fraudulent use of the first party's financial account information is committed.
In another embodiment, a first party's financial transaction card information is entered using the first party's mobile device 100 with a single initial entry to a payment service. Funds are transferred from the first party's financial transaction card to a second party using the payment service. The first party is registered with the payment service, or becomes registered prior to transferring funds to and/or from the first party's financial transaction card using the payment service. For future uses of the first party's financial transaction card to transfer funds to and/or from the first party's financial transaction card, the first party's financial transaction card information need not be entered again with the payment service the first party's financial. In response to, (i) entering the first party's financial transaction card information or (ii) using the first party's mobile device 100 for a financial transaction following the single initial entry to the payment service, a determination is made to see if a fraudulent attempt or fraudulent use of the first party's financial account information is committed.
In another embodiment, a first party accesses names of one or more qualified second parties. The qualified second parties are defined as second parties having an association with the payment service, and second parties that if they do not have an established association with the payment service, have an established association with the payment service prior to payment. The first party has an association with the payment service. A tab is opened by the first party that can be selected by the qualified second party at any geographic location of a first party's mobile device 100. The qualified second party is only able to charge a first party's financial account when the first party's mobile device 100 is within a defined geographic area. The tab is a relationship between the first party, the payment service and the qualified second party. The qualified second party can engage in a financial transaction with the first party when the first party is within the defined geographic area. In response to the second party, (i) attempting to charge the first party or (ii) charging the first party, a determination is made to see if a fraudulent attempt or fraudulent use of the first party's financial account is committed.
In another embodiment, names of one or more qualified second parties are accessing by the first party with the first party's mobile device 100. The second parties have an association with the payment service, or if not have one prior to payment. The first party has an association with the payment service. A tab is opened by the first party that can be selected by the qualified second party at any geographic location of the first party's mobile device 100. The qualified second party is only able to charge a first party's financial transaction card when the first party's mobile device 100 is within a defined geographic area. The qualified second party can engage in a financial transaction with the first party when the first party is within the defined geographic area. In response to the use of the first party's mobile device 100 to pay the second party, a determination is made to see if a fraudulent attempt or fraudulent use of the first party's financial transaction card is committed.
In another embodiment, a first party accesses a second party on-line entity. The mobile device 100 is configured to communicate with the payment service. The first party considers conducting a transaction with the second party on-line entity. The second party on-line entity is registered with the payment service or in response to the first party's desire to transact with the second party on-line entity, the second party on-line entity becomes registered with the payment service. The first party enters personal identifying information that is sent to the payment service. The first party receives a push notification to the first party's mobile device 100 that enables the first party to complete the transaction with the second party on-line entity. In response to the first party receiving the push notification to the first party's mobile device 100, a determination is made to see if a fraudulent attempt or fraudulent use of the first party's financial transaction card is committed.
In another embodiment, a first party visits a second party on-line entity. The first party considers conducting a transaction with the second party on-line entity. The first party enters personal identifying information using the first party's mobile device 312 and this is sent to the payment service. The first party receives a push notification of the first party's mobile device 312 that enables the first party to complete the transaction with the second party on-line entity. In response to the first party receiving the push notification to the first party's mobile device 312, a determination is made to see if a fraudulent attempt or fraudulent use of the first party's financial transaction card is committed.
Referring now to
Payment system 414 can be configured to check position information of the mobile device 412 against the permissible and/or impermissible use areas for each user, and thereby determine if the device is being used in an impermissible use area for the user. If so, the payment system 414 is configured to indicate that a possibility of fraud exists in the pending transaction. If the possibility of fraud is detected, the system may be configured to take an action, such as preventing fulfillment of the transaction due to the possibility of fraud.
The payment system 414 can be as described above and can include a conventional computing system with storage medium having programming instructions designed to implement the present invention, and one or more processors to execute the programming instructions.
In one embodiment, when a financial transaction cardholder is issued a financial transaction card, the cardholder may be asked to give the geographic location of their home and office, as well as any other locations that the cardholder frequently place on-line orders and use the credit card. This information may be obtained during the application process or on an ongoing basis. The information may be entered into a database.
Thus, when a financial transaction is conducted using a mobile device 412 current location information can be provided to the payment system 414 where a check can be performed for whether the financial transaction is being conducted from a permissible location. If the financial transaction is not being conducted from a permissible location, the financial transaction may be rejected. Additionally, a warning in the form of a message and/or a call may be provided to the financial transaction cardholder.
Referring to
The payment processing system 414 can detect the position of the card reader 418 and therefore, the position of the payment device in a payment device-present transaction.
In another embodiment, a position sensing device 420 can be included. The position-sensing device 420 can be configured to send position information to a position tracking system 422. The communication link between position tracking system 422 and position-sensing device 420 may be a satellite link such as used in a global positioning satellite system, radio frequency link, optical link such as infrared, or virtually any other communication link suitable for use in position detection.
As shown in
Security access control system 430 is further configured to detect the location or position of security device 426 and/or security reader 428 by the position information received from position sensor 416. Alternatively, the security access control system 430 can be configured to detect the position of the security device reader (and therefore the position of the security device in a device-present transaction), by resolving a security identifier using a database of known security identifier locations. For example, the security identifier 1234567 may correspond to a gated entrance to a secured building.
In order to detect an improper use of security device 426, security access control system 430 is configured to compare the position of position-sensing device 416 the location or position of a current transaction involving security device 426 (i.e., the location or position of security device 426 and/or security device reader 428). If the locations of the position-sensing device 416 and the security device 426 are different, or alternatively, if the locations of position-sensing device 416 and security reader 428 are different, then the security access control system is configured to determine that there is a possibility of improper use of the security device in the current transaction.
Upon determining the possibility of improper use, the system 430 is configured to take a designated action, such as warning a security attendant and/or by automatically locking an entrance to a secured area.
The security control system may be implemented with conventional computing system with storage medium having programming instructions designed to implement the present invention, and one or more processors to execute the programming instructions.
In one embodiment of the present invention, illustrated in
Referring now to
The microcontroller 526 is configured to convert raw bit patterns into formatted credit card 520 information. The microcontroller 526 can independently determine if the card data is valid. The card reader 510 can accept motion of the card 520 bi-directionally at either end of the slot 518 and at varying velocities as it is swiped through the slot 518. In one embodiment, the mobile device 516 detects the card reader 510 as a microphone.
In various embodiments, the output jack signal is an encrypted output jack signal, and encrypted and signed output jack signal and the like. The signal from the microcontroller 526 can be the output jack signal. The output jack signal can be a synchronous Manchester encoded stream, an asynchronized stream and the like. In one embodiment, the output jack signal is at a frequency that the output jack signal appears to look AC to a microphone input of the mobile device 516. In one embodiment, a frequency of the output jack signal is 2 KHz to 48 kHz, and in another it is 2.4 kHz. The output jack signal can be a low-amplitude analog waveform.
In one embodiment, the read head 514 sends the output jack signal to the mobile device 516 at a constant baud rate. As a non-limiting example, the constant baud rate is 2400 to 9200 baud.
In one embodiment, the microcontroller 526 has a non-volatile memory with a size of 2-8 kbytes, and RAM with a size 128-512 bytes. In an embodiment, the analog to digital front end 524 is configured to capture card 520 readings that are swept at a rate of 5 inches to 50 inches per second.
In one embodiment, the analog to digital front end 524 includes, an amplifier or amplifier/filter, (collectively 532) (
In one embodiment, the wake-up electronics 538 are powered by a microphone bias of a mobile device 516. In another embodiment, the microphone-bias line is used both for power and for data transmission back to the mobile device 516.
The wake-up electronics 538 detects when there is an edge from leading zeros of a card 520 being swiped and alerts to wake up the microcontroller 526 and device electronics 522. The device electronics 522 wakes up in enough time to process and encrypt a card 520 swipe signal.
The device electronics 522 can include the amplifier/filter 532, differentiator 534, comparator 536, transmission electronics 542 (
The raw magnetic head signal is amplified by the amplifier/filter 532 and processed before the microcontroller 526 accepts it as an input. The differentiator 534 takes the output of the amplifier/filter 532 and differentiates it, looking for peaks in the input signal. The comparator 536 takes the output of the differentiator 534 and compares it to a reference voltage and produces an output that is a processed digital version of a magnetic swipe. The comparator 536 looks for where an input signal crosses zero. The microcontroller 526 accepts the comparator 536 inputs, processes the comparator 536 inputs and encrypts at least a portion of data of the comparator 536 input. The microcontroller 526 controls power to the amplifier/filter 532, differentiator 534 and the comparator 536. The comparator 536 can be included as part of the microcontroller 526. The transmission electronics 542 accepts output data of the microcontroller 526 as an input and uses this to modulate a microphone-bias line of the mobile device 516.
In another embodiment, a method is provided of transmitting information to a mobile device 516 using the card reader 510. In this embodiment, the raw magnetic head signal is received at the analog to digital front end 524 and converted into a processed digital signal that the microcontroller 526 can interpret. The output jack signal is thereafter delivered to the mobile device 516.
In another embodiment, the card reader 510 includes a housing 512. The read head 514 is positioned in the housing 512 and is configured to be coupled to the mobile device 516. In this embodiment, the power supply is coupled to the wake-up electronics 538 and the microcontroller 526. The output jack 530 is adapted to be inserted in a port of the mobile device 516 and deliver the output jack signal to the mobile device 516. The wake-up electronics 538 is powered by a microphone bias of a mobile device 516.
In another embodiment, a method is provided of transmitting information to a mobile device 516. The read head 514 includes the power supply coupled to wake-up electronics 538 and the microcontroller 526. The wake-up electronics 538 is powered by a microphone bias of the mobile device 516.
In another embodiment, the card reader 510 includes a housing 512, a read head 514 positioned in the housing 512, the power supply coupled to wake-up electronics 538 and the microcontroller 526 and the output jack 530 adapted to be inserted in a port of the mobile device 516 and deliver an output jack signal to the mobile device 516.
In another embodiment, a method is of transmitting information to a mobile device 516. A card reader 510 is provided with a read head 514 that has a slot 518 for swiping a magnetic stripe of a card 520, a power supply, the card reader 510 including wake-up electronics 538 and a microcontroller 526, and a power supply coupled to the wake-up electronics 538 and the microcontroller 526. Data is read from the magnetic stripe. A raw magnetic signal is produced indicative of data stored on the magnetic stripe. The raw magnetic head signal is converted into a processed digital signal that the microcontroller 526 interprets. An output jack signal is thereafter sent to the mobile device 516.
In another embodiment of the present invention, illustrated in
In various embodiments, the rocking can be, 2 to 10 degrees of rotation, 3 to 10 degrees of rotation, 4 to 10 degrees of rotation and the like.
The rotation can be in a direction of a plane of the card 520. Accommodation of rocking enables a bottom of the card 520 to be moved in a direction away from a bottom of the slot 518 while the card 520 is slid through the slot 518 (
In one embodiment, the slot 518 is configured to provide for directionality of card 520 swipe directions (
As illustrated in
In another embodiment, a method is provided of transmitting information to a mobile device 516 with a small reader 510. The card reader 510 has length and height dimensions that are less than length or height dimensions of a coupled mobile device 516 (
Referring now to
The asymmetric spring 544 can be a cantilever with a pre-load onto an opposing wall on a back bone to provide that the read head 514 is substantially perpendicular to the magnetic strip of the card 520 when the card 520 is read by the read head 514. The asymmetric spring 544 can be configured to provide read head 514 positional adjustment when a card 520 is in the card reader slot 518. Accommodation of rocking enables a card 520 to be moved in a direction away from a bottom of the slot 518 while the card 520 is slid through the slot 518. The asymmetric spring 544 can be attached at a single point to a side of the housing 512.
In one embodiment, the asymmetric spring 544 angles the read head 514 to create an angled read head 514. This provides that when a card 520 is inserted in the slot 518 the read head 514 is parallel to the card 520. The angled head is substantially parallel with a card 520 as it is swiped through the slot 518.
As illustrated in
In one embodiment, the read head 514 is shifted up with respect to a center line of the magnetic track. The card 520 can be rotated farther off a bottom of the slot 518 before a read head active area is no longer on the magnetic track of the card 520. In various embodiments, the read head 514 is configured to be positioned to, (i) be offset from a center of track 1 or track 2 of the card 520; provide up to 10 degrees of rotation and still register on track 1 or track 2 of the card 520, and the like.
As shown in
By offsetting, the housing 512 has a bottom surface that is adjacent to the mobile device 516, and the read head 514 is positioned in the housing 512 to be non-parallel to the bottom surface and the associated surface of the mobile device 516. Off setting provides a higher success rate of swipes achieved with rotation of the card 520 in the slot 518.
In one embodiment, the device electronics receives a raw signal from the read head 514 and converts it into a process digital signal that the microcontroller 526 can interpret. The microcontroller 526 has associated logic resources and code that receives a digital signal from the device electronics 522 and creates an encrypted and signed message based on the contents of the signal. The output jack 530 delivers an encrypted and signed output jack signal to the mobile device 516, with at least a portion of the output jack signal being encrypted. The message created can contain both encrypted and non-encrypted data, and a signature that can be used to verify that the data has not been modified.
In one embodiment, the microcontroller code uses a block cipher for encryption and signing. In one embodiment, the microcontroller uses the CCFB+H cipher mode for encryption and signing. Some embodiments of the encryption logic are described in Two-Pass Authenticated Encryption Faster than Generic Composition, S. Lucks, University of Mannheim, Germany; http://th/informatic-uni-mannheim/de/people/lucks/.; and Comparing Block Cipher Modes of Operation on MICAz Sensor Nodes, G. Bauer et al., Institute for Applied Information Processing and Communications, Gran University of Technology, both fully incorporated herein by reference.
The microcontroller code can include a unique identifier and cryptographic key. The code can inspect itself to see if it, its cryptographic key, or its identifier has been modified. In one embodiment, the code includes countermeasures to detect tampering and attacks on the card reader.
In one embodiment, the card reader 514 disables itself when modification or tampering is detected. In one embodiment, the code is no more than 8 kilobytes in size.
The cryptographic key can be expanded before programming, and the microcontroller code does not include or require key expansion functionality. The microcontroller can be configured to recalculate the bit period in real time to capture variable-speed swipes. In one embodiment, the microcontroller is configured to parse and error-check card data. Additionally, the microcontroller can be configured to run periodic checksums on code and memory.
In one embodiment, the microcontroller uses thresholds to filter out erroneous data and/or false edges. The microcontroller can be configured to determine 1's and 0's by checking the frequency of polarity changes within a bit period.
In one embodiment, the microcontroller 526 is configured to produce a synchronous Manchester encoded stream that makes a greater number of 0 crossings. The output jack 530 is adapted to be inserted in a port of the mobile device 516 and deliver a Manchester encoded stream via the output jack 530 to the mobile device 516.
The number of 0 crossings is sufficient to simulate a signal with a sufficiently high frequency so that the mobile device's active filter does not cut off the output jack signal. AC coupling/filtering can be applied to the output jack signal.
Referring to
The packet can contain both encrypted and non-encrypted data. The signature can be used to verify that the data has not been modified. In one embodiment, the encrypted and signed packet includes an identifier that is unique to the card reader 510. The cryptographic key associated with the card reader 510 is derived from a master secret and the card reader's unique identifier. The master secret can be created in a hardware security module and never transmitted to or shared with the card reader 510 manufacturing facility, payment gateway, mobile devices, or any other third party.
The back end derives the cryptographic key used to encrypt a packet based on the unique identifier contained within the packet. In one embodiment, the back end uses a block cipher algorithm to decrypt and verify the contents of the packet, and the CCFB+H cipher mode to decrypt and verify the contents of the packet.
An acknowledgment of successful or unsuccessful transactions can be sent from the back-end to the mobile device. Selected information about the packet and transaction can be stored at the back-end and used for data mining. The stored information can be used for communicating to a purchaser relative to the purchaser's purchasing history and activity.
In one embodiment, the encrypted and signed signal is created by the microcontroller 526 with no more than 8 kilobytes of code. The microcontroller 526 can be used to recalculate a bit period in real time to capture variable-speed swipes. Additionally, the microcontroller 526 can be used to parse and error-check card 520 data. In one embodiment, the microcontroller 526 is used to run periodic checksums on code and memory.
Thresholds can be used to filter out erroneous data and/or false edges. The microcontroller 526 can be used to determine 1's and 0's by checking the frequency of polarity changes within a bit period.
The foregoing description of various embodiments of the claimed subject matter has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the claimed subject matter to the precise forms disclosed. Many modifications and variations will be apparent to the practitioner skilled in the art. Particularly, while the concept “component” is used in the embodiments of the systems and methods described above, it will be evident that such concept can be interchangeably used with equivalent concepts such as, class, method, type, interface, module, object model, and other suitable concepts. Embodiments were chosen and described in order to best describe the principles of the invention and its practical application, thereby enabling others skilled in the relevant art to understand the claimed subject matter, the various embodiments and with various modifications that are suited to the particular use contemplated.
This application is a continuation-in-part of U.S. Ser. No. 13/192,147 filed Jul. 27, 2011, which application is a divisional of U.S. Ser. No. 13/179,836, filed Jul. 11, 2011, which application is a continuation-in-part of U.S. Ser. No. 12/707,228 filed Feb. 17, 2010, which is a continuation of U.S. Ser. No. 12/050,752 filed Mar. 18, 2008, which is a continuation of U.S. Ser. No. 10/355,557 filed Jan. 31, 2003, which claims the benefit of U.S. 60/355,667 filed Feb. 5, 2002, U.S. 60/356,861 filed Feb. 12, 2002, and U.S. 60/361,646 filed Mar. 4, 2002. Said Ser. No. 12/707,228 is also a continuation-in-part of U.S. Ser. No. 12/903,753, U.S. Ser. No. 12/903,823, both filed Oct. 13, 2010, U.S. Ser. No. 13/005,822 filed Jan. 13, 2011 and U.S. Ser. No. 12/985,982, filed Jan. 6, 2011, U.S. Ser. No. 13/010,976, filed Jan. 21, 2011, U.S. Ser. No. 13/012,495, filed Jan. 24, 2011 and U.S. Ser. Nos. 13/043,203, 13/043,258, 13/043,263, 13/043,268, and 13/043,270, all filed Mar. 8, 2011. This application is related to U.S. Ser. No. 12/456,134, filed Jun. 10, 2009, and is hereby incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3854036 | Gupta | Dec 1974 | A |
| 4035614 | Frattarola et al. | Jul 1977 | A |
| 4254441 | Fisher | Mar 1981 | A |
| 4591937 | Nakarai et al. | May 1986 | A |
| 4609957 | Gentet et al. | Sep 1986 | A |
| 4727544 | Brunner et al. | Feb 1988 | A |
| 4788420 | Chang et al. | Nov 1988 | A |
| 4845740 | Tokuyama et al. | Jul 1989 | A |
| 5173597 | Anglin | Dec 1992 | A |
| 5266789 | Anglin et al. | Nov 1993 | A |
| 5406627 | Thompson et al. | Apr 1995 | A |
| 5434395 | Storck et al. | Jul 1995 | A |
| 5434400 | Scherzer | Jul 1995 | A |
| 5463678 | Kepley et al. | Oct 1995 | A |
| 5589855 | Blumstein et al. | Dec 1996 | A |
| 5603078 | Henderson et al. | Feb 1997 | A |
| 5616904 | Fernadez | Apr 1997 | A |
| 5679943 | Schultz et al. | Oct 1997 | A |
| 5729591 | Bailey | Mar 1998 | A |
| 5764742 | Howard et al. | Jun 1998 | A |
| 5850599 | Seiderman | Dec 1998 | A |
| 5878337 | Joao et al. | Mar 1999 | A |
| 5945654 | Huang | Aug 1999 | A |
| 5991749 | Morrill, Jr. | Nov 1999 | A |
| D417442 | Butts et al. | Dec 1999 | S |
| 6006109 | Shin | Dec 1999 | A |
| 6021944 | Arakaki | Feb 2000 | A |
| 6032859 | Hughes et al. | Mar 2000 | A |
| 6061666 | Do et al. | May 2000 | A |
| 6129277 | Grant et al. | Oct 2000 | A |
| 6234389 | Valliani et al. | May 2001 | B1 |
| 6308227 | Kumar et al. | Oct 2001 | B1 |
| 6363139 | Zurek et al. | Mar 2002 | B1 |
| 6400517 | Murao | Jun 2002 | B1 |
| 6431445 | DeLand et al. | Aug 2002 | B1 |
| 6476743 | Brown et al. | Nov 2002 | B1 |
| 6481623 | Grant et al. | Nov 2002 | B1 |
| 6497368 | Friend et al. | Dec 2002 | B1 |
| 6536670 | Postman et al. | Mar 2003 | B1 |
| 6579728 | Grant et al. | Jun 2003 | B2 |
| D477321 | Baughman | Jul 2003 | S |
| 6612488 | Suzuki | Sep 2003 | B2 |
| 6813608 | Baranowski | Nov 2004 | B1 |
| 6832721 | Fujii | Dec 2004 | B2 |
| 6850147 | Prokoski et al. | Feb 2005 | B2 |
| 6868391 | Hultgren | Mar 2005 | B1 |
| 6896182 | Sakaguchi | May 2005 | B2 |
| 6944782 | von Mueller et al. | Sep 2005 | B2 |
| 6979231 | Shinohara | Dec 2005 | B2 |
| 7003316 | Elias et al. | Feb 2006 | B1 |
| 7013149 | Vetro et al. | Mar 2006 | B2 |
| 7149296 | Brown et al. | Dec 2006 | B2 |
| 7163148 | Durbin et al. | Jan 2007 | B2 |
| 7167711 | Dennis | Jan 2007 | B1 |
| 7252232 | Fernandes et al. | Aug 2007 | B2 |
| 7309012 | Von Mueller et al. | Dec 2007 | B2 |
| 7324836 | Steenstra et al. | Jan 2008 | B2 |
| 7363054 | Elias et al. | Apr 2008 | B2 |
| D575056 | Tan | Aug 2008 | S |
| 7409234 | Glezerman | Aug 2008 | B2 |
| 7424732 | Matsumoto et al. | Sep 2008 | B2 |
| 7433452 | Taylor et al. | Oct 2008 | B2 |
| 7505762 | Onyon et al. | Mar 2009 | B2 |
| 7506812 | Von Mueller et al. | Mar 2009 | B2 |
| D590828 | Sherrod et al. | Apr 2009 | S |
| 7520430 | Stewart et al. | Apr 2009 | B1 |
| 7581678 | Narendra et al. | Sep 2009 | B2 |
| 7600673 | Stoutenburg et al. | Oct 2009 | B2 |
| D607000 | Cheng et al. | Dec 2009 | S |
| 7703676 | Hart et al. | Apr 2010 | B2 |
| 7708189 | Cipriano | May 2010 | B1 |
| 7757953 | Hart et al. | Jul 2010 | B2 |
| 7793834 | Hachey et al. | Sep 2010 | B2 |
| 7810729 | Morley, Jr. | Oct 2010 | B2 |
| 7869591 | Nagel et al. | Jan 2011 | B1 |
| 7896248 | Morley, Jr. | Mar 2011 | B2 |
| 7918394 | Morley et al. | Apr 2011 | B1 |
| 7945494 | Williams | May 2011 | B2 |
| 8011587 | Johnson et al. | Sep 2011 | B2 |
| 8015070 | Sinha et al. | Sep 2011 | B2 |
| D646264 | Dong | Oct 2011 | S |
| D653664 | Turnbull et al. | Feb 2012 | S |
| 8132670 | Chen | Mar 2012 | B1 |
| 8231055 | Wen | Jul 2012 | B2 |
| 8297507 | Kayani | Oct 2012 | B2 |
| 8302860 | McKelvey | Nov 2012 | B2 |
| 8336771 | Tsai et al. | Dec 2012 | B2 |
| D675618 | Behar et al. | Feb 2013 | S |
| 8376239 | Humphrey | Feb 2013 | B1 |
| D677667 | Smith et al. | Mar 2013 | S |
| D679714 | Smith et al. | Apr 2013 | S |
| D680537 | Miller et al. | Apr 2013 | S |
| 8413901 | Wen | Apr 2013 | B2 |
| 8452004 | Lee | May 2013 | B2 |
| D686208 | Miller et al. | Jul 2013 | S |
| 8500010 | Marcus et al. | Aug 2013 | B1 |
| 8500018 | McKelvey et al. | Aug 2013 | B2 |
| 8560823 | Aytek et al. | Oct 2013 | B1 |
| 8571989 | Dorsey et al. | Oct 2013 | B2 |
| 8573486 | McKelvey et al. | Nov 2013 | B2 |
| 8573487 | McKelvey | Nov 2013 | B2 |
| 8573489 | Dorsey et al. | Nov 2013 | B2 |
| 8584946 | Morley, Jr. | Nov 2013 | B2 |
| 8602305 | Dorsey et al. | Dec 2013 | B2 |
| 8612352 | Dorsey et al. | Dec 2013 | B2 |
| 8615445 | Dorsey et al. | Dec 2013 | B2 |
| 8640953 | Dorsey et al. | Feb 2014 | B2 |
| D700606 | Lo | Mar 2014 | S |
| 8662389 | Dorsey et al. | Mar 2014 | B2 |
| 8678277 | Dorsey et al. | Mar 2014 | B2 |
| D703211 | Weller et al. | Apr 2014 | S |
| 8701996 | Dorsey et al. | Apr 2014 | B2 |
| 8701997 | Dorsey et al. | Apr 2014 | B2 |
| D706266 | Rotsaert | Jun 2014 | S |
| 8740072 | Dorogusker | Jun 2014 | B1 |
| 8763900 | Marcus et al. | Jul 2014 | B2 |
| D711876 | McWilliam et al. | Aug 2014 | S |
| 8794517 | Templeton et al. | Aug 2014 | B1 |
| D712892 | Hong et al. | Sep 2014 | S |
| 8820650 | Wilson et al. | Sep 2014 | B2 |
| 8840017 | Chan et al. | Sep 2014 | B2 |
| 8840024 | McKelvey et al. | Sep 2014 | B2 |
| 8870070 | McKelvey et al. | Oct 2014 | B2 |
| 8870071 | McKelvey | Oct 2014 | B2 |
| 8876003 | McKelvey | Nov 2014 | B2 |
| 8910868 | Wade et al. | Dec 2014 | B1 |
| 8931699 | Wade et al. | Jan 2015 | B1 |
| D724094 | Blochinger et al. | Mar 2015 | S |
| D725655 | Debaigue et al. | Mar 2015 | S |
| 8967465 | Wade et al. | Mar 2015 | B1 |
| D726171 | Edwards | Apr 2015 | S |
| 9016570 | Gluck | Apr 2015 | B1 |
| 9016572 | Babu et al. | Apr 2015 | B2 |
| D728549 | Su et al. | May 2015 | S |
| D728568 | Debaigue et al. | May 2015 | S |
| D731493 | Mills | Jun 2015 | S |
| 9063737 | Babu et al. | Jun 2015 | B2 |
| D740820 | Templeton et al. | Oct 2015 | S |
| 20010001856 | Gould et al. | May 2001 | A1 |
| 20020002507 | Hatakeyama | Jan 2002 | A1 |
| 20020017568 | Grant et al. | Feb 2002 | A1 |
| 20020030871 | Anderson et al. | Mar 2002 | A1 |
| 20020073304 | Marsh et al. | Jun 2002 | A1 |
| 20020077974 | Ortiz | Jun 2002 | A1 |
| 20020099648 | DeVoe et al. | Jul 2002 | A1 |
| 20020108062 | Nakajima et al. | Aug 2002 | A1 |
| 20020165462 | Westbrook et al. | Nov 2002 | A1 |
| 20020169541 | Bouve et al. | Nov 2002 | A1 |
| 20020188535 | Chao et al. | Dec 2002 | A1 |
| 20030089772 | Chien | May 2003 | A1 |
| 20030132300 | Dilday et al. | Jul 2003 | A1 |
| 20030135463 | Brown et al. | Jul 2003 | A1 |
| 20030144040 | Liu | Jul 2003 | A1 |
| 20040011650 | Zenhausern et al. | Jan 2004 | A1 |
| 20040012875 | Wood | Jan 2004 | A1 |
| 20040033726 | Kao | Feb 2004 | A1 |
| 20040041911 | Odagiri et al. | Mar 2004 | A1 |
| 20040058705 | Morgan et al. | Mar 2004 | A1 |
| 20040087339 | Goldthwaite et al. | May 2004 | A1 |
| 20040093496 | Colnot | May 2004 | A1 |
| 20040104268 | Bailey | Jun 2004 | A1 |
| 20040127256 | Goldthwaite et al. | Jul 2004 | A1 |
| 20040128256 | Dhanjal et al. | Jul 2004 | A1 |
| 20040151026 | Naso et al. | Aug 2004 | A1 |
| 20040204074 | Desai | Oct 2004 | A1 |
| 20040204082 | Abeyta | Oct 2004 | A1 |
| 20040230489 | Goldthwaite et al. | Nov 2004 | A1 |
| 20040230526 | Praisner | Nov 2004 | A1 |
| 20050009004 | Xu et al. | Jan 2005 | A1 |
| 20050010702 | Saito et al. | Jan 2005 | A1 |
| 20050077870 | Ha et al. | Apr 2005 | A1 |
| 20050156037 | Wurzburg | Jul 2005 | A1 |
| 20050156038 | Wurzburg | Jul 2005 | A1 |
| 20050194452 | Nordentoft et al. | Sep 2005 | A1 |
| 20050209719 | Beckert et al. | Sep 2005 | A1 |
| 20050219728 | Durbin et al. | Oct 2005 | A1 |
| 20050236480 | Vrotsos et al. | Oct 2005 | A1 |
| 20050242173 | Suzuki | Nov 2005 | A1 |
| 20050247787 | Von Mueller et al. | Nov 2005 | A1 |
| 20060000917 | Kim et al. | Jan 2006 | A1 |
| 20060049255 | Von Mueller et al. | Mar 2006 | A1 |
| 20060049256 | Von Mueller et al. | Mar 2006 | A1 |
| 20060094481 | Gullickson | May 2006 | A1 |
| 20060122902 | Petrov et al. | Jun 2006 | A1 |
| 20060142058 | Elias et al. | Jun 2006 | A1 |
| 20060152276 | Barksdale | Jul 2006 | A1 |
| 20060208066 | Finn et al. | Sep 2006 | A1 |
| 20060219776 | Finn | Oct 2006 | A1 |
| 20060223580 | Antonio et al. | Oct 2006 | A1 |
| 20060234771 | Shavrov | Oct 2006 | A1 |
| 20060273158 | Suzuki | Dec 2006 | A1 |
| 20070063048 | Havens et al. | Mar 2007 | A1 |
| 20070067833 | Colnot | Mar 2007 | A1 |
| 20070100651 | Ramer et al. | May 2007 | A1 |
| 20070124211 | Smith | May 2007 | A1 |
| 20070155430 | Cheon et al. | Jul 2007 | A1 |
| 20070174080 | Outwater | Jul 2007 | A1 |
| 20070201492 | Kobayashi | Aug 2007 | A1 |
| 20070221728 | Ferro et al. | Sep 2007 | A1 |
| 20070244811 | Tumminaro | Oct 2007 | A1 |
| 20070250623 | Hickey et al. | Oct 2007 | A1 |
| 20070255620 | Tumminaro et al. | Nov 2007 | A1 |
| 20070255643 | Capuano et al. | Nov 2007 | A1 |
| 20070255653 | Tumminaro et al. | Nov 2007 | A1 |
| 20080017712 | Hart et al. | Jan 2008 | A1 |
| 20080027815 | Johnson et al. | Jan 2008 | A1 |
| 20080040265 | Rackley, III et al. | Feb 2008 | A1 |
| 20080040274 | Uzo | Feb 2008 | A1 |
| 20080059370 | Sada et al. | Mar 2008 | A1 |
| 20080059375 | Abifaker | Mar 2008 | A1 |
| 20080103972 | Lanc | May 2008 | A1 |
| 20080147564 | Singhal | Jun 2008 | A1 |
| 20080172306 | Schorr et al. | Jul 2008 | A1 |
| 20080177662 | Smith et al. | Jul 2008 | A1 |
| 20080208762 | Arthur et al. | Aug 2008 | A1 |
| 20080238610 | Rosenberg | Oct 2008 | A1 |
| 20080249939 | Veenstra | Oct 2008 | A1 |
| 20080275779 | Lakshminarayanan | Nov 2008 | A1 |
| 20090048978 | Ginter et al. | Feb 2009 | A1 |
| 20090068982 | Chen et al. | Mar 2009 | A1 |
| 20090098908 | Silverbrook et al. | Apr 2009 | A1 |
| 20090100168 | Harris | Apr 2009 | A1 |
| 20090104920 | Moon et al. | Apr 2009 | A1 |
| 20090117883 | Coffing et al. | May 2009 | A1 |
| 20090119190 | Realini | May 2009 | A1 |
| 20090125429 | Takayama | May 2009 | A1 |
| 20090144161 | Fisher | Jun 2009 | A1 |
| 20090159681 | Mullen et al. | Jun 2009 | A1 |
| 20090166422 | Biskupski | Jul 2009 | A1 |
| 20090187492 | Hammad et al. | Jul 2009 | A1 |
| 20100063893 | Townsend | Mar 2010 | A1 |
| 20100108762 | Morley, Jr. | May 2010 | A1 |
| 20100127857 | Kilmurray et al. | May 2010 | A1 |
| 20100184479 | Griffin | Jul 2010 | A1 |
| 20100191653 | Johnson et al. | Jul 2010 | A1 |
| 20100222000 | Sauer et al. | Sep 2010 | A1 |
| 20100241838 | Cohen et al. | Sep 2010 | A1 |
| 20100243732 | Wallner | Sep 2010 | A1 |
| 20100289390 | Kenney | Nov 2010 | A1 |
| 20100314446 | Morley, Jr. | Dec 2010 | A1 |
| 20110033910 | Yamanaka et al. | Feb 2011 | A1 |
| 20110053560 | Jain et al. | Mar 2011 | A1 |
| 20110062235 | Morley, Jr. | Mar 2011 | A1 |
| 20110084131 | McKelvey | Apr 2011 | A1 |
| 20110084139 | McKelvey et al. | Apr 2011 | A1 |
| 20110084140 | Wen | Apr 2011 | A1 |
| 20110084147 | Wilson et al. | Apr 2011 | A1 |
| 20110137803 | Willins | Jun 2011 | A1 |
| 20110161235 | Beenau et al. | Jun 2011 | A1 |
| 20110165896 | Stromberg et al. | Jul 2011 | A1 |
| 20110174879 | Morley, Jr. | Jul 2011 | A1 |
| 20110180601 | Morley, Jr. | Jul 2011 | A1 |
| 20110191196 | Orr et al. | Aug 2011 | A1 |
| 20110198395 | Chen | Aug 2011 | A1 |
| 20110202463 | Powell | Aug 2011 | A1 |
| 20110258120 | Weiss | Oct 2011 | A1 |
| 20110259957 | Tsai | Oct 2011 | A1 |
| 20110313880 | Paul et al. | Dec 2011 | A1 |
| 20120008851 | Pennock et al. | Jan 2012 | A1 |
| 20120011024 | Dorsey et al. | Jan 2012 | A1 |
| 20120011071 | Pennock et al. | Jan 2012 | A1 |
| 20120012653 | Johnson et al. | Jan 2012 | A1 |
| 20120016794 | Orr et al. | Jan 2012 | A1 |
| 20120026018 | Lin | Feb 2012 | A1 |
| 20120052910 | Mu et al. | Mar 2012 | A1 |
| 20120095869 | McKelvey | Apr 2012 | A1 |
| 20120095870 | McKelvey | Apr 2012 | A1 |
| 20120097739 | Babu et al. | Apr 2012 | A1 |
| 20120097740 | Lamba et al. | Apr 2012 | A1 |
| 20120118956 | Lamba | May 2012 | A1 |
| 20120118959 | Sather et al. | May 2012 | A1 |
| 20120118960 | Sather et al. | May 2012 | A1 |
| 20120126005 | Dorsey et al. | May 2012 | A1 |
| 20120126006 | Dorsey et al. | May 2012 | A1 |
| 20120126007 | Lamba | May 2012 | A1 |
| 20120126010 | Babu et al. | May 2012 | A1 |
| 20120126011 | Lamba et al. | May 2012 | A1 |
| 20120126012 | Lamba et al. | May 2012 | A1 |
| 20120126013 | Sather et al. | May 2012 | A1 |
| 20120126014 | Sather et al. | May 2012 | A1 |
| 20120130903 | Dorsey et al. | May 2012 | A1 |
| 20120132712 | Babu et al. | May 2012 | A1 |
| 20120138683 | Sather et al. | Jun 2012 | A1 |
| 20120154561 | Chari | Jun 2012 | A1 |
| 20120168505 | Sather et al. | Jul 2012 | A1 |
| 20120234918 | Lindsay | Sep 2012 | A1 |
| 20120246074 | Annamalai et al. | Sep 2012 | A1 |
| 20120259651 | Mallon et al. | Oct 2012 | A1 |
| 20120270528 | Goodman | Oct 2012 | A1 |
| 20130031003 | Dorsey et al. | Jan 2013 | A1 |
| 20130031004 | Dorsey et al. | Jan 2013 | A1 |
| 20130087614 | Limtao et al. | Apr 2013 | A1 |
| 20130137367 | Fisher | May 2013 | A1 |
| 20130200147 | Dorsey et al. | Aug 2013 | A1 |
| 20130200148 | Dorsey et al. | Aug 2013 | A1 |
| 20130200149 | Dorsey et al. | Aug 2013 | A1 |
| 20130200153 | Dorsey et al. | Aug 2013 | A1 |
| 20130200154 | Dorsey et al. | Aug 2013 | A1 |
| 20130204788 | Dorsey et al. | Aug 2013 | A1 |
| 20130204791 | Dorsey et al. | Aug 2013 | A1 |
| 20130204792 | Dorsey et al. | Aug 2013 | A1 |
| 20130207481 | Gobburu et al. | Aug 2013 | A1 |
| 20130254117 | von Mueller et al. | Sep 2013 | A1 |
| 20130254118 | Dorsey et al. | Sep 2013 | A1 |
| 20130304244 | Ojanpera | Nov 2013 | A1 |
| 20130320089 | Marcus et al. | Dec 2013 | A1 |
| 20140001257 | Dorsey et al. | Jan 2014 | A1 |
| 20140001263 | Babu et al. | Jan 2014 | A1 |
| 20140017955 | Lo et al. | Jan 2014 | A1 |
| 20140018016 | Chang et al. | Jan 2014 | A1 |
| 20140061301 | Cho et al. | Mar 2014 | A1 |
| 20140076964 | Morley, Jr. | Mar 2014 | A1 |
| 20140089205 | Kapur et al. | Mar 2014 | A1 |
| 20140097242 | McKelvey | Apr 2014 | A1 |
| 20140124576 | Zhou | May 2014 | A1 |
| 20140131442 | Morrow et al. | May 2014 | A1 |
| 20140144983 | Dorsey et al. | May 2014 | A1 |
| 20140203082 | Huh | Jul 2014 | A1 |
| 20150149992 | Wade et al. | May 2015 | A1 |
| 20150161419 | Wade et al. | Jun 2015 | A1 |
| 20150199677 | Wade et al. | Jul 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 2 812 251 | Apr 2012 | CA |
| 1 145 766 | Oct 2001 | EP |
| 2003-108777 | Apr 2003 | JP |
| 2004078662 | Mar 2004 | JP |
| 2005-063869 | Mar 2005 | JP |
| 2005-242550 | Sep 2005 | JP |
| 2005269172 | Sep 2005 | JP |
| 2009-199649 | Sep 2009 | JP |
| 2001-313714 | Nov 2011 | JP |
| 2013-518344 | May 2013 | JP |
| 10-0452161 | Oct 2004 | KR |
| 1020050077659 | Aug 2005 | KR |
| 1020080039330 | May 2008 | KR |
| WO0165827 | Sep 2001 | WO |
| 02084548 | Oct 2002 | WO |
| 2007070592 | Jun 2007 | WO |
| 2009128483 | Oct 2009 | WO |
| 2010111130 | Sep 2010 | WO |
| WO2010097711 | Sep 2010 | WO |
| WO2010111130 | Sep 2010 | WO |
| WO2010135174 | Nov 2010 | WO |
| 2013009891 | Jan 2013 | WO |
| Entry |
|---|
| “Reading magnetic cards (almost) for free” by Sébastien Bourdeauducq (“Lekernel”), posted on Jan. 26, 2009 at http://lekernel.net/blog/?p=12. |
| “MSR500EX (Mini123EX) Portable Magnetic Stripe Card Reader” by Tyner (“Tyner”), posted on Apr. 27, 2007 at http://www.tyner.com/magnetic/msr500ex.htm. |
| “Turning your mobile into a magnetic stripe reader” by Luis Padilla Visclornine (“Padilla I”), dated Aug. 30, 2004 El. |
| “Magnetic stripe reader circuit” (“Padilla II”) dated Jan. 28, 1997, Luis Padilla Visdómine. |
| “The simplest magnetic stripe reader”, posting from www.gae.ucm.esi˜padilla/extrawork/soundtrack.html dated Jan. 27, 2003, Luis Padilla Visd6mine. |
| “Travel industry targeted for Palm PDA card reader” http://www.m-travel.com/news/2001/08/travel—industry.html, dated Aug. 22, 2001. |
| “Semtek to target healthcare with HandEra PDAs and PDA swipe card reader”, http://www.pdacortex.com/semtek.htm, dated Aug. 29, 2001. |
| “Semtek 3913 Insert Magentic Card Reader 20 Pin Serial RS232” product description, RecycledGoods.com, Apr. 19, 2011. |
| “Credit Card Swiper and Reader for iPhone, iPad, Blackberry, Android and more”, http://hubpages.com/hub/Credit-Card-Swiper-and-Reader-for-iPhone-iPad-Blackberry-An . . . , accessed Apr. 20, 2011. |
| “ROAMpay is like Square for Blackberry (Plus Android, iOS and Desktops)” by John Paul Titlow, Dec. 1, 2010; http://www.readwriteweb.com/biz/2010/12/roampay-is-like-square-for-bla.php. |
| “Use a cellphone as a magnetic card reader”, Apr. 15, 2005, by Vince Veneziani, http://hackaday.com/2005/04/15/use-a-cellphone-as-a-magnetic-card . . . . |
| “Merchants eye mobile phones to transact card payments”, by Amy E. Buttell, Feb. 3, 2010, http://www.merchantaccountguide.com/merchant-account-news/cell-phone-credit-card-mer. |
| Online shopping page for “USB Magnetic Stripe Credit/Card Track-2 Reader and Writer (75/210BPI)”, Deal Extreme (dealextreme.com), Nov. 15, 2008. |
| Online shopping page for “Mophie Marketplace Magnetic Strip Reader/Case for iPhone 3G & 3GS—Grey”, J&R (JR. cam), accessed Feb. 8, 2011. |
| Online shopping page for “Barcode scanner and Magnetic Stripe Reader (MSR) for Pocke . . . ”, Tom's Hardware (tomshardware.com), accessed Feb. 8, 2011. |
| “A Magnetic Stripe Reader—Read Credit Cards & Driver Licences!”, Articlesbase (articlesbase.com), Sep. 7, 2009. |
| “U.S. Credit Cards to get a high-tech makeover”, by Roland Jones, Oct. 22, 2010, http://lifeinc.today.com/news/2010/10/22/5334208-us-credit-cards-to-get-a-high-tech-mak. |
| “Arduino magnetic stripe decoder”, Instructables, Feb. 8, 2011, http://www.instructables.com/id/Arduino-magnetic-stripe-decorder/. |
| Online shopping page for “Magnetic Stripe Reader (MSR) MSR7000-100R”, Motorola Solutions, accessed Feb. 8, 2011, http://www.motorola.com/business/US-EN/MSR7000-100R—US-EN.do?vgnextoid=164fc3 . . . . |
| Pay@PC, http://www.merchantanywhere.com/PAY—AT—PCT@PC.htm, accessed Feb. 11, 2011. |
| “Get paid on the spot from your mobile phone”, http://payments.intuit.com/products/basic-payment-solutions/mobile-credit-card-processin . . . , accessed Feb. 11, 2011. |
| “Touch-Pay Wireless Credit Card Processing”, MerchantSeek, http://www.merchantseek.com/wireless-credit-card-processing.htm, accessed Feb. 11, 2011. |
| “Announcement: Semtek Introduces Side Swipe II Card Reader for Wireless Devices”, Brighthand, http://forum.brighthand.com/pdas-handhelds/173285-announcement-semtek-introduces-sid . . . , accessed Apr. 19, 2011. |
| vTerminal Credit Card Processing App for AuthorizeNet and PayPal Payflow Pro for Curve 8350 8500 8900 and Bold 9000, by Dr. Knox Grandison; https://appworld.blackberry.com/webstore/content/3374, accessed Apr. 20, 2011. |
| “Magnetic Stripe Card Spoofer” by Adam Harris, Aug. 4, 2008, http://hackaday.com/2008/08/04/magnetic-stripe-card-spoofer/. |
| Website page snapshot for “Headphone Jack (3.5mm)”, http://www.phonescoop.com/glossary/term.php?gid=440, accessed May 5, 2011. |
| Website page snapshot for “2.5mm Headset Jack”, http://www.phonescoop.com/glossary/term.php?gid=360, accessed May 5, 2011. |
| “Reference Designations for Electrical and Electronics Parts and Equipment, Engineering Drawing and Related Documentation Practices”, The American Society of Mechanical Engineers, Nov. 21, 2008. |
| “Magstripe Interfacing—A Lost Art” by Acidus, http://www.scribd.com/doc/18236182/Magstripe-Interfacing#open—. . . , accessed Feb. 7, 2011. |
| “Mag-stripe readers the hunt for a homebrew mag-stripe reader that'll work with modern”, posted Jan. 21, 2009, http://www.hak5.org/forums/index.php?showtopic=11563&st=20 . |
| “Hijacking Power and Bandwidth from the Mobile Phone's Audio Interface”, Ye-Sheng Kuo, Sonal Verma, Thomas Schmid, and Prabal Dutta, Dec. 17, 2010. |
| Website: www.alexwinston.com, Aug. 31, 2009. |
| “Magnetic Card Reader”, accessed Apr. 25, 2011, http://lekernel.net/scrapbook/old/cardreader.html. |
| “Magnetic stripe reader/writer” http://www.gae.ucm.es/˜padilla/extrawork/stripe.html, Oct. 29, 1996. |
| Two-Pass Authenticated Encryption Faster than Generic Composition, S. Lucks, University of Mannheim, Germany; http://th/informatic-uni-mannheim/de/people/lucks/. |
| Comparing Block Cipher Modes of Operation on MICAz Sensor Nodes, G. Bauer et al., Institute for Applied Information Processing and Communications, Gran University of Technology. |
| English-language translation of Search Report for Japanese Patent Application No. 2013-533897, mailed Apr. 14, 2014. |
| Certificate of Design Registration for European Patent Application No. 002578674, mailed Nov. 14, 2014 (Registration No. 002578674-0001). |
| Notice of Allowance mailed Sep. 2, 2015, for U.S. Appl. No. 14/578,107, of Wade, J. et al., filed Dec. 19, 2014. |
| Notice of Allowance mailed Oct. 17, 2014, for U.S. Appl. No. 14/220,967, of Wade, J., et al., filed Mar. 20, 2014. |
| Notice of Allowance mailed Dec. 18, 2014, for U.S. Appl. No. 14/220,967, of Wade, J., et al., filed Mar. 20, 2014. |
| Notice of Allowance mailed May 19, 2015, for U.S. Appl. No. 14/620,765, of Wade, J., et al., filed Feb. 12, 2015. |
| Non-Final Office Action mailed May 26, 2015, for U.S. Appl. No. 14/551,681, of Wade, J., et al., filed Nov. 24, 2014. |
| Notice of Allowance mailed Jun. 10, 2014, for U.S. Appl. No. 29/491,147, of Templeton, T. et al., filed May 16, 2014. |
| Non-Final Office Action mailed Sep. 11, 2014, for U.S. Appl. No. 13/298,506, of Lamba, K., et al., filed Nov. 17, 2011. |
| Final Office Action mailed May 6, 2015, for U.S. Appl. No. 13/298,506, of Lamba, K., et al., filed Nov. 17, 2011. |
| Non-Final Office Action mailed Sep. 30, 2011, for U.S. Appl. No. 13/005,822, of McKelvey, J., et al., filed Jan. 13, 2011. |
| Notice of Allowance mailed Aug. 28, 2015, for U.S. Appl. No. 13/298,510, of Lamba, K., et al., filed Nov. 17, 2011. |
| Non-Final Office Action mailed Sep. 11, 2014, for U.S. Appl. No. 13/298,510, of Lamba, K., et al., filed Nov. 17, 2011. |
| Final Office Action mailed May 6, 2015, for U.S. Appl. No. 13/298,510, of Lamba, K., et al., filed Nov. 17, 2011. |
| Final Office Action mailed Jul. 9, 2012, for U.S. Appl. No. 13/005,822, of McKelvey, J., et al., filed Jan. 13, 2011. |
| Non-Final Office Action mailed Jun. 18, 2013, for U.S. Appl. No. 13/005,822, of McKelvey, J., et al., filed Jan. 13, 2011. |
| Non-Final Office Action mailed Dec. 10, 2013, for U.S. Appl. No. 13/005,822 of McKelvey, J., et al., filed Jan. 13, 2011. |
| Non-Final Office Action mailed Oct. 7, 2011, for U.S. Appl. No. 13/043,258, of McKelvey, J., filed Mar. 8, 2011. |
| Final Office Action mailed Jul. 13, 2012, for U.S. Appl. No. 13/043,258, of McKelvey, J., filed Mar. 8, 2011. |
| Non-Final Office Action mailed Dec. 11, 2013, for U.S. Appl. No. 13/043,258, of McKelvey, J., filed Mar. 8, 2011. |
| Notice of Allowance mailed Jul. 1, 2014, for U.S. Appl. No. 13/043,258, of McKelvey, J., filed Mar. 8, 2011. |
| Advisory Action mailed Aug. 15, 2012, for U.S. Appl. No. 13/043,258, of McKelvey, J., filed Mar. 8, 2011. |
| Advisory Action mailed Aug. 17, 2012, for U.S. Appl. No. 13/005,822, of McKelvey, J., et al., filed Jan. 13, 2011. |
| Notice of Allowance mailed Jun. 24, 2014, for U.S. Appl. No. 13/005,822, of McKelvey, J., et al., filed Jan. 13, 2011. |
| Non-Final Office Action mailed Oct. 7, 2014, for U.S. Appl. No. 13/298,534, of Lamba, K., et al., filed Nov. 17, 2011. |
| Final Office Action mailed Apr. 8, 2015, for U.S. Appl. No. 13/298,534, of Lamba, K., et al., filed Nov. 17, 2011. |
| Final Office Action mailed Sep. 6, 2013, for U.S. Appl. No. 13/298,560, of Lamba K. et al., filed Nov. 17, 2011. |
| Advisory Action mailed Oct. 21, 2013, for U.S. Appl. No. 13/298,560 of Lamba K. et al., filed Nov. 17, 2011. |
| Final Office Action mailed Aug. 15, 2013, for U.S. Appl. No. 13/043,263, of McKelvey, J., filed Mar. 8, 2011. |
| Advisory Action mailed Nov. 8, 2013, for U.S. Appl. No. 13/043,263, of McKelvey, J., filed Mar. 8, 2011. |
| Non-Final Office Action mailed Feb. 24, 2014, for U.S. Appl. No. 13/043,263, of McKelvey, J., filed Mar. 8, 2011. |
| Notice of Allowance mailed Jul. 15, 2014, for U.S. Appl. No. 13/043,263, of McKelvey, J., filed Mar. 8, 2011. |
| Non-Final Office Action mailed Jul. 22, 2014, for U.S. Appl. No. 13/298,560, of Lamba K. et al., filed Nov. 17, 2011. |
| Final Office Action mailed Jan. 28, 2015, for U.S. Appl. No. 13/298,560, of Lamba K. et al., filed Nov. 17, 2011. |
| Non-Final Office Action mailed Oct. 11, 2011, for U.S. Appl. No. 13/043,203, of McKelvey. J., et al., filed Mar. 8, 2011. |
| Final Office Action mailed Jul. 6, 2012, for U.S. Appl. No. 13/043,203, of McKelvey. J., et al., filed Mar. 8, 2011. |
| Non-Final office Action mailed Oct. 11, 2011, for U.S. Appl. No. 13/043,263, of McKelvey, J., filed Mar. 8, 2011. |
| Advisory Action mailed Aug. 1, 2012, for U.S. Appl. No. 13/043,203, of McKelvey, J., filed Mar. 8, 2011. |
| Advisory Action mailed Aug. 16, 2012, for U.S. Appl. No. 13/043,263, of McKelvey, J., filed Mar. 8, 2011. |
| Non-Final Office Action mailed Apr. 29, 2013, for U.S. Appl. No. 13/043,263, of McKelvey, J., filed Mar. 8, 2011. |
| Non-Final office Action mailed Apr. 30, 2013, for U.S. Appl. No. 13/043,203, of McKelvey, J., filed Mar. 8, 2011. |
| Non-Final Office Action mailed May 28, 2013, for U.S. Appl. No. 13/298,560, of Lamba K. et al., filed Nov. 17, 2011. |
| Notice of Allowance mailed Jul. 9, 2013, for U.S. Appl. No. 13/043,203, of McKelvey, J., filed Mar. 8, 2011. |
| Non-Final Office Action mailed Jul. 6, 2015, for U.S. Appl. No. 13/298,534, of Lamba K. et al., filed Nov. 17, 2011. |
| Advisory Action mailed Apr. 9, 2015, for U.S. Appl. No. 13/298,560, of Lamba K. et al., filed Nov. 17, 2011. |
| Final office Action mailed Jul. 9, 2012, for U.S. Appl. No. 13/043,263, of McKelvey, J., filed Mar. 8, 2011. |
| Non-Final Office Action mailed Jul. 16, 2015, for U.S. Appl. No. 13/298,560, of Lamba K. et al., filed Nov. 17, 2011. |
| Application for Registration of an Industrial Design Examiner's Report for Canadian Design Application No. 159528, mailed Jun. 11, 2015. |
| English-language translation of Notice of Reasons for Rejection for Japanese Application No. 2014-0255525, mailed Mar. 31, 2015. |
| Certificate of Registration of Design for Indian Design Application No. 267386 mailed Nov. 14, 2014 (Registration No. 39149). |
| Non-Final Office Action mailed Jul. 27, 2015, for U.S. Appl. No. 29/493,212, of Edwards, T., et al., filed Jun. 6, 2014. |
| English-language translation of Decision of Final Rejection for Japanese Patent Application No. 2013-533897, mailed Feb. 23, 2015. |
| English-language translation of Office Action for Japanese Patent Application No. 2013-533897, mailed Jun. 5, 2014. |
| Non-Final Office Action mailed Nov. 21, 2013, for U.S. Appl. No. 14/052,009, of Wilson, M., et al., filed Oct. 11, 2013. |
| Non-Final Office Action mailed Jul. 19, 2012, for U.S. Appl. No. 12/903,758, of Wilson, M., et al., filed Oct. 13, 2010. |
| European Search Report and Opinion for European Patent Application No. 11 786 731.7, mailed Mar. 28, 2014. |
| Office Action for European Patent Application No. 11 786 731.7, mailed Jul. 16, 2015. |
| Non-Final Office Action mailed Sep. 30, 2011, for U.S. Appl. No. 12/903,753, of McKelvey, J., et al., filed Oct. 13, 2010. |
| Final Office Action mailed Jul. 6, 2012, for U.S. Appl. No. 12/903,753, of McKelvey, J., et al., filed Oct. 13, 2010. |
| Non-Final Office Action mailed Jul. 8, 2013, for U.S. Appl. No. 12/903,753, of McKelvey, J., et al., filed Oct. 13, 2010. |
| Notice of Allowance mailed Oct. 10, 2013, for U.S. Appl. No. 12/903,753, of Mckelvey, J., filed Oct. 13, 2010. |
| Final Office Action mailed Apr. 24, 2013, for U.S. Appl. No. 12/903,758, of Wilson, M., et al., filed Oct. 13, 2010. |
| Notice of Allowance mailed Aug. 6, 2013, for U.S. Appl. No. 12/903,758, of Wilson, M., et al., filed Oct. 13, 2010. |
| Notice of Allowance mailed Apr. 4, 2014, for U.S. Appl. No. 14/052,009, of Wilson, M., et al., filed Oct. 11, 2013. |
| Notice of Allowance mailed Jul. 30, 2014, for U.S. Appl. No. 14/052,009, of Wilson, M., et al., filed Oct. 11, 2013. |
| Non-Final Office Action mailed Sep. 30, 2011, for U.S. Appl. No. 13/010,976, of Babu, A. R., et al., filed Jan. 21, 2011. |
| Final Office Action mailed Jun. 12, 2012, for U.S. Appl. No. 13/010,976, of Babu, A. R., et al., filed Jan. 21, 2011. |
| Advisory Action mailed Aug. 24, 2012, for U.S. Appl. No. 13/010,976, of Babu, A. R., et al., filed Jan. 21, 2011. |
| Non-Final Office Action mailed Aug. 15, 2014, for U.S. Appl. No. 13/010,976, of Babu, A. R., et al., filed Jan. 21, 2011. |
| Notice of Allowance mailed Dec. 24, 2014, for U.S. Appl. No. 13/010,976, of Babu, A. R., et al., filed Jan. 21, 2011. |
| Non-Final Office Action mailed Apr. 2, 2014, for U.S. Appl. No. 14/012,655, of McKelvey, J., filed Aug. 28, 2013. |
| Final Office Action mailed Aug. 15, 2014, for U.S. Appl. No. 14/012,655, of McKelvey, J., filed Aug. 28, 2013. |
| Non-Final Office Action mailed Jan. 20, 2015, for U.S. Appl. No. 14/012,655, of McKelvey, J., filed Aug. 28, 2013. |
| Notice of Allowance mailed Sep. 1, 2015, for U.S. Appl. No. 13/298,487, of Babu, A., et al., filed Nov. 17, 2011. |
| Non-Final Office Action mailed Apr. 29, 2013, for U.S. Appl. No. 13/298,487, of Babu, A., et al., filed Nov. 17, 2011. |
| Final Office Action mailed Aug. 22, 2013, for U.S. Appl. No. 13/298,487, of Babu, A., et al., filed Nov. 17, 2011. |
| Advisory Action mailed Oct. 22, 2013, for U.S. Appl. No. 13/298,487, of Babu, A., et al., filed Nov. 17, 2011. |
| Non-Final Office Action mailed Aug. 21, 2014, for U.S. Appl. No. 13/298,487, of Babu, A., et al., filed Nov. 17, 2011. |
| Final Office Action mailed Mar. 18, 2015, for U.S. Appl. No. 13/298,487, of Babu, A., et al., filed Nov. 17, 2011. |
| Non-Final Office Action mailed Feb. 20, 2015, for U.S. Appl. No. 14/512,104, of Templeton, T., et al., filed Oct. 10, 2014. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2010/052483, mailed Jun. 10, 2011. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2011/055386, mailed Feb. 22, 2012. |
| European Search Report and Opinion for European Application No. 11833172.7, mailed Apr. 22, 2014. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2014/069788, mailed May 14, 2015. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2012/064782, mailed Feb. 26, 2013. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2010/052481, mailed Jun. 23, 2011. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2014/067074, mailed Mar. 15, 2015. |
| Examination Report for Canadian Application No. 2,812,594, mailed on Feb. 24, 2015. |
| Examination Report No. 1 for Australian Application No. 201415781, mailed on Feb. 23, 2015 (Registration No. 359005). |
| “Review: Square, Inc. Square Credit Card Reader (2013),” iLounge, Retrieved from the Internet URL: http://www.ilounge.com/index.php/reviews/entry/square-inc.-square-credit-card-reader-2013/, on Jan. 16, 2014, pp. 3. |
| “TUAW The Unofficial Apple Weblog, Square credit card reader loses weight, gains accuracy”, Retrieved from the Internet URL: http://www.tuaw.com/2013/12/09/square-credit-card-reader-loses-weight-gains-accuracy/, on Dec. 9, 2013, p. 1. |
| Examination Report No. 2 for Australian Application No. 201415781, mailed Aug. 13, 2015 (Registration No. 359005). |
| Ryan, P., “Plug and Pay: A Gallery of 26 Mobile Card Readers,” Aug. 20, 2013, Retrieved from the Internet URL: http://bankinnovation.net/2013/08/plug-and-pay-a-gallery-of-26-mobile-card-readers/, on Feb. 19, 2015, pp. 1-12. |
| Notification of Registration of a Design for Australian Application No. 201415781, mailed on Nov. 27, 2014 (Registration No. 359005). |
| First Examination Report for Indian Design Application No. 267386, mailed Feb. 5, 2015. |
| Non-Final Office Action mailed Jun. 6, 2014, for U.S. Appl. No. 14/231,598, of Wade, J., et al., filed Mar. 31, 2014. |
| Non-Final Office Action mailed Apr. 10, 2015, for U.S. Appl. No. 14/189,997, of Lamfalusi, M., et al., filed Feb. 25, 2014. |
| Notice of Allowance mailed Nov. 25, 2014, for U.S. Appl. No. 14/231,598, of Claude, J. B., et al., filed Mar. 31, 2014. |
| Non-Final Office Action mailed Jun. 22, 2015, for U.S. Appl. No. 14/322,815, of Edwards, T., filed Jul. 2, 2014. |
| Notice of Allowance mailed Aug. 1, 2014 for U.S. Appl. No. 14/203,463, of Wade, J., et al., filed Mar. 10, 2014. |
| Notice of Allowance mailed Aug. 27, 2015, for U.S. Appl. No. 13/298,501, of Babu, A., et al., filed Nov. 17, 2011. |
| Non-Final Office Action mailed Sep. 11, 2014, for U.S. Appl. No. 13/298,501, of Babu, A., et al., filed Nov. 17, 2011. |
| Final Office Action mailed May 6, 2015, for U.S. Appl. No. 13/298,501, of Babu, A., et al., filed Nov. 17, 2011. |
| Advisory Action mailed Sep. 11, 2015 for U.S. Appl. No. 13/298,506, of Lamba, K., et al., filed Nov. 17, 2011. |
| Notice of Allowance mailed Sep. 16, 2015 for U.S. Appl. No. 14/551,681, of Wade, J., et al., filed Nov. 24, 2014. |
| Notice of Allowance mailed Oct. 5, 2015 for U.S. Appl. No. 14/322,815, of Edwards, T., filed Jul. 2, 2014. |
| Notice of Allowance mailed Oct. 7, 2015 for U.S. Appl. No. 13/298,510, of Lamba, K., et al., filed Nov. 17, 2011. |
| Notice of Allowance mailed Oct. 8, 2015 for U.S. Appl. No. 13/298,487, of Lamba, K., et al., filed Nov. 17, 2011. |
| Notice of Allowance mailed Oct. 13, 2015 for U.S. Appl. No. 14/578,107, of Wade, J., et al., filed Dec. 19, 2014. |
| Non-Final Office Action mailed Oct. 29, 2015 for U.S. Appl. No. 14/512,104, of Templeton, T., et al., filed Oct. 10, 2014. |
| Number | Date | Country | |
|---|---|---|---|
| 20120126011 A1 | May 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60355667 | Feb 2002 | US | |
| 60356861 | Feb 2002 | US | |
| 60361646 | Mar 2002 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13179836 | Jul 2011 | US |
| Child | 13192147 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12050752 | Mar 2008 | US |
| Child | 12707228 | US | |
| Parent | 10355557 | Jan 2003 | US |
| Child | 12050752 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13192147 | Jul 2011 | US |
| Child | 13298491 | US | |
| Parent | 12707228 | Feb 2010 | US |
| Child | 13179836 | US |
