SYSTEMS AND METHODS FOR IDENTIFYING POTENTIALLY FRAUDULENT FINANCIAL TRANSACTIONS AND COMPULSIVE SPENDING BEHAVIOR

• US 20080040275A1
• Filed: 12/12/2006
• Published: 02/14/2008
• Est. Priority Date: 04/25/2006
• Status: Abandoned Application

• Current Assignee: Baker Tilly, Trust Payments Ltd. (Trust Payments Holdings Ltd.)
• Original Assignee: UC Group Ltd.
• Inventors: Hughes, Ian, Holland, Mark, Paulsen, Kobus
• Application Number:
  US11/609,785
• Publication Number:
  US 20080040275A1
• Time in Patent Office: Days
• US Class Current: 705/44
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 30/00 Commerce
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/04 Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Abstract

Various embodiments of the invention provide a more secure financial transaction system for e-commerce sectors that (1) more securely processes payment transactions, (2) helps to protect merchants and banks against fraudulent transactions, money laundering, and underage gambling, and (3) helps to limit other abuses in areas of e-commerce that are perceived to pose special risks, such as Internet gaming, travel, and consumer purchasing of electronic goods. To accomplish the above goals, various embodiments of the financial transaction system (1) establish operating and transaction processing protocols for merchants, Internet payment service providers, acquiring banks, and card schemes and (2) provide automated systems for monitoring and securely processing payment and financial transactions.

Claims

1. A fraud prevention system for identifying potentially fraudulent online financial transactions received from a customer for an online merchant, the system comprising a fraud prevention module configured for:

applying one or more fraud filters to each of one or more financial transactions received from one or more customers, the one or more fraud filters being selected from one or more of the following;

(1) comparing a first location associated with a customer account with a second location associated with a customer computing device used to transmit the financial transaction to the online merchant, and in response to the first location being outside of a first predetermined acceptable distance of the second location, marking the financial transaction as potentially fraudulent;

(2) comparing a fourth location associated with a customer billing address for the customer account with the second location, and in response to the fourth location being outside of a third predetermined acceptable distance of the second location, marking the financial transaction as potentially fraudulent;

(3) comparing a customer identification with a list of individuals prohibited from conducting financial transactions, and in response to the customer identification matching one of the individuals on the list, marking the financial transaction as potentially fraudulent;

or

(4) comparing an identification of a customer account with a list of accounts prohibited from conducting financial transactions, and in response to the identification of the customer account matching one of the accounts on the list, marking the financial transaction as potentially fraudulent; and

in response to the financial transaction being marked as potentially fraudulent, storing information associated with the financial transaction in a fraud database.

2. The system of claim 1 wherein the one or more fraud filters further includes:

comparing a third location associated with a customer email address with the second location, and in response to the third location being outside of a second predetermined acceptable distance of the second location, marking the financial transaction as potentially fraudulent.

3. The system of claim 1 wherein the one or more fraud filters further includes:

comparing information associated with one or more subsequent financial transactions to the financial transactions stored in the fraud database, and in response to the customer account, customer identification, or customer billing address of each of the one or more subsequent financial transactions matching any of the financial transactions stored in the fraud database, marking the one or more subsequent financial transactions as potentially fraudulent.

4. The system of claim 1 wherein the one or more fraud filters further includes:

comparing the first location with the third location, and in response to the first location being outside of a first predetermined acceptable distance of the third location, marking the financial transaction as potentially fraudulent.

5. The system of claim 1 wherein the second location comprises a country, and the one or more fraud filters further includes:

comparing the second location with a list of countries that are prohibited from conducting financial transactions with the merchant, and in response to the second location being on the list of countries, preventing the financial transaction from being conducted.

6. The system of claim 1 wherein the list of accounts prohibited from conducting financial transactions is a list of stolen accounts.

7. The system of claim 1 wherein the first location is a location associated with a financial institution that manages the customer account.

8. The system of claim 1 wherein the first location is a billing address associated with the customer account.

9. The system of claim 1 wherein the first location, the second location, the third location, and the fourth location are selected from one or more of a country, a region, a state, a locality, a county, a city, or a postal district defined by one or more postal codes.

10. The system of claim 1 wherein the list of individuals is published by a government authority.

11. The system of claim 1 wherein the list of accounts is published by a government authority.

12. The system of claim 1 wherein:

the payment service provider module is further configured for receiving a payback request for the customer; and

the fraud prevention module is further configured for comparing an identity of the customer requesting the payback to a list of officers, directors, or owners associated with the online merchant, and in response to the customer being on the list of directors, officers, or owners, marking the payback request as potentially fraudulent.

13. The system of claim 1 wherein the financial transaction is a gambling payout request and the fraud prevention module is further configured for comparing an identification of an account named by the customer for receiving a payout from the merchant with an identification of an account used by the customer to place bets with the merchant, and in response to the identification of the account named for receiving the payout not matching the identification of the account used to place bets with the merchant, marking the payout request as potentially fraudulent.

14. The system of claim 13 wherein the fraud prevention module is further configured for preventing a payout amount provided in the payout request from being transferred to the account named for receiving the payout.

15. The system of claim 13 wherein the account named for receiving the payout request is associated with a first payment card and the account used to place bets with the merchant is associated with a second payment card, and the fraud prevention module is further configured for comparing the first payment card to the second payment card, and in response to the first payment card not matching the second payment card, marking the payout request as potentially fraudulent.

16. The system of claim 1 wherein the one or more fraud filters are selected based on the location of the merchant.

17. The system of claim 1 wherein the one or more fraud filters are selected based on the second location.

18. The system of claim 1 wherein the one or more fraud filters are selected based on the first location.

19. A system for monitoring a compulsive spending behavior of a customer, said system comprising a processor and a memory, said processor configured for:

storing, in the memory, information associated with each of one or more requests from the customer to conduct financial transactions with a merchant, the information comprising an amount of funds;

receiving a new request to conduct a financial transaction with the merchant, the request comprising an amount of funds;

in response to receiving the new request, retrieving a total amount of funds stored in the memory;

comparing a sum of the total amount of funds and the amount of funds in the new request with a pre-determined acceptable limit; and

in response to the sum exceeding the pre-determined acceptable limit, notifying one or more of the customer, a payment source associated with the customer, or the merchant that the pre-determined acceptable limit has been exceeded.

20. The system of claim 19 wherein the information stored in the memory further comprises a date on which each request was received by the merchant;

and wherein the processor is further configured for comparing the sum of the total amount of funds stored in the memory within a particular time period and the amount of funds in the new request with the pre-determined acceptable limit.

21. A system for monitoring a compulsive gambling behavior of a customer, said system comprising a processor and a memory, said processor configured for:

storing, in the memory, information associated with each of one or more requests from the customer to conduct a financial transaction with the merchant, the information comprising an amount of funds and a type of financial transaction;

receiving a new request to conduct a financial transaction with the merchant, the request comprising an amount of funds and a type of financial transaction;

in response to receiving the new request, retrieving a total amount of funds stored in the memory for the type of financial transaction in the new request;

comparing a sum of the total amount of funds and the amount of funds in the new request with a pre-determined acceptable limit associated with the type of financial transaction in the new request; and

in response to the sum exceeding the pre-determined acceptable limit, notifying one or more of the customer, a payment source associated with the customer, or the merchant that the pre-determined acceptable limit has been exceeded.

22. The system of claim 21 wherein the type of transaction is a request to transfer funds to the merchant from an account associated with the customer.

23. The system of claim 21 wherein the type of transaction is a request to place a bet using funds previously transferred to the merchant.

24. The system of claim 21 wherein the one or more requests and the new request are received by a computing device associated with the merchant from one or more computing devices associated with the customer over a network.

25. The system of claim 21 wherein the processor is further configured for preventing the new request from being processed in response to the sum exceeding the pre-determined acceptable limit.

26. The system of claim 21 wherein the information stored in the memory further comprises a date on which the request was received by the merchant;

and wherein the processor is further configured for comparing the sum of the total amount of funds requested by the customer within a particular time period and the amount of funds in the new request with the pre-determined acceptable limit.

27. A system for monitoring a compulsive spending behavior of a customer, said system comprising a processor and a memory, said processor configured for:

storing, in the memory, information associated with each of one or more requests from the customer to transfer funds to the merchant and a date on which the request was received by the merchant;

receiving a new request to transfer funds to the merchant;

in response to receiving the new request, retrieving a total number of transactions stored in the memory within a particular time period;

comparing the total number of transactions with a pre-determined acceptable limit; and

in response to the total number of transactions exceeding the pre-determined acceptable limit, notifying one or more of the customer, a payment source associated with the customer, or the merchant that the limit has been exceeded.