Systems and Methods to Restrict Payment Transactions

• US 20120171990A1
• Filed: 03/24/2011
• Published: 07/05/2012
• Est. Priority Date: 01/04/2011
• Status: Active Grant

• Current Assignee: Boku Incorporated
• Original Assignee: Boku Incorporated
• Inventors: Kingston, Jonathan Michael, Williams, Michael, Mullins, Kelly Jane
• Granted Patent: US 8,700,524 B2
• Time in Patent Office: Days
• US Class Current: 455/406
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/16 Payments settled via telecommunication systems
• CPC Class Codes: G06Q 20/384 using social networks
• CPC Class Codes: H04M 15/47 Fraud detection or prevention means
• CPC Class Codes: H04M 15/888 severing connection after predetermined time or data
• CPC Class Codes: H04W 4/24 Accounting or billing

Abstract

Systems and methods are provided to selectively restrict payment transactions. In one aspect, a system includes: a data storage facility to store restriction data in association with a phone number; and an interchange coupled with the data storage facility. The interchange includes a common format processor and a plurality of converters to interface with mobile controllers. The converters are configured to communicate with the controllers in different formats and to communicate with the common format processor in a common format. In response to a payment request identifying the phone number and a merchant, the common format processor determines whether to reject the payment request based at least in part on the restriction data and the identity of the merchant. If the request is not rejected, the common format processor uses one of the converters to communicate with a telephonic apparatus at the phone number to confirm the payment request.

Claims

1. A computer-implemented method, comprising:

storing, in a computing device, restriction data in association with a phone number;

receiving, in the computing device, a payment request identifying the phone number and a merchant;

determining, by the computing device, whether to reject the payment request based at least in part on the restriction data and an identity of the merchant;

if the payment request is not rejected based on the determining, communicating with a telephonic apparatus at the phone number to confirm the payment request; and

after confirmation of the payment request, transmitting a notification to the merchant.

2. The method of claim 1, further comprising:

transmitting, from the computing device, at least one premium message to the phone number to collect, via a telecommunication carrier of the telephonic apparatus, funds for the payment request;

wherein the notification is transmitted to the merchant after receiving a confirmation from the telecommunication carrier for the delivery of the at least one premium message; and

the premium message is transmitted via a short message service.

3. The method of claim 1, further comprising:

fulfilling the payment request using funds associated with the phone number.

4. The method of claim 3, wherein the fulfilling the payment request comprises charging a financial account associated with the phone number to collect funds for fulfillment of the payment request.

5. The method of claim 4, wherein the financial account is one of:

a credit account, a debit account, a prepaid account, a checking account, and a savings account.

6. The method of claim 1, wherein the restriction data identifies a merchant category;

the determining of whether to reject the payment request includes determining whether the merchant is in the merchant category; and

if the merchant is in the merchant category, the payment request is to be rejected.

7. The method of claim 1, wherein the restriction data identifies a list of one or more banned merchants;

the determining of whether to reject the payment request includes determining whether the merchant is in the list; and

if the merchant is in the list, the payment request is to be rejected.

8. The method of claim 1, wherein the restriction data allows payments using funds associated with the phone number for purchasing a first item from the merchant but not a second item from the merchant.

9. The method of claim 8, wherein the first item and the second item are one of:

products and services.

10. The method of claim 9, wherein the restriction data identifies a purchase category including the second item;

the payment request identifies an item to be paid for; and

the determining of whether to reject the payment request includes determining whether the item to be paid for is in the purchase category.

11. The method of claim 1, wherein the restriction data allows payments using funds associated with the phone number for purchasing from the merchant during a first time period but not a second time period.

12. The method of claim 1, wherein the restriction data includes a threshold for an aggregated amount;

and the determining of whether to reject the payment request includes determining whether the threshold would be exceeded by fulfillment of the payment request.

13. The method of claim 1, wherein the restriction data includes a threshold for purchase frequency;

and the determining of whether to reject the payment request includes determining whether the threshold would be exceeded by fulfillment of the payment request.

14. The method of claim 1, further comprising:

generating, by the computing device, at least a portion of the restriction data based on input from a parent of a user of the phone number.

15. The method of claim 1, further comprising:

generating, by the computing device, at least a portion of the restriction data based on input from a merchant from which a user of the phone number has made a purchase paid for via the computing device using the phone number.

16. The method of claim 1, further comprising:

generating, by the computing device, at least a portion of the restriction data based on past payment transactions processed by the computing device using funds associated with the phone number.

17. The method of claim 1, wherein the restriction data includes indications of reasons for the restrictions;

and wherein the reasons identify entities that are authorized to modify respective restrictions in the restriction data.

18. A computer-readable storage medium storing instructions which, when executed by a computer, cause the computer to perform a method, the method comprising:

storing, in a computing device, restriction data in association with a phone number;

receiving, in the computing device, a payment request identifying the phone number and a merchant;

determining, by the computing device, whether to reject the payment request based at least in part on the restriction data and an identity of the merchant;

if the payment request is not rejected based on the determining, communicating with a telephonic apparatus at the phone number to confirm the payment request; and

after confirmation of the payment request, transmitting a notification to the merchant.

19. A system, comprising:

a data storage facility to store restriction data in association with a phone number; 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 payment request identifying the phone number and a merchant, the common format processor determines whether to reject the payment request based at least in part on the restriction data and an identity of the merchant;

if the payment request is not rejected based on the determining, the common format processor uses one converter of the converters to communicate with a telephonic apparatus at the phone number to confirm the payment request; and

the common format processor transmits a notification to the merchant after confirmation of the payment request.

20. The system of claim 19, wherein the common format processor includes a decision engine to decide whether to reject the payment request based on whether the identity of the merchant is identified in the restriction data and whether an item to be purchased via the payment request is identified in the restriction data.