IP Library Granted Patent US 8,543,087
Granted Patent B2
US 8,543,087 · App. 13/453,198 · Granted Sep 24, 2013

Systems and methods to facilitate repeated purchases

Inventors: Kurt Davis (San Francisco, CA); Jang Kim (San Francisco, CA); David Yoo (San Mateo, CA); James Goodsall (Bollington, GB)
Assignee: Boku, Inc.
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,543,087
App. No.
13/453,198
Granted
Sep 24, 2013
Kind
B2
Abstract

Systems and methods are provided to facilitate repeated purchase and payment transactions. In one aspect, a system includes an interchange and a data storage facility configured to store payment transaction records associated with phone numbers. 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 to communicate with the common format processor in a common format. The common format processor is configured to identify a prior payment transaction associated with a phone number in response to a message from a mobile phone having the phone number, communicate with a merchant to repeat a purchase according to the prior payment transaction, and transmit via one of the converters premium messages to the mobile phone to collect funds for a payment to repeat the purchase.

Claims (44)

1. A computer-implemented method, comprising:

receiving, in a computing device, a message from a mobile phone having a phone number;

identifying, by the computing device in response to the message, a previous payment transaction processed by the computing device for the phone number;

communicating, by the computing device, with a merchant to repeat a purchase identified according to the previous payment transaction; and

processing, by the computing device, a payment to the merchant using funds associated with the phone number to repeat the purchase.

2. The method of claim 1 , wherein the identifying of the previous payment transaction comprises identifying a most recent payment transaction associated with the phone number as the previous payment transaction.

3. The method of claim 1 , wherein the previous payment transaction is identified based on the message.

4. The method of claim 1 , wherein the message is a reply to a previous message transmitted from the computing device to the mobile phone in connection with the previous payment transaction.

5. The method of claim 4 , wherein the message received from the mobile phone is received via a short message service (SMS).

6. The method of claim 5 , wherein the previous message transmitted from the computing device to the mobile phone includes a code to identify the previous payment transaction.

7. The method of claim 6 , wherein the message received from the mobile phone includes the code to identify the previous payment transaction.

8. The method of claim 1 , further comprising:

communicating, by the computing device, with the mobile phone to request confirmation of a request for the previous payment transaction; and

wherein the payment to repeat the purchase is processed without the computing device communicating with the mobile phone to request confirmation.

9. The method of claim 8 , further comprising:

providing, by the computing device, a user interface to receive the phone number from a user of the phone number to receive the request for the previous payment transaction, the user interface including an option to authorize the merchant to request a subsequent payment on behalf of the user; and

storing, by the computing device, authorization data to indicate a user selection of the option, if the option is selected in the user interface in connection with the request for the previous payment transaction.

10. The method of claim 9 , wherein the authorization data is configured to allow the merchant to request a payment to repeat the purchase.

11. The method of claim 10 , wherein the authorization data is configured to further allow the merchant to request a payment for a purchase different from the purchase associated with the previous payment transaction.

12. The method of claim 11 , wherein the authorization data is stored in association with the previous payment transaction.

13. The method of claim 9 , further comprising:

receiving, by the computing device, a payment request from the merchant to repeat the purchase;

communicating, by the computing device, with the mobile phone to request confirmation of the payment request received from the merchant, if the authorization data is stored in association with the previous payment transaction.

14. The method of claim 13 , wherein the payment request does not go through a device of the user between being transmitted by the merchant and being received by the computing device.

15. The method of claim 9 , further comprising:

receiving, by the computing device, a payment request from the merchant;

determining, by the computing device, whether the authorization data is stored in association with the previous payment transaction; and

if the authorization data is not stored in association with the previous payment transaction, rejecting the payment request.

16. The method of claim 1 , wherein the processing of the payment comprises:

transmitting, by the computing device, a plurality of premium messages to the mobile phone according to the phone number;

receiving funds corresponding to the plurality of premium messages from a telecommunication carrier of the mobile phone; and

providing the funds to the merchant as the payment.

17. The method of claim 1 , wherein the processing of the payment comprises:

charging a financial account associated with the phone number to collect funds for the payment.

18. A non-transitory computer-readable storage media storing instructions which, when executed on a computer, cause the computer to perform a method, the method comprising:

receiving, in a computer, a message from a mobile phone having a phone number;

identifying, by the computer in response to the message, a previous payment transaction processed by the computing device for the phone number;

communicating, by the computer, with a merchant to repeat a purchase identified according to the previous payment transaction; and

processing, by the computer, a payment to the merchant using funds associated with the phone number to repeat the purchase.

19. A computing apparatus, comprising:

a data storage facility configured to store payment transaction records associated with phone numbers, the payment transaction records including at least one record for a successful prior payment transaction, the record including data indicating a user selection of an option to authorize a respective merchant involved in the prior payment transaction to request payments on behalf of a user of a phone number associated with the record; and

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, the converters configured to communicate with the controllers in different formats, the converters to communicate with the common format processor in a common format;

wherein in response to a message from a mobile phone having the phone number, the common format processor is configured to identify the prior payment transaction associated with the phone number of the mobile phone, communicate with the merchant to repeat a purchase identified according to the prior payment transaction, and transmit via one of the converters a plurality of premium messages to the mobile phone to collect funds for a payment to repeat the purchase.

20. The apparatus of claim 19 , wherein in response to a payment request from the merchant, the common format processor is configured to determine whether to accept or reject the payment request based at least in part on the data indicating the user selection of the option.

Assignments (7)
CHANGE OF ADDRESS Recorded Nov 29, 2021
From: BOKU, INC.
To: BOKU, INC.
Reel/Frame 058257/0283 →
SECURITY INTEREST Recorded Jun 17, 2020
From: BOKU, INC.
To: CITIBANK, N.A.
Reel/Frame 052962/0236 →
RELEASE OF SECURITY INTEREST Recorded Jun 16, 2020
From: SILICON VALLEY BANK
To: BOKU, INC.; BOKU NETWORK SERVICES, INC.; BOKU PAYMENTS, INC.
Reel/Frame 052949/0784 →
RELEASE OF SECURITY INTEREST Recorded Jun 16, 2020
From: SILICON VALLEY BANK
To: BOKU, INC.
Reel/Frame 052949/0412 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Dec 31, 2019
From: BOKU, INC.; BOKU NETWORK SERVICES, INC.; BOKU PAYMENTS, INC.
To: SILICON VALLEY BANK
Reel/Frame 051451/0349 →
SECURITY AGREEMENT Recorded Mar 4, 2013
From: BOKU, INC.
To: SILICON VALLEY BANK
Reel/Frame 029918/0774 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 23, 2012
From: DAVIS, KURT; KIM, JANG; YOO, DAVID; GOODSALL, JAMES
To: BOKU, INC.
Reel/Frame 028089/0694 →
Continuity (2)
Provisional Application 61479200 · Apr 26, 2011
Related Publication 20120276870A1 · Nov 1, 2012