The solution refers to a payment terminal of a simplified structure that is uses the paying customer's mobile communication device, such as a mobile phone, and which is designed above all for small business premises such as mobile kiosks and similar merchants.
The existing POS terminals are widespread in business premises and they are distinguished by a stable structure, which besides other things includes a communication channel connected to the payment processing centre, a printer, an encryption key, a display, the card reader, which is mainly a reader of different format cards, and also a keyboard for PIN code entering. This kind of technical configuration requires certain space and is relatively expensive. The realizations of known POS terminals are intended for stable sale locations in physical shops, where high costs of purchase, installation and operation of POS terminals are offset by reasonable turnovers of payments for purchases.
The solution according to the published patent WO2008061790 describes a system, in which the POS terminal does not have a communication channel with the payment processing center and uses a mediated connection over customer's mobile phone for it. This solution has lower security since the payment terminal application itself runs on a remote computer and the mobile phone is only a mediator of communication. Other published patents describe a divided POS terminal in such a way in which directly on the payment location there is only its managing part that is connected to the remaining part located in some other part of the shop. The existing solutions and published patents do not offer a simple instruction of how to create a cheap, non-complicated and eventually also portable POS payment terminal, which would create payment cryptograms according to the current standards, especially the EMV standards.
All solutions currently existing require a relatively complicated installation and encompass many input and output devices, which increase their price. Until now, there are known no such devices that would be characterized by both simplicity and high security and that would be portable and usable even in small shops such as in newspaper kiosks or in mobile counters selling fast food.
The important requirement is for the new solution to be compatible with the current payment data structures on the payment processor's level. In practice, it would not be possible to establish a configuration, which would require a completely new hierarchy or possibly a new verification process.
The deficiencies mentioned are to a great extent eliminated by a POS payment terminal using a mobile communication device, such as a mobile phone, in which the POS payment terminal contains, among other things, a unit for the run of the payment terminal application, a secured memory with identification data for the matching and identification of the merchant, a display, a keyboard and an interface according to this solution, the subject matter of which lies in the fact that the POS payment terminal is formed by a temporary connection of the Sales Device with a removable memory card that is inserted in the slot of the mobile communication device, such as a mobile phone, belonging to the paying customer. The Sales Device can belong to the merchant or it can be held by him and contains a memory with identification data, which above all, encompass data necessary for matching the POS payment terminal to the corresponding merchant's bank account. Basically the Sales Device is formed by hardware, which ensures a correct identity of the temporarily created POS payment terminal.
The important characteristic of the solution presented lies in the fact that the POS terminal is created from temporary connection of two parts. The connection is labeled as temporary, since after the payment process is ended, the parts can be disconnected, the communication channel is interrupted and another new connection between Sales Device and another removable memory card can be created. Naturally, a repeated connection of the beforehand cooperating removable memory card with the Sales Device is also not excluded. The temporality of the connection is understood as a time phase in reality limited by one payment process, while it can be supposed that there is even some time of connection before beginning and after the end of the payment process. The possibility to always pair a new pair of elements on the side of the merchant and the paying customer is a solution, in which it is always possible to create a POS terminal in the mobile communication device of a paying customer, with the POS terminal having the identity of the corresponding merchant.
The Sales Device collocation of words is not a commonly used term in the field of POS payment terminals and under this collocation it is necessary to understand any type of hardware element equipped with corresponding software for the realization of functions according to this description. The Sales Device behaves as a POS payment terminal outwardly and the merchants will usually call it that way in practice, however from the structure and run of the application point of view, the Sales Device is only an important but not sufficient part of the entire POS payment terminal. Therefore, it is necessary to understand the term Sales Device in a general meaning as a part of the terminal, which is basically connected to the merchant, or to the purchase location and ensures the correct routing of debit payments.
In the entire POS payment terminal the Sales Device can have two basic functions—to carry the identity of the POS terminal and to enter the value of the payment. In principle, even a narrower hardware version is possible, in which the payment's value is entered over the keyboard of the mobile communication device. However this kind of version is uncomfortable for the merchant since he would have to control the customer's mobile communication device or he would have to trust the customer to enter the correct payment amount into the payment terminal application. The inserted value could be displayed also on the Sales Device display so the merchant could check it, however it would be much more comfortable if the paid amount was entered through the elements on the merchant's side. The version described in this section with entering the payment value over the mobile communication's device's keyboard would not have to fulfill some standards (e.g. EMV) on the merchant's behavior and operations during debit payment realization, however it is in principle realizable using the principle of the solution presented.
The Sales Device is not able to perform the payment terminal application independently and it does not have to have communication channels for the creation of the connection to the payment processing centre (e.g. a bank, a clearing house etc.). The hardware set is capable of fulfilling all basic functions of a common POS payment terminal only by connection of Sales Device of the merchant to the removable memory card, inserted into the customer's mobile communication device. The temporary connection can be basically created for the realization of each individual payment, while it can always be a different communication device on the side of different customers. Exactly the mobile communication device is capable to create the necessary connection to the payment centre thanks to the existing GSM/GPRS (Global System for Mobile Communications/General packet radio service). However, this connection does not have to be created during each payment since the solution according to our description is capable of processing off-line and on-line payments.
The important element of the POS payment terminal according to the solution presented is a removable memory card, which also contains hardware and software elements in order for the set made of Sales Device and mobile communication device to be capable to run and execute the payment terminal application, which in the process view forms the kernel of the debit, for example, payment operation, directly on the removable memory card. Since the set made of Sales Device and the mobile communication device does not have to be equipped with the external payment card's reader, it will be suitable if even secured memory with at least one payment card unit, will be directly on the removable memory card. Also a unit for the run of payment terminal application and the communication element for the connection to Sales Device will be on the removable memory card. Besides the secured memory with identification data of the POS payment terminal, the Sales Device can also contain a communication element for the connection to the removable memory card. Thanks to these elements the POS payment terminal is created with the help of a common mobile phone with the slot for the card which extends memory. So the removable memory card can encompass generic payment terminal which will become a specific payment terminal with unique identity only after it connects with Sales Device. The Sales Device will give a clear identification, for the benefit of who should the payment be made, to this temporary connection. Since there is interest in this function even in the mobile phones without an NFC (Near Field Communication) communication element, such NFC communication element can be included directly on the removable memory card. In principle, the connection between the mobile communication device and Sales Device can be in the form of contact interface, however that would require a complicated unification of the connectors and problems with compatibility. Therefore it will be suitable, if not only solution, for the connection between the Sales Device and removable memory card to be in the form of an NFC communication channel, which is widely standardized.
Thanks to the described configuration it will be possible for the merchant to have only a very simple Sales Device, which will carry the information on identity, terminal's number and to that one an account number of the corresponding merchant can be assigned in the payment processor centre. This kind of Sales Device will be very small and simple. It can be in the form of a small box with a display and keyboard through which the merchant will enter the required payment amount. The identification data can be stored directly in the corresponding element on the printed circuit of Sales Device, or they can be stored on the ICC (integrated circuit card) card or on other carriers as e.g. up until now known SAM (Security Authentication Module) cards with cryptographic key. In this version a SAM card of the size of a common SIM card (Subscriber Identity Module) that is available after taking off the cover of the Sales Device. SAM card is inserted into Sales Device before the first activation.
The customer will tap his mobile communication device to the Sales Device. By tapping it a NFC communication channel will be created and information on the identity of this temporarily created POS payment terminal will be sent from the Sales Device into the removable memory card. Then the identification data can be encrypted by a Master Key that is stored within the Secure Element in the Sales Device. Under the term Secure Element we can understand especially, however not exclusively, a secured memory with necessary interface that can be in the form of an independent chip with a corresponding computing capacity. The Secure Element can be configured in such a way so the data that are stored in it cannot be accessed from the outside but can be used as input parameters for the realization of computing operation within the Secure Element. Only the results of these computing operations e.g. in the form of cryptograms get out of the Secure Element. The input data from the Sales Device will become the basis for the run of the payment terminal application after they are read on the removable memory card. The payment-terminal application can be loaded in indifferent form, without its own identity on the removable memory card. Basically, after the creation of the temporary connection between the Sales Device and the removable memory card, the general, generic, indifferent terminal will transform into a particular POS terminal, which is assigned to a corresponding merchant into the system. This phase forms some kind of preparation on the start of the new one-time POS terminal. Subsequently, a payment terminal application e.g. of the EMV type can run during the connection in a similar way as in standard POS terminals as it is up till now.
The encryption of the POS terminal's identification data can be done using a Master Key, which in general can be and mostly even will be different from the encryption keys, which are used later on by the payment terminal application for the creation of the payment cryptogram. The Master Key can be e.g. from the supplier of the Sales Device hardware and encryption keys of the payment-terminal application can be issued by a bank or a payment processor. The difference of the encryption keys in practice will be conditional on different requests of individual entities operating in the payment clearing system.
From the increase of security point of view even the entry about the payment amount can be encrypted during the transfer from the Sales Device to the mobile communication device. By this the risk that the paying user could lower the payment value even before the payment terminal application kernel is run is lowered. This kind of change would show itself on the final confirmation of the payment on the side of the merchant in the form of displaying the paid amount, however in case of inobservance and routine approach the merchant would not have to notice the change in the amount.
The configuration in which the communication with the unit of the selected payment card is done directly on the removable memory card during the run of the payment terminal application is suitable. Several units of independent payment cards can be stored on the removable memory card and that either on the physical separate secure elements or on independent domains of one secure element. In this configuration the payment terminal application can run directly on the removable memory card and the data on the customer's payment card are not sent over external readers and neither into internet area, a fact that has positive impact on the security of the payment operation.
The Sales Device can be in different forms; besides a small single-purpose box with a keyboard, which contains the Secure Element with identification data directly, it can be created even in such a way that within it is a created reader of external cards preferably of classical standard ICC (integrated circuit card) card format. Then the sensitive data can be loaded into the chip of this kind of card. The card's chip also contains a certain memory capacity which can be used suitably for the entry of data on realized payment transactions. After the day is over, the merchant can leave the basic part of the Sales Device in the shop, e.g. in the newspaper stand and take only the ICC card with him. In case he takes ICC card from the Sales Device, he can take it for processing into the bank or he can back up the data from it in his home computer by using a reader. In case the merchant has several mobile stands, there can be several Sales Devices combined with one ICC card with identification data of one terminal and one banking account and on the other hand one Sales Device can be used successively with several ICC cards belonging to different merchants within multiple shift business premises of one store.
It is suitable, but not necessary, if Sales Device has its own interface, e.g. of the USB format for the connection to extending accessories, which enables for the payment data to be printed directly from Sales Device, or respectively over this connector it is possible to connect the payment card reader, GPRS modem and similar.
The solution is explained in detail on the
On the
On the
On the
On the
On the
On the
On the
On the
In this example according to the
The merchant uses the Sales Device 2 in such a way that when selling he enters the amount he wants for his goods or his service over the keyboard 13 to the display 14. After checking the amount on the display 14, the merchant presses the confirming button. After this act, the POS payment terminal's 1 identification data is encrypted using Master Key and this encryption data, along with the payment amount is sent to the NFC communication element 11 which sends the encrypted message over antenna 21 and expects the mobile communication device 4 to be placed to the Sales Device 2. In his mobile communication device 4 the customer activates the launch of the payment application and he does that e.g. through a special hardware keyboard or over a software button. After the creation of the NFC communication channel, the encrypted data from the Sales Device 2 are read and decrypted, the result of which are the POS terminal's 1 identification data and the required payment amount.
This part of the transfer can be expressed also as
where 3DES means encryption over Triple Data Encryption Algorithm, where Mk is Master Key supplied by the payment processor, where Cfg means configuration data and NFC presents the transfer path between the Sales Device and the removable memory card.
The paid amount can be verified by the customer on the display of his mobile communication device 4. The identification data from the Sales Device 2 serve for the indifferent POS terminal 1 on the removable memory card 18 to become a specific POS payment terminal 1 for the benefit of a given merchant.
This process can be expressed as
Cfg+generic POS=ACg POS,
where Generic POS represents the identification of the indifferent, generic POS and ACg POS is the POS of a corresponding merchant.
Subsequently the payment terminal application runs in the normal way, e.g. according to the EMV standard. According to preset risk management of the payment card 7 and with respect to the value of the amount being paid, it might be requested to enter the password, PIN code, which is entered by the customer on the keyboard of its mobile communication device 4. In this way high security is reached, since the payment terminal application runs directly on the removable memory card 18, where there are stored also the payment cards' 7 units and the sensitive data do not leave the hardware of the connection between the Sales Device 2 and the removable memory card 18. The result of the payment application is the creation of the payment cryptogram, which is sent to the Sales Device 2 and also in the case of online payment is sent over the interface 8 into the mobile communication device 4 and subsequently over the mobile network to the payment processor. The payment cryptogram can be also created and sent according to the relationship:
pertinently to the payment processor's side as
The removable memory card is in this case in the form of a microSD card.
In this example according to the
The advantage of the configuration according to this example is also the possibility that one device with the reader, display 14 and keyboard 13 can be used by several merchants working in shifts in one business premises, while the payments are processed for the benefit of the corresponding merchant who has his ICC card 9 inserted in the reader at the moment.
Besides the elements mentioned in the previous examples, the Sales Device 2 according to the
The result from the cash registrar 10 is transferred into the Sales Device 2 over the cable connection 16. There the result appears on the display 14 and the merchant confirms it by a confirming button. Subsequently the process runs in the same way as if the paid amount was entered over the Sales Device's 2 keyboard 13. In this configuration it would not even be necessary for the Sales Device 2 to contain a keyboard 13 for the entry of the paid amount, however due to the usability of the Sales Device 2 in various systems' point of view, the keyboard 13 is part of the Sales Device 2 even in this example.
The industrial applicability is obvious. With this invention, it is possible to industrially and repeatedly manufacture and use the POS payment terminals, which are created temporarily for the purpose of a specific payment by a connection of Sales Device and the mobile communication device. The necessary structures of the merchant's POS terminal are then created only after the connection with the removable memory card in the mobile communication device of the paying user is established.
Number | Date | Country | Kind |
---|---|---|---|
00032-2009 | May 2009 | SK | national |
50009-2010 | Mar 2010 | SK | national |
50012-2010 | Apr 2010 | SK | national |
50016-2010 | Apr 2010 | SK | national |
This application is a divisional of U.S. patent application Ser. No. 12/899,378 filed Oct. 6, 2010, now U.S. Pat. No. 8,606,711 which is a continuation of PCT Application No. PCT/IB2010/051915, filed May 1, 2010, which claims priority from Slovak patent applications nos. PP00032-2009, filed May 3, 2009, PP50009-2010, filed Mar. 27, 2010, PP50012-2010, filed Apr. 8, 2010, and PP50016-2010, filed Apr. 19, 2010. The entire disclosure of each of the above-referenced patent applications is hereby incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4962415 | Yamamoto et al. | Oct 1990 | A |
5288979 | Kreft | Feb 1994 | A |
5303198 | Adachi et al. | Apr 1994 | A |
5574470 | de Vall | Nov 1996 | A |
5578808 | Taylor | Nov 1996 | A |
5608417 | de Vall | Mar 1997 | A |
5671279 | Elgamal | Sep 1997 | A |
6062472 | Cheung | May 2000 | A |
6070795 | Feiken | Jun 2000 | A |
6070796 | Sirbu | Jun 2000 | A |
6154181 | Hu-Guo et al. | Nov 2000 | A |
6292561 | Benson | Sep 2001 | B1 |
6323064 | Lee et al. | Nov 2001 | B1 |
6450407 | Freeman et al. | Sep 2002 | B1 |
6615243 | Meggeid et al. | Sep 2003 | B1 |
6745935 | Grieu et al. | Jun 2004 | B1 |
6828670 | Hayana et al. | Dec 2004 | B2 |
6847816 | Sarradin | Jan 2005 | B1 |
6976011 | Capitant et al. | Dec 2005 | B1 |
7051429 | Kerr et al. | May 2006 | B2 |
7083085 | Daniels et al. | Aug 2006 | B1 |
7364092 | Narendra et al. | Apr 2008 | B2 |
7374100 | Jei et al. | May 2008 | B2 |
7436965 | Sherman | Oct 2008 | B2 |
7458518 | Fukuda et al. | Dec 2008 | B2 |
7478065 | Ritter | Jan 2009 | B1 |
7481358 | Honjo et al. | Jan 2009 | B2 |
7568065 | D'Athis | Jul 2009 | B2 |
7581678 | Narendra et al. | Sep 2009 | B2 |
7689932 | Maktedar | Mar 2010 | B2 |
7775442 | Saarisalo | Aug 2010 | B2 |
7775446 | Ochi et al. | Aug 2010 | B2 |
7805615 | Narendra et al. | Sep 2010 | B2 |
7828214 | Narendra et al. | Nov 2010 | B2 |
8055184 | DiMartino et al. | Nov 2011 | B1 |
8127999 | Diamond | Mar 2012 | B2 |
8341083 | Jain | Dec 2012 | B1 |
8355670 | White | Jan 2013 | B2 |
8596547 | Diamond | Dec 2013 | B2 |
8602304 | Cohen | Dec 2013 | B2 |
8620299 | Kumar | Dec 2013 | B2 |
8700003 | Klein | Apr 2014 | B2 |
8763900 | Marcus | Jul 2014 | B2 |
8977569 | Rao | Mar 2015 | B2 |
8990121 | Guise | Mar 2015 | B1 |
20010005832 | Cofta et al. | Jun 2001 | A1 |
20010033013 | Lee | Oct 2001 | A1 |
20020023963 | Luu | Feb 2002 | A1 |
20020062249 | Iannacci | May 2002 | A1 |
20020131245 | Clayton et al. | Sep 2002 | A1 |
20020147658 | Kwan | Oct 2002 | A1 |
20020163479 | Lin | Nov 2002 | A1 |
20020164031 | Piikivi | Nov 2002 | A1 |
20030055738 | Alie | Mar 2003 | A1 |
20030105930 | Okamoto | Jun 2003 | A1 |
20030138135 | Chung et al. | Jul 2003 | A1 |
20040066278 | Hughes et al. | Apr 2004 | A1 |
20040087339 | Goldthwaite et al. | May 2004 | A1 |
20040104268 | Bailey | Jun 2004 | A1 |
20040127256 | Goldthwaite et al. | Jul 2004 | A1 |
20040235450 | Rosenburg | Nov 2004 | A1 |
20050011960 | Koike et al. | Jan 2005 | A1 |
20050072595 | Cho | Apr 2005 | A1 |
20050092835 | Chung et al. | May 2005 | A1 |
20050116050 | Jei et al. | Jun 2005 | A1 |
20050125745 | Engestrom | Jun 2005 | A1 |
20050222949 | Inotay et al. | Oct 2005 | A1 |
20050269401 | Spitzer et al. | Dec 2005 | A1 |
20050269402 | Spitzer et al. | Dec 2005 | A1 |
20060083955 | Kanouda et al. | Apr 2006 | A1 |
20060143578 | Maktedar | Jun 2006 | A1 |
20060146023 | Kidron | Jul 2006 | A1 |
20060152288 | Peng et al. | Jul 2006 | A1 |
20060186209 | Siva et al. | Aug 2006 | A1 |
20060196931 | Holtmanns et al. | Sep 2006 | A1 |
20060219776 | Finn | Oct 2006 | A1 |
20060224470 | Garcia et al. | Oct 2006 | A1 |
20060226217 | Siva et al. | Oct 2006 | A1 |
20060255160 | Winkler | Nov 2006 | A1 |
20070014407 | Siva et al. | Jan 2007 | A1 |
20070014408 | Siva et al. | Jan 2007 | A1 |
20070016957 | Seaward et al. | Jan 2007 | A1 |
20070050871 | Mashhour | Mar 2007 | A1 |
20070083772 | Harada et al. | Apr 2007 | A1 |
20070106564 | Matotek et al. | May 2007 | A1 |
20070125840 | Law et al. | Jun 2007 | A1 |
20070135164 | Lee | Jun 2007 | A1 |
20070152035 | Adams et al. | Jul 2007 | A1 |
20070158438 | Fukuda et al. | Jul 2007 | A1 |
20070171079 | Saito | Jul 2007 | A1 |
20070233615 | Tumminaro | Oct 2007 | A1 |
20070235539 | Sevanto et al. | Oct 2007 | A1 |
20070241180 | Park et al. | Oct 2007 | A1 |
20070278290 | Messerges et al. | Dec 2007 | A1 |
20070293155 | Liao | Dec 2007 | A1 |
20080011833 | Saarisalo | Jan 2008 | A1 |
20080017704 | VanDeburg et al. | Jan 2008 | A1 |
20080048036 | Matsumoto et al. | Feb 2008 | A1 |
20080051122 | Fisher | Feb 2008 | A1 |
20080059375 | Abifaker | Mar 2008 | A1 |
20080093467 | Siva et al. | Apr 2008 | A1 |
20080111756 | Ochi et al. | May 2008 | A1 |
20080120129 | Seubert et al. | May 2008 | A1 |
20080129629 | Kimura et al. | Jun 2008 | A1 |
20080207124 | Raisanen et al. | Aug 2008 | A1 |
20080233906 | Mitomo et al. | Sep 2008 | A1 |
20080250244 | Baentsch et al. | Oct 2008 | A1 |
20080270246 | Chen | Oct 2008 | A1 |
20090043935 | Huomo et al. | Feb 2009 | A1 |
20090063312 | Hurst | Mar 2009 | A1 |
20090063340 | Chiang | Mar 2009 | A1 |
20090065571 | Deepak | Mar 2009 | A1 |
20090065572 | Deepak | Mar 2009 | A1 |
20090069049 | Deepak | Mar 2009 | A1 |
20090069050 | Deepak et al. | Mar 2009 | A1 |
20090069051 | Deepak et al. | Mar 2009 | A1 |
20090069052 | Deepak et al. | Mar 2009 | A1 |
20090070272 | Jain | Mar 2009 | A1 |
20090070691 | Deepak | Mar 2009 | A1 |
20090070861 | Deepak | Mar 2009 | A1 |
20090088077 | Brown et al. | Apr 2009 | A1 |
20090098825 | Huomo et al. | Apr 2009 | A1 |
20090108063 | Deepak et al. | Apr 2009 | A1 |
20090119190 | Realini | May 2009 | A1 |
20090124273 | Back | May 2009 | A1 |
20090132418 | Morsillo et al. | May 2009 | A1 |
20090143104 | Loh et al. | Jun 2009 | A1 |
20090157936 | Goss et al. | Jun 2009 | A1 |
20090191812 | Teruyama et al. | Jul 2009 | A1 |
20090193491 | Rao | Jul 2009 | A1 |
20090199206 | Finkenzeller et al. | Aug 2009 | A1 |
20090199283 | Deepak | Aug 2009 | A1 |
20090200371 | Kean et al. | Aug 2009 | A1 |
20090261172 | Kumar et al. | Oct 2009 | A1 |
20090265544 | Moona et al. | Oct 2009 | A1 |
20090265552 | Moshir et al. | Oct 2009 | A1 |
20090287589 | Fivel | Nov 2009 | A1 |
20090298540 | Siva et al. | Dec 2009 | A1 |
20090307139 | Mardikar et al. | Dec 2009 | A1 |
20090307142 | Mardikar | Dec 2009 | A1 |
20090319287 | Hammad et al. | Dec 2009 | A1 |
20100012721 | Jain et al. | Jan 2010 | A1 |
20100023449 | Skowronek et al. | Jan 2010 | A1 |
20100044444 | Jain et al. | Feb 2010 | A1 |
20100045425 | Chivallier | Feb 2010 | A1 |
20100062808 | Cha et al. | Mar 2010 | A1 |
20100063893 | Townsend | Mar 2010 | A1 |
20100082490 | Rosenblatt et al. | Apr 2010 | A1 |
20100181377 | Chen et al. | Jul 2010 | A1 |
20100197224 | Lahdenniemi et al. | Aug 2010 | A1 |
20100203870 | Hubinak et al. | Aug 2010 | A1 |
20100205432 | Corda et al. | Aug 2010 | A1 |
20100213265 | Siva et al. | Aug 2010 | A1 |
20100258639 | Florek et al. | Oct 2010 | A1 |
20100262503 | Florek et al. | Oct 2010 | A1 |
20100264211 | Jain et al. | Oct 2010 | A1 |
20100274677 | Florek et al. | Oct 2010 | A1 |
20100274726 | Florek et al. | Oct 2010 | A1 |
20100323617 | Hubinak et al. | Dec 2010 | A1 |
20110264543 | Taveau et al. | Oct 2011 | A1 |
20110269438 | Narendra | Nov 2011 | A1 |
20110282753 | Mullen et al. | Nov 2011 | A1 |
20140365374 | Baldwin | Dec 2014 | A1 |
20150170138 | Rao | Jun 2015 | A1 |
20150363377 | Dojo | Dec 2015 | A1 |
20160071089 | Boivie | Mar 2016 | A1 |
Number | Date | Country |
---|---|---|
1450782 | Oct 2003 | CN |
1627321 | Jun 2005 | CN |
1835007 | Sep 2006 | CN |
1870012 | Nov 2006 | CN |
101013903 | Aug 2007 | CN |
101136123 | Mar 2008 | CN |
101329801 | Dec 2008 | CN |
101339685 | Jan 2009 | CN |
101351819 | Jan 2009 | CN |
10130019 | Jan 2003 | DE |
10 2005 02643 | Dec 2006 | DE |
10 2006 01962 | Oct 2007 | DE |
10 2007 01927 | Oct 2007 | DE |
0704928 | Apr 1996 | EP |
601091 | Dec 1997 | EP |
1365451 | Nov 2003 | EP |
1450233 | Aug 2004 | EP |
1536573 | Jun 2005 | EP |
1729253 | Dec 2006 | EP |
1752902 | Feb 2007 | EP |
1752903 | Feb 2007 | EP |
1785915 | May 2007 | EP |
1943606 | Jul 2008 | EP |
2390817 | Nov 2011 | EP |
0611189 | Sep 1926 | FR |
0611190 | Sep 1926 | FR |
2390509 | Jan 2004 | GB |
2424151 | Sep 2006 | GB |
2432031 | Sep 2007 | GB |
980562 | Feb 2000 | IE |
2003-131808 | May 2003 | JP |
2004-348235 | Dec 2004 | JP |
2005-284862 | Oct 2005 | JP |
2006-033229 | Feb 2006 | JP |
2007-060076 | Mar 2007 | JP |
2007-166379 | Jun 2007 | JP |
2007-304910 | Nov 2007 | JP |
2008-083867 | Apr 2008 | JP |
2002-0012738 | Feb 2002 | KR |
2002-0051696 | Jun 2002 | KR |
2002-0073106 | Sep 2002 | KR |
2003-0005088 | Jan 2003 | KR |
2004-0012401 | Feb 2004 | KR |
2004-0060249 | Jul 2004 | KR |
2004-0089800 | Oct 2004 | KR |
2005-0008622 | Jan 2005 | KR |
2007-0093133 | Sep 2007 | KR |
22595 | Feb 2009 | SI |
WO 2003012717 | Feb 2003 | WO |
WO 2005057316 | Jun 2005 | WO |
WO 2005086456 | Sep 2005 | WO |
WO 2006009460 | Jan 2006 | WO |
WO 2007076456 | Jul 2007 | WO |
WO 2007105469 | Sep 2007 | WO |
WO 2007136939 | Nov 2007 | WO |
WO 2008012416 | Jan 2008 | WO |
WO 2008041861 | Apr 2008 | WO |
WO 2008063990 | May 2008 | WO |
WO 2008105703 | Sep 2008 | WO |
WO 2009014502 | Jan 2009 | WO |
WO 2009087539 | Jul 2009 | WO |
WO 2009118681 | Oct 2009 | WO |
WO 2010011670 | Jan 2010 | WO |
WO 2010023574 | Mar 2010 | WO |
WO 2010032215 | Mar 2010 | WO |
WO 2010032216 | Mar 2010 | WO |
WO 2010041245 | Apr 2010 | WO |
WO 2010044041 | Apr 2010 | WO |
WO 2010097777 | Sep 2010 | WO |
WO 2010122520 | Oct 2010 | WO |
WO 2010128442 | Nov 2010 | WO |
WO 2010131226 | Nov 2010 | WO |
Entry |
---|
“EMV Mobile Contactless Payment: Technical Issues and Position Paper”, www.emvco.com/mobile.aspx, © Oct. 11, 2007, accessed Apr. 20, 2009, 37 pages. |
“NFC Frequently Asked Questions,” NFC for Customers, www.nfc-forum.org., Retrieved from the internet on Nov. 7, 2008, 5 pages. |
Smart Card Alliance, “RF-Enabled Applications and Technology: Comparing and Contrasting RFID and RF-Enabled Smart Cards”, Smart Card Alliance Identity Council, Jan. 2007, 7 pages. |
Smart Card Alliance: “Proximity Mobile Payments: Leveraging NFC and the Contactless Financial Payments Infrastructure a Smart Card Alliance Contactless Payments Council White Paper”, www.smartcardalliance.org, © Sep. 1, 2007, accessed Nov. 7, 2008, 10 pages. |
Madlmayar et al., “Management of Multiple Cards in NFC-Deivces”, LNCS, 2008, 21 pages. |
Wikipedia, “Bluetooth”, Wikipedia, The Free Encyclopedia, http://enwikipedia.orq/wiki/bluetooth, accessed Apr. 8, 2012, 19 pages. |
Wikipedia, “Cellular Frequencies” Wikipedia, The Free Encyclopedia, http://en.wikipedia.orq/wiki/cellular_frequencies, accessed Apr. 8, 2012, 5 pages. |
“Intelligent Mouse”, IBM Technical Disclosure Bulletin, International Business Machines Corp., Thornwood, US, Feb. 1, 1995, 38(2), p. 463. |
Finkenzeller (Ed.), “RFID-Handbuch: Grundlagen und praktische Anwendungen Induktiver Funkanlagen, Transponder und kontaktloser Chipkarten”, Jan. 1, 2002, 225-231 (English abstract attached). |
Number | Date | Country | |
---|---|---|---|
20140058953 A1 | Feb 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12899378 | Oct 2010 | US |
Child | 14072434 | US |
Number | Date | Country | |
---|---|---|---|
Parent | PCT/IB2010/051915 | May 2010 | US |
Child | 12899378 | US |