US20130124405A1 - Mobile-To-Mobile Payment System and Method - Google Patents

Mobile-To-Mobile Payment System and Method Download PDF

Info

Publication number
US20130124405A1
US20130124405A1 US13/738,515 US201313738515A US2013124405A1 US 20130124405 A1 US20130124405 A1 US 20130124405A1 US 201313738515 A US201313738515 A US 201313738515A US 2013124405 A1 US2013124405 A1 US 2013124405A1
Authority
US
United States
Prior art keywords
mobile device
payee
payor
payment
payment server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US13/738,515
Inventor
Mehrak Hamzeh
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Globaltel Media Inc
Original Assignee
Globaltel Media Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US85914306P priority Critical
Priority to US11/940,288 priority patent/US8369828B2/en
Application filed by Globaltel Media Inc filed Critical Globaltel Media Inc
Priority to US13/738,515 priority patent/US20130124405A1/en
Publication of US20130124405A1 publication Critical patent/US20130124405A1/en
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices using wireless devices
    • G06Q20/322Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3223Realising banking transactions through M-devices
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/22Payment schemes or models
    • G06Q20/223Payment schemes or models based on the use of peer-to-peer networks
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices using wireless devices
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices using wireless devices
    • G06Q20/322Aspects of commerce using mobile devices [M-devices]
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

A mobile-to-mobile payment method and system are presented. One or more payor messages are received at a payment server from a mobile device associated with a payor. The one or more payor messages include an identifier of a payee and an amount. The identifier of the payee is associated with a payee account, and the mobile device is associated with a payor account. The payment server executes a transfer of funds of the amount from the payor account to the payee account.

Description

    CROSS REFERENCE TO RELATED APPLICATION
  • The present patent application claims priority under 35 U.S.C. §119 to U.S. Provisional Patent Application Ser. No. 60/859,143, filed on Nov. 14, 2006, and entitled, “Mobile-to-Mobile Payment System and Method”, the entire disclosure of which is incorporated by reference herein.
  • BACKGROUND
  • This disclosure relates generally to mobile computing applications, and more particularly to techniques for employing a credit device processor on a mobile device such as a cellular phone.
  • Currently, there is no credit device processor on a mobile device such as cellular phone. A credit device processor can process transactions using a credit device such as a credit card. Thus, many consumers are currently having to write a paper check, wire funds, or send payments for something via, mail, which includes electronic mail as well as regular mail. Many, if not all, of these payment schemes include transaction fees.
  • What is needed is a cost-effective and convenient way for payments to be made from one mobile device to another, whether such mobile-to-mobile arrangement is a business-to-business (B2B), a business-to-consumer (B2C), or consumer-to-consumer (C2C).
  • SUMMARY
  • In general, this document discusses systems and methods for mobile-to-mobile payment. In some implementations, the term “mobile” can include a device such as a cellular phone or other wireless communication device.
  • The system and method facilitate mobile payment using the short messaging service (SMS) or text messaging application on a mobile device. In most implementations, a mobile payment method includes paying people for services, money owed, or anything related to the exchange of money or funds.
  • In one aspect, a mobile-to-mobile payment method includes a step of receiving at a payment server one or more payor messages from a mobile device associated with a payor, the one or more payor messages including an identifier of a payee and an amount. The method further includes the steps of associating the identifier of the payee with a payee account, associating the mobile device with a payor account, and the payment server executing a transfer of funds of the amount from the payor account to the payee account.
  • In another aspect, a mobile-to-mobile payment system includes a communications network having at least one wireless link to communicate with a plurality of mobile devices. The system further includes a payment server adapted to receive one or more payment messages from a payor's mobile devices, the one or more payor messages including an identifier of a payee and an amount. The payment server is further adapted to associate the identifier of the payee with a payee account, associate the payor's mobile device with a payor account, and execute a transfer of funds of the amount from the payor account to the payee account.
  • In yet another aspect, a mobile device includes a user interface for receiving instruction data for a mobile-to-mobile payment process, and a translator to translate the instruction data to one or more payment messages to control a payment server that executes the mobile-to-mobile payment process, the payment messages including an identifier of a payee and an amount of a payment. The mobile device further includes a messaging service adapted to transmit the payment messages to a payment server via a communications network having at least one wireless link.
  • In still another aspect, a mobile messaging service for a mobile device, includes an outbound messaging component for sending payment messages from the mobile device to a payment server, the payment messages including an identifier of a payee and an amount of a payment. The messaging service further includes an inbound messaging component for receiving confirmation messages from the payment server to the mobile device, the confirmation messages including prompts for further information and/or prompts for an acknowledgement to be sent on the outbound messaging component.
  • The advantages include lower risk of exposing financial information over wireless networks, quick and easy payment, no wire transfer fees, secure payment transfer of funds over the Internet and not wireless network. Other advantages include no need of credit card processor on cell phone, no credit card transaction fees, and no need for a user to write checks. Further, the system and method supports international transactions.
  • The details of one or more embodiments are set forth in the accompanying drawings and the description below. Other features and advantages will be apparent from the description and drawings, and from the claims.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • These and other aspects will now be described in detail with reference to the following drawings.
  • FIG. 1 illustrates one scenario of a mobile-to-mobile payment arrangement.
  • FIG. 2 illustrates another scenario of a mobile-to-mobile payment arrangement.
  • FIG. 3 illustrates a mobile-to-mobile payment system.
  • Like reference symbols in the various drawings indicate like elements.
  • DETAILED DESCRIPTION
  • This document describes systems and methods for mobile-to-mobile payment. The term “mobile” can include a device such as a cellular phone or other wireless communication device. The systems and methods facilitate payment from one party to another using the short messaging service (SMS) or text messaging application on a mobile device and via a communications network having at least one wireless link. In most implementations, a mobile payment method includes paying people for services, money owed, or anything related to the exchange of money or funds.
  • As an illustrative example, two people, Payor and Payee, have signed up ahead of time online through a website for a service for enabling mobile-to-mobile payments, but instead of making a payment from Payor to Payee through email, payment is actually made from an account associated with one mobile device to an account with another mobile device. The enabling mechanism is a messaging or text service operable by at least one, and preferably both, mobile devices. Each mobile device may be, without limitation, a cellular phone, a personal digital assistant, a handheld computer, or any other device that enables wireless data communication, and which includes an alphanumeric keypad by which a user can enter in alphanumeric codes and commands. Each person in the example can represent an individual or an entity, such as a business, group, or other such entity.
  • With reference to FIG. 3, the mobile-to-mobile payment system 300 enables a payment from a first mobile device 302 to a second mobile device 304. For sake of simplicity and for exemplary purposes only, the first mobile device 302 is associated with a payor, and the second mobile device 304 is associated with a payee. The first mobile device 302 interacts with a payment server 306 via a messaging service. The messaging service can be the Short Messaging Service (SMS) or other messaging application used by the first mobile device 302. The messages communicated to the payment server 306 from first mobile device 302 can include a payor ID (i.e. identifier such as mobile device ID or telephone number of the first mobile device 302), an identifier associated with payee (i.e. identifier such as mobile device ID or telephone number of the second mobile device 304, etc.), an amount to be paid, and request codes, confirmation codes, and other messages. For example, to access the payment server 306, payor can enter a random or predetermined alphanumeric code on the first mobile device 302 and transmit the code to the payment server to begin the payment process.
  • The payment server 306 can include a website that may include a mobile-formatted webpage through which users can interact via mobile devices. The payment server 306 includes a database, and is configured to receive messages from the mobile devices, identify and associate accounts with users, and automatically match received messages with users based either on a caller ID or embedded code within a message. The code may be the result of an interactive graphical user interface (GUI) provided by the website to the display screen of a mobile device. The GUI can have a number of graphical buttons, boxes or links, some of which are associated with or otherwise manipulated by activatable keys on a keypad or other physical controls of a mobile device.
  • The payment server 306 associates a payor with a payor account, receives an indication of the payee and payment amount from a mobile device associated with the payor, associates the payee, payor, and payment amount information with their respective embodiments as represented by data stored in the database 308, and at least partially interactively, via mobile devices 302 and 304, executes the payment transaction from the payor's account 310 to the payee's account 312.
  • A first scenario 100 is illustrated in a flowchart shown in FIG. 1, and discussed in further detail below:
  • At 102, Payor sends, via text messages or other messaging service to Payee, a message including a code or a keyword such as “Pay to 10958.” The code 10958 represents a short code which directs communication to a payment server that hosts a mobile-to-mobile payment website. The keyword is an identifier of the function, and as such the keyword can be any string of alphanumeric characters or symbols. Once Payor text messages “Pay to 10958,” the payment server recognizes the requesting Payor through caller ID, and determines which account is to be debited, i.e. an account associated with Payor.
  • At 104, the payment server responds back to Payor, via SMS or other text messaging service, with a message including a prompt for Payor to enter a cell phone number or other identifying number associated with a mobile device of Payee, who Payor wants to pay. This and other messages from the payment server can be interpreted by a local application on a mobile device used by the payor to generate an interactive GUI, which translates messages into interactive components and user inputs into messages. In preferred implementations, at 106, Payor enters in his mobile device the Payee's cell phone number, or other identifier, and hits “send.”
  • At 108, the payment server matches the Payee's cell phone number to an account to be paid, and generates response message to Payor prompting Payor to enter in the amount to pay Payee. At 110 Payor enters in an amount, such as “10.00,” and hits “SEND.” At 112, a message with prompt for a confirmation is sent to Payor or even Payee to indicates that Payor has paid Payee $10.00, and the payment is transferred to an account associated with Payee. In some implementations, the specific account can be identified by either Payee or Payor via text messaging of an account code. At 114, Payor responds with a confirmation to the payment server. At 116, the payment server causes the transfer of the payment from Payor's account to the Payee's account, and can send another confirmation message to either Payor and/or Payee.
  • A second scenario 200 is shown in the flowchart of FIG. 2.
  • At 202 Payor text messages a keyword such as “Pay to 10958,” which is a code that directs communication to a payment server. The short code can be anything that is issued by any of the wireless carriers or government agencies. Once Payor text messages “Pay to 10958,” the payment server recognizes the requesting Payor through caller ID and knows which account is going to be debited. At 204, the payment server responds back to Payor via SMS or other messaging server, prompting Payor to enter in a Payee identifying number or code and an amount, which indicates that Payee is the person to be paid and how much should be paid, respectively.
  • At 206 Payor enters in the number of the person to pay, and the amount to pay, Payor hits “send” or a similar button or function of the mobile device. In one implementation, the format on a display appears as follows: “8586996163, 10.00”. A response text message is returned to Payor confirming the phone number or name of person that Payor is about to pay, along with amount to be paid to Payee. At 208, the payment server associates the Payee's identifier with an account, and responds to payor with a message having a confirmation of the Payee and the amount.
  • At 210 Payor replies with an acknowledgement message, i.e. “yes” to confirm or “no” to cancel. If yes, then a confirmation text message to Payee gets sent that says Payor has paid $10.00 to Payee, and the funds are transferred from an account associated with Payor to an account associated with Payee. If no, then a text message is returned to Payor prompting for the cell phone number of Payee, the text message asking whether Payee is the person they want to pay and how much. At 212, the payment server credits an account of the Payee, via banking application connected with Payor's and Payee's account, and sends a message to either Payee and/or Payor with a confirmation of the completion of the transaction.
  • Embodiments of the invention and all of the functional operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of them. Embodiments of the invention can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium, e.g., a machine readable storage device, a machine readable storage medium, a memory device, or a machine-readable propagated signal, for execution by, or to control the operation of, data processing apparatus.
  • The term “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of them. A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.
  • A computer program (also referred to as a program, software, an application, a software application, a script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
  • The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).
  • Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to, a communication interface to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks.
  • Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio player, a Global Positioning System (GPS) receiver, to name just a few. Information carriers suitable for embodying computer program instructions and data include all forms of non volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
  • To provide for interaction with a user, embodiments of the invention can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
  • Embodiments of the invention can be implemented in a computing system that includes a back end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the invention, or any combination of such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.
  • The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
  • Certain features which, for clarity, are described in this specification in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features which, for brevity, are described in the context of a single embodiment, may also be provided in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
  • Particular embodiments of the invention have been described. Other embodiments are within the scope of the following claims. For example, the steps recited in the claims can be performed in a different order and still achieve desirable results. In addition, embodiments of the invention are not limited to database architectures that are relational; for example, the invention can be implemented to provide indexing and archiving methods and systems for databases built on models other than the relational model, e.g., navigational databases or object oriented databases, and for databases having records with complex attribute structures, e.g., object oriented programming objects or markup language documents. The processes described may be implemented by applications specifically performing archiving and retrieval functions or embedded within other applications.

Claims (19)

1.-20. (canceled)
21. A mobile-to-mobile payment method comprising:
receiving at a payment server one or more payment messages from a mobile device associated with a payor, the one or more payment messages including a code for transmitting the one or more payment messages to the payment server;
sending a prompt from the payment server to the mobile device associated with the payor to enter an identifier of a mobile device associated with a payee;
receiving at the payment server from the mobile device associated with the payor a message including the identifier of the mobile device associated with the payee;
sending a prompt from the payment server to the mobile device associated with the payor to enter an amount to be paid to the payee;
receiving at the payment server from the mobile device associated with the payor a message including the amount to be paid to the payee;
in response to the message received from the mobile device associated with the payor including the amount to be paid to the payee, sending a message from the payment server to the mobile device associated with the payor confirming the amount to be paid to the payee;
receiving at the payment server from the mobile device associated with the payor an acknowledgement message confirming that funds should be transferred by the payment server from an account associated with the payor to an account associated with the payee.
22. The method of claim 21, further comprising the payment server generating a confirmation message indicating that the transferring of funds has been completed.
23. The method of claim 22, further comprising transmitting the confirmation message to the mobile device associated with the payor.
24. The method of claim 21, wherein the one or more payment messages are short messaging service messages.
25. The method of claim 21, wherein the one or more payment messages are generated by a client application on the mobile device associated with the payor.
26. The method of claim 21, wherein the identifier of the mobile device associated with the payee is a cell phone number of the mobile device.
27. A mobile-to-mobile payment system comprising:
a communications network having at least one wireless link to communicate with a plurality of mobile devices; and
a payment server adapted to:
receive one or more payment messages from a payor's mobile device, the one or more payment messages including a code for transmitting the one or more payment messages to the payment server;
send a prompt to the payor's mobile device to enter an identifier of a mobile device associated with a payee;
receive a message from the payor's mobile device including the identifier of the mobile device associated with the payee;
send a prompt to the payor's mobile device to enter an amount to be paid to the payee;
receiving at the payment server from the mobile device associated with the payor message including the amount to be paid to the payee;
in response to the message from the payor's mobile device including the amount to be paid to the payee, send a message to the payor's mobile device confirming the amount to be paid to the payee;
receive an acknowledgement message from the payor's mobile device confirming that funds should be transferred from an account associated with the payor to an account associated with the payee.
28. The system of claim 27, wherein payment server is further adapted to generate a confirmation message indicating that the transferring of funds has been completed.
29. The system of claim 27, wherein the payment server is further adapted to transmit the confirmation message to the payor's mobile device.
30. The system of claim 27, wherein the one or more payment messages are short messaging service messages.
31. The system of claim 27, wherein the one or more payment messages are generated by a client application on the payor's mobile device.
32. The system of claim 27, wherein the identifier of the mobile device associated with the payee is a cell phone number of the mobile device.
33. A mobile device comprising:
a user interface for receiving instruction data for a mobile-to-mobile payment process;
a translator to translate the instruction data to one or more payment messages to control a payment server that executes the mobile-to-mobile payment process, wherein:
the payment messages include an identifier of a mobile device associated with a payee, an amount of a payment to be paid to the payee and a code for transmitting the one or more payment messages to the payment server, and
the mobile-to-mobile payment process includes:
sending a prompt from the payment server to a mobile device associated with a payor to enter the identifier of the mobile device associated with the payee;
receiving at the payment server from the mobile device associated with the payor message including the identifier of the mobile device associated with the payee;
sending a prompt from the payment server to the mobile device associated with the payor to enter amount to be paid to the payee;
receiving at the payment server from the mobile device associated with the payor a message including the amount to be paid to the payee;
in response to the message received from the mobile device associated with the payor including the amount to be paid to the payee, sending a message from the payment server to the mobile device associated with the payor confirming the amount to be paid to the payee;
receiving at the payment server from the mobile device associated with the payor an acknowledgement message confirming that funds should be transferred by the payment server from an account associated with the payor to an account associated with the payee; and
a messaging service adapted to transmit the one or more payment messages to the payment server via a communications network having at least one wireless link.
34. The mobile device of claim 33, further comprising a display for displaying confirmation messages received from the payment server.
35. A mobile messaging service thr enabling mobile-to-mobile payments, the service comprising:
a messaging component operating on a mobile device, wherein the messaging component:
sends one or more payment messages to a payment server, the one or more payment messages including a code for transmitting the one or more payment messages to the payment server;
receives a prompt from the payment server to enter an identifier of a mobile device associated with a payee;
sends to the payment server a message including the identifier of the mobile device associated with the payee;
receives a prompt from the payment server to enter an amount to be paid to the payee;
send to the payment server a message including the amount to be paid to the payee;
in response to the message sent to the payment server including the amount to be paid to the payee, receives a message from the payment server confirming the amount to be paid to the payee;
sends an acknowledgement message to the payment server confirming that funds should be transferred from an account associated with the payor to an account associated with the payee; and
receives a confirmation message from the payment server indicating that the funds have been transferred from the account associated with the payor to the account associated with the payee.
36. The mobile messaging service of claim 35, wherein the messaging component includes a short messaging service.
37. The mobile messaging service of claim 35, further comprising a translation component for translating the single prompt, the message confirming the identifier of the mobile device associated with the payee and the amount to be paid to the payee, or the confirmation message indicating that the funds have been transferred from the account associated with the payor to the account associated with the payee from the payment server from text-based messages to graphical elements.
38. The mobile messaging service of claim 37, wherein the translation component is further adapted to translate the one or more payment messages into text-based messages.
US13/738,515 2006-11-14 2013-01-10 Mobile-To-Mobile Payment System and Method Abandoned US20130124405A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US85914306P true 2006-11-14 2006-11-14
US11/940,288 US8369828B2 (en) 2006-11-14 2007-11-14 Mobile-to-mobile payment system and method
US13/738,515 US20130124405A1 (en) 2006-11-14 2013-01-10 Mobile-To-Mobile Payment System and Method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US13/738,515 US20130124405A1 (en) 2006-11-14 2013-01-10 Mobile-To-Mobile Payment System and Method

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/940,288 Continuation US8369828B2 (en) 2006-11-14 2007-11-14 Mobile-to-mobile payment system and method

Publications (1)

Publication Number Publication Date
US20130124405A1 true US20130124405A1 (en) 2013-05-16

Family

ID=39311032

Family Applications (2)

Application Number Title Priority Date Filing Date
US11/940,288 Active - Reinstated 2029-11-12 US8369828B2 (en) 2006-11-14 2007-11-14 Mobile-to-mobile payment system and method
US13/738,515 Abandoned US20130124405A1 (en) 2006-11-14 2013-01-10 Mobile-To-Mobile Payment System and Method

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US11/940,288 Active - Reinstated 2029-11-12 US8369828B2 (en) 2006-11-14 2007-11-14 Mobile-to-mobile payment system and method

Country Status (2)

Country Link
US (2) US8369828B2 (en)
WO (1) WO2008061151A2 (en)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070203836A1 (en) * 2006-02-28 2007-08-30 Ramy Dodin Text message payment
US20110264543A1 (en) * 2010-04-26 2011-10-27 Ebay Inc. Reverse payment flow
US10078821B2 (en) 2012-03-07 2018-09-18 Early Warning Services, Llc System and method for securely registering a recipient to a computer-implemented funds transfer payment network
US10318936B2 (en) 2012-03-07 2019-06-11 Early Warning Services, Llc System and method for transferring funds
US10395223B2 (en) 2012-03-07 2019-08-27 Early Warning Services, Llc System and method for transferring funds
US10395247B2 (en) 2012-03-07 2019-08-27 Early Warning Services, Llc Systems and methods for facilitating a secure transaction at a non-financial institution system
US10438175B2 (en) 2015-07-21 2019-10-08 Early Warning Services, Llc Secure real-time payment transactions
US10504082B2 (en) * 2011-04-11 2019-12-10 Visa International Service Association Interoperable financial transactions via mobile devices

Families Citing this family (61)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7567937B2 (en) * 2001-01-17 2009-07-28 Xprt Ventures, Llc System and method for automatically effecting payment for a user of an electronic auction system
US7483856B2 (en) 2001-01-17 2009-01-27 Xprt Ventures, Llc System and method for effecting payment for an electronic auction commerce transaction
US7146338B2 (en) 2001-06-28 2006-12-05 Checkfree Services Corporation Inter-network financial service
US20080288376A1 (en) 2007-04-27 2008-11-20 Cashedge, Inc. Centralized payment hub method and system
US8768778B2 (en) * 2007-06-29 2014-07-01 Boku, Inc. Effecting an electronic payment
US20090063312A1 (en) * 2007-08-28 2009-03-05 Hurst Douglas J Method and System for Processing Secure Wireless Payment Transactions and for Providing a Virtual Terminal for Merchant Processing of Such Transactions
GB0809383D0 (en) * 2008-05-23 2008-07-02 Vidicom Ltd Customer to supplier funds transfer
GB0809381D0 (en) * 2008-05-23 2008-07-02 Vidicom Ltd Funds transfer electronically
US8385913B2 (en) 2008-09-08 2013-02-26 Proxicom Wireless, Llc Using a first wireless link to exchange identification information used to communicate over a second wireless link
US20100082466A1 (en) * 2008-09-26 2010-04-01 Mark Carlson Beneficiary initiated p2p, p2b payment model
WO2010086879A1 (en) * 2009-01-16 2010-08-05 Mchek India Payment Systems Pvt. Ltd. A system and method for carrying out a financial transaction
US9652761B2 (en) * 2009-01-23 2017-05-16 Boku, Inc. Systems and methods to facilitate electronic payments
US8041639B2 (en) * 2009-01-23 2011-10-18 Vidicom Limited Systems and methods to facilitate online transactions
US8548426B2 (en) * 2009-02-20 2013-10-01 Boku, Inc. Systems and methods to approve electronic payments
US9990623B2 (en) 2009-03-02 2018-06-05 Boku, Inc. Systems and methods to provide information
US8160943B2 (en) * 2009-03-27 2012-04-17 Boku, Inc. Systems and methods to process transactions based on social networking
WO2010110966A1 (en) * 2009-03-27 2010-09-30 Boku, Inc. Systems and methods to process transactions based on social networking
US8131258B2 (en) * 2009-04-20 2012-03-06 Boku, Inc. Systems and methods to process transaction requests
US20100299220A1 (en) * 2009-05-19 2010-11-25 Boku, Inc. Systems and Methods to Confirm Transactions via Mobile Devices
US8224727B2 (en) * 2009-05-27 2012-07-17 Boku, Inc. Systems and methods to process transactions based on social networking
US20100306015A1 (en) * 2009-05-29 2010-12-02 Boku, Inc. Systems and Methods to Schedule Transactions
US9595028B2 (en) 2009-06-08 2017-03-14 Boku, Inc. Systems and methods to add funds to an account via a mobile communication device
US20100312645A1 (en) * 2009-06-09 2010-12-09 Boku, Inc. Systems and Methods to Facilitate Purchases on Mobile Devices
US9697510B2 (en) 2009-07-23 2017-07-04 Boku, Inc. Systems and methods to facilitate retail transactions
US9519892B2 (en) 2009-08-04 2016-12-13 Boku, Inc. Systems and methods to accelerate transactions
US8660911B2 (en) 2009-09-23 2014-02-25 Boku, Inc. Systems and methods to facilitate online transactions
US20110078077A1 (en) * 2009-09-29 2011-03-31 Boku, Inc. Systems and Methods to Facilitate Online Transactions
US8224709B2 (en) * 2009-10-01 2012-07-17 Boku, Inc. Systems and methods for pre-defined purchases on a mobile communication device
US20110125610A1 (en) * 2009-11-20 2011-05-26 Boku, Inc. Systems and Methods to Automate the Initiation of Transactions via Mobile Devices
US8412626B2 (en) * 2009-12-10 2013-04-02 Boku, Inc. Systems and methods to secure transactions via mobile devices
US20110143710A1 (en) * 2009-12-16 2011-06-16 Boku, Inc. Systems and methods to facilitate electronic payments
US8458068B2 (en) * 2010-01-04 2013-06-04 Bank Of America Corporation Monitoring in an automated clearing house processing environment
US20110196783A1 (en) * 2010-01-11 2011-08-11 Gad Liwerant Wireless payment platform and mobile reseller system
US8566188B2 (en) * 2010-01-13 2013-10-22 Boku, Inc. Systems and methods to route messages to facilitate online transactions
US20110185406A1 (en) * 2010-01-26 2011-07-28 Boku, Inc. Systems and Methods to Authenticate Users
US20110217994A1 (en) * 2010-03-03 2011-09-08 Boku, Inc. Systems and Methods to Automate Transactions via Mobile Devices
US8219542B2 (en) 2010-03-25 2012-07-10 Boku, Inc. Systems and methods to provide access control via mobile phones
US8583504B2 (en) 2010-03-29 2013-11-12 Boku, Inc. Systems and methods to provide offers on mobile devices
US8355987B2 (en) 2010-05-06 2013-01-15 Boku, Inc. Systems and methods to manage information
WO2012006358A2 (en) * 2010-07-06 2012-01-12 Boku, Inc. Systems and methods to receive funds via mobile devices
AU2011289300B2 (en) 2010-08-11 2014-11-13 Boku, Inc. Systems and methods to identify carrier information for transmission of premium messages
US8699994B2 (en) 2010-12-16 2014-04-15 Boku, Inc. Systems and methods to selectively authenticate via mobile communications
US8412155B2 (en) 2010-12-20 2013-04-02 Boku, Inc. Systems and methods to accelerate transactions based on predictions
EP2659443A1 (en) * 2010-12-27 2013-11-06 Mehrak Hamzeh Mobile payment system and method
US8583496B2 (en) 2010-12-29 2013-11-12 Boku, Inc. Systems and methods to process payments via account identifiers and phone numbers
US8700524B2 (en) 2011-01-04 2014-04-15 Boku, Inc. Systems and methods to restrict payment transactions
US9135612B1 (en) 2011-04-17 2015-09-15 Proctor Consulting, LLC Proximity detection, virtual detection, or location based triggering of the exchange of value and information
GB201106555D0 (en) * 2011-04-19 2011-06-01 Tomtom Int Bv Taxi dispatching system
US8543087B2 (en) 2011-04-26 2013-09-24 Boku, Inc. Systems and methods to facilitate repeated purchases
US9830622B1 (en) 2011-04-28 2017-11-28 Boku, Inc. Systems and methods to process donations
US9191217B2 (en) 2011-04-28 2015-11-17 Boku, Inc. Systems and methods to process donations
US20130031009A1 (en) * 2011-07-28 2013-01-31 Apple Inc. Ad-hoc cash dispensing network
WO2013028910A2 (en) * 2011-08-23 2013-02-28 Visa International Service Association Mobile funding method and system
KR20150022754A (en) * 2012-03-30 2015-03-04 아이피 페이오베이션 피티와이 엘티디 Payment apparatus and method
US8626659B1 (en) 2012-09-28 2014-01-07 Fiserv, Inc. Facilitating presentation of content relating to a financial transaction
US20140248941A1 (en) * 2013-03-01 2014-09-04 Igt Transfer verification of mobile payments
US10185946B2 (en) 2014-12-31 2019-01-22 Fiserv, Inc. Facilitating presentation of content relating to a financial transaction
US9756032B2 (en) * 2015-04-24 2017-09-05 Paypal, Inc. Identity data based on aggregating input data
US10140600B2 (en) 2015-07-01 2018-11-27 Liveensure, Inc. System and method for mobile peer authentication and asset control
US10395253B2 (en) 2015-07-01 2019-08-27 Liveensure, Inc. System and method for securing and monetizing peer-to-peer digital content
TWI613603B (en) * 2015-07-16 2018-02-01 蓋特資訊系統股份有限公司 Off-line mobile transaction method and transaction system thereof

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040019487A1 (en) * 2002-03-11 2004-01-29 International Business Machines Corporation Multi-modal messaging
US20060265325A1 (en) * 2003-12-18 2006-11-23 Fajardo Alfredo C System and method for facilitating payment via a communications network using value accredited to a customer of the communications network
US20070270124A1 (en) * 2006-05-19 2007-11-22 Asiatone Llc, D/B/A Gorilla Mobile Systems and methods for adding credit to a wireless telecommunications account

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI109505B (en) 1997-03-24 2002-08-15 Fd Finanssidata Oy The use of banking services in a digital cellular radio system,
US6873691B1 (en) 1999-04-06 2005-03-29 Bellsouth Intellectual Property Corporation Methods and systems for using the public switched telephone network to conduct a transaction between customer accounts
US6609113B1 (en) * 1999-05-03 2003-08-19 The Chase Manhattan Bank Method and system for processing internet payments using the electronic funds transfer network
AT5596U1 (en) 2000-11-29 2002-08-26 Mobilkom Austria Ag & Co Kg Device for transmitting financial values ​​between subscribers of a telecommunication network
GB2372615A (en) 2000-12-27 2002-08-28 Robert Joseph Gerard Macnamee Telephone based payment system
CN1592911A (en) * 2001-11-26 2005-03-09 罗纳德·H·鲍尔 Portable messaging device adapted to perform financial transactions
US6996409B2 (en) * 2002-06-26 2006-02-07 Level Z, L.L.C. Multi-party concurrence through short message service exchanges
US7529706B2 (en) * 2004-07-14 2009-05-05 Yahoo! Inc. Systems and methods for performing international money exchanges

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040019487A1 (en) * 2002-03-11 2004-01-29 International Business Machines Corporation Multi-modal messaging
US20060265325A1 (en) * 2003-12-18 2006-11-23 Fajardo Alfredo C System and method for facilitating payment via a communications network using value accredited to a customer of the communications network
US20070270124A1 (en) * 2006-05-19 2007-11-22 Asiatone Llc, D/B/A Gorilla Mobile Systems and methods for adding credit to a wireless telecommunications account

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070203836A1 (en) * 2006-02-28 2007-08-30 Ramy Dodin Text message payment
US8662384B2 (en) * 2006-02-28 2014-03-04 Google Inc. Text message payment
US20110264543A1 (en) * 2010-04-26 2011-10-27 Ebay Inc. Reverse payment flow
US10504082B2 (en) * 2011-04-11 2019-12-10 Visa International Service Association Interoperable financial transactions via mobile devices
US10078821B2 (en) 2012-03-07 2018-09-18 Early Warning Services, Llc System and method for securely registering a recipient to a computer-implemented funds transfer payment network
US10318936B2 (en) 2012-03-07 2019-06-11 Early Warning Services, Llc System and method for transferring funds
US10395223B2 (en) 2012-03-07 2019-08-27 Early Warning Services, Llc System and method for transferring funds
US10395247B2 (en) 2012-03-07 2019-08-27 Early Warning Services, Llc Systems and methods for facilitating a secure transaction at a non-financial institution system
US10438175B2 (en) 2015-07-21 2019-10-08 Early Warning Services, Llc Secure real-time payment transactions

Also Published As

Publication number Publication date
WO2008061151A3 (en) 2008-08-28
US20080133403A1 (en) 2008-06-05
WO2008061151A2 (en) 2008-05-22
US8369828B2 (en) 2013-02-05

Similar Documents

Publication Publication Date Title
US7031939B1 (en) Systems and methods for implementing person-to-person money exchange
US8515870B2 (en) Electronic payment systems and supporting methods and devices
US8359005B2 (en) Systems and methods to process transaction requests
US7827102B2 (en) System and method for secure distribution of information via email
US7016875B1 (en) Single sign-on for access to a central data repository
US9830596B2 (en) Method for conducting a transaction between a merchant site and a customer's electronic device without exposing payment information to a server-side application of the merchant site
CA2748913C (en) Payment system
US9710812B2 (en) Social network payment system
US8447700B2 (en) Transaction authorization service
US20090234751A1 (en) Electronic wallet for a wireless mobile device
US20140052633A1 (en) Payment in a chat session
US20090254479A1 (en) Transaction server configured to authorize payment transactions using mobile telephone devices
US20070287413A1 (en) Method and system for mobile billing and content delivery
US20110040686A1 (en) Mobile payment system and method using alias
JP2013101676A (en) Dynamic parse/build engine for parsing multi-format messages
US20060036553A1 (en) Automatic authorization of programmatic transactions
CA2748914C (en) Payment system
JP2009543185A (en) Method and system for financial transactions in a mobile environment
US20150149354A1 (en) Real-Time Data Recognition and User Interface Field Updating During Voice Entry
US20020120571A1 (en) Wireless financial system
US20170286926A1 (en) Communication device including multi-part alias identifier
KR20150107889A (en) A method and system for conducting mobile transaction and computer-readable media
US7831246B1 (en) Mobile merchant
US20070208816A1 (en) System and method for electronically facilitating, recording, and tracking transactions
US8566248B1 (en) Initiation of an information transaction over a network via a wireless device

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION