Source: http://www.google.com/patents/US20070022058?dq=7350717
Timestamp: 2017-04-25 07:35:21
Document Index: 278852466

Matched Legal Cases: ['application No. 60', 'application No. 60', 'application No. 60', 'application No. 60', 'arty 120', 'arty 120', 'art) 406', 'art 408', 'art 408', 'art 406', 'art 408', 'art 406']

Patent US20070022058 - Wireless computer wallet for physical point of sale (POS) transactions - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsMethods and systems provide a secure transaction server (STS); provide an authentic point of sale (POS) device, according to a first authentication parameter of the STS; provide an authentic mobile purchasing device, according to a second authentication parameter of the STS; provide a short-range communication...http://www.google.com/patents/US20070022058?utm_source=gb-gplus-sharePatent US20070022058 - Wireless computer wallet for physical point of sale (POS) transactionsAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS20070022058 A1Publication typeApplicationApplication numberUS 11/488,178Publication dateJan 25, 2007Filing dateJul 18, 2006Priority dateAug 8, 2002Also published asEP1758053A1, US7784684Publication number11488178, 488178, US 2007/0022058 A1, US 2007/022058 A1, US 20070022058 A1, US 20070022058A1, US 2007022058 A1, US 2007022058A1, US-A1-20070022058, US-A1-2007022058, US2007/0022058A1, US2007/022058A1, US20070022058 A1, US20070022058A1, US2007022058 A1, US2007022058A1InventorsYannis Labrou, Jonathan AgreOriginal AssigneeFujitsu LimitedExport CitationBiBTeX, EndNote, RefManPatent Citations (99), Referenced by (393), Classifications (28), Legal Events (4) External Links: USPTO, USPTO Assignment, EspacenetWireless computer wallet for physical point of sale (POS) transactions
CROSS-REFERENCE TO RELATED APPLICATIONS [0001] This application claims the benefit of priority under 35 USC 119(e) to U.S. Provisional Application Ser. No. 60/703,862, entitled WIRELESS WALLET FOR PHYSICAL POINT OF SALE (POS) TRANSACTIONS, by Yannis Labrou and Jonathan Agre, filed Aug. 1, 2005 in the U.S. Patent and Trademark Office, the contents of which is incorporated herein by reference. [0002] This application is a continuation-in-part of U.S. patent application Ser. No. 11/388,202, filed Mar. 24, 2006, entitled “Authentication Services Using Mobile Device,” which claims priority to U.S. Provisional Application Ser. No. 60/669,375 filed Apr. 8, 2005; and also a continuation-in-part of U.S. patent application Ser. No.11/045,484, filed Jan. 31, 2005, entitled “WIRELESS WALLET” which claim priority to U.S. Provisional Application Ser. No. 60/544,300 filed Feb. 17, 2004; and also a continuation-in-part of U.S. application Ser. No. 10/458,205, filed Jun. 11, 2003, which claims the benefit of U.S. provisional application No. 60/401,807, filed Aug. 8, 2002; and also a continuation-in-part of U.S. application Ser. No. 10/628,584 filed Jul. 29, 2003, which claims the benefit of U.S. provisional application No. 60/401,807 filed Aug. 8, 2002; and also a continuation-in-part of U.S. application Ser. No. 10/628,569 filed Jul. 29, 2003, which claims the benefit of U.S. provisional application No. 60/401,807 filed Aug. 8, 2002; and also a continuation-in-part of U.S. application Ser. No. 10/628,583 filed Jul. 29, 2003, which claims the benefit of U.S. provisional application No. 60/401,807 filed Aug. 8, 2002. [0003] This application is also related to pending U.S. patent application Ser. No. 11/388,202, filed Mar. 24, 2006, entitled AUTHENTICATION SERVICES USING MOBILE DEVICE, the entire disclosure of which is hereby incorporated herein by reference and attached hereto. This application is also related to pending U.S. patent application Ser. No. 11/045,484, filed Jan. 31, 2005, entitled WIRELESS WALLET, the entire disclosure of which is hereby incorporated herein by reference and attached hereto. [0004] This application is also related to pending U.S. patent application Ser. No. 10/458,205, filed Jun. 11, 2003; Ser. No. 10/628,584, filed Jul. 29, 2003; Ser. No. 10/628,569, filed Jul. 29, 2003; and Ser. No. 10/628,583, filed Jul. 29, 2003, the entire disclosures of all of which are hereby incorporated herein by reference.
BACKGROUND OF THE INVENTION [0005] 1. Field of the Invention [0006] The present invention relates to a wireless computing apparatus/device for physical Point of Sale (POS) transactions. [0007] 2. Description of the Related Art [0008] There is a need to improve payment speed at a physical POS. There is also a need to improve the cost of a transaction with the physical POS using a wireless communication computing apparatus. There is also a need to reduce the size of messages for communication efficiency in short-range communication methods. SUMMARY OF THE INVENTION [0009] The present invention provides a wireless communication computing apparatus/device for physical Point of Sale (POS) transactions. For example, a mobile phone and/or a personal digital assistant (PDA) wireless communication wallet for physical POS transactions. [0010] The above as well as additional aspects and advantages will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the described embodiments. [0011] Methods and systems providing a secure transaction server (STS); providing an authentic point of sale (POS) device, according to a first authentication parameter of the STS; providing an authentic mobile purchasing device, according to a second authentication parameter of the STS; providing a short-range communication method between the POS device and the mobile purchasing device; correlating by the STS a personal identification entry (PIE) and the authentic mobile purchasing device; transmitting, by the POS device, a time dependent transformed secure POS authenticable POS purchase action to the STS; inputting the PIE to the mobile purchasing device to transmit a time dependent transformed secure user authenticable POS purchase action to the POS device via the short-range communication method; and approving, by the STS, the POS purchase action for the POS device and for the mobile purchasing device, according to the authentic POS device, and according to the authentic mobile purchasing device and the STS correlating of the PIE and the authentic mobile purchasing device. [0012] According to an aspect of the embodiments, the POS purchase action identifies payment for a good and/or a service.
BRIEF DESCRIPTION OF THE DRAWINGS [0013] The above-described aspects and advantages together with other aspects and advantages will become apparent and more readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which: [0014] FIG. 1 is a diagram of a computer system 100 to provide a mobile wireless communication apparatus to a physical point of sale (POS) transaction service, according to an embodiment of the present invention, [0015] FIG. 2 is a functional block diagram of Universal Pervasive Transaction Framework Secure Agreement Submission (UPTF SAS) system architecture to execute a mobile device POS authenticable transaction, according to an embodiment of the present invention, [0016] FIG. 3 is a diagram of UPTF mobile device POS authenticable transaction messages based upon Secure Agreement Submission (SAS) protocol to provide an authenticable mobile POS service, according to an embodiment of the present invention, [0017] FIG. 4 is a system flow diagram of provisioning a mobile POS, according to an embodiment of the present invention, and [0018] FIGS. 5-16 are flowcharts of mobile device to POS authenticable transactions, according to the embodiments of the present invention.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0019] Reference will now be made in detail to the present embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the like elements throughout. The embodiments are described below to explain the present invention by referring to the figures. [0020] The described embodiments provide a wireless communication computing apparatus/device for physical Point of Sale (POS) transactions. For example, a mobile phone and/or a personal digital assistant (PDA) wireless communication wallet for physical POS transactions. The discussed methods and apparatuses and variations improve on the speed of a payment at a physical POS, the cost of the transactions since they do not always require that the mobile phone connect to the wireless Internet or cellular telephone network for the transaction to be authenticated and approved. In addition, the size of the messages is reduced for short-range communication methods. [0021] FIG. 1 is a diagram of a computer system 100 to provide a mobile wireless communication apparatus to a physical point of sale (POS) transaction service, according to an embodiment of the present invention. According to the embodiments, a user 102 uses a mobile device 104, such as (without limitation) a mobile phone or a PDA, with wireless communication capability, to transact with a Point of Sale (POS) device 103, such as (without limitation) a cash register, of a provider 106, for example, to purchase an item or receive a service, etc. According to an aspect of the embodiments, the POS 103 can be another mobile device 104, such as another mobile phone. According to an aspect of the embodiments, a provider 106 operates one or a plurality of POSs 103. According to an aspect of the embodiment, the provider 106 and the POS 103 can be collapsed together. The mobile device 104 can be any mobile wireless communication computing device or mobile radio computing device, including, without limitation, a mobile phone, that wirelessly communicates (e.g., wireless Internet or mobile phone network 211) with other mobile devices 104 a-n, with a secure transaction server 120, or with a POS 103, or any combinations thereof. According to an aspect of the embodiments, the mobile device 104 has one or more short-range communication methods 210 implemented therein, for example (without limitation), image, audio, and/or RF, to communicate with the POS 103. [0022] According to an aspect of the embodiments, the invention improves using a mobile device 104, such as a mobile phone 104, for physical POS transactions, within the context of the Universal Pervasive Transactions Framework (UPTF). One main concept behind the discussed methods and variations is that the consumer's or customer's mobile phone 104 communicates to the Point of Sale (POS) 103 a transaction message, for example, a UPTF SAS based transaction message, used to authenticate and approve the transaction via: [0023] (1) An image, [0024] (2) An audio signal, [0025] (3) Any short-range wireless connectivity technology, such as (without limitation) a short range RF signal, such as WiFi, Bluetooth, Radio Frequency Identification (RFID), or smart card, Near Field Communication (NFC) signal, or any combinations thereof, or [0026] (4) Any combinations thereof. [0027] According to an aspect of the embodiments, the POS 103 has equipment that can send, receive, and interpret a locally transmitted/received message to re-construct a corresponding UPTF SAS message for UPTF transaction verification protocol. For example, an image interpreter at the POS 103 can decode a UPTF SAS message from an image displayed on the mobile phone's 104 display. Another example is to use an audio processor at the POS 103 that can decode a UPTF SAS message from an audio signal “played” through the mobile phone's 104 speaker to the POS 103 microphone. Another example is an RF signal between the POS 103 and mobile phone 104. The information received by the POS 103 is used to create one or more of the UPTF SAS messages (i.e., POS transaction view or the provider/merchant/payee transaction view) needed for the UPTF transaction verification protocol, which the mobile device 104 and/or the POS 103 (as the case may be) transceive with the STS 120. According to an aspect of the embodiments, the POS 103 transmits to the Secure Transaction Server (STS) 120 the mobile phone 104 provided RF based UPTF SAS message, or an image, audio after converting the same to a corresponding UPTF SAS message; the result of this conversion being a UPTF SAS based digital message. According to an aspect of the embodiments, the POS also transceives, by passing through any user related UPTF SAS messages (e.g., user transaction view generated at the mobile phone 104), such as an image or audio, without any prior conversion of the same to/from the STS 120. The POS 103 can be connected to the STS 120 possibly through a data network that can be a wireless connection and/or a wired connection. [0028] In the case of an image, the POS 103 equipment can be a barcode scanner, preferably one that is capable of processing 2-Dimensional barcodes. In the case of an audio signal, the POS equipment 103 is an acoustic coupler or a DTMF (Dual Tone Multi-Frequency) tone recognizer. A DTMF recognizer (detector) is usable to recognize touchtone entries into over-the-phone customer service systems. [0029] Another method discussed improves on physical POS 103 purchasing by using Short Message Service (SMS) and/or Multimedia Message Service (MMS) messages to transmit UPTF SAS messages among the mobile phone 104, POS 103 and/or the STS120. More generally, SMS messages can be used as the transported mechanism for all types of UPTF transactions (see co-pending UPTF-related patent applications incorporated herein by reference. [0030] The invention can be implemented in any mobile device 104 capable of executing UPTF SAS based Wireless Wallet software 108, in a POS 103 (a computing apparatus) capable of executing the UPTF SAS protocol and POS functions, and a UPTF-SAS based Secure Transaction Server (STS) 120. Companies interested in allowing their users to securely perform transactions from a mobile device 104 can adopt the UPTF SAS protocol. [0031] Therefore, embodiment(s) described herein relate to a mobile device authenticable transaction with the POS 103. According to an aspect of the embodiments, an authenticated or authenticable transaction is based upon Universal Pervasive Transaction Framework Secure Agreement Submission (UPTF SAS) protocol. Universal Pervasive Transaction Framework (UPTF) is a framework for authenticating transactions initiated by a mobile (radio) device. The UPTF SAS protocol is discussed in related pending U.S. patent application Ser. No. 11/388,202, filed Mar. 24, 2006; Ser. No. 11/045,484, filed Jan. 31, 2005; Ser. No. 10/458,205, filed Jun. 11, 2003; Ser. No. 10/628,584, filed Jul. 29, 2003; Ser. No. 10/628,569, filed Jul. 29, 2003; and Ser. No. 10/628,583, filed Jul. 29, 2003, the entire disclosures of all of which are hereby incorporated herein by reference. According to an aspect of the embodiments, a mobile device 104 provides authenticated transaction services according to authenticable transaction view(s) of one or more parties (i.e., in a typical embodiment paired and/or more than two authenticated transaction views), wherein the authenticated transaction views are time, user and software dependent, secured (e.g., encrypted), matched (verified against each other), and transaction party anonymous to the POS 103 (e.g., a transacting party does not have to receive personal/private/confidential information (e.g., account information) of the other transacting party. Therefore, according to the embodiments authentication includes transaction or agreement of parties verification. [0032] FIG. 2 is a functional block diagram of Universal Pervasive Transaction Framework Secure Agreement Submission (UPTF SAS) system 200 architecture to execute an authenticable transaction using a mobile device and a POS, according to an embodiment of the present invention. In FIG. 2 and other figures, color designations are used to highlight features/concepts described, for example, a type of, or a possible type of, communication channel. For example, communication channels may be Virtual Private Network (VPN), mobile phone or cellular network, or unknown by referring to any known type of computer data communication network. The Universal Pervasive Transaction Framework (UPTF) defines a system architecture based upon independent and anonymous transaction agreement views and a communication security protocol called the Secure Agreement Submission (SAS) protocol to transmit the views. Essentially the UPTF offers a vessel, which is able to securely carry the individual views of a transaction agreement, in this case a mobile device POS authenticable transaction (collectively referred to as a mobile device POS transaction), from each party involved in the transaction to a trusted third party for verification, using a communication network which may comprise insecure segments, such as wireless Internet, mobile telephone network or cellular links, short-range communication methods. According to an aspect of the embodiments, a UPTF SAS message is an authorization for a specific transaction at this time. When a mobile POS 104 is used for a POS transaction, the transaction parties are the user 102 and the provider 106 that operates the POS 103 with which the user 102 desires to conduct a transaction. A typical example of a “mobile device POS transaction” agreement view may comprise: “User A, Transaction Token.”
[0033] In FIG. 2, the UPTF SAS protocol encrypts/decrypts a transaction message using a symmetric, secret-key 352 c,m approach where the secret key 352 c,m is producible only by an individual party's mobile device 104 and a trusted third party (e.g., implemented as STS 120) and without transmission of the secret key among the parties. In other words, the UPTF SAS provides an implicit user authentication, because decryption by a trusted third party, such as STS 120, of a sending party's encrypted message, authenticates the sending party. The SAS insures that the authenticity of the parties is verified and during delivery, the privacy of the information is preserved (transaction party anonymity), even when the parties distrust each other and the messages from one party may be forwarded by the other to the third party verification (as the case may be). The UPTF provides the mechanism for the trusted third party 120 to verify that the independent views of the mobile device POS transaction are consistent with each other. [0034] In FIG. 2, after the STS 120 extracts the mobile device POS transaction data from the transaction views received from the parties and the STS 120 verifies the received mobile device POS transaction data, further actions may be needed, which, for example, may be realized by the trusted third party 120 interacting with financial institutions associated with the user payer 102 and the provider (merchant) payee 106 to cause the transfer of the specified funds between the user payer 102 and the provider payee 106. [0035] In FIG. 2, a UPTF based mobile device POS authenticable transaction system architecture comprises a user 102 operating a UPTF device (also referred to as Universal Pervasive Transaction Device—UPTD), such as a mobile phone 104 loaded with a mobile point of sale (POS) application 109 (hereinafter referred to as mobile POS application that can be implemented in software and/or computing hardware), a provider 106 operating another UPTF based device 205, a Secure Transaction Server (STS) 120, and optionally for additional transactions a number of financial institutions (not shown), and several non-secure and secure (as the case may be) communication channels among them. Typically according to an embodiment, the separation of the STS 120 and the provider 106 as shown in FIG. 2 is a logical separation, as a single entity or separate entities (as the case may be) can implement each. [0036] In FIG. 2, according to an aspect of the embodiment described herein, the STS 120 authenticates a mobile device 104 by an authentication parameter(s) 350 to provide an authenticable mobile POS 104. The authentication parameter(s) of the STS is secret information used for encrypting the messages to/from each user 102 mobile POS 104 and provider 106 (POS 103), which are stored in a database storage 203. The STS 120 receives independently generated UPTF SAS mobile device POS authenticable transaction views (described in more detail further below) from both the user 102 and the provider 106 (POS 103) regarding a transaction conducted between them. The STS 120 is able to decode both of the views based upon information from UPTF SAS mobile device POS authenticable transaction messages and the information stored in the STS 120 database 203. Following successful decoding, the STS 120 verifies that the view messages are original, authentic, involve the intended user 102 and provider 106 and that the information fields in the transaction views are consistent with each other. The STS 120 can maintain a log of messaging activity for non-repudiation purposes. Therefore, the authenticable mobile POS 104 mobile POS application 109 is based on a general framework, called the Universal Pervasive Transaction Framework (UPTF), a generic new architecture and security protocol for conducting secure multi-party agreements, using mobile devices over a wireless transport network. The framework is designed to address several key aspects specific to the envisioned pervasive communication, including wireless, environments. [0037] In FIG. 2, according to an aspect of the embodiments, the mobile device 104 mobile POS application 109 communicates with the POS 103 of the provider 106 via any short-range communication method 210 comprising an image, audio (sound, oral/written communication and recognition thereof, such as voice recognition), or wireless communication connectivity technology, or any combinations thereof. The range of the short-range communication 210 can be according to application design from a few inches or less to a predetermined area. The short-range communication 210 is typically non-secure by itself (meaning that the communication channel might not be secure, but the communication channel can carry a protocol, such as the UPTF SAS scheme, that has the desired security properties). Although the embodiments are not limited to such a configuration and the short-range communication 210 can be secure by itself and also carry the UPTF SAS protocol. The mobile device 104 mobile POS application 109 can also communicate with the STS 120 via a wireless communication channel 211, which is typically non-secure, and can be a wireless Internet, a mobile phone network, a local wireless network, or any combinations thereof. According to an aspect of the embodiment, the wireless communication channel 211 includes SMS and/or MMS. Thus, wireless UPTF SAS based messages are transportable over the wireless communication channel 211 using SMS messages to/from the STS 120, or using HyperText Transfer Protocol (HTTP), or web service calls, or other known wireless message transport services, or any combinations thereof. The provider 106 and the STS 120 can be separate or collapsed (as the case may be), and the provider 106 communicably connects with the STS 120 via known secure, non-secure, wire or wireless, or any combinations thereof communication channel(s) 220. [0038] FIG. 3 is a diagram of UPTF mobile device POS authenticable transaction messages based upon Secure Agreement Submission (SAS) protocol to provide an authenticable mobile POS service, according to an embodiment of the present invention. The SAS protocol is used for encrypting and submitting views of desired UPTF based authenticable transactions. The message structure and encryption mechanism of SAS are designed to provide many of the desired security properties in an insecure pervasive communication, including wireless, environment for transactions, such as: [0039] Authentication: the agreement parties and the verification party are authenticated to each other, as is the integrity of the agreement group; [0040] Anonymity: agreement parties may remain anonymous to each other and personal and/or other account related information is not revealed to the other party; [0041] Protection of the agreement content: the agreement is kept private, it is tamper-resistant, non-replayable, and strong non-repudiation properties are provided. In particular, a continuously changing, time dependent, device specific key is used to encrypt each view. [0042] The underlying SAS algorithms are well-suited for a system using low-cost user devices, which have limited computing resources, while minimizing the complexity of use for the user. In addition, some of the information necessary to use the SAS, in particular a Personal Identification Entry (PIE), is not permanently stored on the mobile POS 104 and not included in any data transmissions, so if the mobile POS 104 is lost or stolen, the mobile POS 104 cannot be used. Additional details of the SAS and the encryption mechanism are provided with reference to FIG. 3, as follows. [0043] FIG. 3 shows the internal structure and the generation process of a mobile device POS authenticable transaction view messages 402, 404 (i.e., UPTF SAS authenticable transaction messages among a mobile device 104, a POS 103 and an STS 120). The provider 106 includes a provider device 103, such as a POS 103, on which the provider UPTF based transaction messages are implemented. The UPTF SAS based views 402, 404 are also implemented in software and/or computing hardware as the mobile POS software 109 that is executed in the mobile POS 104. Since the views 402, 404 from the user 102 and the provider 106, respectively, are symmetrical, the user's 102 view 402 is only described. The identifiers used in FIG. 3 are explained below: [0044] DIDc: device ID, a unique identifier for the mobile POS 104 (the user consumer (c) or source transaction party). [0045] DIDm: device ID, a unique identifier for the provider 106 POS device 103 (the merchant (m) or destination transaction party). [0046] RSN: random sequence number. [0047] TS: local current timestamp. [0048] TID: transaction ID, a unique identification number assigned to an agreement, which is maintained by the STS 120 to identify corresponding UPTF agreement views 402, 404. For example, a purchase transaction identifier uniquely identifying a particular purchase. [0049] MD: message digest 410 [0050] PIE: Personal identification entry, a user and STS 120 maintained input secret entry, such as an alphanumeric string. In a typical embodiment described herein, the PIE is only maintained by the user and the STS 120, is not known to and/or maintained by another party to a transaction and/or any financial institutions and is temporally known as an intermediate parameter to the mobile POS 104 of the user 102 for encrypting the user transaction view 402. More particularly, the PIE is not included in transaction messages (e.g., UPTF SAS messages and/or SAS based informational messages) and, thus, the mobile POS 109 does not transmit the PIE. The PIE can be non-secure by being a substantially short alphanumeric string, such as a 4 digit number. The user enters the PIE whenever the user attempts a transaction. Preferably the PIE is issued to the user when the user registers for the authenticable mobile POS service using a client device 104, which executes the mobile POS 109. The user can also select the PIE at such time of registration. The PIE is, however, a piece of highly secure information in the sense that it is never transmitted during the UPTF protocol execution, it is only known to the user and the STS 120, and its secrecy should be well protected. The PIE can be input by the user on a mobile POS 104 in a secure fashion or it may be deterministically generated using a biometric device, such as a fingerprint sensor. For example, a computation applied on the fingerprint data received from a fingerprint sensor can be used to generate a PIE that is initially communicated by the user to the STS 120. Whenever the user attempts a transaction, the user applies her finger to the fingerprint sensor, thus generating the PIE. The PIE is not kept in permanent storage on the mobile POS 104, but is used as an intermediate parameter required for the generation of the encryption key for a transaction and the mobile POS 104 should not retain the PIE for a period longer than a transaction execution time as determined according to application criteria. If a particular implementation of the present invention uses a form of PIE that is not convenient for a user to input for each agreement transaction and the device needs to store its user's PIN, the storage must be secure and tamper-resistant. According to another aspect of the embodiment, the PIE can be a user 102 biometric input data. [0051] As shown in the FIG. 3, a view 402 comprises a cipher text part (or encrypted part) 406 and a perceptible (e.g., plaintext) part 408. A plaintext part 408 includes the TID, the DlDc of the mobile POS 104 generating the view 402, and the local current timestamp (TS) of device 104. The TS, among other functions described herein, is also used to prevent transaction replay. The encrypted part 406 includes two critical fields: the agreement data (transaction data) and the DIDm of the provider's 106 POS 103 device involved in the agreement. The DIDm is the minimum necessary reference field to provide the desired verification properties of the UPTF protocol. According to an aspect of the embodiments, the DIDm is communicably provided to the user 102 and/or the mobile POS 102 via any known methods, for example, via the short-range communication 210. Therefore, a user can execute a mobile POS 104 authenticable transaction with a transaction party based upon a PIE and a mobile POS application 109 authentication parameter RSN, and authenticable transaction messages comprising an identifier of the mobile device POS 104, an identifier of the transaction party, and an identifier for the transaction (for example, an identifier and/or other transaction related data, such as a type of transaction, payment amount, etc.), thereby providing the mobile POS 104 based upon a combination of the mobile POS application 109 at the mobile POS 104 and the STS 120 association of the PIE and an authentication parameter, which is known and/or determinable by the devices 103, 104 and 120, with the user 102, and exchange of the authenticable transaction messages among the user 102, the provider 106 (POS 103) and the STS 120. [0052] First, DIDc and the TS obtained from the mobile device 104 local clock (and/or as provided as a part of the agreement data) are utilized by the device's 104 pseudorandom number generator to generate a time-dependent RSN. Therefore, the parameters of the generator are particular to each device 104. The encryption key K is then generated from the RSN and user input PIE (shown in FIG. 3 with orange coloring), where the PIE is provided from or generated by the STS 120. Firstly, the RSN and PIE are combined using a function F and then a hash function H is applied to the result (typically a string) to generate the encryption key: [0053] K=H (F ((PIE, RSN)) [0054] A message digest 410 function can be applied to the agreement data, the DIDm, and the DIDc to generate a MD of the view. According to an aspect of the embodiments, the MD 410 is generated by applying a hash function to the UPTF SAS agreement data as shown in FIG. 3 to shorten the same. The MD can further strengthen the security by ensuring that no other party has tampered with or modified the contents of the view 402 in any way. The encryption algorithm with the encryption key K is then applied to the MD, the agreement data, the DIDc, and the DIDm to generate the cipher text part of the view 402, as shown in FIG. 3 with peach coloring. For further protection, the SAS protocol uses random message padding in order to further prevent “known-text” attacks. According to an aspect of the embodiment described herein, the embodiment uses Advanced Encryption Standard (AES) for encryption, a Keyed-Hashing for Message Authentication (HMAC)-based scheme for random number generation, and SHA1 Secure Hash Algorithm for the hash function. [0055] The STS 120 has sufficient prior knowledge of the functions and specific parameters used by each device 104 in the encryption process, so that when combined with the plaintext portions of a message 402, 404, it is possible to decrypt the message 402, 404 by reversing the above process. For example, from the plaintext part 408 of the view 402, the STS 120 recovers the DIDc and TS, which are used to look-up the customer's 102 PIE and other parameters of the RSN generator that can be stored in the STS 120 database 203. These are used to compute the RSN. The encryption key K can then be computed using the same method with which the device 104 generates the encryption key. The cipher text part 406 of the view message 402 is then decoded. [0056] After all applicable fields of the user 102 view 402 are acquired, the STS 120 locates the provider's 106 view 404 for the same transaction, using the DIDm and TID included in the previously decoded user 102 view 402. After going through a similar decryption process, the decoded fields of the agreement data of the provider 106 view 404 are compared with the corresponding fields from the user 102 view 402. If all applicable corresponding fields match (correspond according to application design), the received views 402, 404 are considered verified. Further processing is then carried out and external executions are triggered as necessary. [0057] Any responses from the STS 120 to the user 102 or provider 106 are encrypted by the STS 120 using the same encryption methods and using the parameters for the destination devices 104, 103 and the TS of the original transaction. Only the intended recipient can decrypt the response message, insuring privacy protection and authentication of the STS 120. [0058] Another example encryption key generation for the UPTF SAS is described herein. In FIG. 3, using the view 402, the key KEYc is a hash of a RSNc and a PIEc; the detailed key generation procedure is as follows: [0059] The initialization data for the RSNc are created when the STS 120 creates a new authenticable mobile POS service account (e.g., when the mobile POS 109 is created or initialized by the STS 120). Specifically: [0060] 1. a random 128-bit seed is generated using a software service function. [0061] 2. a random 160-bit initialization timestamp is created also at new authenticable mobile POS service account creation time, using software service function. Therefore, the STS 120 can generate or provide device 104 specific initialization parameters of a random number and an initialization time stamp, both of which are provided (installed) via the mobile POS application. 109 to the mobile device 104. [0062] The PIE creatable by the STS 120 when a new account is created at the STS 120, as follows: a 32-byte random value is created using a software service function, convert each byte to a decimal value string, and concatenate them all to produce a long string. Randomly chop 4 digits from this string to create PIE. [0063] When the key needs to be created in order to encrypt a transaction message, the following steps take place: [0064] 1. A 160-bit current timestamp is generated, as follows: [0065] a. Convert current time to string, for example, converting the current time to a 16 characters string, e.g., 5:04 pm, Jan. 26, 2006 is written in “0000170401262006.”
[0066] b. Take the string and a one way function to output another value, for example by hashing the current time string using SHA1 algorithm, which produces a 160-bit output. [0067] 2. XOR an init timestamp and current timestamp to produce a 160-bit output. This operation is essentially a form of deterministically calculating a difference between two values of time (i.e., a deterministic transformation between two values). [0068] 3. Use the 128-bit seed software authentication parameter as data, and the XORed value of the two time stamps as the key, compute the HMAC result (a 160-bit value). The result of the HMAC is the RSNc. Use of the HMAC accommodates unpredictability in the RSNc generation. [0069] 4. Chop the first 128-bit of the HMAC result, combine (e.g., concatenate) with the 32-bit PIE (convert from a 4 digit string) for a 160-bit value. [0070] 5. Compute the hash (SHA1) value of the 160 bit stream in operation (4), and chop the first 128 bit as the final key. [0071] In the encrypted part of the message a hash of the transaction part of the message (with the padding) using SHA1 (alternatively a CRC can be used) is used. [0072] In the above-described embodiment, the values of a number of bits are provided as unlimiting examples, and the present invention is not limited to a specific number of bits values. Therefore, as illustrated with reference to FIGS. 2 and 3, a UPTF SAS based transaction requires a device 104 which provides device-specific parameters that determine a device-specific and time-specific key and an operator for the device 104 who provides a PIE determinable only by the STS 120 and the operator. The combination of the two is required for an encrypted transaction request that can be validated by the STS 120. Intercepting one (or more) transaction message and successfully decrypting it would not be sufficient for purposes of inferring either the PIE, or the device specific parameters employed in the key generation process. Moreover, a single, time-dependant key is not re-usable because of the pair-wise agreement notion of transactions processed by the STS 120. [0073] According to an aspect of the embodiments, the STS 120 can reset the RSN seed after every successful response from STS 120 to a device 103, 104; after that the STS 120 will expect the new seed to be used by the devices 103, 104. The seed can be derived as follows: [0074] (1) use a predetermined portion of the message padding, and/or [0075] (2) include the new seed in the STS's response (in the transactional content of the response) to the devices 103, 104. [0076] FIG. 4 is a system flow diagram of provisioning (i.e., “providing a service,” which includes distribution to a user and associated system actions) a mobile POS 104, according to an embodiment of the present invention. In FIG. 4, a mobile phone is used as an example mobile POS 104. A method, comprising, at operation 450, a user 102 logs into a mobile phone POS service registration site 205. For example, the provider 106 and/or the STS 120 with which various providers 106 participate can provide the mobile POS service registration. At operation 452, the user selects a mobile POS service, which according to an embodiment is a mobile POS application 109 download request from the provider 106. However, the embodiments are not limited to a configuration of downloading a mobile POS application 109 to the mobile phone 104, and a mobile POS 104 can be activated through other techniques, such as (without limitation) pre-installed software and/or computing hardware (e.g., an integrated circuit), so long as a mobile POS 104 authenticable by the STS 120 is provided. At operation 454, the provider 106 device 205 communicably connects with the STS 120 for providing a mobile POS 104. [0077] In FIG. 4, the method at operation 454 further comprises initializing, at the STS 120, a mobile POS application 109 with software authentication parameter(s), as an authentic mobile POS application 109. Also, at operation 454, correlating, at the STS 120, a personal identification entry (PIE) (e.g., a PIN) and an identifier of the mobile phone 104 with the authentic mobile POS application 109. At operation 456, the PIN can be communicated to the user 102. Of course, at operation 450, the user 102 can supply a PIN. At operation 458, installing, in the mobile phone 104, the authentic mobile POS application 109. According to an aspect of the embodiment, at operation 458, the mobile phone 104 receives a Short Message Service (SMS) with a download link to the authentic mobile POS application 109. At operation 462, the user 102 can download the authentic mobile POS application 109. When the authentic mobile POS application 109 is installed in the mobile phone 104, the user can execute, at the mobile phone 104, the installed authentic mobile POS application 108 using the PIE (e.g., PIN) to execute a mobile phone POS authenticable transaction as an authenticable mobile POS 104. [0078] According to an aspect of the embodiment described herein, at operation 454, one or more software authentication parameters are selected, which can be (without limitation) creation of a new seed, such as a new random seed number, and an initialization time. At operation 454, the STS 120 stores in a database 203, a unique identifier (referred to as Device ID, or DID) for the mobile phone 104, which can, for example, be a mobile phone number of the mobile phone 104 or some randomly generated globally unique identifier (GUID), a mobile phone carrier (as the case may be), or the software authentication parameter(s), and the generated PIE, or any combinations thereof. According to an aspect of the described embodiment, a mobile phone number can also be used as a device identifier for the mobile phone 104. The unique identifier (device ID (DID)) of the mobile phone 104 is used by the STS 120 to correlate a transaction message with the authentic mobile POS application 109 (i.e., to correlate the DID with the software authentication parameter(s) and the PIE stored at the STS 120, so that the STS 120 can generate a key that corresponds to a device 104 having the DID. The mobile phone number can be used to communicate short messages (e.g., notifications, etc.) with the mobile phone 104 (e.g., Short Message Service (SMS), including (and/or) Multimedia Message Service (MMS)). The mobile phone 104 can be an Internet enabled, according to known techniques, mobile phone. According to an aspect of the embodiment(s) described herein, a mobile device POS authenticable transaction message is bound to a unique combination of a user 102 and a mobile POS 104, the binding to the user is via the PIE and the binding to the device 104 is via the software authentication parameter(s) of the authentic mobile POS app 109. In particular, a transaction is an SAS based encrypted message and the encrypted message can be traced back to a combination of the user 102 and the device 104 through the PIE and the software authentication parameter(s) of the authentic mobile POS application 109. Similar binding applies with respect to the POS 103 transaction messages. [0079] According to an aspect of the embodiments, a variation on the sign-up and registration process, which could be particularly useful for person-to-person payments, in which the payer is the payer mobile POS 104 a and the payee serves as a payee mobile POS 104 b, is described next. This method has the advantage that it does not require that a payee is already signed-up with a payment service to receive payment by a payer mobile POS 104 a. A user with mobile POS application 109 on the mobile phone 104 can make a payment to another mobile phone owner that is not registered yet for the mobile POS service. The first user specifies the recipient of the payment via the mobile phone number of the second user. The second user subsequently receives an SMS at the second user's mobile phone with the aforementioned phone number. The SMS informs (with text) the second user of a pending payment to the second user and includes a link for downloading the mobile POS software 109. A version of the mobile POS software 109 for this specific second user was created at the STS 120 upon receipt of the first payment request to the STS 120 from the first user. Upon completion of the download, the second user needs to register for the mobile POS service to complete receiving payment. To maximize security, it is preferred that the second user does the registration at the provider's website, as discussed with reference to FIG. 4. Alternatively, the registration can be done from inside the mobile POS application 109, by invoking a “new account” action. [0080] Wireless communication computing apparatus/device transactions with a physical Point of Sale (POS) are described next. The methods and systems described have several variations that make tradeoffs between various categories, such as convenience to the customer, security, time of transaction, local communication and cellular network communication. For example, whether a customer needs to type any transaction identifying information into the phone is one category. In the case of a mobile phone, another category is whether the transaction can be accomplished with or without any information transmitted over the cellular network. [0081] METHODS (SYSTEMS): The discussed methods/systems consider the following options to better conform to the requirements of the cell phone-POS purchasing environment and constraints: [0082] Communication mechanisms: Several communication mechanisms are utilized by these methods. These are roughly characterized as “local communication” (short-range communication methods 210) and “remote communication”: [0083] Local communication is considered to be [0084] 1. Image, such as any type of barcode and scanner thereof, camera, scanner, or any combinations thereof at the POS 103 and/or the mobile POS 104. According to an aspect of the embodiments, the barcode system is capable of processing 2-Dimensional barcodes. [0085] 2. Audio, such as any output audio signal or Dual Tone Multi-Frequency tone, or voice, or any combinations thereof, and recognizer(s) thereof at the POS 103 and/or the mobile POS 104. [0086] 3. Radio Frequency (RF) (Radio Frequency Identification (RFID), Bluetooth, WLAN, NFC, etc., or any combinations thereof at the POS 103 and/or the mobile POS 104 [0087] Remote Communication is considered to be [0088] 1. Short Message Service (SMS), Multimedia Messaging Service (MMS) [0089] 2. Wired Internet [0090] 3. Cellular Internet (wireless Internet access through the mobile telephone network as implemented according to known techniques) [0091] Message Lengths: Several options for decreasing the size of the UPTF messages are incorporated. The messages can be either: [0092] 1. The full UPTF message is used as the transaction authorization message, and/or [0093] 2. The Message Digest MD 410 of the mobile POS 104 UPTF message is used as the transaction authorization message of the consumer; using the MD instead of a full UPTF message results in a shorter message length. [0094] 3. One-time transaction code—A one-time use random number, called the C-Nonce, generated by the phone using the UPTF key generation scheme to indicate that the customer authorizes the transaction. [0095] Computation reductions: To avoid burdening the phone or the POS equipment 103, the “local send” messages, or rather, their representations (image or audio signal) can be transmitted “as is” by the POS 103 to the STS 120, i.e., there is no conversion of the signal to a UPTF message at the POS 103; rather the STS 120 performs such conversion. [0096] CONSTRAINTS: To understand the described process flows and the related actions, the following constraints should be taken into consideration. The purpose of these constraints is to further the understanding of why the actions have been defined as they have. [0097] Message Length: If sending a SMS to STS, message length preferably needs to comply with applicable SMS, network, phone model, and/or wireless service provider/carrier (as the case may be) requirements for delivering the short messages. For example, message length might need to be <=160 chars, which means either no padding or use of the UPTF SAS based Message Digest (MD). [0098] If a MD is used there can be no padding since then the STS 120 will not know where the payload of the encrypted message begins and ends. [0099] Some barcode types require MD instead of full encrypted message, because they cannot accommodate a full UPTF message length. [0100] The MD with timestamp and DID requires about 16 bytes (for Timestamp), plus 8 Bytes (for DID), plus possibly 10 Bytes (for TID), plus the MD length (typically 16-20 Bytes, although it can be less), for a total of between 40-54 Bytes (typically). By contrast, a full UPTF message's length can vary between 100 and 1024 bytes depending on the message type and the amount of padding [0101] If the MD is used and the message is sent by SMS or MMS, a TID is necessary for the STS to identify which merchant message the customer message matches with. An alternative is to provide the POS ID and transaction amount to the mobile POS application 109. In general, the mobile POS application's 109 and the POS's 103 UPTF messages are not sent in the same communication, although the embodiments are not limited to such a configuration and the mobile POS software 109 and POS 103 UPTF message can be sent in same communication. [0102] The payment account by the payer 102 selection is always optional, and since some of the embodiments are “off-line” schemes, the selected account can be drawn from default settings. [0103] Regardless of using MD or full message, the DID and timestamp are necessary in the unencrypted part of the UPTF message so that the STS 120 knows where and when the message came from and the STS 120 can successfully decrypt the UPTF message. [0104] ACTIONS: Several variations are described based on whether the phone 104 and the POS 103 use short-range communication 210 and whether the transaction details (e.g., merchant ID, amount) are entered by the customer or received automatically via local 210 or remote communication 211. [0105] Table 1 lists the embodiments and variations therefore as described herein. Table 1 lists mobile device 104 with POS 103 transaction variations including communication modes of the mobile device 104 with the POS 103 and/or the STS 120. In particular, for example, in Table 1, variation 1 is applicable when the mobile phone 104 uses SMS to the STS 120 to communicate a UPTF SAS transaction message, and variation 2 is applicable when the mobile phone 104 uses SMS to the STS 120 or when the mobile phone 104 uses a short-range communication method to the POS 103, and so on. TABLE 1 Variation nos./mobile device 104 communication modes 1 2 2-1 3 3-1 4 4-1 Mobile Device Mode 1: X X X X X Phone uses SMS to STS Mobile Device Mode 2: X X X Phone uses short-range communication method to POS Mobile Device Mode 3: X X Phone receives amount and approves Mobile Device Mode: 4 X X X X POS uses short-range communication to phone [0106] The steps involved with the embodiments and variations thereof are described with reference to FIGS. 5-16. FIGS. 5-16 are flowcharts of mobile device to POS authenticable transactions, according to the embodiments of the present invention. According to an aspect of the embodiments, the user/customer/client 102 and mobile device 104 can be collapsed together, since the mobile device 104 can automatically generate and/or reply to any UPTF SAS based transaction messages, obviating any user input. [0107] FIG. 5 is a flow chart of variation 1: Remote Communications 211 with the mobile POS 104. [0108] Step 500. The merchant (cashier POS 103) sends a UPTF message to the STS 120 requesting a transaction ID and receives a transaction ID (TID) reply from the STS 120. The merchant displays the details of the transaction on a monitor (as in a normal store). This information may include the amount, a transaction ID and/or a POS ID to identify the merchant. Then, the merchant sends a UPTF message to the STS 120, called the M-View 404, with the encrypted portion 406 containing the POS ID, transaction ID, the amount, the Time stamp (but may or may not contain the device ID of the mobile POS 104), using its preferred connection. According to an aspect of the embodiments, if the views 402, 404 do not contain a device ID, the transaction ID (since both the mobile device 104 and the POS 103 point to the transaction identifier) can be usable to bind the views 402, 404 for STS 120 authentication and verification. [0109] Step 502. The customer launches the mobile POS application 109 and enters the transaction ID and/or the POS ID as obtained from the merchant in operation 500. The customer enters the PIN. The customer selects an account. The mobile POS application 109 sends a UPTF message to the STS 120 using a cellular network 211, called the C-View 402. The encrypted portion 406 contains the transaction ID, the account, the time stamp and may or may not contain the POS ID. According to an aspect of the embodiments, the UPTF SAS message 402, 404 agreement data 412 can be explicit transaction information, and/or implicit or abstracted transaction data, such as the transaction identifier (TID) (as the case may be). [0110] Step 504. The STS 120 receives the messages from the merchant 103 and the client 104. The STS 120 decodes the messages and verifies the identity of the parties. The STS authorizes the transaction. The STS 120 sends receipt messages to the merchant using its preferred connection 220 and to the customer over the cellular network 211. [0111] FIG. 5 variation uses the remote messaging over the cellular network 211 to perform the communication from the customer. This customer never explicitly acknowledges the amount of the transaction, except implicitly by optionally typing in the transaction ID and PIN. In general, this method of transaction has been discussed in the above-identified related co-pending patent applications. [0112] FIG. 6 is a flowchart of variation 2: Local Communication 210 between the mobile POS 104 and the POS 103. [0113] Step 600. The merchant optionally sends a UPTF message to the STS requesting a transaction ID (see operation 500). The merchant provides the details of the transaction, for example, on a monitor (as in a normal store). This transaction information may include the amount, a transaction ID and/or a POS ID to identify the merchant 103. [0114] Step 602. The customer launches the mobile POS application 109 and enters the transaction ID and/or the POS ID as obtained from the merchant in operation 600. The customer enters the PIN. The customer selects a payment account. The mobile POS application 109 locally via a short-range communication 210 sends a UPTF message to the merchant 103 using the preferred local medium 210. The message can be a complete C-View 402, where the encrypted portion 408 contains the time stamp, a nonce, and optionally contains the transaction ID, the account, and/or the POS ID. If the length of the message is constrained, it is possible to send a shortened message consisting of the digest or the nonce. [0115] Step 604. The merchant 103 receives the local communication and sends both its UPTF M-View 404 message and the received C-view 402 to the STS 120 via the communication channel 220. For example, the encrypted portion 408 of the M-view 404 containing the POS ID, the amount, the Time stamp, optional Transaction ID (but no device ID), is transmitted from the POS 103 to the STS 120 using a preferred connection 220. [0116] Step 606. The STS 120 receives both the messages from the merchant 103 and the client 104. The STS 120 decodes the messages and verifies the identity of the parties. The STS authorizes the transaction. The STS 120 can send receipt messages to the merchant using its preferred connection 220 and to the customer over the cellular network 211. [0117] FIG. 6 variation uses the local messaging 210 to perform the communication from the customer. For example, after the customer types in the PIN to authorize the transaction, the mobile phone 104 creates a 2-d barcode containing the complete C-View 402 message. The customer holds the phone display to an imager at the POS 103 that records the barcode and creates a digital message. Again, this customer never explicitly acknowledges the amount of the transaction, except implicitly by typing in the transaction ID and PIN. The receipts are delivered by the cellular network 211 to the phone 104. [0118] FIG. 7 is a flowchart of variation 2-1: If the phone 104 is capable of receiving local communication via a short-range communication 210 from the POS 103, then, at operation 706 (606 in FIG. 6), the receipts can be delivered by the STS 120 to the POS 103 and the POS 103 can transmit the customer receipt to the phone 104 via local communication 210. This will avoid the need for the mobile POS 104 to have any remote communication 211, thus reducing communication 211 traffic and cost. [0119] FIG. 8 is a flowchart of variation 3: Local Communication 210 from the POS 103 to the mobile phone POS 104: [0120] Step 800: The POS 103 generates a local message via a short-range communication 210 to the phone 104, called the T-Info that contains the transaction ID, the amount and the POS ID. The POS 103 also generates an M-View 404 and sends the same to the STS 120. [0121] Step 802. The customer starts the mobile POS application 109. The phone 104 receives the local message from the POS 103 and decodes the data. The user is asked to approve the transaction by entering the PIN. The Phone 104 generates a C-View message 402 containing a full UPTF message for the transaction. The phone sends the C-View message 402 via the cellular network 211 to the STS 120. [0122] Step 804. The STS 120 receives the messages 402, 404 from the merchant 103 and the client 104. The STS 120 decodes the messages and verifies the identity of the parties. The STS 120 authorizes the transaction. The STS sends receipt messages to the merchant 103 using its preferred connection 220 and to the customer 104 over the cellular network 211. [0123] FIG. 9 is a flowchart of variation 3.1: This variation uses 2-way local communication 210, i.e., both the phone and the POS are capable of local communication via a short-range communication 210. At operation 900, the C-View 402 is first sent to the POS 103 as a local message, and, at operation 902, the POS 103 relays the same along with the M-view 404 to the STS 120. Also, at operation 904, the merchant 103 sends the phone receipt to the phone 104 as a local message via the short-range communication 210. [0124] FIG. 10 is a flowchart of variation 4. This variation uses the cellular network 211 to send the transaction data to the phone 104. [0125] Step 1000. The merchant 103 provides, for example, displays on a monitor, the details of the transaction (as in a normal store). This information may include the amount, a transaction ID and/or a POS ID to identify the merchant. [0126] Step 1002. The user starts the mobile POS application 109 and enters the PIN. The phone 104 sends a message to the POS 103 to identify itself using local communication 210. The message, called a CN-View 402 contains the device ID and a nonce. [0127] Step 1004. The merchant 103 sends both the M-View 404 and the CN-View 402 to the STS 120. The M-View 404 has the encrypted portion 406 containing the POS ID, transaction ID, the amount, and the Time stamp (but no device ID). [0128] Step 1006. The STS 120 generates a UPTF message for the mobile POS 104 called the T-View that contains the transaction information, including amount, via the cellular network 211, based upon the received M-view 404 and the CN-View 402 in operation 1004. [0129] Step 1008. The customer 104 approves the transaction by selecting OK and a C-View message 402 is generated. The C-View message 402 is sent to the STS 120 over the cellular network 211. [0130] Step 1010. The STS 120 receives the messages 402, 404 from the merchant 103 and the client 104. The STS 120 decodes the messages and verifies the identity of the parties. The STS 120 authorizes the transaction according to the verification. At operation 1012, the STS 120 sends receipt messages to the merchant 103 using its preferred connection 220 and to the customer 104 over the cellular network 211. [0131] The FIG. 10 scheme has the STS 120 send the transaction details to the user for approval. It uses both remote 211 and local communication 210 with the mobile POS 104. FIG. 11 is a variation 4-1 of this scheme that transmits transaction information to/from the STS 120 and the mobile POS 104 by using, at operations 1100, 1101, 1102, 1103, 1104 and 1105, only local communication 210 with the mobile POS 104 via the POS 103. [0132] Benefits of the mobile device 104 communication modes are described next. A benefit of the mobile POS communication mode 1 is the mobile POS 104 only needs to have an SMS plan, but does not need to have a wireless Internet access plan from a wireless communication provider, reducing communication and device cost. A benefit of the mobile POS communication mode 2 is the mobile device 104 only needs short-range communication 210, but does not need to have a wireless Internet access plan or an SMS plan, reducing communication cost. A benefit of the mobile POS communication modes 3 and 4 are to reduce and minimize (as the case may be) user input at the mobile device 104, for example, to a single input PIE corresponding to a transaction type (i.e., a purchase) specification or identification at the mobile POS 104 to conclude a transaction, such as a purchase, providing a substantial new effect of inviting a user 102 purchase. [0133] Additional variations 5-8, mostly derived from the variations discussed above with more detailed options, are discussed with reference to FIGS. 12-16 in which the numerals refer to action numbers described herein. FIG. 12 is an action number legend 1200 for variations 5-8, according to an embodiment of the present invention. First the following lower layer actions are defined: [0134] In FIGS. 13-16, actions 1-3 concern the information displayed by the POS 103. [0135] Action number 1. POS 103 displays a POS Identifier. Such an identifier, e.g., a phone number or a 10-digit unique ID, could be posted on the POS itself [0136] Action number 2. POS 103 displays a transaction identifier. The transaction identifier corresponds to the TID in the UPTF message (per the Secure Agreement Submission protocol). The transaction identifier is dynamically created after the POS begins processing for a new transaction and is preferably generated after the amount of the transaction has been identified and so that the transaction identifier can be cross-referenced with the transaction amount. [0137] Action number 3. The POS 103 displays a purchase amount. [0138] Actions 4-10 concern the information input by the user 102 to the mobile POS 104. [0139] Action number 4. The mobile user starts the mobile POS application 109 on the mobile device 104. [0140] Action number 5. The mobile user selects the physical POS option on the mobile POS application 109. [0141] Action number 6. The mobile user enters the POS identifier in the mobile POS application 109; a POS identifier is deemed as the DID of the POS 103. [0142] Action number 7 (optional). The mobile user enters the transaction identifier in the mobile POS application 109. [0143] Action number 8. The mobile user types her PIN in the mobile POS application 109. [0144] Action number 9 (optional). The mobile user types the purchase amount (amount of the transaction) in the mobile POS application 109. [0145] Action number 10 (optional). The mobile user selects an account from the cache of accounts known to the mobile POS application 109. If for some reason the chosen account is not eligible for payment, the default account (or some other alternate account of the consumer) will be used for the payment. [0146] Actions 11-14 concern the messages and the formats created by the mobile device POS 104. [0147] Action number 11. The mobile POS 104 creates a UPTF message for the specific POS identifier, and optionally an amount of transaction and type of transaction (payment at a physical POS). [0148] Action number 12. The mobile POS 104 creates a UPTF message for the specific transaction identifier, and optionally an amount of transaction and type of transaction (payment at a physical POS). [0149] Action number 13. The mobile POS 104 creates a UPTF message for the type of transaction (payment at a physical POS), without specifying the amount of the transaction, a transaction identifier or a POS identifier. When STS 120 processes this message, the STS will assume that the amount of transaction and the POS identifier (essentially the ID of the other transaction party) are those submitted in the POS's UPTF message. This is possible in a case the POS 103 transmits to the STS 120 its message 404 and the mobile phone's message 402 (hence the two messages arrive in the STS 120 together in the same action) [0150] Action number 14. The mobile phone calculates the message digest (MD) 410 of the encrypted part of 11 or 12 or 13 (FIG. 14); the message digest of the encrypted part of the UPTF message can be much shorter than the encrypted part of the UPTF message. For example, if MD5 (a hash function) is used on the UPTF message, the MD 410 will be 16 bytes and if SHA1 is used the MD 410 is 20 bytes; by contrast, a UPTF message can vary between 100 and 1024 bytes depending on the message type and the amount of padding. The mobile POS application's 109 UPTF message has no padding in this case of using an MD; since there is no way for the STS to know the padding parameters, if the message includes padding the STS 120 will be unable to compute the complete UPTF message and then correctly compute the MD for it. The complete UPTF message comprises of the DID of the mobile POS application 109 (DID of the mobile POS 104) and the timestamp (both unencrypted) and of the aforementioned MD. [0151] Actions 15-21 concerns the generation of the local communication 210 message by the mobile POS 104 and processing of a local communication 210 based message received by the POS 103 from the mobile POS 104. [0152] Action number 15. The mobile POS software 109 generates a barcode representation of the message in 11 or 12 or 13. A 2-D type of barcode is used; 2-D barcodes can “encode” up to 3K bytes. The mobile POS application 109 displays the barcode on a barcode screen, for example, display the barcode on a mobile phone POS 104 display. [0153] Action number 16. The mobile POS software 109 generates an audio signal from the message in 11 or 12 or 13. [0154] Action number 17. The mobile POS software 109 generates a barcode or an audio signal as a series of tones (similar to the tones in touch-tone phones), from the message in action number 14 (message digest based message—FIG. 14). [0155] Action number 18. The user of the mobile POS 104 presents the mobile POS 104 display with the displayed barcode image to a barcode reader attached to the POS 103. The merchant's POS 103 might be equipped with (or is) another mobile POS 103 with a camera that takes a picture of the barcode and either does local processing (extract barcode from image) or sends image to STS 120 for server side processing along with the other POS's message(s). [0156] Action number 19. For example, a POS 103 barcode reader processes the displayed mobile POS 104 barcode by converting the displayed image (barcode) to a series of characters, thus reproducing the UPTF message that was used to generate the barcode in the first place. [0157] Action number 20. The user of the mobile POS 104 starts the playback of the audio signal as she presents it to a microphone of an audio signal processing device that will process the audio signal at the POS 103 or sends the same for processing to the STS 120. [0158] Action number 21. For example, the audio signal processing device at the POS 103 processes the audio signal and converts it to a series of characters, thus reproducing the UPTF message that was used to generate the audio signal in the first place. [0159] Action Number 22 concerns the message generated by the POS 103 to the STS 120. At action number 22, the POS 103 generates its UPTF message for the transaction. The UPTF message does not include the device ID of the mobile phone. This device ID can be inferred by the mobile phone's UPTF message since the POS transmits to the STS its message and the mobile phone's message (hence the two message arrive in the STS together in the same action). [0160] Action numbers 23-26 concern the reception of the local communication by the POS with reference to FIG. 15. [0161] Action number 23. The mobile POS 104 user presents the mobile POS's 104 display to a camera that captures the mobile POS's display (as an image); the camera is attached to the POS 103. [0162] Action number 24. The mobile POS 104 user presents the mobile POS's speaker to a microphone that captures (records) the mobile POS's audio signal (as an audio signal); the microphone is attached to the POS 103. [0163] Action number 25. The camera of 23 transmits the captured image to the STS 120 alongside with the UPTF message generated by the POS 103. [0164] Action number 26. The microphone of 24 transmits the captured audio to the STS 120 alongside the UPTF message generated by the POS 103. [0165] Action numbers 27-32 concern the processing of the messages by the STS 120 and the replies back from the STS 120 to the POS 103 and mobile POS 104. [0166] Action number 27. The Secure Transaction Server (STS) receives a UPTF message from the mobile POS software 109 which was transmitted by the POS 103. [0167] Action number 28. The STS 120 receives a UPTF message from the POS 103, which was transmitted by the POS 103. [0168] Action number 29. The STS 120 compares the mobile POS 104 and POS 103 messages 402, 404, and processes them according to the SAS protocol. [0169] Action number 30. The STS 120 determines whether the transaction should be authorized, according to the SAS protocol. [0170] Action number 31. The STS 120 sends a confirmation UPTF message for the transaction to the POS 103. [0171] Action number 32. The STS 120 sends a confirmation SMS message for the transaction to the mobile POS 104 of the consumer 102. [0172] Action numbers 33-34 concern the use of SMS or MMS to transmit messages with reference to FIG. 16. [0173] Action number 33. The mobile POS application 109 sends a SMS to the STS 120 adding to its content the message of 11 or 12 or 13 or 14. The encrypted part of the message is preferably encoded in HEXadecinal [0174] Action number 34. The mobile POS application 109 sends a MMS to the STS 120 adding to its content the message of 11 or 12 or 13 or 14. The encrypted part of the message is preferably encoded in HEXadecinal. [0175] Actions 35-36 concern the use of RF as the local communication medium 210. [0176] 35. The user of the WW sends a local communication to the POS using a short range RF device such as an RF ID, Bluetooth, UWBV or WiFi. The WW software generates an RF signal from the message in 11 or 12 or 13 or 14. [0177] 36. The POS will recognize the RF communication and will receive the UPTF message. The POS 103 will determine whether the message is intended for this POS by matching included information in the unencrypted portion 408 of the UPTF SAS message 402, such as transaction ID or POS ID. [0178] Action numbers 37-42 concern local communication from the POS 103 to the mobile POS 104. [0179] Action number 37. The POS 103 will display on its monitor a barcode representing information contained in 1, 2, or 3 as local communication 210 to the mobile POS software 109. [0180] Action number 38. The POS 103 will play on its speaker audio signals representing information contained in 1, 2, or 3 as local communication 210 to the mobile POS software 109. [0181] Action number 39. The POS 103 will transmit on its RF signals on its local RF transmitter device representing information contained in 1, 2, or 3 for local communication to the mobile POS software 109. [0182] Action number 40. The camera on the mobile POS 104 and a software module decodes a barcode displayed by the POS 103 for local communication 210 of information contained in 1, 2 or 3 to the mobile POS 104. [0183] Action number 41. The microphone on the mobile POS 104 and a software module decodes an audio signal from the POS 103 for local communication 210 of information contained in 1, 2 or 3. [0184] Action number 42. The local RF receiver device on the mobile POS 104 and a software module receives a local RF signal from the POS 103 for local communication 210 of information contained in 1, 2 or 3. [0185] Another variation is the following. The mobile POS 104 is equipped with a RFID chip (any type of RFID tag; passive, active, or any combinations thereof) or Near Field Communication (NFC) chip. This addition might be simply attached to the mobile device 104, without being integrated to the circuitry of thereof, or it might be part of the circuitry thereof. In the latter case the software 109 of the mobile device 104 can communicate with the RFID or NFC chip. In the former case, the software 109 of the mobile device 104 might not communicate with the RFID or NFC chip; for example the RFID or NFC chip might be issued by the issuer of the mobile POS software 109 and be attached (physically) (e.g., via adhesive or other coupling technology) to the mobile device 104. When the user performs a transaction, the RFID reader at the POS 103 reads the RFID or NFC presence and thus identifies the transacting party. The owner of the mobile POS 104 using the mobile POS software 109 further confirms the transaction, for example, via remote communication with the STS 120. The POS 103 upon reading the RFID or NFC identifier transmits its UPTF message to the STS 120 and the STS 120 waits for the consumer's confirmation and/or authorization UPTF message to arrive from the mobile device 104. In the meantime, the consumer starts the mobile POS application 109, types in a PIN resulting in the mobile POS software 109 transmission of the appropriate UPTF message to the STS 120. Upon STS 120 receipt of this message, the STS 120, according to the UPTF protocol, approves or disapproves the transaction and notifies the transacting parties accordingly. According to an aspect of the embodiments, the STS 120 can authenticably approve the transaction, because the STS 120 has correlated the PIN and the mobile device 120 as identified by the RFID or the NFC. This case requires a wireless transmission of the UPTF message from the mobile device 104 to the STS 120. Alternatively, the mobile POS software 109 may display a barcode or image (as previously discussed) that is processed by the POS 103 (as previously discussed). The advantage of this variation is that it increases the security of using the RFID or NFC alone for purchasing. Alternatively, if the RFID or NFC, is capable of two-way communication and it is integrated with the circuitry of the mobile POS 104, the transmission of the UPTF message from the mobile POS 104 to the POS 103 is transmitted over the RFID or NFC, upon entering of the PIN (on the mobile device 104) by the consumer 102. [0186] A method, and apparatus and computer readable medium, thereof, comprises providing a secure transaction server (STS); providing an authentic point of sale (POS) device, according to a first authentication parameter of the STS; providing an authentic mobile purchasing device, according to a second authentication parameter of the STS; providing a short-range communication method between the POS device and the mobile purchasing device; correlating by the STS a personal identification entry (PIE) and the authentic mobile purchasing device; transmitting, by the POS device, a time dependent transformed secure POS authenticable POS purchase action to the STS; inputting (e.g., by a user and/or automatically from a computer readable medium, such as memory, etc.) the PIE to the mobile purchasing device to transmit a time dependent transformed secure user authenticable POS purchase action to the POS device via the short-range communication method; and approving, by the STS, the POS purchase action for the POS device and for the mobile purchasing device, according to the authentic POS device, and according to the authentic mobile purchasing device and the STS correlating of the PIE and the authentic mobile purchasing device. [0187] An apparatus, comprises means for providing an authentic point of sale (POS) device; means for providing an authentic mobile purchasing device; means for a short-range communication between the authentic POS device and the authentic mobile purchasing device to transmit a time dependent POS purchase action to the authentic POS device; means for receiving the time dependent POS purchase action and for authenticating and verifying the time dependent POS purchase action for the POS device and for the mobile purchasing device, according to the authentic POS device and the authentic mobile purchasing device. According to an aspect of the embodiments, the means for providing the authentic POS, the authentic purchasing device, and the authenticating and verifying the time dependent POS purchase action is the UPTF SAS protocol. [0188] According to an aspect of the embodiment, the POS device 103 and the mobile purchasing device 104 become authentic and the transaction messages become authenticable, according to the STS correlation of each device with respective PIEs, time dependency (for example, use of the Time Stamp in generating the key 352 as described herein), and the STS authentication parameter. According to an aspect of the embodiment, the expression “transmitting” refers to communicating or conveying information or knowledge via an image (e.g., a bar code image), audio, or wireless communication connectivity technology, as described herein. So according to an aspect of the embodiments, for example, in case of a bar code image displayed on the display of the mobile device 104 or in case of audio as the short-range communication method, the transmitting a time dependent transformed secure user authenticable POS purchase action to the POS device comprises generating a bar code image or audio that is a representation of a UPTF SAS protocol transaction message view 402 or 404 as a time dependent transformed secure authenticable transaction message, thus providing a time dependent image or audio to prevent reuse of image or audio for replay or fraudulent transactions. [0189] In view of the above described examples of preferred embodiments, an apparatus 104 suitable for use in implementing the embodiments described herein can be any computing apparatus or machine, such as (in an unlimiting example) a programmable device that can store, retrieve, and process data, allow mobile (wireless or radio) telecommunication with other computing devices and have one or more communicably connected components of computer/computing processors, such as Central Processing Units (CPUs); input unit(s)/device(s) (e.g., microphone for voice command/control, etc., keyboard/keypad, pointing device (e.g., mouse, pointer, stylus), touch screen, camera, scanner, etc.); output unit(s)/device(s) (e.g., computer display screen (including user interface thereof, such as graphical user interface), speaker(s), printer(s), etc.); computer network interface(s), including known communication protocols thereof, (e.g., mobile telephone (voice/data (Internet)) (cellular radio networks, satellite, etc.) network, radio frequency technology, local area network, etc.); and recording media to store information/instructions, such as software (e.g., operating system, wireless wallet software, etc.) and/or data (any known recording media, such as volatile and/or non-volatile memory (Random Access Memory), hard disk, flash memory, magnetic/optical disks, etc.) for execution by a computing apparatus, such as a computer/computing processor and/or electronic circuitry. The embodiments provide methods, apparatuses (computer systems) and/or computer readable media for a wireless computing apparatus/device for physical Point of Sale (POS) transactions. The POS 103 and STS 120 can be any computer. [0190] The many features and advantages of the embodiments described herein are apparent from the detailed specification and, thus, it is intended by the appended claims and equivalents to cover all such features and advantages of the embodiments that fall within the true spirit and scope of the embodiments. Further, since modifications and changes might occur to those skilled in the art, it is not desired to limit the embodiments to the exact construction and operation illustrated and described, and accordingly all suitable modifications and equivalents may be resorted to, falling within the scope of the embodiments. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS2002 *Mar 12, 1841 Tor and planter for plowingUS2004 *Mar 12, 1841 Improvement in the manner of constructing and propelling steam-vesselsUS4182261 *May 5, 1977Jan 8, 1980Identicator CorporationCredit card printer for fingerprints and solutionsUS4253086 *Jan 10, 1979Feb 24, 1981Szymon SzwarcbierProcess and apparatus for positive identification of customersUS4582985 *Mar 18, 1982Apr 15, 1986Loefberg BoData carrierUS4636622 *May 6, 1985Jan 13, 1987Clark Clement PCard user identification systemUS5095194 *Oct 12, 1989Mar 10, 1992Joseph BarbanellHolographic credit card with automatical authentication and verificationUS5194289 *Oct 15, 1990Mar 16, 1993Butland Trust OrganizationMethod for labeling an object for its verificationUS5239166 *Sep 9, 1991Aug 24, 1993Graves Marcel ASecure data interchange system erasing a card memory upon an invalid responseUS5256863 *Nov 5, 1991Oct 26, 1993Comark Technologies, Inc.In-store universal control systemUS5485312 *Sep 14, 1993Jan 16, 1996The United States Of America As Represented By The Secretary Of The Air ForceOptical pattern recognition system and method for verifying the authenticity of a person, product or thingUS5521980 *Feb 28, 1994May 28, 1996Brands; Stefanus A.Privacy-protected transfer of electronic informationUS5598474 *Mar 10, 1995Jan 28, 1997Neldon P JohnsonProcess for encrypting a fingerprint onto an I.D. cardUS5631961 *Sep 15, 1995May 20, 1997The United States Of America As Represented By The Director Of The National Security AgencyDevice for and method of cryptography that allows third party accessUS5644118 *Apr 19, 1996Jul 1, 1997Fujitsu LimitedElectronic cashless systemUS5666420 *Nov 18, 1996Sep 9, 1997Micali; SilvioSimultaneous electronic transactionsUS5732148 *Sep 16, 1994Mar 24, 1998Keagy; John MartinApparatus and method for electronically acquiring fingerprint images with low cost removable platen and separate imaging deviceUS5790677 *Jun 29, 1995Aug 4, 1998Microsoft CorporationSystem and method for secure electronic commerce transactionsUS5869822 *Oct 4, 1996Feb 9, 1999Meadows, Ii; Dexter L.Automated fingerprint identification systemUS5913203 *Oct 3, 1996Jun 15, 1999Jaesent Inc.System and method for pseudo cash transactionsUS5917168 *Jun 2, 1994Jun 29, 1999Hewlett-Packard CompanySystem and method for revaluation of stored tokens in IC cardsUS5949043 *May 16, 1997Sep 7, 1999Fujitsu LimitedElectronic cashless systemUS6010068 *Aug 10, 1994Jan 4, 2000Nadir Technology Company LimitedCredit document connected to a document or customized card, independent customized credit card and associated issuance and validation equipmentUS6032258 *Jul 11, 1997Feb 29, 2000Glenayre Electronics, Inc.Apparatus and methods for transmission security in a computer networkUS6044388 *May 15, 1997Mar 28, 2000International Business Machine CorporationPseudorandom number generatorUS6067621 *Oct 6, 1997May 23, 2000Samsung Electronics Co., Ltd.User authentication system for authenticating an authorized user of an IC cardUS6069969 *Mar 23, 1998May 30, 2000Identicator TechnologyApparatus and method for electronically acquiring fingerprint imagesUS6081793 *Dec 30, 1997Jun 27, 2000International Business Machines CorporationMethod and system for secure computer moderated votingUS6098053 *Jan 26, 1999Aug 1, 2000Citibank, N.A.System and method for performing an electronic financial transactionUS6115601 *Oct 15, 1997Sep 5, 2000U.S. Philips CorporationPayment scheme for a mobile communication serviceUS6137884 *May 2, 1997Oct 24, 2000Bankers Trust CorporationSimultaneous electronic transactions with visible trusted partiesUS6175922 *Mar 13, 2000Jan 16, 2001Esign, Inc.Electronic transaction systems and methods thereforUS6175923 *Dec 8, 1998Jan 16, 2001Senetas Corporation LimitedSecure system using images of only part of a body as the key where the part has continuously-changing featuresUS6182892 *Mar 25, 1998Feb 6, 2001Compaq Computer CorporationSmart card with fingerprint image pass-throughUS6199099 *Mar 5, 1999Mar 6, 2001Ac Properties B.V.System, method and article of manufacture for a mobile communication network utilizing a distributed communication networkUS6212290 *Nov 7, 1994Apr 3, 2001Tms, Inc.Non-minutiae automatic fingerprint identification system and methodsUS6226752 *May 11, 1999May 1, 2001Sun Microsystems, Inc.Method and apparatus for authenticating usersUS6257487 *Aug 2, 1999Jul 10, 2001Fujitsu LimitedElectronic cashless systemUS6263436 *Dec 17, 1996Jul 17, 2001At&T Corp.Method and apparatus for simultaneous electronic exchange using a semi-trusted third partyUS6270011 *May 28, 1999Aug 7, 2001Benenson TalRemote credit card authentication systemUS6334575 *Nov 1, 2000Jan 1, 2002Singular Technology Corp.Safety transaction methodUS6356752 *Jul 31, 1998Mar 12, 2002Avaya Technology Corp.Wireless telephone as a transaction deviceUS6366893 *Nov 5, 1996Apr 2, 2002Nokia Telecommunications OySystem, a method and an apparatus for performing an electric payment transaction in a telecommunication networkUS6378073 *Dec 22, 1997Apr 23, 2002Motorola, Inc.Single account portable wireless financial messaging unitUS6378775 *May 11, 2001Apr 30, 2002Fujitsu LimitedElectronic cashless systemUS6405314 *Sep 29, 2000Jun 11, 2002Ecryp, Inc.Secure system using images of only part of a body as the key where the part has continuously-changing featuresUS6435406 *Oct 6, 2000Aug 20, 2002Randolph M. PentelRemote ordering deviceUS6470448 *Mar 31, 1997Oct 22, 2002Fujitsu LimitedApparatus and method for proving transaction between users in network environmentUS6512919 *Mar 30, 1999Jan 28, 2003Fujitsu LimitedElectronic shopping system utilizing a program downloadable wireless videophoneUS6529885 *Sep 24, 1999Mar 4, 2003Oracle CorporationMethods and systems for carrying out directory-authenticated electronic transactions including contingency-dependent payments via secure electronic bank draftsUS6587684 *Jul 28, 1998Jul 1, 2003Bell Atlantic Nynex MobileDigital wireless telephone system for downloading software to a digital telephone using wireless data link protocolUS6687375 *Jun 2, 1999Feb 3, 2004International Business Machines CorporationGenerating user-dependent keys and random numbersUS6715679 *Sep 8, 1999Apr 6, 2004At&T Corp.Universal magnetic stripe cardUS6766453 *Apr 28, 2000Jul 20, 20043Com CorporationAuthenticated diffie-hellman key agreement protocol where the communicating parties share a secret key with a third partyUS6775777 *Jan 26, 2001Aug 10, 2004Ecryp, Inc.Secure system using images of only part of a body as the key where the part has continuously-changing featuresUS6915951 *Jan 15, 2002Jul 12, 2005Fujitsu LimitedElectronic cashless systemUS6926200 *Jul 14, 2000Aug 9, 2005Fujitsu LimitedElectronic cashless systemUS6931431 *Jan 11, 2002Aug 16, 2005International Business Machines CorporationAgreement and atomic broadcast in asynchronous networksUS6957334 *Jun 20, 2000Oct 18, 2005Mastercard International IncorporatedMethod and system for secure guaranteed transactions over a computer networkUS7025256 *Jul 15, 2004Apr 11, 2006Diebold, IncorporatedAutomated banking machine system and methodUS7089208 *Apr 28, 2000Aug 8, 2006Paypal, Inc.System and method for electronically exchanging value among distributed usersUS7099471 *Dec 31, 2001Aug 29, 2006Dategrity CorporationDetecting compromised ballotsUS7167844 *Dec 22, 1999Jan 23, 2007Accenture LlpElectronic menu document creator in a virtual financial environmentUS7239346 *Oct 18, 1999Jul 3, 2007Priddy Dennis GSystem and architecture that supports a multi-function semiconductor device between networks and portable wireless communications productsUS7379916 *Nov 3, 2000May 27, 2008Authernative, Inc.System and method for private secure financial transactionsUS7427033 *Feb 27, 2006Sep 23, 2008James RoskindTime-varying security code for enabling authorizations and other uses of financial accountsUS7578436 *Mar 18, 2005Aug 25, 2009Pisafe, Inc.Method and apparatus for providing secure document distributionUS20010004231 *Jan 26, 2001Jun 21, 2001Secure Id-Net Ltd.Secure system using images of only part of a body as the key where the part has continuously-changing featuresUS20010005840 *Dec 29, 2000Jun 28, 2001Markku VerkamaAuthentication in a telecommunications networkUS20010010723 *Oct 30, 1997Aug 2, 2001Denis PinkasKey recovery process used for strong encryption of messagesUS20010034670 *Feb 21, 2001Oct 25, 2001Blair Jeffery D.Direct point of presence distribution system and methodUS20020017561 *Aug 6, 2001Feb 14, 2002Hiroyuki TomoikeElectronic payment system using accounting function in a mobile communication networkUS20020018585 *Jul 19, 2001Feb 14, 2002Kim Young WanSystem and method for cardless secure credit transaction processingUS20020052841 *Apr 10, 2001May 2, 2002Guthrie Paul D.Electronic payment systemUS20020057803 *May 3, 2001May 16, 2002Loos Michael T.System and method for communicating in a mobile domain across non-persistent data linksUS20020073024 *Dec 7, 2000Jun 13, 2002Gilchrist Alexander Sandy DonaldSystem and methods of using wireless communication devices to conduct financial transactionsUS20020077974 *Dec 19, 2000Jun 20, 2002Ortiz Luis M.Wireless point of saleUS20020082925 *Dec 27, 2000Jun 27, 2002Herwig Nathaniel C.Method and apparatus for utilizing a smart card to maintain a retail application on a number of portable, wireless hand-held computing devicesUS20020087534 *Apr 20, 2001Jul 4, 2002Blackman Robert SageAgreement management system and methodUS20020087869 *Nov 8, 2001Jul 4, 2002Jinsam KimSystem and method of authenticating a credit card using a fingerprintUS20020095296 *Jan 17, 2001Jul 18, 2002International Business Machines CorporationTechnique for improved audio compressionUS20020095570 *Apr 1, 2002Jul 18, 2002Xerox CorporationSecure token-based document serverUS20020097867 *Nov 21, 2001Jul 25, 2002Bartram Anthony V.Communication systemUS20020107007 *Mar 27, 2002Aug 8, 2002Howard GersonMethod for wireless telephony payment and an apparatus thereforUS20020107791 *Jan 12, 2001Aug 8, 2002Nobrega Ryan J.Method and apparatus for performing a credit based transaction between a user of a wireless communications device and a provider of a product or serviceUS20020141575 *Jun 5, 2001Oct 3, 2002Hird Geoffrey R.Method and apparatus for secure cryptographic key generation, certification and useUS20030046541 *Aug 22, 2002Mar 6, 2003Martin GerdesUniversal authentication mechanismUS20030123667 *Dec 28, 2001Jul 3, 2003Cable Television Laboratories, Inc.Method for encryption key generationUS20030174049 *Mar 18, 2002Sep 18, 2003Precision Dynamics CorporationWearable identification appliance that communicates with a wireless communications network such as bluetoothUS20030190046 *Oct 17, 2002Oct 9, 2003Kamerman Matthew AlbertThree party signing protocol providing non-linkabilityUS20030204726 *Apr 25, 2002Oct 30, 2003Kefford Mark GregoryMethods and systems for secure transmission of information using a mobile deviceUS20040030894 *Jun 11, 2003Feb 12, 2004Fujitsu LimitedSecurity framework and protocol for universal pervasive transactionsUS20040104268 *Jul 30, 2002Jun 3, 2004Bailey Kenneth StephenPlug in credit card reader module for wireless cellular phone verificationsUS20040123159 *Dec 19, 2002Jun 24, 2004Kevin KerstensProxy method and system for secure wireless administration of managed entitiesUS20040158492 *Jan 26, 2004Aug 12, 2004Lopez Kermit D.Processing negotiable economic credits through electronic hand held devicesUS20050067485 *Jan 16, 2003Mar 31, 2005Michel CaronApparatus and method of identifying the user thereof by means of a variable identification codeUS20050122209 *Dec 3, 2003Jun 9, 2005Black Gerald R.Security authentication method and systemUS20050194452 *Dec 2, 2004Sep 8, 2005Torsten NordentoftCredit card and a secured data activation systemUS20060004862 *Jun 8, 2004Jan 5, 2006Fisher David LTime synchronized playback and control of dissimilar data files* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7688953Aug 23, 2006Mar 30, 2010Cisco Technology, Inc.Rate control in communications systemsUS7742584Mar 21, 2007Jun 22, 2010Cisco Technology, Inc.Mobile device calls via private branch exchangeUS7783310 *Aug 23, 2006Aug 24, 2010Orative CorporationMelting information on a client deviceUS7787607Mar 21, 2007Aug 31, 2010Cisco Technology, Inc.Mobile device calls via private branch exchangeUS7822189Aug 23, 2006Oct 26, 2010Orative CorporationSearching multiple directories and generating a sorted integrated directoryUS7876888Mar 21, 2007Jan 25, 2011Cisco Technology, Inc.Mobile device calls via private branch exchangeUS7885411Mar 30, 2005Feb 8, 2011Research In Motion LimitedKey agreement and re-keying over a bidirectional communication pathUS7889849Mar 21, 2007Feb 15, 2011Cisco Tech IncMobile device conference calls via private branch exchangeUS7940910Aug 23, 2006May 10, 2011Orative CorporationDirectory integration in mobile systemsUS7974391Aug 23, 2006Jul 5, 2011Orative CorporationConversation-based user interfaceUS8060627Sep 30, 2008Nov 15, 2011Apple Inc.Device-to-device workflowsUS8090107Dec 20, 2010Jan 3, 2012Research In Motion LimitedKey agreement and re-keying over a bidirectional communication pathUS8108318 *Dec 19, 2008Jan 31, 2012Ebay Inc.Trusted service manager (TSM) architectures and methodsUS8131645Sep 30, 2008Mar 6, 2012Apple Inc.System and method for processing media giftsUS8150772Mar 30, 2009Apr 3, 2012Ebay Inc.Biometric authentication of mobile financial transactions by trusted service managersUS8150945 *Jun 23, 2004Apr 3, 2012Broadcom CorporationHost arbitrated user interface resource sharingUS8175979 *Apr 2, 2008May 8, 2012International Business Machines CorporationMethod and system for anonymous electronic transactions using a mobile deviceUS8215546Sep 30, 2008Jul 10, 2012Apple Inc.System and method for transportation check-inUS8219490Oct 24, 2008Jul 10, 2012Visa U.S.A., Inc.Payment transaction using mobile phone as relayUS8229396 *Mar 25, 2005Jul 24, 2012International Business Machines CorporationWireless service purchasing systemUS8238558Nov 24, 2011Aug 7, 2012Research In Motion LimitedKey agreement and re-keying over a bidirectional communication pathUS8239276Sep 30, 2008Aug 7, 2012Apple Inc.On-the-go shopping listUS8301500Mar 26, 2009Oct 30, 2012Global 1 EnterprisesGhosting payment account data in a mobile telephone payment transaction systemUS8317086 *Feb 16, 2011Nov 27, 2012International Business Machines CorporationCommunication of transaction data within a self-checkout environmentUS8325906Jan 25, 2007Dec 4, 2012Cisco Technology, Inc.Class-based call request routingUS8332272 *Dec 27, 2011Dec 11, 2012Blaze Mobile, Inc.Single tap transactions using an NFC enabled mobile deviceUS8352323 *Nov 30, 2007Jan 8, 2013Blaze Mobile, Inc.Conducting an online payment transaction using an NFC enabled mobile communication deviceUS8374588Jun 1, 2009Feb 12, 2013Mocapay, Inc.Method and system for sending marketing messages to mobile-device users from a mobile-commerce platformUS8401681Sep 30, 2008Mar 19, 2013Apple Inc.System and method for placeshifting media playbackUS8417643 *Dec 20, 2011Apr 9, 2013Ebay Inc.Trusted service manager (TSM) architectures and methodsUS8429616 *Mar 19, 2010Apr 23, 2013Ebay Inc.Orthogonal experimentation in a computing environmentUS8438288 *Feb 17, 2010May 7, 2013Microsoft CorporationDevice-pairing by reading an address provided in device-readable formUS8458363Sep 30, 2008Jun 4, 2013Apple Inc.System and method for simplified data transferUS8459545 *Mar 29, 2012Jun 11, 2013Cisco Technology, Inc.Image-based point-of-sale mobile settlement systemUS8463674Dec 23, 2008Jun 11, 2013Mocapay, Inc.System and method for distributing mobile gift cardsUS8490870Oct 18, 2010Jul 23, 2013Six Circle Limited Liability CompanyApparatus and method for POS processingUS8500013Aug 19, 2011Aug 6, 2013General Electric CompanySystems and methods for accessing charging capabilities of electric vehicle charging stationsUS8503658Mar 21, 2007Aug 6, 2013Cisco Technology, Inc.Call notification with rich caller identificationUS8516125Sep 30, 2008Aug 20, 2013Apple Inc.System and method for simplified data transferUS8543091Dec 22, 2008Sep 24, 2013Ebay Inc.Secure short message service (SMS) communicationsUS8555355 *Dec 7, 2010Oct 8, 2013Verizon Patent And Licensing Inc.Mobile pin padUS8566924Aug 12, 2011Oct 22, 2013Six Circle Limited Liability CompanyMethod and system for controlling communication portsUS8583494 *Dec 7, 2012Nov 12, 2013Blaze Mobile, Inc.Processing payments at a management server with user selected payment methodUS8589237 *Dec 7, 2012Nov 19, 2013Blaze Mobile, Inc.Online purchase from a mobile device using a default payment methodUS8589267Dec 23, 2008Nov 19, 2013Mocapay, Inc.System and method for re-distributing and transferring mobile gift cardsUS8589300 *Jun 11, 2012Nov 19, 2013Visa U.S.A. Inc.Payment transaction using mobile phone as relayUS8615086Aug 3, 2012Dec 24, 2013Blackberry LimitedKey agreement and re-keying over a bidirectional communication pathUS8620754 *Jan 7, 2013Dec 31, 2013Blaze Mobile, Inc.Remote transaction processing using authentication informationUS8630905 *Nov 19, 2012Jan 14, 2014Michelle FisherSingle tap transactions using a secure elementUS8630906 *Nov 19, 2012Jan 14, 2014Michelle FisherSingle tap transactions using a point-of-sale terminalUS8635157Jul 19, 2011Jan 21, 2014Payme, Inc.Mobile system and method for payments and non-financial transactionsUS8638910Jan 8, 2007Jan 28, 2014Cisco Technology, Inc.Integration of enterprise voicemail in mobile systemsUS8645280 *Dec 9, 2011Feb 4, 2014Craig McKenzieElectronic credit card with fraud protectionUS8688526 *Dec 7, 2012Apr 1, 2014Michelle FisherFinancial transaction processing with digital artifacts using a mobile communications deviceUS8693995Dec 13, 2007Apr 8, 2014Michelle FisherCustomized mobile applications for special interest groupsUS8694380 *Jan 7, 2013Apr 8, 2014Michelle FisherRemote transaction processing using a default payment method and couponsUS8695001Sep 20, 2007Apr 8, 2014Microsoft CorporationLoading services based on a request and setting permission level to enable execution of commands or services exposed based on a role of requesterUS8725575 *Jan 7, 2013May 13, 2014Michelle FisherRemote transaction processing with multiple payment mechanismsUS8725576 *Jan 7, 2013May 13, 2014Michelle FisherRemote transaction processing with multiple payment methods using authenticationUS8725577 *Aug 29, 2013May 13, 2014Michelle FisherPersonalized mobile banking transactionsUS8732020 *Mar 28, 2007May 20, 2014At&T Intellectual Property I, LpMethod and apparatus for fulfilling purchasesUS8738454 *Jul 23, 2012May 27, 2014Wal-Mart Stores, Inc.Transferring digital receipt data to mobile devicesUS8744940Jan 13, 2012Jun 3, 2014William O. WhiteSystem and method for distributing mobile compensation and incentivesUS8751313 *Nov 19, 2012Jun 10, 2014Michelle FisherSingle tap transactions using a mobile applicationUS8751314 *Nov 19, 2012Jun 10, 2014Michelle FisherSingle tap transactions using a serverUS8751315 *Dec 5, 2012Jun 10, 2014Michelle FisherUsing a mobile device as a point of sale terminalUS8752760 *Jan 30, 2013Jun 17, 2014Six Circle Limited Liability CompanyApparatus and method for POS processingUS8767931Aug 23, 2006Jul 1, 2014Orative CorporationProvisioning in communications systemsUS8789019 *Apr 22, 2013Jul 22, 2014Ebay Inc.Orthogonal experimentation in a computing environmentUS8799085 *Nov 19, 2012Aug 5, 2014Michelle FisherRedeeming coupons using NFCUS8805726 *Dec 10, 2012Aug 12, 2014Michelle FisherOnline shopping using NFC and a mobile deviceUS8818870 *Dec 7, 2012Aug 26, 2014Michelle FisherUsing a secure element coupled to a mobile device as a POS terminal for processing mag stripe transactionsUS8843398 *Jul 23, 2012Sep 23, 2014Wal-Mart Stores, Inc.Transferring digital receipt data to mobile devicesUS8850052Sep 30, 2008Sep 30, 2014Apple Inc.System and method for simplified resource sharingUS8875232Feb 18, 2009Oct 28, 2014Telefonaktiebolaget L M Ericsson (Publ)User authenticationUS8923827Jan 9, 2008Dec 30, 2014Visa U.S.A. Inc.Mobile payment managementUS8944328Jan 6, 2014Feb 3, 2015Cedar Ridge ResearchSystem for data card emulationUS8949146Oct 31, 2007Feb 3, 2015Michelle FisherMethod for purchasing tickets using a mobile communication deviceUS8966096May 6, 2013Feb 24, 2015Microsoft Technology Licensing, LlcDevice-pairing by reading an address provided in device-readable formUS8976959Mar 15, 2013Mar 10, 2015Clinkle CorporationEcho delay encodingUS8977567 *Sep 21, 2009Mar 10, 2015Visa International Service AssociationRecordation of electronic payment transaction informationUS8983438 *Oct 27, 2009Mar 17, 2015Visa U.S.A. Inc.System and method for enabling a mobile communication device to operate as a financial presentation deviceUS9004354 *Mar 31, 2008Apr 14, 2015Amazon Technologies, Inc.Machine-readable code rendering device and methods for using the sameUS9009081Apr 8, 2013Apr 14, 2015Michelle FisherPurchasing tickets using an NFC enabled mobile communication deviceUS9015064 *Dec 11, 2012Apr 21, 2015Michelle FisherUtilizing a secure element for NFC transactions which includes response data during inductionUS9026459 *Dec 10, 2012May 5, 2015Michelle FisherOnline shopping using NFC and a point-of-sale terminalUS9026462Sep 30, 2008May 5, 2015Apple Inc.Portable point of purchase user interfacesUS9037513Sep 30, 2008May 19, 2015Apple Inc.System and method for providing electronic event ticketsUS9053474 *Dec 19, 2008Jun 9, 2015At&T Mobility Ii LlcSystems and methods for handling point-of-sale transactions using a mobile deviceUS9070149Sep 30, 2008Jun 30, 2015Apple Inc.Media gifting devices and methodsUS9098498May 19, 2011Aug 4, 2015Alcatel LucentElectronic transactions with mobile communications devices via encoded graphical representationsUS9123040Feb 24, 2011Sep 1, 2015Iii Holdings 1, LlcSystems and methods for encoded alias based transactionsUS9129269 *Jan 31, 2011Sep 8, 2015Xia DaiSecured point-of-sale transaction systemUS9130802May 3, 2013Sep 8, 2015Apple Inc.System and method for simplified data transferUS9152957Feb 27, 2015Oct 6, 2015The Toronto-Dominion BankSystem and method for downloading an electronic product to a pin-pad terminal after validating an electronic shopping basket entryUS9177331 *Feb 13, 2014Nov 3, 2015Michelle FisherFinancial transaction processing with digital artifacts and a default payment method using a serverUS9183549 *Aug 26, 2009Nov 10, 2015Mts Holdings, Inc.System and method of secure payment transactionsUS9189783 *Jul 16, 2010Nov 17, 2015Margento R&D D.O.OWireless mobile transaction system and the procedure for carrying out transactions with a mobile phoneUS9230268 *Feb 24, 2014Jan 5, 2016Michelle FisherFinancial transaction processing with digital artifacts and a default payment method using a POSUS9232341Feb 14, 2014Jan 5, 2016Michelle FisherCustomized application for proximity transactionsUS9239993May 23, 2013Jan 19, 2016Bytemark, Inc.Method and system for distributing electronic tickets with visual displayUS9262543 *Jun 10, 2014Feb 16, 2016Ebay Inc.Orthogonal experimentation in a computing environmentUS9292862May 14, 2014Mar 22, 2016Mocapay, Inc.Method and system for sending marketing messages to mobile-device users from a mobile-commerce platformUS9305309 *Dec 30, 2013Apr 5, 2016Michelle FisherRemote transaction processing with a point-of-entry terminal using bluetoothUS9311659 *Nov 18, 2013Apr 12, 2016Michelle FisherRemote transaction processing at a server from a list using a payment methodUS9336523 *Jul 28, 2014May 10, 2016International Business Machines CorporationManaging a secure transactionUS9342823 *Jan 4, 2008May 17, 2016Lemon, Inc.Payment clearing network for electronic financial transactions and related personal financial transaction deviceUS9342832 *Aug 12, 2011May 17, 2016Visa International Service AssociationSecuring external systems with account token substitutionUS9349124 *Oct 7, 2010May 24, 2016Xius Corp.Integrated system and method for enabling mobile commerce transactions using active posters and contactless identity modulesUS9367841 *Jul 18, 2011Jun 14, 2016Tiger T G ZhouFacilitating mobile device payments using product code scanningUS9443233 *Oct 18, 2012Sep 13, 2016Intuit Inc.Payment using a fractal imageUS9443238Dec 1, 2014Sep 13, 2016Playspan, Inc.Distributed payment system and methodUS9471920May 10, 2010Oct 18, 2016Idm Global, Inc.Transaction assessment and/or authenticationUS9485286Jun 24, 2014Nov 1, 2016Amazon Technologies, Inc.Sharing media items with pass phrasesUS9521548May 21, 2012Dec 13, 2016Nexiden, Inc.Secure registration of a mobile device for use with a sessionUS9530126Nov 22, 2010Dec 27, 2016Alibaba Group Holding LimitedSecure mobile payment processingUS9537839May 12, 2015Jan 3, 2017Paypal, Inc.Secure short message service (SMS) communicationsUS9547723Aug 29, 2014Jan 17, 2017Alibaba Group Holding LimitedData processing based on two-dimensional codeUS9569768 *Feb 20, 2009Feb 14, 2017First Data CorporationSystems, methods and apparatus for selecting a payment account for a payment transactionUS9569770Jan 13, 2009Feb 14, 2017Amazon Technologies, Inc.Generating constructed phrasesUS20050065768 *Jun 23, 2004Mar 24, 2005Jeyhan KaraoguzHost arbitrated user interface resource sharingUS20050216344 *Mar 25, 2005Sep 29, 2005International Business Machines CorporationWireless service purchasing systemUS20050232428 *Mar 30, 2005Oct 20, 2005Little Herbert ADeploying and provisioning wireless handheld devicesUS20070041542 *Aug 23, 2006Feb 22, 2007Schramm Steven DConnection management in communications systemsUS20070041556 *Aug 23, 2006Feb 22, 2007Hemendra RanaSearching multiple directories and generating a sorted integrated directoryUS20070041557 *Aug 23, 2006Feb 22, 2007Saurav ChatterjeeRate control in communications systemsUS20070041571 *Aug 23, 2006Feb 22, 2007Saurav ChatterjeeDirectory integration in mobile systemsUS20070042756 *Aug 23, 2006Feb 22, 2007Josh PerfettoProvisioning in communications systemsUS20070049304 *Aug 23, 2006Mar 1, 2007Hemendra RanaMelting information on a client deviceUS20070150403 *Dec 28, 2005Jun 28, 2007Motorola, Inc.Method and system for a mobile auction conciergeUS20070197261 *Mar 16, 2005Aug 23, 2007Humbel Roger MMobile Telephone All In One Remote Key Or Software Regulating Card For Radio Bicycle Locks, Cars, Houses, And Rfid Tags, With Authorisation And Payment FunctionUS20070201661 *Jan 25, 2007Aug 30, 2007Paul FullartonClass-based call request routingUS20070207785 *Jan 8, 2007Sep 6, 2007Saurav ChatterjeeIntegration of enterprise voicemail in mobile systemsUS20070223401 *Mar 21, 2007Sep 27, 2007Saurav ChatterjeeMobile device calls via private branch exchangeUS20070223509 *Mar 21, 2007Sep 27, 2007Saurav ChatterjeeMobile device conference calls via private branch exchangeUS20070223679 *Mar 21, 2007Sep 27, 2007Saurav ChatterjeeMobile device calls via private branch exchangeUS20070248221 *Mar 21, 2007Oct 25, 2007Saurav ChatterjeeCall notification with rich caller identificationUS20070253545 *Mar 21, 2007Nov 1, 2007Saurav ChatterjeeMobile device calls via private branch exchangeUS20080052192 *Oct 31, 2007Feb 28, 2008Mobile Candy Dish, Inc.Method and system for purchasing event tickets using a mobile communication deviceUS20080114699 *Oct 29, 2007May 15, 2008Gong Yi YuanSystem, hardware and method for mobile pos paymentUS20080143487 *Dec 14, 2007Jun 19, 2008Broadcom CorporationSystem and method for enabling interrupts for rfid tagsUS20080148395 *Oct 24, 2006Jun 19, 2008Chris BrockSystem and method for securing settings of a computing deviceUS20080167017 *Jan 9, 2008Jul 10, 2008Dave WentkerMobile payment managementUS20080167961 *Jan 9, 2008Jul 10, 2008Dave WentkerContactless transactionUS20080175449 *Jan 19, 2007Jul 24, 2008Wison Technology Corp.Fingerprint-based network authentication method and system thereofUS20080242357 *Mar 28, 2007Oct 2, 2008At&T Knowledge Ventures, L.P.Method and apparatus for fulfilling purchasesUS20080300984 *May 29, 2008Dec 4, 2008Lehmann LiMethods and apparatuses related to the offer of purchase incentivesUS20080313047 *Jan 4, 2008Dec 18, 2008Bling Nation, Ltd.Payment clearing network for electronic financial transactions and related personal financial transaction deviceUS20080313079 *Jun 14, 2007Dec 18, 2008Motorola, Inc.System and method for proximity payment transaction between a wireless communication device and a point of sale terminal in conjunction with a trusted partyUS20080313082 *Jun 14, 2007Dec 18, 2008Motorola, Inc.Method and apparatus for proximity payment provisioning between a wireless communication device and a trusted partyUS20090018964 *Jul 13, 2007Jan 15, 2009Sony Ericsson Mobile Communications AbMethods, systems, and computer program products for performing a transaction in which a certifier provides identification information for authenticating a customer at the point of saleUS20090063312 *Aug 27, 2008Mar 5, 2009Hurst Douglas JMethod and System for Processing Secure Wireless Payment Transactions and for Providing a Virtual Terminal for Merchant Processing of Such TransactionsUS20090083740 *Sep 20, 2007Mar 26, 2009Microsoft CorporationAsynchronous execution of software tasksUS20090106152 *Jun 26, 2008Apr 23, 2009The Western Union CompanyMoney transfers utilizing unique receiver identifierUS20090112768 *Oct 24, 2008Apr 30, 2009Ayman HammadPayment transaction using mobile phone as relayUS20090119170 *Oct 23, 2008May 7, 2009Ayman HammadPortable consumer device including data bearing medium including risk based benefitsUS20090144161 *Nov 30, 2007Jun 4, 2009Mobile Candy Dish, Inc.Method and system for conducting an online payment transaction using a mobile communication deviceUS20090156190 *Dec 13, 2007Jun 18, 2009Mobile Candy Dish, Inc.Method and system for delivering customized information to a mobile communication device based on user affiliationsUS20090179074 *Dec 23, 2008Jul 16, 2009Hurst Douglas JSystem and method for distributing mobile gift cardsUS20090254440 *Mar 26, 2009Oct 8, 2009Pharris Dennis JGhosting payment account data in a mobile telephone payment transaction systemUS20090254479 *Mar 26, 2009Oct 8, 2009Pharris Dennis JTransaction server configured to authorize payment transactions using mobile telephone devicesUS20090254485 *Apr 2, 2008Oct 8, 2009International Business Machines CorporationMethod and system for anonymous electronic transactions using a mobile deviceUS20090265272 *Jun 3, 2009Oct 22, 2009The Western Union CompanyMoney transfers utilizing a unique receiver identifierUS20090271276 *Apr 24, 2008Oct 29, 2009Qualcomm IncorporatedElectronic payment systemUS20090276439 *Sep 30, 2008Nov 5, 2009Apple Inc.System and method for simplified data transferUS20090276547 *Sep 30, 2008Nov 5, 2009Apple Inc.System and method for simplified data transferUS20090281904 *Mar 26, 2009Nov 12, 2009Pharris Dennis JMobile telephone transaction systems and methodsUS20090288012 *May 18, 2009Nov 19, 2009Zetawire Inc.Secured Electronic Transaction SystemUS20090298481 *Jun 1, 2009Dec 3, 2009Hurst Douglas JMethod and system for sending marketing messages to mobile-device users from a mobile-commerce platformUS20090305673 *Dec 22, 2008Dec 10, 2009Ebay, Inc.Secure short message service (sms) communicationsUS20090307139 *Mar 30, 2009Dec 10, 2009Ebay, Inc.Biometric authentication of mobile financial transactions by trusted service managersUS20090307140 *Oct 10, 2008Dec 10, 2009Upendra MardikarMobile device over-the-air (ota) registration and point-of-sale (pos) paymentUS20090307142 *Dec 19, 2008Dec 10, 2009Upendra MardikarTrusted service manager (tsm) architectures and methodsUS20090307778 *Dec 11, 2008Dec 10, 2009Ebay Inc.Mobile User Identify And Risk/Fraud Model ServiceUS20090327086 *Jul 9, 2006Dec 31, 2009Homeier-Beals Thomas ENon-Optical Mobile Electronic Transaction System, Device and Method ThereforUS20100057623 *Aug 26, 2009Mar 4, 2010Adaptive Payments, Inc.System and Method of Secure Payment TransactionsUS20100078471 *Sep 30, 2008Apr 1, 2010Apple Inc.System and method for processing peer-to-peer financial transactionsUS20100078472 *Sep 30, 2008Apr 1, 2010Apple Inc.Group peer-to-peer financial transactionsUS20100078475 *Sep 30, 2008Apr 1, 2010Apple Inc.System and method for transportation check-inUS20100081375 *Sep 30, 2008Apr 1, 2010Apple Inc.System and method for simplified control of electronic devicesUS20100082136 *Sep 30, 2008Apr 1, 2010Apple Inc.System and method for placeshifting media playbackUS20100082444 *Sep 30, 2008Apr 1, 2010Apple Inc.Portable point of purchase user interfacesUS20100082447 *Sep 30, 2008Apr 1, 2010Apple Inc.On-the-go shopping listUS20100082455 *Sep 30, 2008Apr 1, 2010Apple Inc.Real-time bargain huntingUS20100082481 *Sep 30, 2008Apr 1, 2010Apple Inc.Peer-to-peer financial transaction devices and methodsUS20100082485 *Sep 30, 2008Apr 1, 2010Apple Inc.Portable point of purchase devices and methodsUS20100082489 *Sep 30, 2008Apr 1, 2010Apple Inc.System and method for processing media giftsUS20100082490 *Sep 30, 2008Apr 1, 2010Apple Inc.Systems and methods for secure wireless transactionsUS20100082491 *Sep 30, 2008Apr 1, 2010Apple Inc.System and method for providing electronic event ticketsUS20100082784 *Sep 30, 2008Apr 1, 2010Apple Inc.System and method for simplified resource sharingUS20100082821 *Sep 30, 2008Apr 1, 2010Apple Inc.Device-to-device workflowsUS20100125492 *Nov 14, 2008May 20, 2010Apple Inc.System and method for providing contextual advertisements according to dynamic pricing schemeUS20100136913 *Mar 28, 2008Jun 3, 2010France TelecomMethod of communicating and transmitting a message relating to a transaction of a contactless application, associated terminal, secure module and systemUS20100161433 *Dec 19, 2008Jun 24, 2010Spencer WhiteSystems and Methods for Handling Point-of-Sale Transactions Using a Mobile DeviceUS20100179909 *Jan 14, 2009Jul 15, 2010Jubin DanaUser defined udkUS20100211498 *Sep 21, 2009Aug 19, 2010Christian AabyeRecordation of electronic payment transaction informationUS20100217674 *Feb 20, 2009Aug 26, 2010First Data CorporationSystems, methods and apparatus for selecting a payment account for a payment transactionUS20100250436 *Apr 2, 2010Sep 30, 2010The Western Union CompanyMobile customer service centers with a mobile pickup modelUS20100287097 *Jul 30, 2009Nov 11, 2010Bank Of America CorporationConducting Commercial Transactions with a Mobile DeviceUS20110040641 *Oct 18, 2010Feb 17, 2011Quickvault, Inc.Apparatus and Method for POS ProcessingUS20110082800 *Mar 31, 2010Apr 7, 2011Validity Sensors, Inc.Secure Transaction Systems and MethodsUS20110098023 *Oct 27, 2009Apr 28, 2011Visa U.S.A. Inc.System and Method for Enabling a Mobile Communication Device to Operate as a Financial Presentation DeviceUS20110103588 *Dec 20, 2010May 5, 2011Research In Motion LimitedKey Agreement and Re-keying over a Bidirectional Communication PathUS20110105022 *Jan 12, 2011May 5, 2011Verizon Patent & Licensing Inc.Multi-function transaction deviceUS20110112898 *Nov 6, 2009May 12, 2011Wal-Mart Stores, Inc.System and method for communicating information to a customer at a point-of-sale via a wireless link within a retail storeUS20110137804 *Dec 3, 2009Jun 9, 2011Recursion Software, Inc.System and method for approving transactionsUS20110191252 *Jan 31, 2011Aug 4, 2011Xia DaiSecured Point-Of-Sale Transaction SystemUS20110202417 *Oct 7, 2010Aug 18, 2011Cellular Express, Inc. dba Xius-bogiIntegrated system and method for enabling mobile commerce transactions using active posters and contactless identity modulesUS20110202427 *Feb 17, 2010Aug 18, 2011Carlos Garcia Jurado SuarezDevice-Pairing by Reading an Address Provided in Device-Readable FormUS20110208550 *Oct 5, 2009Aug 25, 2011CodapayReverse payment transaction system and methodUS20110231821 *Mar 19, 2010Sep 22, 2011Jasdeep Singh SahniOrthogonal experimentation in a computing environmentUS20110251910 *Apr 13, 2011Oct 13, 2011James DimmickMobile Phone as a SwitchUS20110258122 *Apr 14, 2011Oct 20, 2011Daniel Jeffrey ShaderPayment system to facilitate transactionsUS20110281630 *Jan 29, 2010Nov 17, 2011Omarco Networks Solutions LimitedMultifunction authentication systemsUS20120006891 *Jul 18, 2011Jan 12, 2012Tiger T G ZhouFacilitating mobile device payments using product code scanningUS20120030044 *Aug 15, 2011Feb 2, 2012Mocapay, Inc.Virtual point of sale terminal and electronic wallet apparatuses and methods for processing secure wireless payment transactionsUS20120041881 *Aug 12, 2011Feb 16, 2012Gourab BasuSecuring external systems with account token substitutionUS20120072353 *Aug 16, 2011Mar 22, 2012Christopher BooneEnhanced system and method for multipath contactless transactionsUS20120078800 *Jun 4, 2010Mar 29, 2012Accumlate AbMethod for secure transactionsUS20120089519 *Jun 28, 2011Apr 12, 2012Prasad PeddadaSystem and method for single use transaction signaturesUS20120089520 *Dec 20, 2011Apr 12, 2012Ebay Inc.Trusted service manager (tsm) architectures and methodsUS20120144461 *Dec 7, 2010Jun 7, 2012Verizon Patent And Licensing Inc.Mobile pin padUS20120150601 *Dec 27, 2011Jun 14, 2012Blaze Mobile, Inc.Single tap transactions using an nfc enabled mobile deviceUS20120205433 *Feb 16, 2011Aug 16, 2012International Business Machines CorporationCommunication of transaction data within a self-checkout environmentUS20120209630 *Mar 11, 2011Aug 16, 2012Bytemark, Inc.System and method for trusted mobile device paymentUS20120254032 *Mar 29, 2011Oct 4, 2012Research In Motion LimitedMobile wireless communications device configured to authorize transaction based upon movement sensor and associated methodsUS20130006872 *Jun 29, 2011Jan 3, 2013Chandoor MadhuriNear-field communication based payment methodsUS20130018794 *Jul 12, 2012Jan 17, 2013NetQash LLCMobile communication device based monetary transfer systemUS20130024280 *Sep 24, 2012Jan 24, 2013Blaze Mobile, Inc.Nfc transactions using a user id embedded within secure element for processing at remote serverUS20130029646 *Jul 16, 2010Jan 31, 2013Margento R&D D.O.O.Wireless Mobile Transaction System and the Procedure for Carrying Out Transactions with a Mobile PhoneUS20130046695 *Aug 19, 2011Feb 21, 2013General Electric CompanySystems and Methods for Energy Management Between a Utility Provider and a ConsumerUS20130060701 *Apr 20, 2011Mar 7, 2013Chang Hwa LyouElectronic payment service method, and electronic payment service apparatus, mobile communication terminal, and transaction terminal for performing the methodUS20130073373 *Nov 19, 2012Mar 21, 2013Blaze Mobile, Inc.Single tap transactions using a point-of-sale terminalUS20130073467 *Sep 16, 2011Mar 21, 2013Verizon Patent And Licensing Inc.Method and system for conducting financial transactions using mobile devicesUS20130080228 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap using a user selected cardUS20130080229 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap using user selected couponsUS20130080230 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap using both user selected payment method and user selected couponsUS20130080231 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap transactions using a mobile applicationUS20130080232 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap transactions using a mobile deviceUS20130080233 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap transactions using a secure elementUS20130080240 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap transactions using a serverUS20130080241 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Redeeming coupons using nfcUS20130085941 *Sep 30, 2011Apr 4, 2013Apple Inc.Systems and methods for secure wireless financial transactionsUS20130097032 *Dec 11, 2012Apr 18, 2013Blaze Mobile, Inc.Utilizing shopping lists for nfc transactionsUS20130097034 *Oct 12, 2012Apr 18, 2013First Data CorporationSystems and Methods for Facilitating Point of Sale TransactionsUS20130097036 *Dec 5, 2012Apr 18, 2013Blaze Mobile, Inc.Using a mobile device as a point of sale terminalUS20130097040 *Dec 7, 2012Apr 18, 2013Blaze Mobile, Inc.Online purchase from a mobile device using a default payment methodUS20130097041 *Dec 11, 2012Apr 18, 2013Blaze Mobile, Inc.Online shopping using a cloud-based mobile walletUS20130097083 *Dec 5, 2012Apr 18, 2013Blaze Mobile, Inc.Using a secure element coupled to a mobile device as a pos terminal for processing nfc transactionsUS20130103466 *Dec 7, 2012Apr 25, 2013Blaze Mobile, Inc.Financial transaction processing with digital artifacts using a mobile communications deviceUS20130103478 *Dec 10, 2012Apr 25, 2013Blaze Mobile, Inc.Online shopping using nfc and a mobile deviceUS20130103511 *Dec 10, 2012Apr 25, 2013Blaze Mobile, Inc.Online shopping using nfc and a point-of-sale terminalUS20130103512 *Dec 11, 2012Apr 25, 2013Blaze Mobile, Inc.Online shopping using nfc and a secure elementUS20130103513 *Dec 11, 2012Apr 25, 2013Blaze Mobile, Inc.Online shopping using nfc and a serverUS20130103514 *Dec 11, 2012Apr 25, 2013Blaze Mobile, Inc.Online shopping using a mobile payment systemUS20130103517 *Dec 7, 2012Apr 25, 2013Blaze Mobile, Inc.Using a secure element coupled to a mobile device as a pos terminal for processing mag stripe transactionsUS20130103518 *Dec 12, 2012Apr 25, 2013Blaze Mobile, Inc.In store mobile payment using a default payment methodUS20130103588 *Dec 7, 2012Apr 25, 2013Blaze Mobile, Inc.Processing payments at a management server with a user selected payment methodUS20130124289 *Jan 7, 2013May 16, 2013Blaze Mobile, Inc.Remote transaction processing using authentication informationUS20130124290 *Jan 7, 2013May 16, 2013Blaze Mobile, Inc.Remote transaction processing using a default payment methodUS20130124291 *Jan 7, 2013May 16, 2013Blaze Mobile, Inc.Remote transaction processing with multiple payment mechanismsUS20130124351 *Dec 5, 2012May 16, 2013Blaze Mobile, Inc.Using an nfc enabled mobile device as a pos terminalUS20130124423 *Dec 11, 2012May 16, 2013Blaze Mobile, Inc.Online payment using an nfc enabled deviceUS20130132181 *Jan 7, 2013May 23, 2013Blaze Mobile, Inc.Remote transaction processing with multiple payment methods using authenticationUS20130138517 *Nov 30, 2011May 30, 2013Infosys LimitedMethod and system for integrating wireless devices with existing point of sale systemsUS20130144734 *Dec 6, 2011Jun 6, 2013Richard Scott PerkinsMoney transfer system using pre-funded escrowUS20130144789 *Jan 29, 2013Jun 6, 2013Apple Inc.Method and system for managing credits via a mobile deviceUS20130204789 *Mar 14, 2013Aug 8, 2013Amazon Technologies, Inc.Utilizing phrase tokens in transactionsUS20130204790 *Mar 14, 2013Aug 8, 2013Amazon Technologies, Inc.Utilizing phrase tokens in transactionsUS20130238499 *Mar 6, 2012Sep 12, 2013Ayman HammadSecurity system incorporating mobile deviceUS20130239091 *Apr 22, 2013Sep 12, 2013Ebay Inc.Orthogonal experimentation in a computing environmentUS20130262314 *Mar 30, 2012Oct 3, 2013David G. ButlerEncrypted payment imageUS20130311382 *May 21, 2012Nov 21, 2013Klaus S. FosmarkObtaining information for a payment transactionUS20130346245 *Jun 26, 2012Dec 26, 2013Ebay, Inc.System and Method for Conducting Delegated PaymentsUS20140025517 *Jul 23, 2012Jan 23, 2014Wal-Mart Stores, Inc.Transferring digital receipt data to mobile devicesUS20140040052 *Oct 11, 2013Feb 6, 2014First Data CorporationMobile commercial systems and methodsUS20140052521 *Oct 25, 2013Feb 20, 2014Envizo, Inc.Campaign reward system in communication with financial institutionUS20140074707 *Aug 29, 2013Mar 13, 2014Blaze Mobile, Inc.Personalized mobile banking transactionsUS20140074722 *Sep 12, 2012Mar 13, 2014Microsoft CorporationUse of state objects in near field communication (nfc) transactionsUS20140081784 *Sep 13, 2013Mar 20, 2014Lg Cns Co., Ltd.Payment method, payment server performing the same and payment system performing the sameUS20140099981 *Oct 5, 2012Apr 10, 2014SHC Direct, L.L.C.Method and system for communicating between a mobile device and a remote deviceUS20140108260 *Dec 18, 2013Apr 17, 2014Capital One Financial CorporationSystem and method for token-based paymentsUS20140108265 *Dec 20, 2013Apr 17, 2014The Toronto Dominion BankSystem and method of authenticating a network gatewayUS20140117075 *Oct 26, 2012May 1, 2014Lee S. WeinblattMobile Device-Based Electronic Payment Systems and MethodsUS20140122335 *Oct 30, 2012May 1, 2014International Business Machines CorporationReal-Time Regulation of Personal Expenditures and TransactionsUS20140129441 *Nov 2, 2012May 8, 2014German BlancoSystems and methods for authorizing sensitive purchase transactions with a mobile deviceUS20140143078 *Jun 21, 2012May 22, 2014Planet Payment Solutions LimitedDistributed transaction processing system and methodsUS20140149196 *Oct 28, 2013May 29, 2014Envizio, Inc.Offer redemption of an offer at a retailerUS20140164092 *Feb 14, 2014Jun 12, 2014Michelle FisherRemote transaction processing at a server using a default payment method and couponsUS20140164157 *Feb 13, 2014Jun 12, 2014Michelle FisherFinancial transaction processing with digital artifacts and a default payment method using a serverUS20140195362 *Dec 30, 2013Jul 10, 2014Michelle FisherRemote transaction processing with a point-of-entry terminal using bluetoothUS20140222600 *Apr 9, 2014Aug 7, 2014At&T Intellectual Property I, LpMethod and apparatus for fulfilling purchasesUS20140229259 *Mar 18, 2014Aug 14, 2014Michelle FisherRemote transaction processing with an adUS20140229276 *Feb 24, 2014Aug 14, 2014Michelle FisherFinancial transaction processing with digital artifacts and a default payment method using a posUS20140279108 *Mar 14, 2013Sep 18, 2014William P. VasquezSystems and methods for integrated, secure point-of-sale transactions having a terminal management systemUS20140297439 *Jun 16, 2014Oct 2, 2014Accenture Global Services LimitedCustomer initiated payment method using mobile deviceUS20140297518 *Dec 30, 2013Oct 2, 2014Michelle FisherRemote delivery of digital artifactsUS20140297795 *Jun 10, 2014Oct 2, 2014Ebay Inc.Orthogonal experimentation in a computing environmentUS20140302824 *Mar 24, 2014Oct 9, 2014Michelle FisherRemote access to contentUS20140304073 *Mar 24, 2014Oct 9, 2014Michelle FisherRemote access to couponsUS20140304082 *Mar 19, 2014Oct 9, 2014Michelle FisherPersonalized mobile banking transactions at a server without authentication and adsUS20140304095 *Mar 19, 2014Oct 9, 2014Michelle FisherPersonalized mobile banking transactions at a server without authenticationUS20140304160 *Apr 8, 2014Oct 9, 2014Michelle FisherUsing a mobile device as a point of sale terminal with a server and digital artifactsUS20140304161 *Apr 8, 2014Oct 9, 2014Michelle FisherUsing a mobile device as a point of sale terminal with a server and receiptsUS20140308934 *Apr 1, 2014Oct 16, 2014Michelle FisherRemote delivery of receipts from a serverUS20140310161 *Apr 15, 2014Oct 16, 2014Michelle FisherRemote transaction processing of mediaUS20140324560 *Apr 15, 2014Oct 30, 2014Michelle FisherRemote transaction processing of a ticketUS20140324574 *Apr 15, 2014Oct 30, 2014Michelle FisherRemote access to mediaUS20140324635 *Apr 15, 2014Oct 30, 2014Michelle FisherRemote access to ticketsUS20140324697 *Apr 15, 2014Oct 30, 2014Michelle FisherRemote transaction processing of contentUS20140330626 *Apr 22, 2014Nov 6, 2014Michelle FisherSingle tap transactions using a mobile application with authenticationUS20140379577 *Mar 20, 2014Dec 25, 2014Infosys LimitedMethods, systems, and computer-readable media for providing financial transactionsUS20150032524 *Apr 22, 2014Jan 29, 2015Michelle FisherSingle tap transactions using a server with authenticationUS20150039479 *Jul 31, 2014Feb 5, 2015Toshiba Tec Kabushiki KaishaElectronic receipt system, merchandise sales data processing apparatus, and electronic receipt management serverUS20150058226 *Aug 26, 2013Feb 26, 2015My City Tag LlcToken for short range rf transaction notificationUS20150134539 *Nov 12, 2013May 14, 2015Shashi KapurSystem and method of processing point-of-sale payment transactions via mobile devicesUS20150142541 *Nov 18, 2013May 21, 2015Michelle T. FisherRemote transaction processing at a server based on user confiration and a default payment methodUS20150142542 *Nov 19, 2013May 21, 2015Michelle T FisherRemote transaction processing at a server based on user confiration and multiple payment methodUS20150161579 *Dec 11, 2013Jun 11, 2015Verifone, Inc.Point of sale systemUS20150178731 *Dec 20, 2013Jun 25, 2015Ncr CorporationMobile device assisted serviceUS20150262165 *Apr 14, 2015Sep 17, 2015Miichelle FisherInduction based transactions at a remote server with authenticationUS20150287023 *May 28, 2015Oct 8, 2015Neology, Inc.System and methods for providing secure transactional solutionsUS20150310420 *Apr 14, 2015Oct 29, 2015Michelle FisherInduction based transactions at a remote serverUS20150324800 *Apr 14, 2015Nov 12, 2015Mts Holdings, Inc.System and Method of Processing PIN-Based Payment Transactions via Mobile DevicesUS20160078425 *Oct 5, 2015Mar 17, 2016Michelle FisherFinancial transaction processing with digital artifacts and multiple payment methods using a serverUS20160162390 *Feb 15, 2016Jun 9, 2016Ebay Inc.Orthogonal experimentation in a computing environmentUS20160241541 *Feb 12, 2015Aug 18, 2016At&T Mobility Ii, LlcPoint of Sale PairingUSRE44669May 11, 2012Dec 24, 2013Mocapay, Inc.Systems and method for secure wireless payment transactionsCN102739660A *Jun 16, 2012Oct 17, 2012华南师范大学Key exchange method for single sign on systemCN102742211B *Jan 29, 2010Sep 7, 2016奥马尔科网络解决方案有限公司与多功能认证系统相关的改进CN103477358A *Dec 2, 2011Dec 25, 2013谷歌公司Multiple contactless device interactions and communication protocols per tapDE102007006659A1 *Feb 10, 2007Aug 14, 2008Walter KellerElectronic paying method for use at e.g. automat, involves comparing salesman identification with point-of-sale data so that financial transaction is confirmed or neglected, and routing comparison result to accounts management deviceEP2171659A2 *Jun 25, 2008Apr 7, 2010VISA INTERNATIONAL, Inc.Secure mobile payment systemEP2171659B1 *Jun 25, 2008Apr 6, 2016Visa International Service AssociationSecure mobile payment systemEP2218046A2 *Oct 24, 2008Aug 18, 2010Visa International Service AssociationPayment transaction using mobile phone as relayEP2218046A4 *Oct 24, 2008May 25, 2011Visa Int Service AssPayment transaction using mobile phone as relayEP2232422A1Dec 4, 2008Sep 29, 2010Accumulate AbA method for secure transactionsEP2266087A2 *Apr 2, 2009Dec 29, 2010Global 1 Enterprises, Inc.Mobile telephone transaction systems and methodsEP2266087A4 *Apr 2, 2009Feb 29, 2012Global 1 Entpr IncMobile telephone transaction systems and methodsEP2308014A1 *Jun 4, 2009Apr 13, 2011eBay Inc.Trusted service manager (tsm) architectures and methodsEP2308014A4 *Jun 4, 2009Nov 6, 2013Ebay IncTrusted service manager (tsm) architectures and methodsEP2504801A1 *Nov 23, 2010Oct 3, 2012Alibaba Group Holding LimitedSecure mobile payment processingEP2504801A4 *Nov 23, 2010Feb 25, 2015Alibaba Group Holding LtdSecure mobile payment processingEP2587430A1 *Aug 31, 2012May 1, 2013NCR CorporationCustomer identification with automated transactionsEP2657895A3 *Dec 4, 2008Mar 19, 2014Accumulate AbA method for secure transactionsEP2657896A3 *Dec 4, 2008Mar 19, 2014Accumulate AbMethod for secure transactionsEP2695117A1 *Mar 20, 2012Feb 12, 2014Signature Systems LLCMethod, system and device for executing a mobile transactionEP2695117A4 *Mar 20, 2012Oct 15, 2014Signature Systems LlcMethod, system and device for executing a mobile transactionEP2698754A2Dec 4, 2008Feb 19, 2014Accumulate AbA method for secure transactionsEP2698754A3 *Dec 4, 2008Mar 19, 2014Accumulate AbA method for secure transactionsEP2698755A1 *Aug 17, 2012Feb 19, 2014redpixtec. GmbHMobile Payment SystemEP2702523B1Apr 25, 2012Dec 9, 2015TagattitudeModule for managing a transaction between a terminal and an electronic deviceEP2707843A1 *May 18, 2011Mar 19, 2014Intuit Inc.Processing electronic payment involving mobile communication deviceEP2707843A4 *May 18, 2011Jan 7, 2015Intuit IncProcessing electronic payment involving mobile communication deviceEP2709049A1 *Dec 4, 2008Mar 19, 2014Accumulate AbA method for secure transactionsEP2709050A1 *Dec 4, 2008Mar 19, 2014Accumulate AbA method for secure transactionsEP2711884A1 *Dec 4, 2008Mar 26, 2014Accumulate AbA method for secure transactionsEP2725536A1 *Oct 28, 2013Apr 30, 2014Lee S. WeinblattMobile device-based electronic payment systems and methodsEP2795553A4 *Dec 21, 2011Dec 16, 2015Intel CorpMethod for authentication using biometric data for mobile device e-commerce transactionsEP2828812A4 *Mar 18, 2013Nov 25, 2015Royal Canadian Mint Monnaie Royale CanadienneUsing bar-codes in an asset storage and transfer systemEP3024194A1 *Nov 20, 2014May 25, 2016Gemalto SaMethod for accessing a service and corresponding server, device and systemEP3033724A4 *Aug 13, 2014Feb 22, 2017Blackhawk Network IncOpen payment networkEP3115952A1 *Nov 15, 2013Jan 11, 2017Tenten Technologies LimitedMethod, system and mobile device for providing user rewardsWO2008092770A1 *Jan 21, 2008Aug 7, 2008Trium GmbhElectronic payment method and deviceWO2008103980A1 *Feb 25, 2008Aug 28, 2008Ipdev Co.A secure system and method for payment card and data storage and processing via information splittingWO2010002541A1 *Jun 4, 2009Jan 7, 2010Ebay, Inc.Trusted service manager (tsm) architectures and methodsWO2010095988A1 *Feb 18, 2009Aug 26, 2010Telefonaktiebolaget L M Ericsson (Publ)User authenticationWO2010129332A1 *Apr 28, 2010Nov 11, 2010Bank Of America CorporationConducting commercial transactions with a mobile deviceWO2010140969A1 *Jun 4, 2010Dec 9, 2010Accumulate AbA method for secure transactionsWO2010140971A1 *Jun 4, 2010Dec 9, 2010Accumulate AbA method for secure transactionsWO2011057096A1 *Nov 5, 2010May 12, 2011Wal-Mart Stores, Inc.System and method for communicating information to a customer at a point-of sale via a wireless link within a retail storeWO2011112158A1 *Jul 16, 2010Sep 15, 2011Margento R&D D.O.O.Wireless mobile transaction system and the procedure for carrying out transactions with a mobile phoneWO2011146678A2 *May 19, 2011Nov 24, 2011Intel CorporationMethod and device for conducting trusted remote payment transactionsWO2011146678A3 *May 19, 2011Apr 5, 2012Intel CorporationMethod and device for conducting trusted remote payment transactionsWO2012002852A1 *Jun 29, 2010Jan 5, 2012Telefonaktiebolaget L M Ericsson (Publ)Methods, server, merchant device, computer programs and computer program products for setting up communicationWO2012012445A2 *Jul 19, 2011Jan 26, 2012Universal Commerce, Inc.Mobile system and method for payments and non-financial transactionsWO2012012445A3 *Jul 19, 2011Mar 20, 2014Universal Commerce, Inc.Mobile system and method for payments and non-financial transactionsWO2012158057A1 *May 17, 2011Nov 22, 2012Alcatel LucentElectronic transactions with mobile communications devices via encoded acoustic signalsWO2013010056A2Jul 13, 2012Jan 17, 2013NetQash LLCMobile communication device based monetary transfer systemWO2013010056A3 *Jul 13, 2012May 10, 2013NetQash LLCMobile communication device based monetary transfer systemWO2013095434A1Dec 21, 2011Jun 27, 2013Intel CorporationMethod for authentication using biometric data for mobile device e-commerce transactionsWO2013100825A1 *Dec 28, 2012Jul 4, 2013Bilyukin Evgeniy YakovlevichCash register for a system of mobile paymentsWO2013151818A1 *Mar 25, 2013Oct 10, 2013Clinkle CorporationWireless transaction communication apparatus and methodWO2014030836A1 *Jul 3, 2013Feb 27, 2014Samsung Electronics Co., Ltd.Method and system for authenticating transaction request from deviceWO2014128351A1 *Feb 19, 2014Aug 28, 2014Op-Palvelut OyCommunication during payment procedureWO2015022363A1 *Aug 13, 2014Feb 19, 2015Afc Rechenzentrum GmbhCashless payment handling methodWO2015031843A1 *Aug 29, 2014Mar 5, 2015Alibaba Group Holding LimitedApproval of a payment by reading a qr code generated by a separate user or deviceWO2015071939A1 *Nov 15, 2013May 21, 2015Tenten Technologies LimitedMethod, system and mobile device for providing user rewardsWO2015090393A1 *Dec 19, 2013Jun 25, 2015Sotirios MelioumisMethod to achieve secure data exchangesWO2015103443A1 *Dec 31, 2014Jul 9, 2015Ebay Inc.Wireless beacon communications through magnetic card readersWO2015108568A1 *Aug 4, 2014Jul 23, 2015Framularo NicholeGlobal unique transaction identifier (uti) generatorWO2015163825A1 *Apr 24, 2015Oct 29, 2015Telecom Equipment Pte Ltd.A system and method for managing wireless transactions at a point of sale terminalWO2016079116A1 *Nov 17, 2015May 26, 2016Gemalto SaMethod for accessing a service and corresponding server, device and system* Cited by examinerClassifications U.S. Classification705/67International ClassificationG06Q20/00, G06Q99/00Cooperative ClassificationG06Q20/3272, G06Q20/3274, G06Q20/32, G06Q20/327, G06Q20/3674, G06Q20/20, G06Q20/3552, G07F7/1008, G06Q20/401, G06Q20/322, G06Q20/02, G06Q30/06, G06Q20/382European ClassificationG06Q30/06, G06Q20/32, G06Q20/20, G06Q20/3552, G06Q20/401, G06Q20/02, G06Q20/382, G06Q20/3674, G06Q20/3274, G06Q20/322, G06Q20/327, G07F7/10DLegal EventsDateCodeEventDescriptionSep 29, 2006ASAssignmentOwner name: FUJITSU LIMITED, JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LABROU, YANNIS;AGRE, JONATHAN RUSSELL;REEL/FRAME:018439/0442Effective date: 20060906Jan 10, 2012CCCertificate of correctionJan 29, 2014FPAYFee paymentYear of fee payment: 4Mar 30, 2016ASAssignmentOwner name: PCMS HOLDINGS, INC., DELAWAREFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FUJITSU LIMITED;REEL/FRAME:038139/0896Effective date: 20140404RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services