Consumers can interact with merchants to conduct various financial payment transactions. For example, a consumer can conduct a transaction with a merchant at a point-of-sale system using cash, a transaction card, or other transaction instrument. Conventional systems can include expensive and bulky financial transaction electronics, as may include a card reader for payment cards (e.g., debit or credit cards), a cash drawer, monitors, keyboards, and various other electronic devices. Some point-of-sale systems require multiple types of card readers and/or complex and bulky card-reading equipment in order to accept multiple types of payment cards. Some systems include a card reader that is inserted into a port, such as the audio jack, of a mobile device to read data off a payment card and provide the information to the mobile device.
In order to describe the manner in which features of the disclosure can be obtained, a more particular description of the principles will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. Understanding that these drawings depict only exemplary embodiments of the disclosure and are not therefore to be considered to be limiting of its scope, the principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings in which:
Systems and methods in accordance with various embodiments of the present disclosure overcome one or more of the above-referenced and other deficiencies in conventional approaches to conducting financial transactions. In particular, in accordance with various embodiments, approaches provide for a card reader that is used in performing a payment transaction at a point-of-sale system.
The card reader includes an audio jack configured to be inserted into an audio jack of a mobile device, a slot for receiving a payment card, a media reading device for reading information off the payment card and a wake up circuit.
The wake up circuit includes a conditioning circuit, a comparator and an envelope detector. The conditioning circuit comprises a capacitor coupled to an audio input of the audio jack of the mobile device, and two evenly valued resistors coupled to a microphone bias signal, whereby the capacitor is configured to block any DC component on the audio input and whereby the two evenly valued resistors are configured to bias the microphone bias signal to a biased input voltage. The comparator has a positive terminal and a negative terminal, the positive terminal of the comparator being coupled to the audio input, and the negative terminal being coupled to the biased input voltage, whereby the comparator is configured to output a signal whenever the voltage on the positive terminal is greater than the voltage on the negative terminal. The envelope detector is connected to the output of the comparator, the output of the comparator being a square wave, the envelope detector configured to convert the square wave to a DC voltage signal and provide the DC voltage signal to a voltage regulator connected to the output of the envelope detector.
In some implementations, the card reader is able to detect a rising edge of the microphone bias voltage associated with plugging in the card reader to a mobile device and will turn on accordingly. However, the card reader typically has software that instructs the microcontroller of the card reader to shut the card reader off at appropriate times (for example, after a certain amount of time of non-use). Thus, a problem arises in situations where a card reader is left plugged into a mobile device after it is powered down by the microcontroller as the microphone bias will not change. It is thus desirable to have a means which turn the card reader back on when it is ready to be used again. One possible approach to achieving this goal is to monitor the read head to turn the card reader on in response to a card swipe. However, this monitoring circuitry drains the internal battery of the card reader. With this in mind, embodiments of the present invention propose a solution to turning on the card reader without consuming the battery power of the card reader and without the need to disconnect and reconnect the card reader (i.e. the microphone bias remains present and unchanged). This solution comes in the form of a tone or audio signal, for example provided by the mobile device to which the card reader is connected, which wakes up the card reader using the wake up circuit. Advantageously, such a card reader provides its own ability to turn on and turn off as desired without consuming the internal battery.
Although the system of the present invention is designed so that a user does not necessarily hear the wake up tone, certain situations exist where the tone may be played back to a user, e.g., a user plugs in headphones instead of the card reader, or the user uses headphones in conjunction with the card reader via a Y-splitter inserted into an audio jack of a mobile device. With this in mind, it is desired to provide a tone that is both audibly pleasing to the user and capable of triggering the wake up circuit to wake up the card reader. One example of such a tone is a chime which begins at a lower frequency and ramps or steps up to a higher frequency. By varying the frequency, the probability that a mobile device is capable of transmitting at least a portion of the tone to wake up the card reader is greatly increased.
Other advantages, variations, and functions are described and suggested below as may be provided in accordance with the various embodiments.
After conditioning via conditioning circuit 104, the audio input and the biased input voltage are received by the positive and negative input terminals of comparator 106, respectively. From here, comparator 106 is configured to compare the two signals and output a logical high value whenever the voltage on the positive input terminal is greater than the voltage on the negative input terminal. Due to the AC audio input at the positive input terminal of comparator 106, the output of comparator 106 is typically a square wave signal. Given that this square wave output signal oscillates at the same frequency as audio input 100, it is necessary to ensure the output of comparator 106 is asserted long enough for the wake up circuit to react regardless of the frequency of audio input 100. For example, if a single high-pitched wake up tone with a frequency of 20 kHz were received by the wake up circuit from audio input 100, the resultant square wave output signal of comparator 106 would have an “on time”, or a period of time where the output value is logical high, of 25 μs per period. Depending on the components used in the card reader, this may not be enough time for the wake up circuit to recognize the wake up tone and turn the card reader on. With this in mind, envelope detector 108 is configured to monitor the output of comparator 106 and convert the square wave output signal into a substantially DC voltage signal. The DC voltage signal output from envelope detector 108 is directly coupled to a voltage regulator enable pin 110 that allows a voltage regulator to provide power to the portable card reader in response to a wake up tone.
Reference is now made to
Conditioning circuit 204 also creates a biased input voltage at the negative input terminal of comparator 212 by biasing the input voltage (Vcc) provided by microphone bias 202 using biasing resistors 208A and 208B. In an embodiment, biasing resistors 208A and 208B are of the same value so that the DC voltage level of the biased input voltage is substantially in the middle of a range from Vcc to ground. Conditioning circuit 204 also includes a coupling resistor 210 having a large value, which weakly couples the AC audio input signal to the biased input voltage created by biasing resistors 208A and 208B. In doing so, coupling resistor 210 sets a DC voltage level on the audio input signal at the positive input terminal of comparator 212 that is substantially the same value as the DC voltage level of the biased input voltage at the negative input terminal of comparator 212. This ensures that the audio input signal at the positive input terminal of comparator 212 stays within a range from Vcc to ground.
Once the two signals have been conditioned, comparator 212 compares the audio input signal on the positive input terminal with the biased input voltage on the negative input terminal. If comparator 212 determines that the value of the audio input signal is greater than the value of the biased input voltage, comparator 212 is configured to output a logical high value. As discussed in reference to
Referring now to
Biasing resistors 308A and 308B can be two evenly valued resistors, for example, of approximately 499 k ohms that bias the input voltage received by microphone bias 302 to create a biased input voltage at the negative input terminal of comparator 312. DC blocking capacitor 306, which may be approximately 1000 pF, serves to remove any DC component from the audio input signal of left audio channel 300A. Equivalent capacitor 340, which is the same value as DC blocking capacitor 306, is coupled to right audio channel 300B to provide load symmetry between both audio channels. A coupling resistor 310 with a value of approximately 499 k ohms weakly couples the biased input voltage created by biasing resistors 308A and 308B to the conditioned left audio channel 300A. In doing so, coupling resistor 310 re-establishes the DC voltage level of the conditioned left audio channel 300A to a value that is substantially the same as the DC voltage level of the biased input voltage. This ensures that the conditioned audio input signal at the positive input terminal of comparator 312 remains within the comparator's acceptable voltage range.
Comparator 312 is a rail-to-rail input comparator capable of operation on low supply voltages. In an embodiment, one rail of comparator 312 is coupled to the input voltage (Vcc) received from microphone bias 302, and the other rail is coupled to a low impedance ground. Comparator 312 is configured to compare the voltage of the audio input signal on the positive input terminal with the biased input voltage on the negative input terminal. If comparator 312 determines that the voltage present on the positive input terminal is greater than the voltage on the negative input terminal, comparator 312 is configured to output a logical high value that is substantially the same value as the input voltage received from microphone bias 302. In doing so, comparator 312 effectively amplifies the low voltage audio input signal to a DC voltage substantially the same as microphone bias 302.
When a tone-based wake up signal is received by the wake up circuit, comparator 312 typically produces a square wave at its output due to the AC component of the audio input signal. Envelope detector 314 serves to convert this square wave signal into a substantially DC signal that is asserted long enough for the wake up circuit to power on the card reader in response to a wake up tone. To do so, envelope detector 314 employs both a diode 316 and a capacitor 318, wherein the anode of capacitor 318 is directly coupled to a voltage regulator enable pin 324 of a voltage regulator 322. In an embodiment diode 316 can be a Schottky diode with a low voltage drop to minimize the energy lost from the comparator's output signal. Diode 316 must also be capable of fast switching speeds to keep up with potential high frequency wake up tones. Upon receipt of a logical high value from the output of comparator 312, diode 316 begins to conduct. While diode 316 is in a conduction state, capacitor 318, which may be approximately 1000 pF, stores charge. When the square wave output from comparator 312 transitions to a logical low state such as ground, diode 316 stops conducting and capacitor 318 begins discharging its stored charged through resistor 320. However, resistor 320 is chosen to be a large value, such as 499 k ohms, so that capacitor 318 does not discharge too quickly between subsequent pulses of the square wave output. In this manner, the voltage level of capacitor 318 does not drop below the voltage level required to enable voltage regulator 322 via voltage regulator enable pin 324 throughout the entire duration of the wake up tone.
Once a wake up tone has triggered the wake up circuit to enable voltage regulator 322, a portable card reader and its associated controller (not shown) can be powered on from a low power sleep mode via main voltage 326. In doing so, the wake up signal on voltage regulator enable pin 324 signals the controller to wake up via main voltage 326 provided by voltage regulator 322. In other embodiments, the wake up signal of voltage regulator enable pin 324 may be directly coupled to both voltage regulator enable pin 324 and the controller of the card reader. From here, the controller of the card reader can latch voltage regulator 322 on by outputting a logical high value on input 328. This allows the controller of the card reader to keep voltage regulator 322 on without the presence of a wake up tone. The controller can also assert a logical low value on input 328 to shutdown voltage regulator 322 and return the card reader to a low power sleep mode. To prevent comparator 312 from causing power supply noise, the controller is also configured to set input 330 to a logical low value (i.e. ground). Additionally, the controller sets input 342 to ground so that an equivalent load is seen by both audio input channels.
In order to provide regulated voltage to the card reader via main voltage 326, voltage regulator 322 sources power from either a battery 332 or a USB charger 334 of the card reader. In scenarios where USB charger 334 is connected, a switch, such as P-channel MOSFET 336 of the present embodiment, can be used to disconnect battery 332. Doing so saves power on battery 332 for situations when USB charger 334 is not connected.
As previously discussed, the tone-based wake up circuit of the present invention is configured to power on a portable card reader in response to a wake up tone by enabling voltage regulator 322 via voltage regulator enable pin 324. However, in certain embodiments, other events aside from a wake up tone can trigger the wake up circuit to power on the card reader. For example, when a user inserts the portable card reader into an audio output port of a computing device running point of sale software, it is desirable to have the card reader powered on for immediate use. As such, the present embodiment includes diode 336 directly coupled to microphone bias 302 and a passive differentiator circuit formed by DC blocking capacitor 344 and resistor 320. When the card reader is plugged in, the voltage of microphone bias 302 allows diode 336 to turn on. The rising edge of microphone bias 302 associated with inserting the card reader causes the passive differentiator circuit to output a logical high value at voltage regulator enable pin 324. From here, the controller of the card reader can latch voltage regulator 322 on by outputting a logical high value on input 328 before DC blocking capacitor 344 discharges. Since microphone bias 302 is a substantially constant DC voltage, the output of the passive differentiator circuit which differentiates the signal from microphone bias 302 discharges to a logical low value after insertion of the card reader. This prevents the microphone bias signal coming through diode 336 from always asserting a logical high value at voltage regulator enable pin 324, but still allows the wake up circuit to power on the card reader when the card reader is plugged in. Additionally, this configuration allows the controller of the card reader to transition the card reader from an awake mode to a sleep mode while the microphone bias signal is still present by outputting a logical low value on input 328. In scenarios where USB charger 334 is connected, the power saving features inherent to the tone-based wake up circuit may no longer be necessary, and the card reader can remain in a powered on state. With this in mind, the voltage received from USB charger 334 is biased using resistors 338A and 338B to provide a DC signal to voltage regulator enable pin 324.
Having now described various example embodiments of the point-of-sale system used in a point-of-sale transaction, some example environments for conducting a financial transaction at a point-of-sale system will now be described. Other environments and applications of the point-of-sale system should be apparent to those ordinarily skilled in the art.
As described, the point-of-sale systems 510 and 511 can include the hub (e.g., hub 204) and computing device, where the computing device can be coupled to or in communication with the merchant payment system through a data communication network 508, e.g., the Internet. These devices each generally include a memory, e.g., a random access memory (RAM), for storing instructions and data, and a processor for executing stored instructions. The devices and can each include one or more components, e.g., software or hardware, that are operable to send and receive requests, messages, or other types of information over the network. Some examples of computing devices include personal computers, cellular phones, handheld messaging devices, laptop computers, personal data assistants, tablet devices, and the like.
The network 508 can include any appropriate network, including an intranet, the Internet, a cellular network, a local area network, a wide area network, or any other such network, or combination thereof. Components used for such a system can depend at least in part upon the type of network, the environment selected, or both. Protocols and components for communicating over such a network are well known and will not be discussed herein in detail. The devices and the referral system can communicate over the network using wired or wireless connections, and combinations thereof.
Each of the computing devices is configured to send to the merchant payment system respective financial data that corresponds to a financial transaction that was processed by the computing device. The financial data can include, for example, data stored in a financial payment card, e.g., Track 1 data, receipt email addresses, and information describing a card-less payment account. Other examples of financial data that can be captured includes purchase data, e.g., an itemized listing of purchases, card mix data, geolocation data indicating a geographic location of a particular transaction, online/offline card data, data describing the merchant, e.g., merchant category codes (MCCs), and any type of data that is received upon a customer's authentication into a social network.
The user device and the merchant device can each be a computer coupled to the payment system through a data communication network 650, e.g., the Internet. The user device and the merchant device each generally include a memory, e.g., a random access memory (RAM), for storing instructions and data, and a processor for executing stored instructions. The user device and the merchant device can each include one or more components, e.g., software or hardware, that are configured to respectively determine a geographic location of the user device or the merchant device, using, for example, various geolocation techniques, e.g., a global positioning system (GPS). Further, the user device and the merchant device can each be any appropriate device operable to send and receive requests, messages, or other types of information over the network. Some examples of user devices include personal computers, cellular phones, handheld messaging devices, laptop computers, personal data assistants, tablet devices, and the like.
The network can include any appropriate network, including an intranet, the Internet, a cellular network, a local area network, a wide area network, or any other such network, or combination thereof. Components used for such a system can depend at least in part upon the type of network, the environment selected, or both. Protocols and components for communicating over such a network are well known and will not be discussed herein in detail. The payment system, the merchant device, and the user device can communicate over the network using wired or wireless connections, and combinations thereof.
As used in this specification, a financial transaction is a transaction that is conducted between a customer and a merchant at a point-of-sale. When paying for a financial transaction, the customer can provide the merchant with cash, a check, or credit card for the amount that is due. The merchant can interact with a point-of-sale device, e.g., merchant device, to process the financial transaction. During financial transactions, the point-of-sale device can collect data describing the financial transaction, including, for example, the amount of payment received from customers.
In some implementations, the payment system is configured to accept card-less payment transactions from customers, e.g., the customer. As used in this specification, a card-less payment transaction is a transaction conducted between the customer and a merchant at the point-of-sale during which a financial account of the customer is charged without the customer having to physically present a financial payment card to the merchant at the point-of-sale. That is, the merchant need not receive any details about the financial account, e.g., the credit card issuer or credit card number, for the transaction to be processed.
Before conducting card-less payment transactions, the customer typically creates a user account with the payment system. The customer can create the user account, for example, by interacting with a user application that is configured to perform card-less payment transactions and that is running on the user device. When creating a user account with the payment system, the customer will provide information of the customer, data describing a financial account of the customer, e.g., credit card number, expiration date, and a billing address. This user information can be securely stored by the payment system, for example, in a user information database. To accept card-less payment transactions, the merchant typically creates a merchant account with the payment system by providing information describing the merchant including, for example, a merchant name, contact information, e.g., telephone numbers, the merchant's geographic location address, and one or more financial accounts to which funds collected from users will be deposited. This merchant information can be securely stored by the payment system, for example, in a merchant information database.
The payment system is configured to perform card-less payment transactions. The payment system can include one or more servers that are configured to securely perform electronic financial transactions, e.g., electronic payment transactions, between a customer and a merchant, for example, through data communicated between the user device and the merchant device. Generally, when a customer and a merchant enter into an electronic financial transaction, the transaction is processed by transferring funds from a financial account associated with the user account to a financial account associated with the merchant account.
The payment system is configured to send and receive data to and from the user device and the merchant device. For example, the payment system can be configured to send data describing merchants to the user device using, for example, the information stored in the merchant information database 612. For example, the payment system can communicate data describing merchants that are within a threshold geographic distance from a geographic location of the user device, as described in this specification. The data describing merchants can include, for example, a merchant name, geographic location, contact information, and an electronic catalogue, e.g., a menu that describes items that are available for purchase from the merchant.
In some embodiments, the payment system is configured to determine whether a geographic location of the user device is within a threshold geographic distance from a geographic location of the merchant device. The payment system can determine a geographic location of the user device using, for example, geolocation data provided by the user device. Similarly, the payment system can determine a geographic location of the merchant device using, for example, geolocation data provided by the merchant device or using a geographic address, e.g., street address, provided by the merchant. Depending on the implementation, the threshold geographic distance can be specified by the payment system or by the merchant.
Determining whether the user device is within a threshold geographic distance of the merchant device can be accomplished in different ways including, for example, determining whether the user device is within a threshold geographic radius of the merchant device, determining whether the user device is within a particular geofence, or determining whether the user device can communicate with the merchant device using a specified wireless technology, e.g., Bluetooth or Bluetooth low energy (BLE). In some embodiments, the payment system restricts card-less payment transactions between the customer and the merchant to situations where the geographic location of the user device is within a threshold geographic distance from a geographic location of the merchant device.
The payment system can also be configured to communicate with a computer system 616 of a card payment network, e.g., Visa or MasterCard, over the network, or over a different network, for example, to conduct electronic financial transactions. The computer system 616 of the card payment network can communicate with a computer system 618 of a card issuer, e.g., a bank. There may be computer systems of other entities, e.g., the card acquirer, between the payment system and the computer system 618 of the card issuer.
The customer operating the user device that is within a threshold geographic distance of the merchant can interact with a user application running on the user device to conduct a card-less payment transaction with the merchant. While interacting with the user application, the customer can select the merchant, from a listing of merchants, with whom the customer wants to enter into a card-less payment transaction. The user can select the merchant, for example, by selecting a “check in” option associated with the merchant. The user device can communicate data to the payment system indicating that the customer has checked in with the merchant. In response, the payment system can communicate data to notify the merchant device that the user has checked in. A merchant application running on the merchant device can notify the merchant that the user has electronically checked in with the merchant through a display screen of the merchant device.
Once checked in, the customer can collect, or request, items that are available for purchase from the merchant. When the customer is ready to enter into the card-less payment transaction, the customer can, for example, approach a point-of-sale for the merchant and identify him or herself. For example, the customer can verbally notify the merchant that the customer wants to enter into a card-less payment transaction and can provide the merchant with the customer's name. The merchant can then interact with the merchant application to select the customer, from a listing of customers that have checked in with the merchant, to initiate a card-less payment transaction for the items being purchased by the customer. For example, the merchant can determine a total amount to bill the customer for the items being purchased. The customer can verbally approve the total amount to be billed and, in response, the merchant can submit a request for a card-less payment transaction for the total amount to the payment system. In response, the payment system can obtain, for example, from the user information database, data describing a financial account associated with a user account of the customer to which the total amount will be billed.
The payment system can then communicate with the computer system of a card payment network to complete an electronic financial transaction for the total amount to be billed to the customer's financial account. Once the electronic financial transaction is complete, the payment system can communicate data describing the card-less payment transaction to the user device, e.g., an electronic receipt, which can, for example, notify the customer of the total amount billed to the user for the card-less payment transaction with the particular merchant.
For clarity of explanation, in some instances the present technology may be presented as including individual functional blocks including functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.
In some embodiments the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.
Methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media. Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.
Devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include laptops, smart phones, small form factor personal computers, personal digital assistants, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.
The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures.
Although a variety of examples and other information was used to explain aspects within the scope of the appended claims, no limitation of the claims should be implied based on particular features or arrangements in such examples, as one of ordinary skill would be able to use these examples to derive a wide variety of implementations. Further and although some subject matter may have been described in language specific to examples of structural features and/or method steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or acts. For example, such functionality can be distributed differently or performed in components other than those identified herein. Rather, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
3854036 | Gupta et al. | 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, III 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 |
5907801 | Albert et al. | May 1999 | A |
5945654 | Huang | Aug 1999 | A |
5991410 | Albert et al. | Nov 1999 | A |
5991749 | Morrill, Jr. | Nov 1999 | A |
D417442 | Butts et al. | Dec 1999 | S |
6006109 | Shin | Dec 1999 | A |
6010067 | Elbaum | Jan 2000 | A |
6021944 | Arakaki | Feb 2000 | A |
6032859 | Muehlberger 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 | Fujll | 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 |
D590828 | Sherrod et al. | Apr 2009 | S |
7520430 | Stewart et al. | Apr 2009 | B1 |
7581678 | Narendra et al. | Sep 2009 | B2 |
7600673 | Stoutenberg 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, Jr. | Apr 2011 | B1 |
7945494 | Williams | May 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 |
8584956 | Wilson et al. | 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 |
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 et al. | 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 | Krouse 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 et al. | Jul 2005 | A1 |
20050194452 | Nordentoft et al. | Sep 2005 | A1 |
20050209719 | Beckert et al. | Sep 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 |
20060049256 | Von Mueller et al. | Mar 2006 | A1 |
20060094481 | Gullickson | May 2006 | A1 |
20060122902 | Petrov 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 |
20070287498 | Wang et al. | Dec 2007 | 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 | Lane | 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 |
20100127857 | Kilmurray et al. | May 2010 | A1 |
20100184479 | Griffin, Jr. | 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 |
20110033910 | Maho et al. | Feb 2011 | A1 |
20110053560 | Jain et al. | Mar 2011 | A1 |
20110084131 | McKelvey | Apr 2011 | A1 |
20110084139 | McKelvey 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 |
20110191196 | Orr et al. | Aug 2011 | A1 |
20110198395 | Chen | Aug 2011 | A1 |
20110202463 | Powell | Aug 2011 | A1 |
20110258120 | Weiss | Oct 2011 | A1 |
20110313880 | Paul et al. | Dec 2011 | A1 |
20120008851 | Pennock 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 |
20120095867 | 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 et al. | 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 et al. | 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 |
20120293001 | Chan | Nov 2012 | A1 |
20130021046 | Prentice | Jan 2013 | A1 |
20130031004 | Dorsey et al. | Jan 2013 | A1 |
20130087614 | Limtao et al. | Apr 2013 | A1 |
20130137367 | Fisher | May 2013 | A1 |
20130200153 | Dorsey et al. | Aug 2013 | A1 |
20130207481 | Gobburu et al. | Aug 2013 | A1 |
20130254117 | von Mueller et al. | Sep 2013 | A1 |
20130290762 | Pawar | Oct 2013 | A1 |
20130304244 | Ojanpera | Nov 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 et al. | May 2014 | A1 |
20140131442 | Morrow et al. | May 2014 | A1 |
20140144983 | Dorsey et al. | May 2014 | A1 |
20140203082 | Huh | Jul 2014 | A1 |
20140258132 | Swamy | Sep 2014 | A1 |
20140295761 | Lo | Oct 2014 | A1 |
20150078560 | Ilango | Mar 2015 | 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 |
302341093 | Mar 2013 | CN |
302526592 | Aug 2013 | CN |
1 145 766 | Oct 2001 | EP |
2003-108777 | Apr 2003 | JP |
2004-078662 | Mar 2004 | JP |
2005-063869 | Mar 2005 | JP |
2005-242550 | Sep 2005 | JP |
2005-269172 | Sep 2005 | JP |
2009-199649 | Sep 2009 | JP |
2001-313714 | Nov 2011 | JP |
2013-518344 | May 2013 | JP |
10-0452161 | Oct 2004 | KR |
10-2005-0077659 | Aug 2005 | KR |
10-2008-0039330 | May 2008 | KR |
0165827 | Sep 2001 | WO |
02084548 | Oct 2002 | WO |
2007070592 | Jun 2007 | WO |
2009128483 | Oct 2009 | WO |
2010097711 | Sep 2010 | WO |
2010111130 | Sep 2010 | WO |
2010135174 | Nov 2010 | WO |
2011047028 | Apr 2011 | WO |
2011047030 | Apr 2011 | WO |
2012051070 | Apr 2012 | WO |
2013009891 | Jan 2013 | WO |
2013074499 | May 2013 | WO |
2015081002 | Jun 2015 | WO |
2015089301 | Jun 2015 | WO |
Entry |
---|
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/review/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 Apr. 25, 2013, for U.S. Appl. No. 13/298,491, of Lamba, K., et al., filed Nov. 17, 2011. |
Final Office Action mailed Sep. 17, 2013, for U.S. Appl. No. 13/298,491, of Lamba, K. et al., filed Nov. 17, 2011. |
Advisory Action mailed Oct. 22, 2013, for U.S. Appl. No. 13/298,491, of Lamba, K., et al., filed Nov. 17, 2011. |
Non-Final Office Action mailed Jul. 17, 2014, for U.S. Appl. No. 13/298,491, of Lamba, K., et al., filed Nov. 17, 2011. |
Final Office Action mailed Feb. 4, 2015, for U.S. Appl. No. 13/298,491, of Lamba, K., et al., filed Nov. 17, 2011. |
Notice of Allowance mailed Jun. 22, 2015, for U.S. Appl. No. 13/298,491, of Lamba, K., et al., filed Nov. 17, 2011. |
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. |
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. |
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. |
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. 6, 2015 for U.S. Appl. No. 13/298,491, of Lamba, K., et al., filed Nov. 17, 2011. |
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. |
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. |
“Reading magnetic cards (almost) for free,” Lekernel's Scrapbook, (“Lekernel”), Jan. 26, 2009, Retrieved from the Internet URL: http://lekernel.net/blog/?p=12, on May 5, 2011, pp. 1-2. |
“MSR500EX (Mini123EX) Portable Magnetic Stripe Card Reader,” Tyner, Apr. 27, 2007, Retrieved from the Internet URL: http://www.tyner.com/magnetic/msr500ex.htm, on Apr. 22, 2011, pp. 1-3. |
Padilla, L., “Turning your mobile into a magnetic stripe reader,” Retrieved from the Internet URL: http://www.gae.ucm.es/˜padilla/extrawork/mobilesoundtrack.html, on Feb. 7, 2011, pp. 1-4. |
Padilla, L., “Magnetic stripe reader circuit,” Jan. 28, 1997, Retrieved from the Internet URL: http://www.gae.ucm.es/˜padilla/extraworklmagamp.html, on May 5, 2011, pp. 1-7. |
Padilla, L. “The simplest magnetic stripe reader,” Jan. 27, 2003, Retrieved from the Internet URL: www.gae.ucm.esi˜padilla/extrawork/soundtrack.html, on Dec. 21, 2009, pp. 1-5. |
“Travel industry targeted for Palm PDA card reader,” Retrieved from the Internet URL: http://www.m-travel.com/news/2001/08/travel—industry.html, on Apr. 19, 2011, pp. 1-2. |
“Semtek to target healthcare with HandEra PDAs and PDA swipe card reader,” Aug. 29, 2001, Retrieved from the Internet URL: http://www.pdacortex.com/semtek.htm, on Apr. 19, 2011, pp. 1-2. |
“Semtek 3913 Insert Magnetic Card Reader 20 Pin Serial RS232,” Product description, RecycledGoods.com, Retrieved from the Internet URL: http://www.recycledgoods.com/products/Semtek-3913-Insert-Magnetic-Card-Reader-20-Pi . . . , on Apr. 19, 2011, pp. 1-3. |
“Credit Card Swiper and Reader for iPhone, iPad, Blackberry, Android and more,” Retrieved from the Internet URL: http://hubpages.com/hub/Credit-Card-Swiper-and-Reader-for-iPhone-iPad-Blackberry-An . . . , on Apr. 20, 2011, pp. 1-2. |
Titlow, J.P., “Roam pay is like Square for Blackberry (Plus Android, iOS and Desktops),” Dec. 1, 2010, Retrieved from the Internet URL: http://www.readwriteweb.com/biz/2010/12/roampay-is-like-square-for-bla.php, on Apr. 20, 2011, pp. 1-12. |
Veneziani, V., “Use a cellphone as a magnetic card reader,” Apr. 15, 2005, Retrieved from the Internet URL: http://hackaday.com/2005/04/15/use a-cellphone-as-a-magnetic-card . . . , on Feb. 7, 2011, pp. 1-10. |
Buttell, A.E., “Merchants eye mobile phones to transact card payments,” Feb. 3, 2010, Retrieved from the Internet URL: http://www.merchantaccountguide.com/merchant-account-news/cell-phone-credit-card-mer . . . , on Feb. 8, 2011, pp. 1-3. |
“USB Magnetic Stripe Credit/Card Track-2 Reader and Writer (75/210BPI),” Deal Extreme (dealextreme.com), Nov. 15, 2008, Retrieved from the Internet URL: http://www.dealextreme.com/p/usb-magnetic-stripe-credit-debit-card-track-2-reader-and-wr . . . , on Feb. 8, 2011, pp. 1-3. |
“Mophie Marketplace Magnetic Strip Reader/Case for iPhone 3G & 3GS—Grey,” J&R (JR.com), Retrieved from the Internet URL: http://www.jr.com/mophie/pe/MPE—MPIP3GBLK/, on Feb. 8, 2011, pp. 1-1. |
“Barcode scanner and Magnetic Stripe Reader (MSR) for Pocke . . . ,” Tom's Hardware (tomshardware.com), Retrieved from the Internet URL: http://www.tomshardware.com/forum/24068-36-barcode-scanner-magnetic-stripe-reader-po . . . , on Feb. 8, 2011, pp. 1-2. |
“A Magnetic Stripe Reader—Read Credit Cards & Driver Licences!,” Articlesbase (articlesbase.com), Sep. 7, 2009, Retrieved from the Internet URL: http://www.articlesbase.com/electronics-articles/a-magnetic-stripe-reader-read-credit-cards- . . . , on Feb. 8, 2011, pp. 1-3. |
Jones, R., “U.S. Credit Cards to get a high-tech makeover,” Oct. 22, 2010, Retrieved from the Internet URL: http://lifeine.today.com/—news/2010/10/22/5334208-us-credit-cards-to-get-a-high-tech-mak . . . , on Feb. 8, 2011, pp. 1-8. |
“Arduino magnetic stripe decoder,” Instructables, Retrieved from the Internet URL: http://www.instructables.com/id/Arduino-magneticstripe-decorder/, on Feb. 8, 2011, pp. 1-5. |
“Magnetic Stripe Reader (MSR) MSR7000-100R,” Motorola Solutions, Retrieved from the Internet URL: http://www.motorola.com/business/US-EN/MSR7000-100R—US-EN.do?vgnextoid=164fc3 . . . , on Feb. 8, 2011, pp. 1-1. |
“Pay@PC” Retrieved from the Internet URL: http://www.merchantanywhere.com/PAY—AT—PCT@PC.htm, on Feb. 11, 2011, pp. 1-2. |
“Get paid on the spot from your mobile phone,” Retrieved from the Internet URL: http://payments.intuit.com/products/basic-payment-solutions/mobile-credit-card-processin . . . , on Feb. 11, 2011, pp. 1-3. |
“Touch-Pay Wireless Credit Card Processing,” MerchantSeek, Retrieved from the Internet URL: http://www.merchantseek.com/wireless-credit-card-processing.htm, on Feb. 11, 2011, pp. 1-5. |
“Announcement: Semtek Introduces Side Swipe II Card Reader for Wireless Devices,” Brighthand, Retrieved from the Internet URL: http://forum.brighthand.com/pdas-handhelds/173285-announcement-semtek-introduces-sid . . . , on Apr. 19, 2011, pp. 1-2. |
Grandison, K., “vTerminal Credit Card Processing App for AuthorizeNet and PayPal Payflow Pro for Curve 8350 8500 8900 and Bold 9000,” Retrieved from the Internet URL: http://www.4blackberry.net/tag/business-tools/vterminal-credit-card-processing-app-for-authorizenet-and-paypal-payflow-pro-for-curve-8350-8500-890-download-2075.html, on Mar. 30, 2015, pp. 1-4. |
Harris, A., “Magnetic Stripe Card Spoofer,” Aug. 4, 2008, Retrieved from the Internet URL: http://hackaday.com/2008/08/04/magnetic-stripe-card-spoofer/, on Apr. 25, 2011, pp. 1-11. |
“Headphone Jack (3.5mm),” Retrieved from the Internet URL: http://www.phonescoop.com/glossary/term.php?gid=440, on May 5, 2011, pp. 1-1. |
“2.5mm Headset Jack,” Retrieved from the Internet URL: http://www.phonescoop.com/glossary/term.php?gid=360, on May 5, 2011, pp. 1-1. |
“Reference Designations for Electrical and Electronics Parts and Equipment,” Engineering Drawing and Related Documentation Practices, ASME Y14.44/2008, The American Society of Mechanical Engineers, Nov. 21, 2008, pp. 1-31. |
Acidus, “Mag-stripe Interfacing—A Lost Art,” Retrieved from the Internet URL: http://www.scribd.com/doc/18236182/Magstripe-Interfacing#open— . . . , on Feb. 7, 2011, pp. 1-4. |
“Mag-stripe readers The hunt for a homebrew mag-stripe reader that'll work with modern,” Jan. 16, 2009, Retrieved from the Internet URL: http://www.hak5.org/forums/index.php?showtopic=11563&st=20, on Apr. 25, 2011, pp. 1-6. |
Kuo, Y-S et al., “Hijacking Power and Bandwidth from the Mobile Phone's Audio Interface,” Proceedings of the First ACM Symposium on Computing for Development, (DEV'10), Dec. 17, 2010, pp. 1-10. |
Website: www.alexwinston.com, Aug. 31, 2009, pp. 1-5. |
“Magnetic Card Reader,” lekernel.net˜scrapbook, Retrieved from the Internet URL: http://lekernel.net/scrapbook/old/cardreader.html, on Apr. 25, 2011, pp. 1-4. |
“Magnetic stripe reader/writer,” Retrieved from the Internet URL: http://www.gae.ucm.es/-padilla/extrawork/stripe.html, on Dec. 21, 2009, pp. 1-2. |
Lucks, S., “Two-Pass Authenticated Encryption Faster than Generic Composition,” H. Gilbert and H. Handschuh (Eds.): FSE 2005, LNCS 3557, © International Association for Cryptologic Research 2005, pp. 284-298. |
Bauer, G.R. et al., “Comparing Block Cipher Modes of Operation on MICAz Sensor Nodes,” 17th Euromicro International Conference on Parallel, Distributed and Network-based Processing, 2009, Feb. 18-20, 2009, pp. 371-378. |
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. |
English-language translation of Final Rejection for Japanese Application No. 2014-025525, mailed Oct. 20, 2015. |
Notice of Allowance mailed Nov. 13, 2015, for U.S. Appl. No. 13/298,487, of Lamba, K., et al., filed Nov. 17, 2011. |
Corrected Notice of Allowance mailed Nov. 18, 2015, for U.S. Appl. No. 14/578,107, of Wade, J., et al., filed Dec. 19, 2014. |
Notice of Allowance mailed Nov. 19, 2015, for U.S. Appl. No. 13/298,491, of Lamba, K., et al., filed Nov. 17, 2011. |
Corrected Notice of Allowance mailed Nov. 19, 2015, for U.S. Appl. No. 13/298,510, of Lamba, K., et al., filed Nov. 17, 2011. |
Notice of Allowance mailed Nov. 20, 2015, for U.S. Appl. No. 13/298,501, of Babu, A., et al., filed Nov. 17, 2011. |
Notice of Allowance mailed Nov. 23, 2015 for U.S. Appl. No. 14/189,997, of Lamfalusi, M., et al., filed Feb. 25, 2014. |
Non-Final Office Action mailed Dec. 14, 2015, for U.S. Appl. No. 13/298,506, of Lamba, K., et al., filed Nov. 17, 2011. |
Notice of Allowance mailed Jan. 12, 2016, for U.S. Appl. No. 13/298,534, of Lamba, K. et al., filed Nov. 17, 2011. |
Final Office Action mailed Jan. 15, 2016, for U.S. Appl. No. 29/493,212, of Edwards, T., et al., filed Jun. 6, 2014. |