Systems and Methods to Automate Transactions via Mobile Devices

• US 20110217994A1
• Filed: 05/03/2010
• Published: 09/08/2011
• Est. Priority Date: 03/03/2010
• Status: Abandoned Application

• Current Assignee: Boku Incorporated
• Original Assignee: Boku Incorporated
• Inventors: RINGEWALD, Erich L., YOO, David, HIRSON, Ron
• Application Number:
  US12/772,937
• Publication Number:
  US 20110217994A1
• Time in Patent Office: Days
• US Class Current: 455/466
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/326 Payment applications installed on the mobile devices
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 30/0641 Shopping interfaces
• CPC Class Codes: H04M 15/00 Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04W 4/24 Accounting or billing

Abstract

Systems and methods are provided to automate transactions via mobile communications. In one aspect, a system includes a data storage facility to store data associating phone numbers with accounts and an interchange coupled with the data storage facility. The interchange includes a common format processor and a plurality of converters to interface with a plurality of different controllers of mobile communications. The converters are configured to communicate with the controllers in different formats and with the common format processor in a common format. The common format processor has an application programming interface to receive requests, such as a charge request having an identification of a phone number, an identification of a merchant, and an amount, and a status request having an identification of the first request, and is to transmit a message to a telephonic apparatus at the phone number to confirm the charge request, using one of the converters.

Claims

1. A method, comprising:

providing a computing device configured with an application programming interface;

receiving requests using the computing device through the application programming interface, the requests comprising

a first request having an identification of a phone number, an identification of a merchant, and an amount, and

a second request having an identification of the first request;

transmitting a message from the computing device to a telephonic apparatus at the phone number to confirm the first request;

after the first request is confirmed via communicating with the telephonic apparatus at the phone number, charging the user of the phone number according to the amount specified in the first request; and

providing a status of the first request in response to the second request, in accordance with the application programming interface.

2. The method of claim 1, further comprising:

providing the identification of the first request as a response to the first request in accordance with the application programming interface.

3. The method of claim 1, wherein the application programming interface is implemented via a web service.

4. The method of claim 1, wherein the requests further comprise a third request having the phone number;

and the method further comprises;

identifying a mobile carrier of the phone number in response to the third request;

determining a set of discrete price points supported by the mobile carrier, wherein the user of the phone number is chargeable via the mobile carrier at the set of discrete price points; and

providing the set of discrete price points as a response to the third request.

5. The method of claim 4, wherein the amount is according to the set of discrete price points;

and the charging the user comprises transmitting one or more premium messages of discrete prices to the telephonic apparatus at the phone number.

6. The method of claim 5, wherein the one or more premium messages are transmitted via a short message service (SMS).

7. The method of claim 1, wherein the requests further comprise a third request having the phone number;

and the method further comprises;

determining a list of funding sources associated with the phone number; and

providing a list of identifiers corresponding to the list of funding sources respectively as a response to the third request.

8. The method of claim 7, wherein the first request further specifies one identifier from the list of identifiers;

and the charging the user is to use a funding source identified by the identifier.

9. The method of claim 8, wherein the list of identifiers are named by the user of the phone number.

10. The method of claim 8, wherein the funding source is one of:

a credit card account, a debit card account, a bank account, and an account with a payment intermediary service.

11. The method of claim 1, wherein the first request further identifies a uniform resource identifier (URI);

and the method further comprises;

upon successfully charging the user according to the amount specified in the first request, visiting the URI specified in the first request.

12. A method, comprising:

providing a software development kit to a developer of a mobile application, the software development kit including a set of instructions to be included as part of the mobile application, when executed on a mobile phone the set of instructions to cause the mobile phone to;

identify a Mobile Subscriber Integrated Services Digital Network Number (MSISDN) of the mobile phone,

communicate with a remote server to determine a set of discrete price points supported by a mobile carrier of the mobile phone, wherein the user of the phone number is chargeable via the mobile carrier at the set of discrete price points,

provide the set of discrete price points to the mobile application,

receive a charge request from the mobile application in accordance with an application programming interface provided by the software development kit, the charge request being based on the set of discrete price points,

communicate the charge request to the remote server,

monitor an inbox of the mobile phone for a message from the remote server indicating a success in fulfilling the charge request, and

notify the mobile application of the success in accordance with the application programming interface.

13. The method of claim 12, wherein the messages in the inbox of the mobile phone are received via a short message service (SMS).

14. The method of claim 13, wherein the charge request is communicated to the remote server via a Hypertext Transfer Protocol (HTTP) request;

and the set of instructions is to further cause the mobile phone to receive an identification to represent the charge request and to transmit an SMS message including the identification to confirm the charge request.

15. The method of claim 13, wherein the charge request is communicated to the remote server via the short message service (SMS).

16. The method of claim 13, wherein the message from the remote server indicating the success in fulfilling the charge request comprises a mobile terminated premium message;

and the charge request is at least partially funded by the mobile terminated premium message.

17. The method of claim 12, wherein the charge request is communicated to the remote server via one or more mobile initiated premium messages.

18. The method of claim 12, wherein the set of instructions are further configured to cause the mobile phone to encrypt the charge request using a public key associated with a merchant of the mobile application.

19. The method of claim 18, wherein the charge request comprises an identification of the merchant, an amount specified according to one or more of the discrete price points, and the MSISDN.

20. A system, comprising:

a data storage facility to store data associating phone numbers with accounts;

an interchange coupled with the data storage facility, the interchange including a common format processor and a plurality of converters to interface with a plurality of controllers of mobile communications, the converters configured to communicate with the controllers in different formats, the converters to communicate with the common format processor in a common format, the common format processor configured with an application programming interface to receive requests via Hypertext Transfer Protocol, the requests including

a first request having an identification of a phone number, an identification of a merchant, and an amount, and

a second request having an identification of the first request,

wherein the common format processor is to use one converter of the converters to transmit a message to a telephonic apparatus at the phone number to confirm the first request;

wherein after the first request is confirmed via communicating with the telephonic apparatus at the phone number, the common format processor is to charge the user of the phone number according to the amount specified in the first request; and

wherein the common format processor is to provide a status of the first request in response to the second request, in accordance with the application programming interface.