Patent Grant
10083434
A number of payment solutions exist. Existing payment solutions include smart cards. A smart card is typically a credit card-sized plastic card that includes an integrated circuit chip. The smart card interfaces with a card reader at a point-of-sale terminal at a merchant. The card reader interface on the card can include contacts, which can contact contacts on the card reader. During operation, signals from the integrated circuit are routed to the contacts on the card which come into physical contact with similar contacts in the card reader device so that the smart card can communicate with the outside world.
While smart cards are desirable, a number of improvements could be made. For example, existing smart cards do not allow a payer to choose an exact source account for providing the payment and do not allow a payee to choose an exact target account for receiving the payment. They also do not allow payers and payees who might not have traditional card reader hardware to conduct financial transactions. For example, one family member may owe a debt to another family member. This transaction would be limited to either a cash or check-type transaction, since the family members would not operate card reader devices like those operated by merchants.
Also, when using a smart card, a payer may initiate a request for payment at a card reader at a point of sale. The card reader then communicates with a remotely located server computer, which approves of the transaction and facilitates subsequent processing to conclude the transaction. Since the initial request for payment and the subsequent acceptance of the initial request for payment requires a server computer, a payer and a payee that do not have immediate access to a server computer may not be able to conduct the transaction at any time and at any location. For example, the payer and the payee may be at a location which does not provide for easy access to any computer network, let alone a particular payment server computer.
Embodiments of the invention address the above-noted problems, and other problems, individually and collectively.
Embodiments of the invention are directed to methods, systems, computer readable media, and portable electronic devices that are useful for conducting transactions.
One embodiment of the invention is directed to a method for conducting a transaction comprising: using a first portable electronic device, directly transmitting a request for payment to a second portable electronic device through a wireless link; receiving approval of the request for payment at the first portable electronic device, wherein the approval is sent directly from the second portable electronic device to the first portable electronic device through the wireless link; and then sending the request for payment to a payment hub service, which facilitates the transfer of funds from a payer institution to a payee institution.
Another embodiment of the invention is directed to a method of facilitating a transaction comprising: receiving an approval of a request for payment at a server computer at a payment hub service, wherein the approval of the request for payment was obtained after a first portable electronic device directly transmitted a request for payment to a second portable electronic device through a wireless link, and after the approval of the request was received at the first portable electronic device, wherein the approval was sent directly from the second portable electronic device to the first portable electronic device through the wireless link; and then facilitating payment from a payer institution to a payee institution.
Other embodiments of the invention are directed to computer readable media comprising code for performing the above-noted methods.
Other embodiments of the invention are directed to portable electronic devices and server computers.
Embodiments of the invention have a number of advantages. Embodiments of the invention can be used to conduct financial transactions using an existing payments infrastructure and using the computing capabilities in common handheld wireless devices like cell phones or personal digital assistants. Embodiments of the invention can also support the sending and receiving of payments between dissimilar payment methods and services. Payment requests can be submitted to a trusted intermediary capable of brokering between dissimilar payer and payee payment methods. Embodiments of the invention also can also allow payers and payees to specify the exact source and target financial accounts and institutions to be used in conducting a transaction, and can also establish trust between parties.
These and other embodiments of the invention are described below with reference to the Figures and the Detailed Description.
Embodiments of the invention include transactions between two or more parties (e.g., a payer, a payee, etc.) using portable electronic devices that communicate through one or more wireless links. The parties' portable electronic devices preferably initially communicate with each other directly through the one or more wireless links, rather than indirectly through a server computer.
In one exemplary illustration of an embodiment of the invention, a payee directly transmits a request for payment from a first portable electronic device operated by the payee to a second portable electronic device operated by the payer. The transmission of the request for payment occurs through a wireless link that provides for a direct communication channel between the first portable electronic device and the second portable electronic device. The second portable electronic device then receives the request for payment. After receiving the request for payment, a payer operating the second portable electronic device transmits an approval of the request for payment to the first portable electronic device through the wireless link.
After the request for acceptance has been initiated and accepted, the request for payment is sent to a payment hub service. Providers of the payment hub service may include entities such as banks or credit card processors. The payment hub service may be remotely located with respect to the portable electronic device and facilitates the transfer of funds from a payer institution such as a payer bank to a payee institution such as a payee bank. The request for payment may be transmitted to the payment hub service by either the first portable electronic device operated by the payee or the second portable electronic device operated by the payer. Further details regarding preferred embodiments of the invention are provided below.
The various parties that participate in the transaction may have different roles. For example, the roles may include a “payer”, a “payee”, a “transmitter”, an “initiator”, and a “recipient”. A single person or organization may have more than one role. For example, a payer can also be a transmitter and an initiator in some embodiments.
As used herein, the “payer” is the party that pays value in a transaction. The “payee” is the party that receives value in the transaction. The “transmitter” may be the party that communicates the request for payment to the payment hub service. Either the payer or the payee may be the transmitter. The transmitter can have a relationship with the payment hub service.
The “initiator” of the request for payment in the transaction is the party whose portable electronic device (or application residing in the portable electronic device) will begin the transaction by initiating the request for payment. Either the payer or payee may initiate the request. The “recipient” of the request for payment is the party whose portable electronic device (or application residing in the portable electronic device) will receive the initial request for payment. Either the payer or payee may receive the request.
Embodiments of the invention provide for a number of advantages. First, embodiments of the invention can be used for a wide variety of payments between individuals, partnerships or corporations in place of cash or personal checks. For example, embodiments of the invention can be used for traditional purchases from established merchants; or other payments to individuals or groups where cash or checks are most common today. Second, embodiments of the invention also provide the payer with the convenience of paying in an auditable, secure manner. They can decrease risk of loss through theft, and can provide a record of payment date, amount and payee. They can also provide the payee with the security of payments facilitated by trusted institutions, thereby providing for reduced repudiation risk, faster funds availability, and decreased risk of loss through theft.
Embodiments of the invention can be used in any suitable environment including traditional and non-traditional payment settings. For example, they can be used to support payments to traditional bricks-and-mortar and Internet vendors. They can also be used in different ways including, but not limited to: casual purchasing at events such as garage sales; transferring money to a child attending college; repaying personal debts; paying child support; and paying domestic employees such as nannies and gardeners.
Specific embodiments of the invention can be described with reference to
The portable electronic devices 12, 14 may have any suitable characteristics, and may be the same or different. For example, the portable electronic devices may be selected from the group consisting of portable computers, hand-held mobile phones (e.g., cell phones), personal digital assistants, etc. Both portable electronic devices 12, 14 are capable of short range (e.g., line of sight) wireless communication.
In embodiments of the invention, the portable electronic devices 12, 14 may contain digital certificates and cryptogram capabilities that support two-factor authentication and transmission encryption. Security can be established between the portable electronic devices 12, 14, and between at least one of the portable electronic devices 12, 14 and the payment hub service 18. As explained below, software applications residing in the portable electronic devices 12, 14 can provide the desired security. Further details regarding the portable electronic devices 12, 14 are provided below.
The first and second portable electronic devices 12, 14 can communicate though a wireless link 50. The wireless link 50 provides a short range communication channel for the first and second portable electronic devices 12, 14. It may be based on known technologies including infrared, Wi-Fi, and Bluetooth technologies. See “Evaluation of Wireless Techniques for Short Range Communication” by Jonas Söderkuist.
Providing for direct wireless communication between the first and second portable electronic devices 12, 14 without a server computer provides a number of advantages. Because an intermediate server computer is not needed for initial communication between the payer and the payee, embodiments of the invention are more likely to be adopted by more users. First, known servers that act as intermediaries to payers and payees are typically tied to only one type of payment processing system. This limits the number of potential users. For example, if a server computer is operated by the well known company PayPal™, then both the payee and the payer must be affiliated with PayPal™. The payer cannot, for example, transfer funds from the payer's PayPal™ account to the payee's mutual fund account. However, in embodiments of the invention, since initial communication between the payer and the payee does not require a server computer that is tied to only one type of payment processing system, different source and target accounts can be provided by the payer and the payee to conduct the desired transaction. As explained in detail below, the hub service provider 18 may subsequently facilitate the task of transferring the appropriate funds from the selected source account to the selected target account, after the request for payment has been presented to the payee and accepted by the payee. Second, since the payer and the payee do not rely on an intermediary server computer for initial communication, the payer and payee could, but need not have immediate access to a server computer to conduct the transaction. This allows the payer and the payee to conduct the transaction in more places than would be possible if an intermediary server computer was used.
The first and second portable electronic devices 12, 14 may communicate with a network 16. The network 16 may comprise any suitable wired and/or wireless communication medium. For example, the network 16 may include the Internet.
A payment hub service 18 is in communication with the network 16. At least one of the portable electronic devices 12, 14 is capable of long-range communication, using WiFi, Internet or mobile voice telephone capability so that communication with the hub service 18 is possible.
The payment hub service 18 may include a server computer. A server computer is typically a powerful computer or cluster of computers. For example, the server computer an be a large mainframe, a minicomputer cluster, or a group of servers functioning as a unit. In one example, the server computer may be a database server coupled to a web server. Moreover, the server computer can behave as a single computer, which services the requests of one or more client computers or portable electronic devices.
The server computer at the payment hub service 18 may include a computer readable medium that may be embodied by one or more data storage devices using any suitable mechanism for data storage. The computer readable medium may have computer code for performing any of the functions of the payment hub service 18. For example, the computer readable medium may comprise code for receiving an approval of a request for payment at a server computer at a payment hub service, where the approval of the request for payment was obtained after a first portable electronic device directly transmitted a request for payment to a second portable electronic device through a wireless link, and after the approval of the request was received at the first portable electronic device, where the approval was sent directly from the second portable electronic device to the first portable electronic device through the wireless link. The computer readable medium may also comprise code for facilitating payment from a payer institution to a payee institution.
At least one of the portable electronic devices can communicate with the remotely located payment hub service 18. The payment hub service 18 communicates with a payer institution 20 such as a payer bank and a payee institution 24 such a payee bank. An optional intermediary 22 may be in communication with the payer institution 20 and the payee institution 24 to help facilitate the transaction. The intermediary 22 could be a credit card processing organization, an ACH (automated clearing house), etc.
The one or more input devices 72 may include a keyboard, a touch sensitive pad, a voice-recognition system, etc. The display 70 may be an LCD (liquid crystal display), LED (light emitting diodes), or any other suitable display. The display 70 allows the payer and the payee to select the appropriate target and source accounts for their funds transfer. An optional audio output device such as a speaker or earphone jack could also be included.
The computer readable medium in the memory unit 64 may comprise use any suitable electrical, magnetic, or optical mechanism for storing computer readable data. For example, the computer readable medium may comprise one or more of an optical disk, memory chips (e.g., RAM chip, ROM chip, EEPROM chip), etc.
Any of the functions performed by the portable electronic device may be stored as computer code. For example, the computer readable medium may comprise code for directly transmitting a request for payment from a first portable electronic device to a second portable electronic device through a wireless link, code for receiving approval of the request for payment, wherein the approval is sent directly from the second portable electronic device to the first portable electronic device through the wireless link, and code for sending the request for payment to a payment hub service which facilitates the transfer of funds from a payer institution to a payee institution. The computer readable medium may also comprise code for allowing the payer to select one or more source accounts and for allowing a payee to select one or more target accounts for use in the transaction between the payer and the payee. Examples of target and source accounts may include bank accounts, mutual fund accounts, debit card accounts, etc.
The wireless transmitter 66 and wireless receiver 68 may transmit or receive signals from other wireless transmitters and wireless receivers through a wireless link. They may receive and transmit wireless signals such as optical signals, IR signals, RF signals, etc. Suitable wireless transmitters and receivers are commercially available and need not be described in detail herein.
Preferred methods according to embodiments of the invention can be described with reference to both
A payee 8 and the payer 10 first authenticate themselves to their respective portable electronic devices 12, 14 (step 102). Software applications in the first and second portable electronic devices 12, 14 are initiated and “unlocked” by the payee 8 and the payer 10 before the payment by the payer 10 can be enabled. For example, to unlock the software application in the first portable electronic device 12, the payee 8 provides a secure password to the portable electronic device 12.
In embodiments of the invention, until the software application on a portable electronic device is unlocked by the appropriate party, no other function is permitted. After a specified number of unsuccessful attempts to unlock the software application have occurred, the software application can be disabled and cannot be used until the application service provider resets the device. This process may be reused during other steps of the payment process to ensure security.
As an additional security measure, in some embodiments, neither the payer nor the payee can view the other's payment account information. Account information can be encrypted in the application and may not be stored in the portable electronic device after the transaction ends.
The software applications residing on the first and second portable electronic devices 12, 14 may be payment method neutral. In other words, the first and second portable electronic devices may not require the payer and the payee to use a particular payment method. For example, although in some embodiments, the software applications in the portable electronic devices 12, 14 may be generalized to support dissimilar payer and payee payment methods. In other embodiments, the portable electronic devices 12, 14 may work in concert with a single service provider such as Visa.
Before the transfer of funds takes place, the payer 10 and payee 8 agree on the manner in which information is exchanged between their portable electronic devices 12, 14 though a wireless communication link 50. The communication link 50 may use, for example, WiFi or infrared technology.
After the payer 10 and the payee 8 agree on the manner in which information is exchanged, the payee 8 uses the first portable electronic device 14 to initiate a request for payment (step 104). The request for payment may include role information, the amount of the payment, and the currency being used. Although the payee 8 initiates the payment request in this example, it is understood that in other embodiments, the payer 10 can alternatively begin the payment process by selecting a “request for payment” in the software application that resides in the payer's portable electronic device 12, 14. In this alternative embodiment, the second portable electronic device 14 would initiate the request for payment.
After the payee initiates the request for payment, trust is established between the first and second portable electronic devices 12, 14 (step 106). Put another way, security is established between the portable electronic devices 12, 14 before the payment process can proceed. Each portable electronic device 12, 14 can establish the identity of the other portable electronic device for checking in all subsequent data transmissions. For example, the first portable electronic device 12 establishes a secure network connection to the second portable electronic device 14 for checking in all subsequent data transmissions. Establishment of identity is performed using credentials present within the software applications in the first and second portable electronic devices 12, 14, without need for both the first and second portable electronic devices 12, 14 to authenticate to an intermediary such as an intermediary server computer.
Then, the request for payment is approved by the payer 10 (step 108). The payer's second portable electronic device 14 receives the request for payment data, and reviews it for acceptability. If the request is acceptable, the payer 10 indicates approval of the requested payment amount and indicates the payer's role in the transaction using the software application residing on the payee's second portable electronic device 14. The payer 10 then uses the second portable electronic device 14 to transmit the approval of the request for payment to the payee 8. If the request for payment is not acceptable, then the payer 10 denies the request and the denial is transmitted to the payee 8. If the payment request is acceptable, the payer 10 and payee 9 choose a payment method before the proceeding to the next step in the process. Any suitable type of payment method may be used. For example, the payer 10 may pay the payee 8 using a credit account, a debit account, etc.
Then, payer 10 account information is provided to the payee 8 (step 110). In this step, the software application residing, for example, on the first portable electronic device 14 collects information from several sources to create a set of data records that will be used with a payment hub service 18 to facilitate the payment. Several data exchanges between first and second portable electronic devices 12, 14 may be required to bring all of the data to the transmitter. In this instance, the transmitter may be the first portable electronic device 14 and/or the payee 8. The exact data exchange process is determined by the roles being played by the payee 8, payer 10, and the first and second portable electronic devices 12, 14. The software applications residing on the first and second portable electronic devices 12, 14 ensure that they are in constant contact during the transaction process.
The payment hub service 18 can act as a broker between different payment methods (e.g., credit, debit, and stored value). The payer 10 and payee 8 do not have to use the same payment method to accomplish the transfer. For example, the payer 10 may specify that the source of the funds (including account tokens if necessary) will come from the payer's debit card account. The payee 8 may specify that the target account for the funds will be the payee's checking account. If the payee 8 and/or the payer 10 do not want to use their actual financial accounts, proxy accounts may be used by the payee 8 and/or the payer 10.
Then, the second portable electronic device 14 provides payment audit details to the first portable electronic device 12 (step 112). At the beginning of this step, the payer 8 and the payee 10 confirm the details of the payment again. The software application residing in the second portable electronic device 14 creates an audit record and transmits it to the first portable electronic device 12. This provides a record indicating that a request for payment and approval thereof has occurred between the two portable electronic devices 12, 14. The audit record contains a tracking number that will be used in subsequent payment hub service processing to ensure integrity and audit ability. Each software application in each portable electronic device 12, 14 records the tracking number and payment date, time and amount for subsequent display and reconciliation.
Trust is then established between the payment hub service 18 and the first portable electronic device 12 (step 114). The first portable electronic device 12 may communicate with the payment hub service 18 through a network 16. In some embodiments, only one portable electronic device transmits the request for payment to the payment hub service 18. The transmission may occur shortly after the request for payment has been accepted, or may occur sometime after it has been accepted. Either the payer 10 or payee 8 can transmit the request to the payment hub service 18. In this step, the transmitter (which may be the payer 10 or the payee 8) and the payment hub service 18 establish the security needed for the transmission of payment request data to the payment hub service 18. Establishment of identity will be performed using credentials held within the software application residing in the transmitting portable electronic device and the payment hub service 18, without need for both parties to authenticate to an intermediary. The payment hub service 18 and the first portable electronic device 12 will be able to establish the identity of each other for checking in all subsequent data transmissions.
Then, a request payment transaction is performed (step 116). In this step, payment request data is transmitted from the transmitter device to the payment hub service, using the secure network connection and credentials established in the previous step. For example, in
Then, a payment transaction audit trail is provided (step 118). The payment hub service 18 provides advice records to the payer 10 and payee 8 account providers for audit and tracking purposes. The advice records may be used for many purposes, including, but not limited to financial reconciliation, risk management, and transaction research.
After the payment hub service 18 receives the request for payment, the payment hub service 18 transmits advice notification to the payer 10 and the second portable electronic device 14 (step 122). In some embodiments, the payment hub service 18 retains payment transaction records for audit and research. Tracking information supplied by a software application residing on at least one of the portable electronic devices can provide a key for locating audit records.
The payment hub service 18 can also facilitate the transfer of funds from a payer institution 20 such as a payer bank to the payee institution 24 such a payee bank by contacting one or more of these institutions. An intermediary 22 such as a credit card organization, an ACH (automated clearing house), etc. may facilitate the transfer of funds from the payer institution 20 to the payee institution 24.
Embodiments of the invention are not limited to those embodiments specifically described with reference to
The terms and expressions which have been employed herein are used as terms of description and not of limitation, and there is no intention in the use of such terms and expressions of excluding equivalents of the features shown and described, or portions thereof, it being recognized that various modifications are possible within the scope of the invention claimed. Moreover, any one or more features of any embodiment of the invention may be combined with any one or more other features of any other embodiment of the invention, without departing from the scope of the invention.
Also, it should be understood that the present invention as described above can be implemented in the form of control logic using computer software in a modular or integrated manner. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will know and appreciate other ways and/or methods to implement the present invention using hardware and a combination of hardware and software.
All references, patent applications, and patents mentioned above are herein incorporated by reference in their entirety for all purposes. None of them are admitted to be prior art to the presently claimed inventions.
This application is a continuation of U.S. patent application Ser. No. 12/263,254 filed Oct. 31, 2008, which is a continuation of U.S. patent application Ser. No. 11/877,842 filed on Oct. 24, 2007, now Abandoned, which is a continuation of U.S. patent application Ser. No. 11/519,276, filed Sep. 11, 2006, and issued as U.S. Pat. No. 7,407,094 on Aug. 5, 2008, which is a continuation application of U.S. patent application Ser. No. 11/040,640, filed Jan. 21, 2005, and issued as U.S. Pat. No. 7,124,937 on Oct. 24, 2006, all of which are herein incorporated by reference in their entirety for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4613904 | Lurie | Sep 1986 | A |
| 4674041 | Lemon et al. | Jun 1987 | A |
| 5305196 | Deaton et al. | Apr 1994 | A |
| 5327508 | Deaton et al. | Jul 1994 | A |
| 5353218 | DeLapa et al. | Oct 1994 | A |
| 5388165 | Deaton et al. | Feb 1995 | A |
| 5393965 | Bravman et al. | Feb 1995 | A |
| RE34915 | Nichtberger et al. | Apr 1995 | E |
| 5420606 | Begum et al. | May 1995 | A |
| 5430644 | Deaton et al. | Jul 1995 | A |
| 5448471 | Deaton et al. | Sep 1995 | A |
| 5483444 | Heintzeman et al. | Jan 1996 | A |
| 5502636 | Clarke | Mar 1996 | A |
| 5564073 | Takahisa | Oct 1996 | A |
| 5577266 | Takahisa et al. | Nov 1996 | A |
| 5579537 | Takahisa | Nov 1996 | A |
| 5592560 | Deaton et al. | Jan 1997 | A |
| 5595264 | Trotta, Jr. | Jan 1997 | A |
| 5604921 | Alanara | Feb 1997 | A |
| 5608874 | Ogawa et al. | Mar 1997 | A |
| 5621812 | Deaton et al. | Apr 1997 | A |
| 5627549 | Park | May 1997 | A |
| 5638457 | Deaton et al. | Jun 1997 | A |
| 5642485 | Deaton et al. | Jun 1997 | A |
| 5644723 | Deaton et al. | Jul 1997 | A |
| 5649114 | Deaton et al. | Jul 1997 | A |
| 5659469 | Deaton et al. | Aug 1997 | A |
| 5675662 | Deaton et al. | Oct 1997 | A |
| 5687322 | Deaton et al. | Nov 1997 | A |
| 5710886 | Christensen et al. | Jan 1998 | A |
| 5717866 | Naftzger | Feb 1998 | A |
| 5761648 | Golden et al. | Jun 1998 | A |
| 5791991 | Small | Aug 1998 | A |
| 5793972 | Shane | Aug 1998 | A |
| 5806044 | Powell | Sep 1998 | A |
| 5822735 | De Lapa et al. | Oct 1998 | A |
| 5855007 | Jovicic et al. | Dec 1998 | A |
| 5870030 | DeLuca et al. | Feb 1999 | A |
| 5878141 | Daly | Mar 1999 | A |
| 5878337 | Joao et al. | Mar 1999 | A |
| 5884277 | Khosla | Mar 1999 | A |
| 5905246 | Fajkowski | May 1999 | A |
| 5907830 | Engel et al. | May 1999 | A |
| 5917913 | Wang | Jun 1999 | A |
| 5920847 | Kolling | Jul 1999 | A |
| 5924080 | Johnson | Jul 1999 | A |
| 5959577 | Fan et al. | Sep 1999 | A |
| 5974399 | Giuliani et al. | Oct 1999 | A |
| 5979757 | Tracy et al. | Nov 1999 | A |
| 5982891 | Ginter et al. | Nov 1999 | A |
| 5991749 | Morrill, Jr. | Nov 1999 | A |
| 6002771 | Nielsen | Dec 1999 | A |
| 6009411 | Kepecs | Dec 1999 | A |
| 6009415 | Shurling et al. | Dec 1999 | A |
| 6012038 | Powell | Jan 2000 | A |
| 6014634 | Scroggie et al. | Jan 2000 | A |
| 6018718 | Walker et al. | Jan 2000 | A |
| 6035280 | Christensen | Mar 2000 | A |
| 6041309 | Laor | Mar 2000 | A |
| 6049778 | Walker et al. | Apr 2000 | A |
| 6062991 | Moriarty et al. | May 2000 | A |
| 6067526 | Powell | May 2000 | A |
| 6067529 | Ray et al. | May 2000 | A |
| 6076068 | DeLapa et al. | Jun 2000 | A |
| 6076069 | Laor | Jun 2000 | A |
| 6076101 | Kamakura et al. | Jun 2000 | A |
| 6098053 | Slater | Aug 2000 | A |
| 6128599 | Walker et al. | Oct 2000 | A |
| 6175922 | Wang | Jan 2001 | B1 |
| 6185541 | Scroggie et al. | Feb 2001 | B1 |
| 6189787 | Dorf | Feb 2001 | B1 |
| 6237145 | Narasimhan et al. | May 2001 | B1 |
| 6279112 | O'Toole, Jr. et al. | Aug 2001 | B1 |
| 6292786 | Deaton et al. | Sep 2001 | B1 |
| 6307958 | Deaton et al. | Oct 2001 | B1 |
| 6318631 | Halperin | Nov 2001 | B1 |
| 6321208 | Barnett et al. | Nov 2001 | B1 |
| 6330543 | Kepecs | Dec 2001 | B1 |
| 6334108 | Deaton et al. | Dec 2001 | B1 |
| 6336098 | Fortenberry et al. | Jan 2002 | B1 |
| 6336099 | Barnett et al. | Jan 2002 | B1 |
| 6351735 | Deaton et al. | Feb 2002 | B1 |
| 6366893 | Hannula et al. | Apr 2002 | B2 |
| 6377935 | Deaton et al. | Apr 2002 | B1 |
| 6386451 | Sehr | May 2002 | B1 |
| 6424949 | Deaton et al. | Jul 2002 | B1 |
| 6424951 | Shurling et al. | Jul 2002 | B1 |
| 6434534 | Walker et al. | Aug 2002 | B1 |
| 6438527 | Powar | Aug 2002 | B1 |
| 6464139 | Wilz et al. | Oct 2002 | B1 |
| 6470181 | Maxwell | Oct 2002 | B1 |
| 6473739 | Showghi et al. | Oct 2002 | B1 |
| 6484146 | Day et al. | Nov 2002 | B2 |
| 6490443 | Freeny, Jr. | Dec 2002 | B1 |
| 6493676 | Levy | Dec 2002 | B1 |
| 6505046 | Baker | Jan 2003 | B1 |
| 6516302 | Deaton et al. | Feb 2003 | B1 |
| 6560581 | Fox et al. | May 2003 | B1 |
| 6587835 | Treyz et al. | Jul 2003 | B1 |
| 6601759 | Fife et al. | Aug 2003 | B2 |
| 6609104 | Deaton et al. | Aug 2003 | B1 |
| 6611811 | Deaton et al. | Aug 2003 | B1 |
| 6647256 | Stewen et al. | Nov 2003 | B1 |
| 6647257 | Owensby | Nov 2003 | B2 |
| 6647269 | Hendrey et al. | Nov 2003 | B2 |
| 6664948 | Crane et al. | Dec 2003 | B2 |
| 6685093 | Challa et al. | Feb 2004 | B2 |
| 6697944 | Jones | Feb 2004 | B1 |
| 6726092 | Goldberg et al. | Apr 2004 | B2 |
| 6736322 | Gobburu et al. | May 2004 | B2 |
| 6684195 | Deaton et al. | Jun 2004 | B1 |
| 6775539 | Deshpande | Aug 2004 | B2 |
| 6784874 | Shimizu | Aug 2004 | B1 |
| 6816724 | Asikainen | Nov 2004 | B1 |
| 6837425 | Gauthier et al. | Jan 2005 | B2 |
| 6868391 | Hultgren | Mar 2005 | B1 |
| 6873970 | Showghi et al. | Mar 2005 | B2 |
| 6888443 | Ritter | May 2005 | B2 |
| 6912398 | Domnitz | Jun 2005 | B1 |
| 6913191 | Goldberg et al. | Jul 2005 | B2 |
| 6925565 | Black | Aug 2005 | B2 |
| 6934689 | Ritter et al. | Aug 2005 | B1 |
| 6988657 | Singer et al. | Jan 2006 | B1 |
| 7003495 | Burger et al. | Feb 2006 | B1 |
| 7013286 | Aggarwal et al. | Mar 2006 | B1 |
| 7014107 | Singer et al. | Mar 2006 | B2 |
| 7025256 | Drummond et al. | Apr 2006 | B1 |
| 7028008 | Powar | Apr 2006 | B2 |
| 7028906 | Challa et al. | Apr 2006 | B2 |
| 7039022 | Hedeas | May 2006 | B1 |
| 7039440 | Rodriguez et al. | May 2006 | B2 |
| 7040533 | Ramachandran | May 2006 | B1 |
| 7051923 | Nguyen et al. | May 2006 | B2 |
| 7055031 | Platt | May 2006 | B2 |
| 7080037 | Burger et al. | Jul 2006 | B2 |
| 7085556 | Offer | Aug 2006 | B2 |
| 7089214 | Wang | Aug 2006 | B2 |
| 7096003 | Joao et al. | Aug 2006 | B2 |
| 7124937 | Myers et al. | Oct 2006 | B2 |
| 7131578 | Paschini et al. | Nov 2006 | B2 |
| 7133659 | Zalewski et al. | Nov 2006 | B2 |
| 7150393 | Drummond et al. | Dec 2006 | B1 |
| 7201313 | Ramachandran | Apr 2007 | B1 |
| 7207477 | Ramachandran | Apr 2007 | B1 |
| 7280981 | Huang et al. | Oct 2007 | B2 |
| 7315823 | Brondrup | Jan 2008 | B2 |
| 7349871 | Labrou et al. | Mar 2008 | B2 |
| 7376587 | Neofytides et al. | May 2008 | B1 |
| 7386491 | Ashizaki et al. | Jun 2008 | B2 |
| 8205794 | Myers et al. | Jun 2012 | B2 |
| 20020052193 | Chetty | May 2002 | A1 |
| 20020052841 | Guthrie et al. | May 2002 | A1 |
| 20020062281 | Singhai | May 2002 | A1 |
| 20020065774 | Young | May 2002 | A1 |
| 20020069165 | O'Neil | Jun 2002 | A1 |
| 20020073046 | David | Jun 2002 | A1 |
| 20020091569 | Kitaura et al. | Jul 2002 | A1 |
| 20020128928 | Sukegawa | Sep 2002 | A1 |
| 20020147913 | Lun Yip | Oct 2002 | A1 |
| 20020152123 | Giordano et al. | Oct 2002 | A1 |
| 20020152178 | Lee | Oct 2002 | A1 |
| 20020161704 | Powar | Oct 2002 | A1 |
| 20020165775 | Tagseth et al. | Nov 2002 | A1 |
| 20020178112 | Goeller et al. | Nov 2002 | A1 |
| 20020194137 | Park et al. | Dec 2002 | A1 |
| 20020198777 | Yuasa | Dec 2002 | A1 |
| 20030004876 | Jacobson | Jan 2003 | A1 |
| 20030120593 | Bansal et al. | Jan 2003 | A1 |
| 20030055792 | Kinoshita et al. | Mar 2003 | A1 |
| 20030058261 | Challa et al. | Mar 2003 | A1 |
| 20030078844 | Takatori et al. | Apr 2003 | A1 |
| 20030089767 | Kiyomatsu | May 2003 | A1 |
| 20030101134 | Liu et al. | May 2003 | A1 |
| 20030126076 | Kwok et al. | Jul 2003 | A1 |
| 20030144907 | Cohen et al. | Jul 2003 | A1 |
| 20030212595 | Antonucci | Nov 2003 | A1 |
| 20040004117 | Suzuki | Jan 2004 | A1 |
| 20040019564 | Goldthwaite et al. | Jan 2004 | A1 |
| 20040030601 | Pond et al. | Feb 2004 | A1 |
| 20040044621 | Huang et al. | Mar 2004 | A1 |
| 20040050922 | Gauthier et al. | Mar 2004 | A1 |
| 20040054575 | Marshall | Mar 2004 | A1 |
| 20040054581 | Redford et al. | Mar 2004 | A1 |
| 20040054591 | Spaeth et al. | Mar 2004 | A1 |
| 20040103063 | Takayama et al. | May 2004 | A1 |
| 20040107170 | Labrou et al. | Jun 2004 | A1 |
| 20040117254 | Nemirofsky et al. | Jun 2004 | A1 |
| 20040122685 | Bunce | Jun 2004 | A1 |
| 20040148224 | Gauthier et al. | Jul 2004 | A1 |
| 20040148254 | Hauser | Jul 2004 | A1 |
| 20040167820 | Melick et al. | Aug 2004 | A1 |
| 20040199474 | Ritter et al. | Oct 2004 | A1 |
| 20040254848 | Golan et al. | Dec 2004 | A1 |
| 20050017068 | Zalewski et al. | Jan 2005 | A1 |
| 20050027543 | Labrou et al. | Feb 2005 | A1 |
| 20050036611 | Seaton et al. | Feb 2005 | A1 |
| 20050045718 | Bortolin | Mar 2005 | A1 |
| 20050058427 | Nguyen et al. | Mar 2005 | A1 |
| 20050071225 | Bortolin et al. | Mar 2005 | A1 |
| 20050071226 | Nguyen et al. | Mar 2005 | A1 |
| 20050071227 | Hammad et al. | Mar 2005 | A1 |
| 20050071228 | Bortolin et al. | Mar 2005 | A1 |
| 20050121506 | Gauthier et al. | Jun 2005 | A1 |
| 20050149439 | Suisa | Jul 2005 | A1 |
| 20050149455 | Bruesewitz et al. | Jul 2005 | A1 |
| 20050154877 | Trench | Jul 2005 | A1 |
| 20050216354 | Bam | Sep 2005 | A1 |
| 20060004658 | Chau et al. | Jan 2006 | A1 |
| 20060074768 | Horton | Apr 2006 | A1 |
| 20060080243 | Kemper et al. | Apr 2006 | A1 |
| 20060085260 | Yamagishi | Apr 2006 | A1 |
| 20060085848 | Aissi et al. | Apr 2006 | A1 |
| 20060111967 | Forbes | May 2006 | A1 |
| 20070001001 | Myers et al. | Jan 2007 | A1 |
| 20070124211 | Smith | May 2007 | A1 |
| 20070192245 | Fisher | Aug 2007 | A1 |
| 20070203833 | Huang et al. | Aug 2007 | A1 |
| 20080255890 | Hilliard | Oct 2008 | A1 |
| 20150032634 | D'Agostino et al. | Jan 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 10007518 | Aug 2001 | DE |
| 1109138 | Jun 2001 | EP |
| 08-087655 | Apr 1996 | JP |
| 9745814 | Dec 1997 | WO |
| 1999051038 | Jul 1999 | WO |
| 2000003328 | Jan 2000 | WO |
| 0171627 | Sep 2001 | WO |
| Entry |
|---|
| U.S. Appl. No. 12/263,320 , “Non-Final Office Action”, dated Dec. 9, 2016, 12 pages. |
| Office Action dated Feb. 27, 2014 in Canadian Patent Application No. 2,595,176, 3 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/462,745. dated Aug. 28, 2012. 10 pages. |
| Office Action dated Oct. 18, 2012 in Canadian Patent Application No. 2,595,176. |
| “Paying by text, down to a tea,” Sunday Business Post, Oct. 31, 2002, Cork, Ireland, 2 pages. |
| Non-Final Office Action dated May 26, 2006 in U.S. Appl. No. 11/040,640, 7 pages. |
| International Search Report and Written Opinion of the International Searching Authority for Int'l Patent Application No. PCT/US2006/002049 dated Jun. 22, 2006, 5 pages. |
| Non-Final Office Action dated Sep. 25, 2007 in U.S. Appl. No. 11/519,276, 7 pages. |
| Supplementary European Search Report dated Jun. 16, 2009 in European Patent Application No. 06719027.2, 7 pages. |
| Non-Final Office Action dated Jun. 8, 2010 in U.S. Appl. No. 12/263,320, 7 pages. |
| Non-Final Office Action dated Nov. 19, 2010 in U.S. Appl. No. 11/928,700, 9 pages. |
| Final Office Action dated Nov. 24, 2010 in U.S. Appl. No. 12/263,320, 9 pages. |
| Non-Final Office Action dated Jul. 26, 2011 in U.S. Appl. No. 12/263,298, 9 pages. |
| Final Office Action dated Dec. 19, 2011 in U.S. Appl. No. 12/263,298, 8 pages. |
| Non-Final Office Action dated Mar. 20, 2013 in U.S. Appl. No. 13/462,745, 8 pages. |
| Ramfos, A. et al.; “Semops: Paying with Mobile Personal Devices”; 2004, Fourth IFIP Conference on e-Commerce, e-Business and e-Government, 16 pages. |
| Soderkvist, Jonas; “Evaluation of Wireless Techniques for Short-Range Communication”; 2003, Master's Thesis, performed in Data Transmission, Department of Electrical Engineering, at Linkopings University, pp. 1-95. |
| Steve Glassman et al., The Millicent Protocol for Inexpensive Electronic Commerce. The Millicent Protocol for Inexpensive Electronic Commerce [online] pp. 1-16, URL: http://www.w3.org/Conferences/WWW4/Papers/246/ [Accessed Jan. 22, 2008]. |
| Stig F. Mj{acute over (ø)}lsnes et al., “Localized Credentials for Server Assisted Mobile Wallet”, 2001 International Conference on Computer Networks and Mobile Computing (ICCNMC'01), pp. 203-208, IEEE Computer Society Press, (2001). |
| Anderson, Ross et al.; “NetCard—A Practical Electronic Cash System”; Computer Laboratory, Pembroke Street, Cambridge, 1996, 9 pages. |
| Balan, Rajesh et al.; “The Case for Cyber Foraging”; School of Computer Science, Carnegie Mellon University, 2002, 6 pages. |
| Belaramani, Nalini Moti et al.; “A Component-based Software Architecture for Pervasive Computing”; Department of Computer Science and Information Systems, University of Hong Kong, 2004, 20 pages. |
| Cox, Benjamin et al.; “NetBill Security and Transaction Protocol”; School of Computer Science, Carnegie Mellon University, 1995, 12 pages. |
| Iftode, Liviu et al.; “Smart Phone: An Embedded System for Universal Interactions”; Department of Computer Science, Rutgers University, 2004, 7 pages. |
| Knospe, Heiko et al.; “Online Payment for Access to Hetrogeneous Mobile Networks”; Information Security Group, Royal Holloway, University of London, 2002, 5 pages. |
| Poslad, Stefan et al.; “Crumpet: Creation of User-Friendly Mobile Services Personalised for Tourism”; University of London, 2001, 5 pages. |
| Ravi, Nishkam et al.; “Split Smart Messages: Middleware for Pervasive Computing on Smart Phones”; Department of Computer Science, Rutgers University, 2004, 10 pages. |
| Tygar, J.D.; “Atomicity in Electronic Commerce”; School of Computer Science, Carnegie Mellon University, 1996, 19 pages. |
| Non-Final Office Action dated Oct. 27, 2014 in U.S. Appl. No. 12/263,320, 15 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20160012407 A1 | Jan 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12263254 | Oct 2008 | US |
| Child | 14686146 | US | |
| Parent | 11877842 | Oct 2007 | US |
| Child | 12263254 | US | |
| Parent | 11519276 | Sep 2006 | US |
| Child | 11877842 | US | |
| Parent | 11040640 | Jan 2005 | US |
| Child | 11519276 | US |
