This disclosure relates to cardless payment transactions.
When searching for merchants, a user can enter a search query into a search engine. The search query can include a merchant's name or a name of a desired product or service. The user can limit the search by location. The search engine can return results to the user in response to the search query, including any limitations provided by the user. To perform a transaction (e.g., a purchase) with a merchant listed in the search results, the user must visit the merchant's retail store or the merchant's online shopping portal.
In a conventional point-of-sale electronic credit card transaction, the transaction is authorized and captured. In the authorization stage, a physical credit card with a magnetic stripe is swiped through a merchant's magnetic card reader, e.g., as part of a point-of-sale device. A payment request is sent electronically from the magnetic card reader to a credit card processor. The credit card processor routes the payment request to a card network, e.g., Visa or Mastercard, which in turn routes the payment request to the card issuer, e.g., a bank. Assuming the card issuer approves the transaction, the approval is then routed back to the merchant. In the capture stage, the approved transaction is again routed from the merchant to the credit card processor, card network and card issuer, and the payment request can include the cardholder's signature (if appropriate). The capture state can trigger the financial transaction between the card issuer and the merchant, and optionally creates a receipt. There can also be other entities, e.g., the card acquirer, in the route of the transaction. Debit card transactions have a different routing, but also require swiping of the card.
This specification relates to updating data describing merchants in a listing of merchants that allow cardless payment transactions. A convenient graphical user interface that lists merchants that accept cardless payment transactions can be displayed on a user's user device, e.g., a mobile device. Merchants included in the listing can be ranked based on a geographic distance from the user to the respective merchant. The user can choose to conduct a transaction with a merchant after selecting the merchant using the graphical user interface. As used in this specification, a cardless payment transaction is one where a user conducts the transaction with a merchant at a point of sale using a financial account without physically presenting a payment card to the merchant at the point of sale. In fact, the merchant need not receive any details about the financial account, e.g., the credit card issuer, credit card number, and the like is not provided to the merchant.
Electronic payment transactions between a user and a merchant are generally restricted to situations in which the user is within a predetermined distance of the merchant. The geographic distance between the user and a merchant is generally based on the user's geographic position, for example, as determined by a geolocation data from the user device, and a geographic location of the merchant, as determined by, for example, a known street address for the merchant or by geolocation data from the user device.
In some cases, a merchant's geographic location, as determined by the merchant's known street address, is inconsistent with the merchant's actual geographic location. For example, the merchant may have relocated to a different geographic location or the merchant's known street address was incorrect. In such cases, the listing of merchants may indicate that a merchant is not within a predetermined distance of a user despite the user being located within a predetermined distance of the merchant. In some cases, the merchant's place of business is a mobile shop (e.g., a food truck) that regularly changes geographic locations. In such cases, a user may travel to the merchant's geographic location that was provided in a listing of merchants only to discover that the merchant has relocated to a different geographic location. In either case, the user may be prohibited from conducting an electronic payment transaction with the merchant, since the two are not within a predetermined distance of each other.
To address this issue, the user device sends a request to a payment service system requesting that the merchant's geographic location, as provided in the listing of merchants, be updated to the merchant's correct geographic location. The payment service system sends a request for an updated geographic location to a computing device of the merchant. In response to receiving the request, the merchant updates its geographic location, for example, by providing an updated street address, and sends geolocation data describing the updated geographic location to the payment service system. Alternatively, in response to receiving the request, the merchant's computing device can send geolocation data describing the updated geographic location to the payment service system. The payment service system can update the data describing the merchant in the listing of merchants to include the updated geographic location.
In one aspect, a method includes receiving, from a user device, a request for a listing of merchants; in response to receiving the request for a listing of merchants, sending, to the user device, data describing one or more merchants and respective initial geographic locations of the one or more merchants; receiving, from the user device, a user request for updating a geographic location of a particular merchant in the one or more merchants; sending a request for an updated geographic location to a computing device of the particular merchant; receiving, from the computing device of the particular merchant, data describing an updated geographic location of the particular merchant; and providing, to the user device, data describing the updated geographic location of the particular merchant.
Implementations may include one or more of the following features. Data describing the one or more merchants includes, for each merchant, a respective merchant name and one or more of: a respective initial geographic location of the merchant, one or more coupons provided by the merchant, an icon representing the merchant, or an icon indicating whether the merchant is authorized to perform a transaction with the user. The method further includes updating the data describing the one or more merchants with the updated geographic location of the particular merchant. The method further includes receiving, from the user device, a current geographic location of the user device; and wherein the one or more merchants are located within a threshold distance from the current geographic location of the user device.
In one aspect, a method includes receiving, from a user device, a user request for data describing a particular merchant that is within a threshold distance from a current geographic location of the user device, wherein the data describes the particular merchant as not being within the threshold distance from the current geographic location of the user device; in response to receiving the request for data describing the particular merchant, providing, to the user device, data describing the particular merchant; receiving, from the user device, a user request for updating an initial geographic location of the particular merchant; sending a request for an updated geographic location to a computing device of the particular merchant; receiving, from the computing device of the particular merchant, data describing an updated geographic location of the particular merchant; and providing, to the user device, data describing the updated geographic location of the particular merchant.
Implementations may include one or more of the following features. Data describing the particular merchant includes a respective merchant name and one or more of: a respective initial geographic location of the merchant, one or more coupons provided by the merchant, an icon representing the merchant, or an icon indicating whether the merchant is authorized to perform a transaction with the user. The method further includes updating the data describing the one or more merchants with the updated geographic location of the particular merchant.
Advantages may include one or more of the following. A customer can send a request to update a merchant's geographic location provided in a listing of merchants. Geographic locations of merchants in a listing of merchants can be validated by users. Correction of geographic locations of merchants can be initiated by users.
Like reference numbers and designations in the various drawings indicate like elements.
A cardless payment processor operates a payment service system 108. The user device 102 and the merchant device 104 can communicate with the payment service system 108 through the network 106. The payment service system 108 includes one or more servers 112, at least some of which are configured to service secured transactions (e.g., a secure server), and to process electronic payment transactions between the user device 102 and the merchant device 104. In general, servers 112 can store public merchant information, e.g., the merchant's name, street address, and telephone numbers. The servers 112 can also be configured to transfer and update the user application to the user device 102, and to transfer and update the merchant application to the merchant device 104. The servers 112 can store data describing merchants that have merchant accounts 114 with the payment server system 108. The data describing the merchants can include a merchant name, street address, telephone numbers, and theme, e.g., color motif and logos. The servers 112 can be also be configured to send and receive data describing merchants that have merchant accounts 114 with the payment server system 108 to and from the user device 102 and the merchant device 104. The servers 112 can also be configured to send and receive secure information, e.g., credit card numbers, debit card numbers, bank accounts, user accounts, user identifying information, or other sensitive information to and from the user device 102 and the merchant device 104.
The payment service system 108 can communicate with a computer system 116 of a card payment network, e.g., Visa or MasterCard. The payment service system 108 can communicate with a computer system 116 over the network 106, or over a different network. The computer system 116 of the card payment network can communicate with a computer system 118 of a card issuer, e.g., a bank. There can also be computer systems of other entities, e.g., the card acquirer, between the payment service system 108 and the card issuer.
Generally, transactions between the user and the merchant are permitted using the payment server system 108 when the user has a user account with the payment service system 108. Similarly, the merchant also has a merchant account with the payment service system 108. When the user and the merchant enter into a transaction, the transaction can be processed through the exchange of funds between the user account and the merchant account.
In some implementations, when conducting cardless transactions, the payment service system 208 defines a geo-location radius, e.g., the geo-location radius 206 and the geo-location radius 256, around the geographic location of a merchant. In such implementations, transactions between a user device and a merchant device are permitted when both the user device and the merchant device are geographically located within the defined geo-location radius. Depending on the implementation, the merchant's geographic location can be determined by geo-locating the merchant device, e.g., the merchant device 204, or based on the merchant's street address. In some implementations, the geo-location radius is defined as a 500 foot radius around the merchant's geographic location. In some implementations, the geo-location radius is set by the merchant. In such implementations, the payment service system 208 receives input from the merchant device, e.g., the merchant device 204, or another computer system of the merchant, specifying the geo-location radius.
In the example of
In contrast, the example of
In the example of
The user operating the user device 302 may request that the merchant update its geographic location, e.g., street address, with the payment service system 208. When making the request, the user interacts with the user device 302 to send the request to the payment service system 308 requesting that the merchant's geographic location, as provided in the listing of merchants, be updated. In such implementations, the payment service system 308 sends a request for an updated geographic location to the merchant device 304 of the merchant. In response to receiving the request, the merchant interacts with the merchant device 304 to update its geographic location, for example, by providing an updated street address and sending the updated geographic location to the payment service system 308. For example, in responding to the request, the merchant device 304 can initiate a geolocation query to determine the merchant's geographic location and then send the geolocation data describing the merchant's geographic location to the payment service system 308. The system 308 updates the data describing the merchant in the listing of merchants to include the merchant's updated geographic location. The payment service system 308 can also send data describing the merchant's updated geographic location to the user device 302. Once the merchant's geographic location has been updated, the payment service system 308 can define a new geo-location radius 356 for the merchant's updated geographic location. The payment service system 308 can then determine whether the user device 302 is within the new geo-location radius 356 of the merchant device 304. In
In the example of
The system receives, from the user device, a request for a listing of merchants (step 402). Typically, the user launches the user application on the user device. When launching the user application, the user device can communicate a request to the system to identify merchants that can perform cardless payment transactions. The request can include data describing a location of the user device, for example, as determined by the user device.
In response to receiving the request for a listing of merchants, the system sends, to the user device, data describing a listing of one or more merchants (step 404). The listing of one or more merchants includes merchants that have been identified by the system based on the location information of the user device, as described above in reference to
In some implementations, the data describing the one or more merchants includes, for each merchant, a respective merchant name and one or more of: a respective initial geographic location of the merchant, one or more coupons provided by the merchant, an icon representing the merchant, or an icon indicating whether the merchant is authorized to perform a transaction with the user.
The system receives, from the user device, a user request for updating a geographic location of a particular merchant in the one or more merchants (step 406). A user can interact with the user device to identify a particular merchant and to request an update of a geographic location of that merchant, as described above in reference to
The system sends a request for an updated geographic location to a computing device of the particular merchant (step 408). The system can send the request to a merchant device, as described above in reference to
The system receives, from the computing device of the particular merchant, data describing an updated geographic location of the particular merchant (step 410). For example, the merchant can provide the system with an updated geographic location, e.g., street address, as described above in reference to
The system optionally provides, to the user device, data describing the updated geographic location of the particular merchant (step 412). The system can optionally provide the user device with the updated geographic location to be presented in the listing of merchants.
The system receives, from a user device, a user request for data describing a particular merchant that is within a threshold distance from a current geographic location of the user device, where the data describes the particular merchant as not being within the threshold distance from the current geographic location of the user device (step 502). For example, the user operating the user device may be located at a store of the particular merchant. However, the data describing the particular merchant may indicate that the user is not within a threshold distance of the particular merchant. In particular, the user device may not be within a geo-location radius that was determined for the particular merchant using an incorrect street address.
In instances where the user device is not geographically located within a threshold distance of the particular merchant, the user device can display a message indicating its inability to “check in,” or conduct a transaction with the particular merchant (e.g., by displaying a “too far to pay” message). In other words, the merchant cannot charge the user's financial account for a cardless payment transaction until the user is within a threshold distance and the merchant has the user's consent, as described further in reference to
In response to receiving the request for data describing the particular merchant, the system provides, to the user device, data describing the particular merchant (step 504). In some implementations, the data describing the particular merchant includes a respective merchant name and one or more of: a respective initial geographic location of the merchant, one or more coupons provided by the merchant, an icon representing the merchant, or an icon indicating whether the merchant is authorized to perform a transaction with the user.
The system receives, from the user device, a user request for updating an initial geographic location of the particular merchant (step 506). A user can interact with the user device to identify a particular merchant and to request an update of an initial geographic location of that merchant, as described above.
The system sends a request for an updated geographic location to a computing device of the particular merchant (step 508). The system can send the request to a merchant device, as described above in reference to
The system receives, from the computing device of the particular merchant, data describing an updated geographic location of the particular merchant (step 510). For example, the merchant can provide the system with an updated geographic location, e.g., street address, as described above. In some implementations, the system updates the data describing the one or more merchants with the updated geographic location of the particular merchant.
The system provides, to the mobile device, data describing the updated geographic location of the particular merchant (step 512).
Each merchant can be represented with a custom-designed “card.” In some implementations, tapping the row containing the name 612a of the merchant, or tapping the name 612a of the merchant, will cause the user's user device to display more information regarding the respective merchant. In some implementations, the additional merchant information is represented by a custom-designed merchant page. For example, the user device can display a map around the merchant's area, the merchant's phone number, the merchant's operating hours, or other merchant information, as described in reference to
The application can present user account information by tapping an account button 602. When provided with input, the application can search for merchants in a search bar 604. For example, the application can send the search query to a cardless payment system and be provided with merchants that are relevant to the search query.
If the current location of the user device is within a threshold distance of a merchant, the application can display a representative symbol (e.g., “Check-in” button 614). By tapping the check in button, the application can, among other things, conduct transactions with the merchant. If the user device's current location is not within the predetermined distance, the application can display a distance 610 from the user device to the merchant.
In the example of
Embodiments of the subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on a non-transitory computer storage medium for execution by, or to control the operation of, data processing apparatus. Alternatively or in addition, the program instructions can be encoded on an artificially-generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. A computer storage medium can be, or be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them. Moreover, while a computer storage medium is not a propagated signal, a computer storage medium can be a source or destination of computer program instructions encoded in an artificially-generated propagated signal. The computer storage medium can also be, or be included in, one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices).
The operations described in this specification can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources.
The term “data processing apparatus” encompasses all kinds of apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, a system on a chip, or multiple ones, or combinations, of the foregoing The apparatus can include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). The apparatus can also include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination of one or more of them. The apparatus and execution environment can realize various different computing model infrastructures, such as web services, distributed computing and grid computing infrastructures.
A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language resource), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform actions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for performing actions in accordance with instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device (e.g., a universal serial bus (USB) flash drive), to name just a few. Devices suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
To provide for interaction with a user, embodiments of the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending resources to and receiving resources from a device that is used by the user; for example, by sending web pages to a web browser on a user's client device in response to requests received from the web browser.
Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), an inter-network (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).
The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In some embodiments, a server transmits data (e.g., an HTML page) to a client device (e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device). Data generated at the client device (e.g., a result of the user interaction) can be received from the client device at the server.
A system of one or more computers can be configured to perform particular operations or actions by virtue of having software, firmware, hardware, or a combination of them installed on the system that in operation causes or cause the system to perform the actions. One or more computer programs can be configured to perform particular operations or actions by virtue of including instructions that, when executed by data processing apparatus, cause the apparatus to perform the actions.
While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any inventions or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
Thus, particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous.
This application claims priority to and is a continuation of U.S. patent application Ser. No. 13/763,504, filed on Feb. 8, 2013, the entire contents of which are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4035614 | Frattarola et al. | Jul 1977 | A |
4254441 | Fisher | Mar 1981 | A |
4591937 | Nakarai et al. | May 1986 | A |
4845740 | Tokuyama et al. | Jul 1989 | A |
5266789 | Anglin et al. | Nov 1993 | A |
5434400 | Scherzer | Jul 1995 | A |
5463678 | Kepley, III et al. | Oct 1995 | A |
5589855 | Blumstein et al. | Dec 1996 | A |
5764742 | Howard et al. | Jun 1998 | A |
5850599 | Seiderman | Dec 1998 | A |
5945654 | Huang | Aug 1999 | A |
6006109 | Shin | Dec 1999 | A |
6021944 | Arakaki | Feb 2000 | A |
6026375 | Hall et al. | 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 |
6341353 | Herman et al. | Jan 2002 | B1 |
6363139 | Zurek et al. | Mar 2002 | B1 |
6374176 | Schmier et al. | Apr 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 |
6526275 | Calvert | Feb 2003 | B1 |
6536670 | Postman et al. | Mar 2003 | B1 |
6579728 | Grant et al. | Jun 2003 | B2 |
6612488 | Suzuki | Sep 2003 | B2 |
6659344 | Otto et al. | Dec 2003 | B2 |
6820062 | Gupta et al. | Nov 2004 | B1 |
6832721 | Fujii | Dec 2004 | B2 |
6850147 | Prokoski et al. | Feb 2005 | B2 |
6868391 | Hultgren | Mar 2005 | B1 |
6888443 | Ritter | May 2005 | B2 |
6896182 | Sakaguchi | May 2005 | B2 |
6898598 | Himmel et al. | May 2005 | B2 |
6944782 | von Mueller et al. | Sep 2005 | B2 |
7003316 | Elias et al. | Feb 2006 | B1 |
7149296 | Brown et al. | Dec 2006 | B2 |
7207480 | Geddes | Apr 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 |
7376431 | Niedermeyer | May 2008 | B2 |
7376433 | Hose | May 2008 | B1 |
7376583 | Rolf | May 2008 | B1 |
7403762 | Morgan et al. | Jul 2008 | B2 |
7409234 | Glezerman | Aug 2008 | B2 |
7433452 | Taylor et al. | Oct 2008 | B2 |
7506812 | von Mueller et al. | Mar 2009 | B2 |
7520430 | Stewart et al. | Apr 2009 | B1 |
7581678 | Narendra et al. | Sep 2009 | B2 |
7600673 | Stoutenburg et al. | Oct 2009 | B2 |
7620404 | Chesnais et al. | Nov 2009 | B2 |
7684809 | Niedermeyer | Mar 2010 | B2 |
7708189 | Cipriano | May 2010 | B1 |
7711100 | Dennis | May 2010 | B2 |
7793834 | Hachey et al. | Sep 2010 | B2 |
7810729 | Morley | Oct 2010 | B2 |
7848765 | Phillips et al. | Dec 2010 | B2 |
7869591 | Nagel et al. | Jan 2011 | B1 |
7896248 | Morley | Mar 2011 | B2 |
7918394 | Morley, Jr. | Apr 2011 | B1 |
7945494 | Williams | May 2011 | B2 |
8050984 | Bonner et al. | Nov 2011 | B2 |
8090351 | Klein | Jan 2012 | B2 |
8135624 | Ramalingam | Mar 2012 | B1 |
8231055 | Wen | Jul 2012 | B2 |
8376239 | Humphrey | Feb 2013 | B1 |
8413901 | Wen | Apr 2013 | B2 |
8438066 | Yuen et al. | May 2013 | B1 |
8509734 | Gupta | Aug 2013 | B1 |
8554670 | Blank et al. | Oct 2013 | B1 |
8684261 | Burdett et al. | Apr 2014 | B2 |
8707319 | Nguyen | Apr 2014 | B2 |
8750901 | Gupta | Jun 2014 | B1 |
8766791 | Koen et al. | Jul 2014 | B2 |
8777104 | Brock et al. | Jul 2014 | B1 |
8967471 | Rosenthal et al. | Mar 2015 | B1 |
9055400 | Lee | Jun 2015 | B1 |
9113344 | Lee | Aug 2015 | B1 |
9204257 | Mendelson | Dec 2015 | B1 |
9264850 | Lee | Feb 2016 | B1 |
9373112 | Henderson et al. | Jun 2016 | B1 |
9407689 | Casares et al. | Aug 2016 | B1 |
9451397 | Lee | Sep 2016 | B1 |
9652791 | Brock | May 2017 | B1 |
9730015 | Lee | Aug 2017 | B1 |
9767474 | Ramalingam | Sep 2017 | B1 |
9838840 | Lee | Dec 2017 | B1 |
9924322 | Post et al. | Mar 2018 | B2 |
10163148 | Chatterjee et al. | Dec 2018 | B1 |
10373151 | Lee | Aug 2019 | B1 |
20010001856 | Gould et al. | May 2001 | A1 |
20020002507 | Hatakeyarna | Jan 2002 | A1 |
20020030871 | Anderson et al. | Mar 2002 | A1 |
20020049644 | Kargman | Apr 2002 | A1 |
20020077974 | Ortiz | Jun 2002 | A1 |
20020099648 | DeVoe et al. | Jul 2002 | A1 |
20020108062 | nakajima et al. | Aug 2002 | A1 |
20020169541 | Bouve et al. | Nov 2002 | A1 |
20020198818 | Scott et al. | Dec 2002 | A1 |
20030004842 | Williams et al. | Jan 2003 | 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 |
20030194071 | Ramian | Oct 2003 | A1 |
20030200180 | Phelan et al. | Oct 2003 | A1 |
20040002897 | Vishik | Jan 2004 | A1 |
20040012875 | Wood | Jan 2004 | A1 |
20040015475 | Scheepsma | Jan 2004 | A1 |
20040041911 | Odagiri et al. | Mar 2004 | A1 |
20040049451 | Berardi et al. | Mar 2004 | A1 |
20040064378 | Yoshida | Apr 2004 | A1 |
20040093274 | Vanska et al. | May 2004 | A1 |
20040093496 | Colnot | May 2004 | A1 |
20040104268 | Bailey | Jun 2004 | A1 |
20040107170 | Labrou et al. | Jun 2004 | A1 |
20040127256 | Goldthwaite et al. | Jul 2004 | A1 |
20040128256 | Krouse et al. | Jul 2004 | A1 |
20040204074 | Desai | Oct 2004 | A1 |
20050004757 | Neeman et al. | Jan 2005 | A1 |
20050048961 | Ribaudo et al. | Mar 2005 | A1 |
20050077870 | Ha et al. | Apr 2005 | A1 |
20050159133 | Hasan et al. | Jul 2005 | A1 |
20050242173 | Suzuki | Nov 2005 | A1 |
20050251440 | Bednarek | Nov 2005 | A1 |
20050256782 | Sands et al. | Nov 2005 | A1 |
20050266798 | Moloney et al. | Dec 2005 | A1 |
20060089909 | Mcleod et al. | Apr 2006 | A1 |
20060094481 | Gullickson | May 2006 | A1 |
20060122902 | Petrov et al. | Jun 2006 | A1 |
20060200378 | Sorensen | Sep 2006 | A1 |
20060208066 | Finn et al. | Sep 2006 | A1 |
20060223580 | Antonio et al. | Oct 2006 | A1 |
20060234771 | Shavrov | Oct 2006 | A1 |
20060293968 | Brice et al. | Dec 2006 | A1 |
20070030824 | Ribaudo et al. | Feb 2007 | A1 |
20070067833 | Colnot | Mar 2007 | A1 |
20070072678 | Dagres | Mar 2007 | A1 |
20070100651 | Ramer et al. | May 2007 | A1 |
20070118429 | Subotovsky | May 2007 | A1 |
20070124211 | Smith | May 2007 | A1 |
20070138268 | Tuchman | Jun 2007 | A1 |
20070150369 | Zivin | Jun 2007 | A1 |
20070150414 | Templeton | Jun 2007 | A1 |
20070155430 | Cheon et al. | Jul 2007 | A1 |
20070221728 | Ferro et al. | Sep 2007 | A1 |
20070244778 | Bailard | Oct 2007 | A1 |
20070244811 | Tumminaro | Oct 2007 | A1 |
20070250623 | Hickey et al. | Oct 2007 | A1 |
20070255653 | Tumminaro et al. | Nov 2007 | A1 |
20070281689 | Altman et al. | Dec 2007 | A1 |
20070282700 | Masse | Dec 2007 | A1 |
20070299722 | Stoffelsma et al. | Dec 2007 | A1 |
20080027815 | Johnson et al. | Jan 2008 | A1 |
20080040219 | Kim et al. | Feb 2008 | A1 |
20080040274 | Uzo | Feb 2008 | A1 |
20080054072 | Katragadda et al. | Mar 2008 | A1 |
20080059297 | Vallier et al. | Mar 2008 | A1 |
20080059370 | Sada et al. | Mar 2008 | A1 |
20080059375 | Abifaker | Mar 2008 | A1 |
20080061150 | Phillips | Mar 2008 | A1 |
20080084977 | Nayak et al. | Apr 2008 | A1 |
20080147507 | Langhammer | Jun 2008 | A1 |
20080147564 | Singhal | Jun 2008 | A1 |
20080177662 | Smith et al. | Jul 2008 | A1 |
20080189170 | Ramachandra et al. | Aug 2008 | A1 |
20080195428 | O'Sullivan | Aug 2008 | A1 |
20080215380 | Graeber | Sep 2008 | A1 |
20080238610 | Rosenberg | Oct 2008 | A1 |
20080242278 | Rekimoto | Oct 2008 | A1 |
20080249865 | Angell et al. | Oct 2008 | A1 |
20080249882 | Spolar | Oct 2008 | A1 |
20080249939 | Veenstra | Oct 2008 | A1 |
20080277183 | Huang et al. | Nov 2008 | A1 |
20080306678 | Miyawaki | Dec 2008 | A1 |
20090024533 | Fernandes et al. | Jan 2009 | A1 |
20090030885 | DePasquale et al. | Jan 2009 | A1 |
20090043696 | Ornce 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 | Coifing et al. | May 2009 | A1 |
20090119190 | Realini | May 2009 | A1 |
20090159681 | Mullen et al. | Jun 2009 | A1 |
20090166422 | Biskupski | Jul 2009 | A1 |
20090171844 | Olliphant et al. | Jul 2009 | A1 |
20090210334 | Russell | Aug 2009 | A1 |
20090216676 | Mathur et al. | Aug 2009 | A1 |
20090287408 | Gerdes et al. | Nov 2009 | A1 |
20090298514 | Ullah | Dec 2009 | A1 |
20090328052 | Nguyen | Dec 2009 | A1 |
20100057503 | Katz | Mar 2010 | A1 |
20100063893 | Townsend | Mar 2010 | A1 |
20100087144 | Korenshtein | Apr 2010 | A1 |
20100125495 | Smith et al. | May 2010 | A1 |
20100135178 | Aggarwal et al. | Jun 2010 | A1 |
20100144375 | Pfister et al. | Jun 2010 | A1 |
20100145868 | Niedermeyer | Jun 2010 | A1 |
20100184479 | Griffin | Jul 2010 | A1 |
20100191653 | Johnson et al. | Jul 2010 | A1 |
20100197325 | Dredge | Aug 2010 | A1 |
20100243732 | Wallner | Sep 2010 | A1 |
20100287250 | Carlson et al. | Nov 2010 | A1 |
20100306080 | Trandal et al. | Dec 2010 | A1 |
20100328029 | Kolek | Dec 2010 | A1 |
20110045840 | Alizadeh-Shabdiz et al. | Feb 2011 | A1 |
20110047037 | Wu | Feb 2011 | A1 |
20110060600 | Fox et al. | Mar 2011 | A1 |
20110063138 | Berkobin et al. | Mar 2011 | A1 |
20110084131 | McKelvey | Apr 2011 | A1 |
20110084139 | McKelvey et al. | Apr 2011 | A1 |
20110084147 | Wilson et al. | Apr 2011 | A1 |
20110090124 | Liu et al. | Apr 2011 | A1 |
20110137773 | Davis, III et al. | Jun 2011 | A1 |
20110137803 | Willins | Jun 2011 | A1 |
20110153495 | Dixon et al. | Jun 2011 | A1 |
20110161235 | Beenau et al. | Jun 2011 | A1 |
20110180601 | Morley | Jul 2011 | A1 |
20110198395 | Chen | Aug 2011 | A1 |
20110202393 | DeWakar et al. | Aug 2011 | A1 |
20110202463 | Powell | Aug 2011 | A1 |
20110208612 | Shader et al. | Aug 2011 | A1 |
20110213652 | Gillen et al. | Sep 2011 | A1 |
20110238476 | Carr et al. | Sep 2011 | A1 |
20110238517 | Ramalingam et al. | Sep 2011 | A1 |
20110249668 | Van Milligan et al. | Oct 2011 | A1 |
20110258120 | Weiss | Oct 2011 | A1 |
20120005096 | Dorsey et al. | Jan 2012 | A1 |
20120008851 | Pennock et al. | Jan 2012 | A1 |
20120012653 | Johnson et al. | Jan 2012 | A1 |
20120052874 | Kumar | Mar 2012 | A1 |
20120052910 | Mu et al. | Mar 2012 | A1 |
20120101942 | Park | Apr 2012 | A1 |
20120109781 | Felt et al. | May 2012 | A1 |
20120115512 | Grainger et al. | May 2012 | A1 |
20120116861 | Dobyns | May 2012 | A1 |
20120128089 | Tsutsui | May 2012 | A1 |
20120130895 | Granbery et al. | May 2012 | A1 |
20120149390 | Gravely et al. | Jun 2012 | A1 |
20120158500 | Hochstatter et al. | Jun 2012 | A1 |
20120166267 | Beatty et al. | Jun 2012 | A1 |
20120195295 | Elmaleh | Aug 2012 | A1 |
20120209686 | Horowitz et al. | Aug 2012 | A1 |
20120209773 | Ranganathan | Aug 2012 | A1 |
20120235812 | Maia et al. | Sep 2012 | A1 |
20120252500 | Mitsuya et al. | Oct 2012 | A1 |
20120278150 | Chen | Nov 2012 | A1 |
20120278172 | Mercuri et al. | Nov 2012 | A1 |
20120296724 | Faro et al. | Nov 2012 | A1 |
20120303425 | Katzin et al. | Nov 2012 | A1 |
20120310760 | Phillips et al. | Dec 2012 | A1 |
20130002840 | Toney et al. | Jan 2013 | A1 |
20130024018 | Chang et al. | Jan 2013 | A1 |
20130027227 | Nordstrom | Jan 2013 | A1 |
20130030931 | Moshfeghi | Jan 2013 | A1 |
20130054281 | Thakkar et al. | Feb 2013 | A1 |
20130073365 | Mccarthy | Mar 2013 | A1 |
20130079037 | Dobyns | Mar 2013 | A1 |
20130110659 | Phillips et al. | May 2013 | A1 |
20130132274 | Henderson et al. | May 2013 | A1 |
20130144715 | Kranzley et al. | Jun 2013 | A1 |
20130157685 | Young | Jun 2013 | A1 |
20130185123 | Krivopaltsev et al. | Jul 2013 | A1 |
20130191195 | Carlson et al. | Jul 2013 | A1 |
20130217332 | Altman et al. | Aug 2013 | A1 |
20130217333 | Sprigg et al. | Aug 2013 | A1 |
20130226800 | Patel | Aug 2013 | A1 |
20130238540 | O'Donoghue et al. | Sep 2013 | A1 |
20130268378 | Yovin | Oct 2013 | A1 |
20130282438 | Hunter et al. | Oct 2013 | A1 |
20130297422 | Hunter et al. | Nov 2013 | A1 |
20130304898 | Aggarwal et al. | Nov 2013 | A1 |
20140028440 | Takeuchi et al. | Jan 2014 | A1 |
20140052615 | Andersen | Feb 2014 | A1 |
20140068719 | Kiukkonen et al. | Mar 2014 | A1 |
20140123043 | Schmidt et al. | May 2014 | A1 |
20140149282 | Philliou et al. | May 2014 | A1 |
20140179340 | Do et al. | Jun 2014 | A1 |
20140187257 | Emadzadeh et al. | Jul 2014 | A1 |
20140370879 | Redding et al. | Dec 2014 | A1 |
20150031388 | Chatterjee et al. | Jan 2015 | A1 |
20150079942 | Kostka et al. | Mar 2015 | A1 |
20150126119 | Schulz et al. | May 2015 | A1 |
20150178698 | Schulz et al. | Jun 2015 | A1 |
20160019531 | Gormley | Jan 2016 | A1 |
20160210606 | Henderson et al. | Jul 2016 | A1 |
20160259616 | Hosein et al. | Sep 2016 | A1 |
20180227712 | Post et al. | Aug 2018 | A1 |
Number | Date | Country |
---|---|---|
2017208387 | Aug 2017 | AU |
2 919 238 | Jan 2015 | CA |
2 506 642 | Oct 2012 | EP |
2004-078662 | Mar 2004 | JP |
2005-269172 | Sep 2005 | JP |
10-0452161 | Oct 2004 | KR |
10-2005-0077659 | Aug 2005 | KR |
10-2008-0039330 | May 2008 | KR |
0165827 | Sep 2001 | WO |
2010097711 | Sep 2010 | WO |
2010135174 | Nov 2010 | WO |
2013009891 | Jan 2013 | WO |
2015013170 | Jan 2015 | WO |
Entry |
---|
“Payments without taking out wallet—or phone,” Temple, James. San Francisco Chronicle Feb. 5, 2012; Dialog #278966926, 5pgs (Year: 2012). |
Non-Final Office Action dated Aug. 7, 2009, for U.S. Appl. No. 12/050,752, of Niedermeyer, B.J., filed Mar. 18, 2008. |
Notice of Allowance dated Dec. 16, 2009, for U.S. Appl. No. 12/050,752, of Niedermeyer, B.J., filed Mar. 18, 2008. |
Non-Final Office Action dated Sep. 10, 2010, for U.S. Appl. No. 12/707,228, of Niedermeyer, B.J., filed Feb. 17, 2010. |
Final Office Action dated Mar. 31, 2011, for U.S. Appl. No. 12/707,228, of Niedermeyer, B.J., filed Feb. 17, 2010. |
Non-Final Office Action dated Oct. 10, 2012, for U.S. Appl. No. 13/179,832, of Dorsey, J., et al., filed Jul. 11, 2011. |
Final Office Action dated Jun. 27, 2013, for U.S. Appl. No. 13/179,832, of Dorsey, J., et al., filed Jul. 11, 2011. |
Advisory Action dated Oct. 24, 2013, for U.S. Appl. No. 13/179,832, of Dorsey, J., et al., filed Jul. 11, 2011. |
Non-Final Office Action dated Jan. 8, 2014, for U.S. Appl. No. 13/179,832, of Dorsey, J., et al., filed Jul. 11, 2011. |
Non Final Office Action dated Dec. 1, 2014, for U.S. Appl. No. 13/802,064, of Lee, B., filed Mar. 13, 2013. |
Notice of Allowance dated Feb. 6, 2015, for U.S. Appl. No. 13/802,290, of Lee, B., filed Mar. 13, 2013. |
Final Office Action dated Mar. 20, 2015, for U.S. Appl. No. 13/802,064, of Lee, B., filed Mar. 13, 2013. |
Notice of Allowance dated Apr. 13, 2015, for U.S. Appl. No. 13/801,340, of Lee, B., filed Mar. 13, 2013. |
Non Final Office Action dated Oct. 1, 2015, for U.S. Appl. No. 14/803,850, of Lee, B., filed Jul. 20, 2015. |
Notice of Allowance dated Oct. 13, 2015, for U.S. Appl. No. 13/802,064, of Lee, B., filed Mar. 13, 2013. |
Non-Final Office action dated Oct. 19, 2015, for U.S. Appl. No. 13/948,871, of Post, J.D., et al., filed Jul. 23, 2013. |
Non Final Office Action dated Jan. 13, 2016, for U.S. Appl. No. 14/726,165, of Lee, B., filed May 29, 2015. |
Non-Final Office Action dated Mar. 10, 2016, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
Notice of Allowance dated May 12, 2016, for U.S. Appl. No. 14/726,165, of Lee, B., filed May 29, 2015. |
Final Office action dated May 17, 2016, for U.S. Appl. No. 13/948,871, of Post, J.D., et al., filed Jul. 23, 2013. |
Final Office Action dated Jul. 6, 2016, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
Final Office Action dated Jul. 22, 2016, for U.S. Appl. No. 14/803,850, of Lee, B., filed Jul. 20, 2015. |
Non-Final Office Action dated Jul. 29, 2016, for U.S. Appl. No. 14/079,320, of Chatterjee, S., et al., filed Nov. 13, 2013. |
Examination Report No. 1 for Australian Patent Application No. 2014293388, dated Aug. 2, 2016. |
Advisory Action dated Sep. 1, 2016, for U.S. Appl. No. 13/948,871, of Post, J.D., et al., filed Jul. 23, 2013. |
Non-Final Office Action dated Sep. 28, 2016, for U.S. Appl. No. 14/042,366, of Brock, Z., et al., filed Sep. 30, 2013. |
Non-Final Office action dated Dec. 16, 2016, for U.S. Appl. No. 13/948,871, of Post, J.D., et al., filed Jul. 23, 2013. |
Examiner Requisition for Canadian Patent Application No. 2,919,238, dated Feb. 6, 2017. |
Non Final Office Action dated Mar. 1, 2017, for U.S. Appl. No. 14/941,020, of Lee, B., filed Nov. 13, 2015. |
Non-Final Office Action dated Apr. 4, 2017, for U.S. Appl. No. 15/269,865, of Lee, B., filed Sep. 19, 2016. |
Non-Final Office Action dated Apr. 6, 2017, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
Notice of Allowance dated Apr. 7, 2017, for U.S. Appl. No. 14/803,850, of Lee, B., filed Jul. 20, 2015. |
Final Office Action dated Apr. 11, 2017, for U.S. Appl. No. 14/079,320, of Chatterjee, S., et al., filed Nov. 13, 2013. |
Non-Final Office Action dated May 4, 2017, for U.S. Appl. No. 15/084,390, of Henderson, W., et al., filed Mar. 29, 2016. |
Advisory Action dated Jul. 20, 2017, for U.S. Appl. No. 14/079,320, of Chatterjee, S., et al., filed Nov. 13, 2013. |
Final Office action dated Jul. 20, 2017, for U.S. Appl. No. 13/948,871, of Post, J.D., et al., filed Jul. 23, 2013. |
Notice of Allowance dated Jul. 25, 2017, for U.S. Appl. No. 15/269,865, of Lee, B., filed Sep. 19, 2016. |
Final Office Action dated Sep. 27, 2017, for U.S. Appl. No. 14/941,020, of Lee, B., filed Nov. 13, 2015. |
Advisory Action dated Oct. 5, 2017, for U.S. Appl. No. 13/948,871, of Post, J.D., et al., filed Jul. 23, 2013. |
Non-Final Office Action dated Oct. 6, 2017, for U.S. Appl. No. 14/079,320, of Chatterjee, S., et al., filed Nov. 13, 2013. |
Final Office Action dated Oct. 18, 2017, for U.S. Appl. No. 15/084,390, of Henderson, W., et al., filed Mar. 29, 2016. |
Final Office Action dated Nov. 1, 2017, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
Notice of Allowance dated Nov. 6, 2017, for U.S. Appl. No. 13/948,871, of Post, J.D., et al., filed Jul. 23, 2013. |
Advisory Action dated Jan. 4, 2018, for U.S. Appl. No. 14/941,020, of Lee, B., filed Nov. 13, 2015. |
Final Office Action dated Jan. 8, 2018, for U.S. Appl. No. 14/042,366, of Brock, Z., et al., filed Sep. 30, 2013. |
Examiner Requisition for Canadian Patent Application No. 2,919,238, dated Feb. 9, 2018. |
Final Office Action dated Feb. 22, 2018, for U.S. Appl. No. 14/079,320, of Chatterjee, S., et al., filed Nov. 13, 2013. |
Examination Report No. 1 for Australian Patent Application No. 2017208387, dated Feb. 26, 2018. |
Advisory Action dated Feb. 28, 2018, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
Non-Final Office Action dated Mar. 22, 2018, for U.S. Appl. No. 14/941,020, of Lee, B., filed Nov. 13, 2015. |
International Search Report and Written Opinion for International Application No. PCT/US2012/046282, dated Oct. 4, 2012. |
Burke, R.R., “The Third Wave of Marketing Intelligence,” Retailing in the 21st Century: Current and Future Trends, pp. 103-115 (2010). |
Chediak, M., “Retail technology; Grocers get taste of future; Store owners who want to stand out in the crowd these days are embracing cutting-edge services,” The Orlando Sentinel, pp. 1-2 (Jan. 21, 2006). |
Shekar, S., et al., “iGrocer—A Ubiquitous and Pervasive Smart Grocery Shopping System,” Proceedings of the 2003 ACM Symposium on Applied Computing, pp. 645-652 (Mar. 9, 2003). |
Non-Final Office Action dated May 16, 2018, for U.S. Appl. No. 15/084,390, of Henderson, W., et al., filed Mar. 29, 2016. |
Non-Final Office Action dated Jun. 25, 2018, for U.S. Appl. No. 14/042,366, of Brock, Z., et al., filed Sep. 30, 2013. |
Non-Final Office Action dated Aug. 6, 2018, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
Notice of Allowance dated Aug. 8, 2018, for U.S. Appl. No. 14/079,320, of Chatterjee, S., et al., filed Nov. 13, 2013. |
Goode, L., “Paying With Square's New Mobile-Payments App,” All Things D., published on Apr. 30, 2012, Retrieved from the Internet URL: http://allthingsd.com/20120430/paying-with-squares-new-mobile-payments-app/, on Nov. 7, 2014, pp. 1-3. |
Non-Final Office Action dated Jun. 23, 2015, for U.S. Appl. No. 13/763,504, of Brock, Z., filed Feb. 8, 2013. |
Final Office Action dated Jan. 4, 2016, for U.S. Appl. No. 13/763,504, of Brock, Z., filed Feb. 8, 2013. |
Non-Final Office Action dated Sep. 12, 2016, for U.S. Appl. No. 13/763,504, of Brock, Z., filed Feb. 8, 2013. |
Notice of Allowance dated Jan. 6, 2017, for U.S. Appl. No. 13/763,504, of Brock, Z., filed Feb. 8, 2013. |
Advisory Action dated May 15, 2018, for U.S. Appl. No. 14/042,366, of Brock, Z., et al., filed Sep. 30, 2013. |
International Search Report and Written Opinion for International Application No. PCT/US2014/047381 dated Nov. 25, 2014. |
Advisory Action dated Mar. 29, 2019, for U.S. Appl. No. 15/084,390, of Henderson, W., et al., filed Mar. 29, 2016. |
“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. |
“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. |
“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. |
“Arduino magnetic stripe decoder,” Instructables, Retrieved from the Internet URL: http://www.instructables.com/id/Arduino-magneticstripe-decorded, on Feb. 8, 2011, pp. 1-5. |
“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. |
“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. |
“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. |
“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. |
“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 (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. |
“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. |
“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. |
“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. |
“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. |
“Pay@PC,” Retrieved from the Internet URL: http://www.merchantanywhere.com/PAY_AT_PCT@PC.htm, on Feb. 11, 2011, pp. 1-2. |
“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. |
“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. |
“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. |
“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. |
“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. |
“Uber—Android Apps on Google Play,” dated Nov. 10, 2014, Retrieved from the internet URL: https://play.google.com/store/apps/details?id=com.ubercab&hl=en, on Nov. 12, 2014, pp. 2. |
“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. |
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. |
Bauer, Gr. 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. |
Bourdeauducq, S., “Reading magnetic cards (almost) for free” (“Lekemel”), Jan. 26, 2009, Retrieved from the Internet URL: http://lekernel.net/blog/?p=12, on May 5, 2011, pp. 1-2. |
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. |
Finzgar et. al.; “Use of NFC and QR code identification in an electronic ticket system for public transport”; Published in SoftCOM 2011, 19th International Conference on Software, Telecommunications and Computer networks; Published Nov. 1, 2011 (Year: 2011). |
Goode, L., “Paying With Square's New Mobile-Payments App,” All Things D., published on Apr. 30, 2012, Retrieved from the Internet URL: http://allthingsd.com/20120430/paying-with-squares-new-mobile-payments-app/, on Nov. 1, 2014, pp. 1-3. |
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.netnag/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. |
Hachman, M., “MobilePay: Your Phone Is Your Credit Card,” dated Sep. 28, 2010, Retrieved from the Internet URL: http://www.pcmag.com/article2/0,2817,2369877,00.asp, on Sep. 25, 2013, p. 1. |
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. |
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. |
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. |
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. |
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. |
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., “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. |
Siegler, MG., “MobilePay May Be the Death of the Wallet. Yes, for Real This Time,” TechCrunch, dated Sep. 28, 2010, Retrieved from the Internet URL: http:/ /techcrunch.com/2010/09/28/mobilepayusai, on Sep. 22, 2013, pp. 12. |
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. |
Website: www.alexwinston.com, Aug. 31, 2009, pp. 1-5. |
Final Office Action dated Oct. 30, 2018, for U.S. Appl. No. 14/941,020, of Lee, B., filed Nov. 13, 2015. |
Examination Report No. 2 for Australian Patent Application No. 2017208387, dated Nov. 9, 2018. |
Non-Final Office Action dated Dec. 13, 2018, for U.S. Appl. No. 15/909,005, of Post, J.D., et al., filed Mar. 1, 2018. |
Final Office Action dated Dec. 13, 2018, for U.S. Appl. No. 15/084,390, of Henderson, W., et al., filed Mar. 29, 2016. |
Examiner Requisition for Canadian Patent Application No. 2,919,238, dated Dec. 20, 2018. |
Notice of Allowance dated Feb. 4, 2019, for U.S. Appl. No. 14/042,366, of Brock, Z., filed Sep. 30, 2013. |
Advisory Action dated Feb. 8, 2019, for U.S. Appl. No. 14/941,020, of Lee, B., filed Nov. 13, 2015. |
Examination Report No. 3 for Australian Patent Application No. 2017208387, dated Feb. 11, 2019. |
Notice of Allowance dated Mar. 15, 2019, for U.S. Appl. No. 14/941,020 of Lee, B., filed Nov. 13, 2015. |
Final Office Action dated Apr. 4, 2019, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
Final Office Action dated Apr. 4, 2019, for U.S. Appl. No. 15/909,005, of Post, D. J., et al., filed Jan. 3, 2018. |
Advisory Action dated Jun. 17, 2019, for U.S. Appl. No. 15/909,005, of Post, D. J., et al., filed Jan. 3, 2018. |
Advisory Action dated Jul. 8, 2019, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
Notice of Allowance dated Sep. 25, 2019, for U.S. Appl. No. 15/909,005, of Post, D. J., et al., filed Jan. 3, 2018. |
Non-Final Office Action dated Oct. 30, 2019, for U.S. Appl. No. 15/084,390, of Henderson, W., et al., filed Mar. 29, 2016. |
Examiner Requisition for Canadian Patent Application No. 2,919,238, dated Nov. 5, 2019. |
Examination report for Australian Patent Application No. 2019201310, dated Nov. 25, 2019. |
Notice of Allowance dated May 14, 2020, for U.S. Appl. No. 15/084,390, of Henderson, W., et al., filed Mar. 29, 2016. |
Notice of Acceptance for Australian Patent Application No. 2019201310, dated Jul. 21, 2020. |
Number | Date | Country | |
---|---|---|---|
Parent | 13763504 | Feb 2013 | US |
Child | 15445380 | US |