Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20110040686 A1
Publication typeApplication
Application numberUS 12/914,679
Publication date17 Feb 2011
Filing date28 Oct 2010
Priority date26 Dec 2006
Also published asCA2673983A1, EP2109850A1, EP2109850A4, US7848980, US20080154772, US20150310428, WO2008083022A1
Publication number12914679, 914679, US 2011/0040686 A1, US 2011/040686 A1, US 20110040686 A1, US 20110040686A1, US 2011040686 A1, US 2011040686A1, US-A1-20110040686, US-A1-2011040686, US2011/0040686A1, US2011/040686A1, US20110040686 A1, US20110040686A1, US2011040686 A1, US2011040686A1
InventorsMark Carlson
Original AssigneeMark Carlson
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Mobile payment system and method using alias
US 20110040686 A1
Abstract
Methods and systems are disclosed for allowing financial transactions to be conducted using mobile phones. A payer initiates a transaction by sending a payment request message from a mobile phone which specifies the payee and amount to be paid. Payees are identified by unique aliases, which are maintained in a database. Methods for assembling the enrollment and alias database are included.
Images(7)
Previous page
Next page
Claims(24)
1. A method comprising:
receiving a payment request message from a mobile phone operated by a payer, wherein the payment request message includes a request to pay a payee a predetermined amount of money, and wherein the payment request message comprises a personal alias associated with the payee and a transaction amount;
analyzing the payment request message to determine if the payer is authorized to pay the payee; and
sending a payment notification message to the payee indicating that a payment from the payer to the payee has been made.
2. The method of claim 1, further comprising:
sending an authentication request message to the payer, wherein the authentication request message includes a message asking the payer to enter a PIN; and
receiving the PIN.
3. A computer readable medium comprising code for performing the method of claim 1.
4. A server computer comprising the computer readable medium of claim 3.
5. A system comprising the server computer of claim 4 and the mobile phone.
6. A method comprising:
receiving a payment request message from a payer, the payment request message comprising an amount of money to be paid to a payee and an alias associated with the payee, where the payment request message is sent by the payer via a mobile phone operated by the payer;
sending an authentication request message to the mobile phone in response to the payment request message, where the authentication request message is sent to the mobile phone;
receiving an authentication token from the payer in response to sending the authentication request message, where the authentication token is sent by the payer using the mobile phone;
verifying that the authentication token is associated with the payer; and
if the authentication token is verified as being associated with the payer, then initiating a payment for the amount of money to the payee using the alias.
7. The method according to claim 6, wherein the mobile phone is a first mobile phone, and wherein the method further comprises:
sending an electronic notification of the payment to a second phone mobile operated by the payee.
8. The method according to claim 6, where the payment request message is in the form of a text message.
9. The method according to claim 6, where the payment request message is in the form of an email.
10. The method according to claim 6, where the payment request message comprise a payment card alias.
11. The method according to claim 6, where the authentication request message comprises a telephone call made by an electronic interactive voice response unit.
12. The method of claim 6, where the authentication token comprises a password.
13. The method of claim 6, where the authentication token comprises a piece of personal information associated with the payee.
14. A method comprising:
receiving a registration request from a payee to create an alias uniquely associated with that payee, where the request specifies the alias requested, and wherein the payee operates a mobile phone and can receive or make payments using the alias and mobile phone;
comparing the alias with other previously registered aliases associated with other payees; and
if the requested alias has not already been associated with another payee, registering the alias with the payee.
15. A server computer configured to perform the method of claim 14.
16. A method comprising:
sending a payment request message using a mobile phone to a payment processing network, where the payment request message comprises an amount of money to be paid and an alias, where the alias is associated with a payee;
receiving in response to the payment request message an authentication request message, where the authentication request message is received via the mobile phone; and
sending an authentication token in response to the authentication request message.
17. The method according to claim 16, where the payment request message is in the form of a text message.
18. The method according to claim 16, where the payment request message is in the form of an email.
19. The method according to claim 16, where the payment request message comprises a payment card alias.
20. The method according to claim 16, where the authentication request message comprises a telephone call made by an electronic interactive voice response unit.
21. The method of claim 16, where the authentication token comprises a password.
22. The method of claim 16, where the authentication token comprises a piece of personal information associated with the consumer.
23. A computer readable medium comprising code for performing the method of claim 16.
24. A phone comprising the computer readable medium of claim 23.
Description
    CROSS-REFERENCES TO RELATED APPLICATIONS
  • [0001]
    This patent application is a non-provisional of and claims priority to U.S. provisional patent application No. 60/871,898, filed on Dec. 26, 2006, which is herein incorporated by reference in its entirety for all purposes.
  • BACKGROUND
  • [0002]
    The use of mobile phones to conduct financial transactions is growing in popularity. Various means of using mobile phones to conduct financial transactions have been tried. The most common involves sending a payment to a payee using the payee's cellular phone number as an identifier. This approach gives rise certain difficulties, however. First, the payee must have a cellular phone which is capable of receiving the payments. Second, the payer must know the payee's phone number. As cellular phone numbers tend to change frequently, a payer must make certain that the phone number being used is current. Otherwise, the payer runs the risk of sending a payment to an unintended third party, who has been assigned the intended payee's old phone number. Further, in some cases, the payee and payee may not wish to reveal personal information such as their cellular phone numbers to each other. Accordingly, there is a need for a new method of conducting financial transactions using phones.
  • [0003]
    Embodiments of the invention address these and other problems.
  • BRIEF SUMMARY
  • [0004]
    Embodiments of the invention are directed to methods and systems for allowing payments to be made using mobile phones.
  • [0005]
    One embodiment of the invention is directed to a method. The method comprises receiving a payment request message from a mobile phone operated by a payer, wherein the payment request message includes a request to pay a payee a predetermined amount of money, and wherein the payment request message comprises a personal alias uniquely associated with the payee and a transaction amount. The payment request message is analyzed to determine if the payer is authorized to pay the payee. A payment notification message is sent to the payee indicating that a payment from the payer to the payee has been made.
  • [0006]
    Another embodiment of the invention is directed to a method. The method comprises receiving a payment request message from a payer, the payment request message comprising an amount of money to be paid to a payee and an alias associated with the payee, where the payment request message is sent by the payer via a mobile phone operated by the payer. An authentication request message is sent to the mobile phone in response to the message. An authentication token is received from the payer in response to sending the authentication request message. The authentication token is sent by the payer using the mobile phone, and the authentication token that is associated with the payer is verified. If the authentication token is verified as being associated with the payer, a payment for the amount of money to the payee using the alias is initiated.
  • [0007]
    Another embodiment of the invention is directed to a method. The method comprises receiving a registration request from a payee to create an alias uniquely associated with that payee, where the request specifies the alias requested. The payee operates a mobile phone and can receive or make payments using the alias and mobile phone. The alias is compared with other previously registered aliases associated with other payees. If the requested alias has not already been associated with another payee, the alias associated with the payee is registered.
  • [0008]
    Other embodiments of the invention are directed to systems, computer readable media, and devices adapted to implement the above methods.
  • [0009]
    These and other embodiments of the invention are described in further detail below.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0010]
    FIG. 1 shows a block diagram of a system according to an embodiment of invention.
  • [0011]
    FIG. 2 shows a block diagram of components in a computer.
  • [0012]
    FIG. 3 shows a block diagram of components in a mobile phone.
  • [0013]
    FIG. 4 shows a flowchart illustrating an alias registration process.
  • [0014]
    FIG. 5 shows information that can be provided when registering aliases.
  • [0015]
    FIG. 6 shows a flowchart illustrating a payment method according to an embodiment of the invention.
  • DETAILED DESCRIPTION
  • [0016]
    Embodiments of the invention are directed to making person-to-person (P2P) and/or person-to-business (P2B) payments, using mobile phones. In embodiments of the invention, a payer may send a payment request message to a payment processing network. The payment request message identifies the desired payee using an alias, which is uniquely associated with the payee. The payment processing network may then determine who the payee is using an enrollment and alias database, and may forward the payment request message to a payer institution. The payer institution may be a payer bank and the payer may have a payer account associated with it. The payer institution may thereafter analyze the payment request message and may authorize or not authorize the transaction depending on whether the payer has sufficient credit and/or funds in the payer's account. If the payment request is approved by the payer institution, the payer institution may thereafter transfer funds from the payer's account at the payer institution to a payee account at a payee institution.
  • [0017]
    The payment request message may be sent from the payer's mobile phone in any suitable manner. In one example, a payer may send the payment request message to the payment processing network via a Web page accessed by the phone. In another example, the payer may send the payment request message to the payment processing network using an SMS message (i.e., a text message). In yet another example, the payer may send the payment request message to the payment processing network using a software application on the phone.
  • [0018]
    The payment transactions according to embodiments of the invention may take place in any suitable context. For example, suitable payment transactions may involve purchases of goods and services from merchants or individuals in a person to business or person to person context. However, in some embodiments of the invention, a payer may make payments and the payments can be made without any return consideration (e.g., a good or service purchased). For example, a payment may be a gift to the payee or repayment of a debt to the payee where the pay does not receive immediate consideration for the payment.
  • [0019]
    I. Systems
  • [0020]
    FIG. 1 shows a system that can be used in an embodiment of the invention. Embodiments of the invention may use some or all of the components shown in FIG. 1.
  • [0021]
    The illustrated system includes a payer 302 and a first mobile phone 304 associated with the payer 302. The payer 302 has a payer account 316 at a payer institution 314. Similarly, the system includes a payee 306 and a second mobile phone 308 associated with the payee 306. The payee 306 has a payee account 320 at a payee institution 315.
  • [0022]
    In this example, the payer institution 314 and payee institution 315 are shown as separate entities. The payer 302 and payee 306 could use the same financial institution in other embodiments of the invention.
  • [0023]
    The payer institution 314 and payee institution 315 are typically banks that manage financial accounts for individuals or businesses. However, they could also be business entities such as retail stores.
  • [0024]
    The payer 302 and payee 306 may be individuals, or organizations such as businesses that are capable of entering into financial transactions (e.g., payment transactions).
  • [0025]
    The payment processing network 310 may include data processing subsystems, networks, and operations used to support and deliver authorization services, exception file services, and clearing and settlement services. An exemplary payment processing network may include VisaNet™. Payment processing networks such as VisaNet™ are able to process credit card transactions, debit card transactions, and other types of financial transactions. VisaNet™, in particular, includes a VIP system (Visa Integrated Payments system) which processes authorization requests and a Base II system which performs clearing and settlement services.
  • [0026]
    The payment processing network 310 may include a payment server computer 312. A “server computer” is typically a powerful computer or cluster of computers. For example, a server computer can be a large mainframe, a minicomputer cluster, or a group of servers functioning as a unit. In one example, a server computer may be a database server coupled to a Web server. The server computer 312 may form part of any suitable wired or wireless network, including the Internet.
  • [0027]
    A mobile gateway 332 may be operatively coupled to the payment processing network 310 and may allow the first and second mobile phones 304, 306 to communicate with the payment processing network 310. The mobile gateway 332 may be embodied by any suitable combination of hardware and/or software known to those of ordinary skill in the art.
  • [0028]
    The system may also comprise a payer client computer 330(a) as well as a payee client computer 330(b). They can be in communication with an enrollment server computer 326 operating a host site 324 (e.g., a Web site), via a communication medium 328. The communication medium 328 may comprise any suitable combination of wired and/or wireless networks including the Internet. The enrollment server computer 326 may store aliases in an enrollment and alias database 322. The payment processing network 310 can subsequently identify the payee 302 and payer 306 using the information stored in the enrollment and alias database 322. In other embodiments, there can be a separate enrollment database and a separate alias database.
  • [0029]
    FIG. 2 shows typical components or subsystems of a computer apparatus. Such components or any subset of such components may be present in various components shown in FIG. 1, including the payment server computer 312, the enrollment server computer 326, the client computers 330(a), 330(b), etc. The subsystems shown in FIG. 2 are interconnected via a system bus 775. Additional subsystems such as a printer 774, keyboard 778, fixed disk 779, monitor 776, which is coupled to display adapter 782, and others are shown. Peripherals and input/output (I/O) devices, which couple to I/O controller 771, can be connected to the computer system by any number of means known in the art, such as serial port 777. For example, serial port 777 or external interface 781 can be used to connect the computer apparatus to a wide area network such as the Internet, a mouse input device, or a scanner. The interconnection via system bus 775 allows the central processor 773 to communicate with each subsystem and to control the execution of instructions from system memory 772 or the fixed disk 779, as well as the exchange of information between subsystems. The system memory 772 and/or the fixed disk 779 may embody a computer readable medium.
  • [0030]
    FIG. 3 shows a block diagram of some components of the first mobile phone 304. Some or all of the components in the first mobile phone 304 may also be present in the second mobile phone 308 (illustrated in FIG. 1).
  • [0031]
    The phone 304 may comprise a computer readable medium 304(b) and a body 304(h) as shown in FIG. 3. The computer readable medium 304(b) may be present within body 304(h), or may be detachable from it. The body 304(h) may be in the form a plastic substrate, housing, or other structure. The computer readable medium 304(b) may be a memory that stores data and may be in any suitable form including a magnetic stripe, a memory chip, etc.
  • [0032]
    The computer readable medium 304(b) may comprise code for performing any of the functions described herein. For example, it may comprise code for sending a payment request message using a mobile phone to a payment processing network, where the payment request message comprises an amount of money to be paid and an alias, where the alias is associated with a payee; code for receiving in response to the payment request message an authentication request message, where the authentication request message is received via the mobile phone; and code for sending an authentication token in response to the authentication request message.
  • [0033]
    The phone 304 may further include a contactless element 304(g), which is typically implemented in the form of a semiconductor chip (or other data storage element) with an associated wireless transfer (e.g., data transmission) element, such as an antenna. Contactless element 304(g) is associated with (e.g., embedded within) portable consumer device 304 and data or control instructions transmitted via a cellular network may be applied to contactless element 304(g) by means of a contactless element interface (not shown). The contactless element interface functions to permit the exchange of data and/or control instructions between the mobile device circuitry (and hence the cellular network) and an optional contactless element 304(g).
  • [0034]
    Contactless element 304(g) is capable of transferring and receiving data using a near field communications (“NFC”) capability (or near field communications medium) typically in accordance with a standardized protocol or data transfer mechanism (e.g., ISO 14443/NFC). Near field communications capability is a short-range communications capability, such as RFID, Bluetooth™, infra-red, or other data transfer capability that can be used to exchange data between the phone 304 and a payment processing network 26 or it can be used to exchange data between the phone 304 and an access device (e.g., a POS terminal). Thus, the phone 304 is capable of communicating and transferring data and/or control instructions via both cellular network and near field communications capability.
  • [0035]
    The phone 304 may also include a processor 304(c) (e.g., a microprocessor) for processing the functions of the phone 304 and a display 304(d) to allow a payee to see phone numbers and other information and messages. The phone 304 may further include input elements 304(e) to allow a payee to input information into the device, a speaker 304(f) to allow the payee to hear voice communication, music, etc., and a microphone 304(i) to allow the payee to transmit her voice through the phone 304. The phone 304 may also include an antenna 304(a) for wireless data transfer (e.g., data transmission).
  • [0036]
    II. Enrollment Methods
  • [0037]
    In embodiments of the invention, payers and payees may first enroll in the system. The payee and the payer may enroll in any suitable manner. For example, referring to FIG. 1, the payee and the payer may enroll in the system via the host site 324 using the client computers 330(a), 330(b). Enrollment information such as name, account number, etc. may be stored by the server computer 326 in the enrollment and alias database 322. This information can be used in subsequent payment processes to identify the payer 302 or the payee 306.
  • [0038]
    In some cases, a financial institution such as the payee institution 315 or the payer institution 314 may “push” pre-enrollment data to the enrollment and alias database 322. The payer institution 314, for example, may validate the payer 302 ahead of time. The payer institution 314 may do this ahead of time, because it knows the payer 302 and the payer's credit history and account balance information. After the payer 302 is enrolled in the system, the payer 302 may set up an appropriate alias to use the system. The same may be true for the payee 306. Thus, in some embodiments, the payer 302 need not do anything to enroll and need only set up her payment alias.
  • [0039]
    In embodiments of the invention, a number of aliases may be used. Aliases may include payment processing organization aliases for the payment processing organization that operates the payment processing network, a payee alias associated with the payee and the payee's phone, and a payer alias associated with the payer and the payer's phone. Examples of payer and payee aliases include “worldtraveler” and “beachbum.” An example of a service alias may be “myvisa” for a payment processing organization such as Visa.
  • [0040]
    Other aliases that can be registered include portable consumer device aliases (payment card aliases). For example, the payer 302 may have first and second credit cards and they may have the aliases CC1 and CC2. Such portable consumer device aliases may or may not be uniquely associated with their holders.
  • [0041]
    Referring to FIGS. 1 and 4, in the first step 202, a payee 306 requests assignment of an alias. In preferred embodiments, the payee 306 may specify a particular alias. However, in other embodiments, a payment processing organization may assign an alias to the payee 306. To register an alias, the payee 306 may use the client computer 330(b) to contact the host site 324 on the server computer 326. The host site 324 may comprise a wizard or other mechanism to allow the payer 302 and the payee 306 to enter information.
  • [0042]
    In the next step 204, the server computer 326 checks the enrollment and alias database 322 to see if the requested alias is already being used by another payee or payer. If the requested alias already exists, then the payee 306 may be asked to provide another alias (step 212). Alternatively or additionally, the alias registration request may reject the proposed alias if it is offensive or is a third party trademark or servicemark.
  • [0043]
    If the alias has not been previously registered, then the server computer 326 may register the requested alias for the payee 208. This information may be stored in the enrollment and alias database 322. Once the alias has been registered for the payee 306, the payment processing organization may begin allowing the payee to receive payments made using the alias (step 210).
  • [0044]
    This method and other related embodiments of the invention allow for efficient cross-institution payments to be made, by uniquely identifying an individual, business, etc., via an alias. The aliases may be associated with many accounts or services operated by an individual or entity, if desired. In some embodiments, these various aliases can be registered for a fee, and consumers may be charged a registration and renewal fee for using certain aliases. Other embodiments may provide the enrollment and alias database as a free service, or charge only certain classes of entities (e.g. charge only payees, or for-profit corporations).
  • [0045]
    III. Payment Methods
  • [0046]
    FIG. 6 shows a flowchart illustrating a payment method according to an embodiment of the invention. In the first step 102 the payer 302 decides to pay the payee 306 using the first mobile phone 304.
  • [0047]
    A payer 302 then uses the first mobile phone 304 and sends a payment request message to the payment processing network 310 and the payment processing network 310 receives the payment request message (step 104). The payment request message comprises at least a payment amount and a payee alias. The payment request message may also comprise other information, such as an alias or number identifying a specific financial account from which payment is to be made, or a time in the future at which payment is to be initiated.
  • [0048]
    As noted above, the payment request message may take a variety of different forms. For example, the payment request message could be in the form of an SMS message. The request could also come in the form of an email, or a voice interaction with an IVR unit. The request could also be made via a software application on the phone, which sends one or more network packets containing the request data.
  • [0049]
    In the next step 106, using the enrollment and alias database 322, the server computer 312 in the payment processing network 310 analyzes the payment request message and uses the payee alias in the payment request message to identify the payee 306, and also the payer institution 314 and the payer account 316.
  • [0050]
    To provide security to the system, an optional authentication request message is sent from the payment processing network to the first mobile phone 304 operated by the payer 108. The authentication request message may be initiated by the payer institution 314 or by a payment processing organization affiliated with the payment processing network 310. It may request entry of a password, or personal information such as an address or social security number to verify the identity of the payer 108. The authentication request message may take a variety of forms, as described for the payment request message 104 above. In preferred embodiments, the authentication request message will be sent to the payer's mobile phone 304. It could also be sent to the payer's client computer 330(a).
  • [0051]
    In the next step 110, the payer 302 provides an authentication token to the payment processing network 310. For example, the payer 302 may enter a PIN (personal identification number) into the first mobile phone 304 and may then send the authentication token back to the payment processing network 310, and the payment processing network 310 may or may not forward it to the payer institution 314. Other examples of authentication tokens include passwords, birthdates, and other personal information associated with the payer 302.
  • [0052]
    The payment processing network 310 (or the payer institution 314) then verifies the authentication token 112. If the authentication token is invalid, the payment request in the payment request message may be rejected. Alternatively, the payment processing network 310 may re-verify the authentication token (step 120) by sending another authentication request message to the payer 302 via the first mobile phone 304.
  • [0053]
    If the payer 302 and/or the first mobile phone 304 are authenticated, the payment processing network 310 may send the payment request message to the payer institution 314 for approval. The payment request message may be re-formed to remove various aliases and may include real information, if desired. The payer institution 314 may then approve of the payment request if there are sufficient funds and/or credit in the payer account 316 or disapprove it if there are insufficient funds or credit. If the payment request is approved, at some point in time (e.g., immediately or at the end of the day if clearing and settling need to take place), actual funds may be transferred from the payer account 316 to the payee account 320 via the payment processing network 310.
  • [0054]
    Once the funds have been transferred from the payer account 316 to the payee account 320, a payment notification message may sent to the mobile phone 308 and/or the client computer 330(b) operated by the payee 118 after the payment request in the payment request message has been approved by the payer institution 314.
  • [0055]
    In a specific example, a payer 302 such as Jane and a payer 306 such as John register on the host site 324 run on a remote server computer 326 using their client computers 330(a), 330(b).
  • [0056]
    As shown in FIG. 5, Jane registers personal information 502 including her name, mobile telephone number, first credit card account number, second credit card account number, and a personal alias. John may similarly register his personal information 504. In this example, Jane creates the personal alias “worldtraveler,” while John creates the personal alias “beachbum.”
  • [0057]
    After registering, a payment processing organization may provide both John and Jane with a phone number for the service that will facilitate further payment processing. In other embodiments, the payment processing organization may provide John and Jane with a service alias instead of or in addition to the service phone number. For example, instead of providing John and Jane with the service phone number 555-555-5555, the payment processing organization may provide the service alias “myvisa” to John and Jane. The service alias may be referred to as a “short-code” in some cases, and may include a string of characters of variable length.
  • [0058]
    In an exemplary transaction, Jane may be a payer 302 and wants to pay $15.00 to a payee 306 named John. Payee Jane 302 initiates a payment to John by entering the payment request message “myvisa pay beachbum $15.00” into her phone 304, and sending the message via SMS to the server computer 312 in the payment processing network 310 via the mobile gateway 332. The alias “beachbum” is used instead of John's phone number. The service alias “myvisa” is used instead of the phone number of the service.
  • [0059]
    Jane may also use a portable consumer device alias such as “CC2” to indicate the particular credit card that Jane wants to use to pay John. For example, payee Jane 302 may enter the payment request message “myvisa pay beachbum $15.00 CC2” into her phone 304 to indicate that her second credit card is to be used to make the intended payment. Jane may alternatively or additionally designate a default credit card account number.
  • [0060]
    After entering the payment request message “myvisa pay beachbum $15.00 CC2” into her mobile phone 304, the payment request message is sent from her phone 304 to the payment processing network 310 (e.g., as described above), and then (in this example) to an issuer of the credit card (or other portable consumer device). In this example, the issuer of the credit card may be the payer institution 314.
  • [0061]
    The payment processing network 310 may receive the payment request message and may then optionally respond by sending an authentication request message to the payer 302. In this example, an authentication request message is sent in the form of a call from an interactive voice response unit (IVR) at a telecom server or the like, which asks payer Jane 302 to enter her mobile PIN (personal identification number) 510. After payer Jane 302 enters the correct PIN into her phone 304, the payer institution 314 and/or the server computer 312 in the payment processing network 310 can then analyze the payment request message and can approve or decline the payment request. If the payment request is approved, appropriate funds may be transferred to the payee account 320 at the payee institution 315. For example, payee John's portable consumer device account (e.g., credit card account) at John's bank (e.g., the payee institution 315) can be credited with the payment amount. Payer Jane's account 316 can be subsequently debited for the payment amount.
  • [0062]
    In some embodiments, a payment notification message in the form of an SMS, e-mail, or some other type of message may be sent to the payee's mobile phone 308, informing the payee John 306 that a payment from the payee John 302 has been made. In preferred embodiments, the payment notification message may be sent to payee John's mobile phone 308, but it could be sent to the client computer 330(b) operated by the payee John 306.
  • [0063]
    Embodiments of the invention have a number of advantages. First, the use of an alias allows for a transaction to be completed while keeping the personal information of the transacting parties confidential. This is useful because, for example, a payer may not want to disclose his or her phone number to a payee, or vice versa. Second, the alias allows for payments to be made even if a payee's telephone number or financial account changes. A payer may thus store a list of aliases for payees with whom the payer frequently does business, and may initiate repeated payments without having to verify that the payee's telephone number is the same. Third, aliases tend to be much easier to remember than either phone numbers or financial account numbers. Consequently, embodiments of the invention will be easier to use than other methods. Fourth, embodiments of the invention allow for many accounts to be accessed from a single mobile phone, eliminating the need to carry a large number of portable consumer devices.
  • [0064]
    Any of the above-described methods or steps of such methods may be embodied as software code to be executed by a processor of the server computer or any other suitable combination of devices using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM.
  • [0065]
    It should be understood that the present invention can be implemented in the form of control logic, in a modular or integrated manner, using software, hardware or a combination of both. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will appreciate other ways and/or methods to implement the present invention.
  • [0066]
    Any of the above-described embodiments and/or any features thereof may be combined with any other embodiment(s) and/or feature(s) without departing from the scope of the invention.
  • [0067]
    The above description is illustrative and is not restrictive. Many variations of the invention will become apparent to those skilled in the art upon review of the disclosure. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the pending claims along with their full scope or equivalents.
  • [0068]
    A recitation of “a”, “an” or “the” is intended to mean “one or more” unless specifically indicated to the contrary.
Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
US5305196 *19 May 199219 Apr 1994Credit Verification CorporationCheck transaction processing, database building and marketing method and system utilizing automatic check reading
US5388165 *4 Jan 19947 Feb 1995Credit Verification CorporationMethod and system for building a database and performing marketing based upon prior shopping history
US5483444 *7 Feb 19959 Jan 1996Radisson Hotels International, Inc.System for awarding credits to persons who book travel-related reservations
US5500513 *11 May 199419 Mar 1996Visa InternationalAutomated purchasing control system
US5502636 *31 Jan 199226 Mar 1996R.R. Donnelley & Sons CompanyPersonalized coupon generating and processing system
US5592560 *8 Sep 19947 Jan 1997Credit Verification CorporationMethod and system for building a database and performing marketing based upon prior shopping history
US5604921 *7 Jul 199518 Feb 1997Nokia Mobile Phones Ltd.Radiotelephone user interface for broadcast short message service
US5615110 *22 Aug 199425 Mar 1997Wong; Kam-FuSecurity system for non-cash transactions
US5621201 *5 Feb 199615 Apr 1997Visa InternationalAutomated purchasing control system
US5621812 *17 May 199315 Apr 1997Credit Verification CorporationMethod and system for building a database for use with selective incentive marketing in response to customer shopping histories
US5708422 *31 May 199513 Jan 1998At&TTransaction authorization and alert system
US5710886 *16 Jun 199520 Jan 1998Sellectsoft, L.C.Electric couponing method and apparatus
US5717866 *1 Aug 199610 Feb 1998Codesaver International, Inc.Method for comparative analysis of consumer response to product promotions
US5870030 *4 Apr 19969 Feb 1999Motorola, Inc.Advertiser pays information and messaging system and apparatus
US5884277 *1 May 199516 Mar 1999Vinod KhoslaProcess for issuing coupons for goods or services to purchasers at non-secure terminals
US6012038 *22 Jun 19984 Jan 2000Softcard Systems, Inc.System and method for controlling distribution of coupons
US6014634 *4 Aug 199711 Jan 2000Supermarkets Online, Inc.System and method for providing shopping aids and incentives to customers through a computer network
US6018718 *28 Aug 199725 Jan 2000Walker Asset Management Limited PartnershipMethod and system for processing customized reward offers
US6029151 *12 Dec 199722 Feb 2000Telefonaktiebolaget L M EricssonMethod and system for performing electronic money transactions
US6035280 *10 Apr 19967 Mar 2000Christensen; Scott N.Electronic discount couponing method and apparatus for generating an electronic list of coupons
US6041309 *23 Dec 199821 Mar 2000Oneclip.Com, IncorporatedMethod of and system for distributing and redeeming electronic coupons
US6049778 *31 Oct 199711 Apr 2000Walker Asset Management Limited PartnershipMethod and apparatus for administering a reward program
US6055505 *30 Dec 199725 Apr 2000U S West, Inc.Automatic customer notification system and method
US6185290 *4 Jan 20006 Feb 2001Murex Securities, Ltd.One number, intelligent call processing system
US6185541 *12 May 19996 Feb 2001Supermarkets Online, Inc.System and method for providing shopping aids and incentives to customers through a computer network
US6336098 *11 Dec 19971 Jan 2002International Business Machines Corp.Method for electronic distribution and redemption of coupons on the world wide web
US6336099 *24 Apr 19981 Jan 2002Brightstreet.ComMethod and system for electronic distribution of product redemption coupons
US6341724 *11 Jan 200129 Jan 2002First Usa Bank, NaCardless payment system
US6351735 *22 Aug 199626 Feb 2002Catalina Marketing International, Inc.Check transaction processing, database building and marketing method and system utilizing automatic check reading
US6377935 *12 Mar 199723 Apr 2002Catalina Marketing International, Inc.Method and system for selective incentive point-of-sale marketing in response to customer shopping histories
US6378775 *11 May 200130 Apr 2002Fujitsu LimitedElectronic cashless system
US6381324 *17 Oct 200030 Apr 2002Murex Securities, Ltd.One number, intelligent call processing system
US6505046 *19 Nov 19987 Jan 2003Nortel Networks LimitedMethod and apparatus for distributing location-based messages in a wireless communication network
US6516302 *12 Oct 19994 Feb 2003Incentech, Inc.Method and system for accumulating marginal discounts and applying an associated incentive upon achieving one of a plurality of thresholds
US6529725 *9 Oct 19984 Mar 2003Raymond Anthony JoaoTransaction security apparatus and method
US6535855 *31 Mar 199818 Mar 2003The Chase Manhattan BankPush banking system and method
US6684195 *4 Aug 200027 Jan 2004Catalina Marketing International, Inc.Method and system for selective incentive point-of-sale marketing in response to customer shopping histories
US6685093 *25 Sep 20013 Feb 2004Ecrio, Inc.System, method and apparatus for communicating information between a mobile communications device and a bar code reader
US6837425 *13 Sep 20024 Jan 2005Visa U.S.A. Inc.Compact protocol and solution for substantially offline messaging between portable consumer device and based device
US6868391 *25 Mar 199815 Mar 2005Telefonaktiebolaget Lm Ericsson (Publ)Tele/datacommunications payment method and apparatus
US6877665 *21 Mar 200212 Apr 2005Ecrio, Inc.System, method, and apparatus for communicating information encoded in a light-based signal using a fob device
US6982941 *8 Feb 20023 Jan 2006Texas Instruments IncorporatedMirror detection signal generator
US6990330 *9 Jan 200324 Jan 2006Qualcomm IncorporatedMethod and apparatus providing user with account balance notification of prepaid wireless packet data services
US7003497 *31 Dec 200121 Feb 2006International Business Machines CorporationSystem and method for confirming electronic transactions
US7007840 *2 Jul 20047 Mar 2006Visa U.S.A., Inc.Managing activation of cardholders in a secure authentication program
US7013286 *30 Dec 199914 Mar 2006International Business Machines CorporationGeneration, distribution, storage, redemption, validation and clearing of electronic coupons
US7159770 *9 Jul 20049 Jan 2007Fujitsu LimitedShop settlement method, system and program
US7194437 *14 May 199920 Mar 2007Amazon.Com, Inc.Computer-based funds transfer system
US7343149 *13 Jun 200511 Mar 2008Lucent Technologies Inc.Network support for credit card notification
US20020013711 *12 Apr 200131 Jan 2002Arun AhujaMethod and system for notifying customers of transaction opportunities
US20030004808 *21 Nov 20012 Jan 2003Mehdi ElhaoussineMethod and system for receiving, storing and processing electronic vouchers with a mobile phone or a personal digital assistant
US20030028599 *19 Jun 20016 Feb 2003Kolsky Amir D.Method and system for a communication scheme over heterogeneous networks
US20030058261 *25 Sep 200127 Mar 2003Nagesh ChallaStatic display of a bar code on a display of a mobile communications device
US20040019522 *11 Feb 200329 Jan 2004Visa U.S.A., Inc.Multi-application smart card device software solution integrating sales tax, payment and discount rewards
US20040044621 *27 Aug 20024 Mar 2004Visa U.S.A., Inc.Method and system for facilitating payment transactions using access devices
US20040049455 *6 Jul 200111 Mar 2004Hossein MohsenzadehSecure authentication and payment system
US20040050922 *13 Sep 200218 Mar 2004Visa U.S.A., Inc.Compact protocol and solution for substantially offline messaging between portable consumer device and based device
US20040054575 *13 Sep 200218 Mar 2004Robert MarshallSystem, method and apparatus for distributing and redeeming customer selected coupons
US20040054581 *27 Mar 200318 Mar 2004Visa U.S.A.Network centric loyalty system
US20040054590 *10 Sep 200318 Mar 2004Visa U.S.A., Inc.Method and system for managing limited use coupon and coupon prioritization
US20040054591 *10 Sep 200318 Mar 2004Visa U.S.A., Inc.Opt-in/opt-out in loyalty system
US20040064406 *1 Nov 20011 Apr 2004Yates Martin JTransaction authentication
US20040122685 *20 Dec 200224 Jun 2004Daryl BunceVerification system for facilitating transactions via communication networks, and associated method
US20050021456 *29 Apr 200427 Jan 2005Visa U.S.A.Method and system for facilitating switching of financial institution accounts
US20050027543 *29 Jul 20033 Feb 2005Fujitsu LimitedMethods for purchasing of goods and services
US20050029344 *2 Jul 200410 Feb 2005Visa U.S.A.Managing activation of cardholders in a secure authentication program
US20050035847 *4 Oct 200417 Feb 2005American Express Travel Related Services Company, Inc.Systems and methods for providing a rf transaction device for use in a private label transaction
US20050036611 *31 Mar 200417 Feb 2005Visa U.S.A., Inc.Method and system for secure authentication
US20050045718 *3 Sep 20033 Mar 2005Visa U.S.A., Inc.Method, system and portable consumer device using wildcard values
US20050058427 *12 Sep 200317 Mar 2005Visa U.S.A. Inc.Method and system for providing interactive cardholder rewards image replacement
US20050071225 *30 Sep 200331 Mar 2005Visa U.S.A., Inc.System and apparatus for linking multiple rewards programs to promote the purchase of specific product mixes
US20050071226 *30 Sep 200331 Mar 2005Visa U.S.A. Inc.Method and system for managing dynamic terms and conditions and user interaction
US20050071227 *30 Sep 200331 Mar 2005Visa U.S.A.Method and system for managing concurrent sku-based rewards program
US20050071228 *30 Sep 200331 Mar 2005Visa U.S.A. Inc.Method and system for managing reward reversal after posting
US20050071235 *30 Sep 200331 Mar 2005Visa U.S.A Inc.Method and system for providing a distributed adaptive rules based dynamic pricing system
US20050075958 *1 Oct 20037 Apr 2005Edwin GonzalezCellular phone financial device
US20060053056 *22 Aug 20059 Mar 2006American Express Marketing & Development CorporatiCard member discount system and method
US20060059110 *3 Apr 200216 Mar 2006Ajay MadhokSystem and method for detecting card fraud
US20060080232 *27 May 200513 Apr 2006Randy EppsCellular telephone based payment apparatus and method for use in purchase of good and services
US20070001000 *24 May 20064 Jan 2007Visa U.S.A. Inc.Method and system for providing interactive cardholder rewards image replacement
US20070005613 *29 Jun 20054 Jan 2007Visa U.S.A., Inc.Schema-based dynamic parse/build engine for parsing multi-format messages
US20070005774 *29 Jun 20054 Jan 2007Visa U.S.A., Inc.Adaptive gateway for switching transactions and data on unreliable networks using context-based rules
US20070012764 *20 Jul 200618 Jan 2007Visa U.S.A., Inc.Method, system and portable consumer device using wildcard values
US20070017970 *20 Jul 200625 Jan 2007Visa U.S.A., Inc.Compact protocol and solution for substantially offline messaging between portable consumer device and base device
US20070027803 *14 Mar 20061 Feb 2007Mobipay International, S.A.System and process for remote payments and transactions in real time by mobile telephone
US20070034679 *19 Oct 200615 Feb 2007Visa U.S.A., Inc.Compact protocol and solution for substantially offline messaging between portable consumer device and base device
US20070055597 *16 Mar 20068 Mar 2007Visa U.S.A.Method and system for manipulating purchase information
US20070055630 *5 Apr 20068 Mar 2007Visa U.S.A.System and method for secured account numbers in proximity devices
US20070057034 *19 Oct 200615 Mar 2007Visa U.S.A., Inc.Compact protocol and solution for substantially offline messaging between portable consumer device and base device
US20070057051 *13 Nov 200615 Mar 2007Visa U.S.A., Inc.Method, system and portable consumer device using wildcard values
US20080003987 *29 Jun 20063 Jan 2008Eagle River Holdings LlcSystem and method for wireless coupon transactions
US20080006685 *6 Jul 200610 Jan 2008Firethorn Holdings, LlcMethods and Systems For Real Time Account Balances in a Mobile Environment
US20080021784 *27 Sep 200724 Jan 2008American Express Travel Related Services Co., Inc.System and method for exchanging loyalty points for acquisitions
US20080040265 *6 Jul 200614 Feb 2008Firethorn Holdings, LlcMethods and Systems For Making a Payment Via A Stored Value Card in a Mobile Environment
US20090076896 *13 Sep 200719 Mar 2009Dewitt Jay AllenMerchant supplied offer to a consumer within a predetermined distance
US20090076925 *13 Sep 200719 Mar 2009Dewitt Jay AllenOfferee requested offer based on point-of-service to offeree distance
US20090078777 *26 Sep 200726 Mar 2009Nicole Janine GranucciReal-time card balance on card plastic
US20090081990 *26 Sep 200726 Mar 2009Nicole Janine GranucciReal-Time Balance On a Mobile Phone
US20100017275 *24 Jun 200921 Jan 2010Mark CarlsonMobile communication device configured for transit application
USRE34915 *20 Nov 199125 Apr 1995Coupco, Inc.Paperless system for distributing, redeeming and clearing merchandise coupons
Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US8725635 *23 Sep 201113 May 2014Bank Of America CorporationOnline payment system and method
US8856045 *14 Mar 20147 Oct 2014PayRange Inc.Mobile-device-to-machine payment systems
US91349941 Jul 201415 Sep 2015PayRange Inc.Method and system for updating firmware using a mobile device as a communications bridge
US925687311 Aug 20149 Feb 2016PayRange Inc.Method and device for retrofitting an offline-payment operated machine to accept electronic payments
US92627714 Feb 201516 Feb 2016PayRange Inc.Method and system for providing offers for automated retail machines via mobile devices
US954785918 Jul 201417 Jan 2017PayRange Inc.Method and system for performing mobile device-to-machine payments
US965929612 Aug 201423 May 2017PayRange Inc.Method and system for presenting representations of payment accepting unit events
US97157097 May 200925 Jul 2017Visa International Services AssociationCommunication device including multi-part alias identifier
US20090281948 *7 May 200912 Nov 2009Mark CarlsonCommunication device including multi-part alias identifier
US20110047076 *29 Jul 201024 Feb 2011Mark CarlsonAlias reputation interaction system
US20110153498 *7 Dec 201023 Jun 2011Oleg MakhotinPayment Channel Returning Limited Use Proxy Dynamic Value
US20120116967 *23 Sep 201110 May 2012Bank Of America CorporationMobile payment system and method
US20120116973 *23 Sep 201110 May 2012Bank Of America CorporationOnline payment system and method
US20130018779 *1 Jan 201217 Jan 2013Bank Of America CorporationAlias-based merchant transaction system
US20140310171 *12 Apr 201316 Oct 2014Bank Of America CorporationCertified person-to-person payment system
USD75518318 Dec 20133 May 2016Payrange, Inc.In-line dongle
USD76388822 Apr 201516 Aug 2016PayRange Inc.Display screen or portion thereof with graphical user interface
USD76390522 Apr 201516 Aug 2016PayRange Inc.Display screen or portion thereof with animated graphical user interface
USD76453222 Apr 201523 Aug 2016PayRange Inc.Display screen or portion thereof with animated graphical user interface
USD77350822 Apr 20156 Dec 2016PayRange Inc.Display screen or portion thereof with a graphical user interface
USD77407110 Nov 201513 Dec 2016Bank Of America CorporationCommunication device with graphical user interface
USD77452616 May 201420 Dec 2016Bank Of America CorporationDisplay screen with graphical user interface for funds transfer
USD77452716 May 201420 Dec 2016Bank Of America CorporationDisplay screen with graphical user interface for funds transfer
USD77452816 May 201420 Dec 2016Bank Of America CorporationDisplay screen with graphical user interface for funds transfer
USD77452916 May 201420 Dec 2016Bank Of America CorporationDisplay screen with graphical user interface for funds transfer
USD7824829 Mar 201628 Mar 2017Payrange, Inc.In-line dongle
USD7824839 Mar 201628 Mar 2017Payrange, Inc.In-line dongle
WO2012151251A3 *2 May 201228 Mar 2013Panther Payments, LLCMethod and system for facilitating person-to person payments
WO2013028910A2 *23 Aug 201228 Feb 2013Visa International Service AssociationMobile funding method and system
WO2013028910A3 *23 Aug 201216 May 2013Visa International Service AssociationMobile funding method and system
WO2016055919A1 *5 Oct 201514 Apr 2016Visa International Service AssociationSystem and method for management of payee information
WO2016130406A3 *4 Feb 201610 Nov 2016Alibaba Group Holding LimitedProtecting sensitive data security
Classifications
U.S. Classification705/44
International ClassificationG06Q40/00
Cooperative ClassificationG06Q20/385, G06Q20/3223, G06Q20/3226, G06Q20/04, G06Q20/40, G06Q20/32, G06Q20/4012, G06Q40/02, G06Q20/3255, G06Q40/00
European ClassificationG06Q20/04, G06Q40/02, G06Q20/32, G06Q40/00, G06Q20/3223, G06Q20/40, G06Q20/385, G06Q20/3255