In-application commerce system and method with fraud prevention, management and control

• US 9,785,988 B2
• Filed: 11/23/2011
• Issued: 10/10/2017
• Est. Priority Date: 11/24/2010
• Status: Active Grant

• Current Assignee: Digital River Incorporated (Danube Private Holdings II, LLC)
• Original Assignee: Digital River Incorporated (Danube Private Holdings II, LLC)
• Inventors: Petri, Daniel, Kohout, Georg, Nader, Georg, Mayerhofer, Martin
• Primary Examiner(s): Civan, Ethan D
• Application Number:
  US13/304,191
• Publication Number:
  US 20120130853A1
• Time in Patent Office: 2,148 Days
• Field of Search: 705 261- 272
• CPC Class Codes: G06Q 30/0609 Buyer or seller confidence or verification

Abstract

A full-service turn-key in-application commerce solution with fraud detection is disclosed that provides web service interfaces to a commerce system. The in-application solution features fraud detection with user behavior tracking and fraud controls that limit the features that are offered to a user. Fraud detection involves input from the application, the commerce system, or third party systems. User fraud scores are updated frequently as events are processed. Controls are applied to the user account based on the user fraud score and risk classifications for ranges of fraud scores. An in-application solution also features a wallet with a personal threshold for microtransaction spending, limiting the amount that the user is allowed to spend before a wallet is cleared. The wallet is integrated with the fraud detection such that the personal threshold is determined from the user'"'"'s latest fraud score.

Claims

1. An in-application fraud prevention, management and control system comprising:

a web application server comprising a network communication device, a processor and a memory, the memory having executable instructions stored thereon and executed by the processor, the executable instructions configured to access a database of administrator-defined and configured user behavior events specific to an internet-accessible on-line application and indicating fraudulent behavior, the executable instructions further configured to allow a user to access and interact with the internet-accessible on-line application stored in memory while the system performs user behavior tracking for the configured events;

an e-commerce transaction server providing in-application purchasing, operatively connected to the web application server through the network communication device, comprising a processor and a memory and further comprising;

an account management module containing program code stored in memory which when executed by the processor in the e-commerce transaction server causes the e-commerce transaction server to perform the operations of managing a user account, the user account comprising a fraud score which is a sum of fraud points or a user wallet with a personal threshold for making in-application purchases;

a communications module containing program code stored in memory which when executed by the processor in the e-commerce transaction server causes the e-commerce transaction server to receive event messages from third party systems comprising offer companies, payment providers or technology firms or other applications with which the user'"'"'s user wallet has been integrated;

from the on-line application; and

from within the e-commerce system;

a fraud defender module containing program code stored in memory which when executed by the processor in the e-commerce transaction server causes the e-commerce transaction server to perform a method of;

determining a risk classification applicable to the user;

assigning positive or negative fraud points based on customer-specified, configurable rules defining the events to utilize in generating a fraud score, the rules stored in a fraud database and applied to the event messages received at the communications module via batch and messaging frameworks and associated with particular user behavior occurring in the on-line application, third party systems with which the user wallet has been integrated, or from within the e-commerce system;

updating the fraud score for the user account based on the assigned fraud points in near real time; and

applying application fraud controls in near real time to limit the features available to users within the risk classification, for subsequent user transactions, in response to the updated fraud score and the risk classification, the controls applied to at least one of the following application features available to the user;

(i) offers, (ii) allowed payment types and (iii) reverse wallet thresholds, the application fraud controls changable in near real time as the user interacts with the internet-accessible on-line application.

2. The in-application fraud prevention, management and control system of claim 1 wherein the internet-accessible on-line application comprises a game application and wherein event messages received at the communications module comprise at least game play and game commerce events.

3. The in-application fraud prevention, management and control system of claim 1 wherein the particular user behavior occurring in the internet-accessible on-line application comprises adding a new friend within the on-line application such that one of the fraud events comprises assigning negative fraud points to the user account when a received event message indicates that a new friend was added within the on-line application.

4. The in-application fraud prevention, management and control system of claim 1 wherein the particular user behavior occurring in the internet-accessible on-line application comprises accumulated actions over time within the internet-accessible on-line application such that one of the fraud events comprises assigning negative fraud points to the user account when a received event message indicates that the particular user has accumulated actions over time within the internet-accessible on-line application.

5. The in-application fraud prevention, management and control system of claim 1 wherein the particular user behavior occurring in the internet-accessible on-line application comprises a past suspension from the internet-accessible on-line application such that one of the fraud events comprises assigning negative fraud points to the user account when a received event message indicates that a reactivated user was previously suspended from the internet-accessible on-line application.

6. The in-application fraud prevention, management and control system of claim 1 wherein the particular user behavior occurring in the internet-accessible on-line application comprises a suspension from the internet-accessible on-line application such that one of the fraud events comprises assigning positive fraud points to the user account when a received event message indicates that a user was suspended from the internet-accessible on-line application.

7. The in-application fraud prevention, management and control system of claim 1 wherein the particular user behavior occurring in the internet-accessible on-line application comprises a disputes to total purchases ratio such that one of the fraud events comprises assigning positive fraud points to the user account when a received event message indicates that a user has dispute to total purchases ratio that indicates a higher risk than other users of the internet-accessible on-line application.

8. The in-application fraud prevention, management and control system of claim 1 wherein the particular user behavior occurring in the internet-accessible on-line application comprises a chargebacks to disputes ratio such that one of the fraud events comprises assigning positive fraud points to the user account when a received event message indicates that a user has a chargebacks to dispute ratio that indicates a higher risk than other users of the internet-accessible on-line application.

9. The in-application fraud prevention, management and control system of claim 1 wherein the fraud defender module contains program code stored in memory which when executed by the processor in the server causes the server to assign negative fraud points to the user account when a commerce event indicates a successful transaction occurring in the wallet.

10. The in-application fraud prevention, management and control system of claim 1 wherein the fraud defender module contains program code stored in memory which when executed by the processor in the server causes the server to:

(i) receive a third party payment partners error response associated with a transaction on the user account and (ii) assign fraud points to the user account based on the received error response.

11. The in-application fraud prevention, management and control system of claim 1 wherein the fraud defender module contains program code stored in memory which when executed by the processor in the server causes the server to assign a particular risk class to the user account based on the fraud score and to limit the user account based on the assigned risk class to a limited number of particular payment forms.

12. The in-application fraud prevention, management and control system of claim 1 wherein the fraud defender module contains program code stored in memory which when executed by the processor in the server causes the server to assign a particular risk class to the user account based on the fraud score and to limit the user account based on the assigned risk class to a particular user role.

13. The in-application e-commerce system of claim 1 wherein the user account further comprises a wallet with a personal threshold for spending that the user is allowed to spend in advance before the system clears the wallet and wherein the fraud defender module contains program code stored in memory which when executed by the processor in the server causes the server to update the personal threshold based on changes to the fraud score for the user account.

14. The in-application e-commerce system of claim 13 further comprising a wallet module containing program code stored in memory which when executed by the processor in the server causes the server to:

(i) receive a transaction request with an amount for a micropayment on a shopper order in the in-application e-commerce system, and (ii) debit the wallet based on a determining that the received transaction request amount is below the personal threshold.

15. The in-application e-commerce system of claim 13 further comprising a wallet module containing program code stored in memory which when executed by the processor in the server causes the server to:

(i) receive a transaction request with an amount for a micropayment on a shopper order in the in-application e-commerce system, and (ii) notify the user that the personal threshold would be exceeded based on a determining that the received transaction request amount is above the personal threshold.

16. The in-application e-commerce system of claim 15 wherein the wallet module contains program code stored in memory which when executed by the processor in the server causes the server to load the wallet with an amount that exceeds the personal threshold based upon the user responding to a notification that the personal threshold would be exceeded.

17. The in-application e-commerce system of claim 13 further comprising a wallet module containing program code stored in memory which when executed by the processor in the server causes the server to clear the wallet once spending in the wallet has exceeded the personal threshold.

18. The in-application e-commerce system of claim 1 further comprising updating the risk classification applicable to the user in near real time as the user interacts with the internet-accessible on-line application in response to events communicated by the communications.

19. A method for managing the risk of fraudulent transactions performed by users of an internet application stored and processed on a web application server, the internet application operatively connected to an in-application e-commerce system transaction server and third-party systems, the method comprising steps of:

maintaining a user account in the e-commerce system transaction server, the user account comprising a wallet for making in-application purchases and a fraud score which is a sum of fraud points;

receiving event messages through the network, wherein event messages related to user behavior tracked as the user interacts with the internet application, from the internet application, third-party systems with which the user'"'"'s wallet is integrated, or the in-application e-commerce system for a user associated with the user account;

assigning positive or negative fraud points based on the received event messages associated with particular user behavior occurring in the internet application, third-party systems or the in-application e-commerce system;

updating the fraud score for the user account based the assigned fraud points in near real time;

determining a risk classification based on the assigned fraud points; and

applying fraud controls in near real time to limit the features of the internet application available to users within a risk classification, for the user'"'"'s subsequent interaction with the internet application based on the user'"'"'s updated fraud score and risk classification, where the controls are applied to at least one of the following features available to the user;

(i) offers, (ii) allowed payment types and (iii) reverse wallet thresholds, the fraud controls changable in near real time as the user interacts with the internet application.

20. The method of claim 19 wherein the particular user behavior occurring in the internet application comprises adding a new friend within the on-line application and wherein the assigning step comprises assigning negative fraud points to the user account when a received event message indicates that a new friend was added within the internet application.

21. The method of claim 19 wherein the particular user behavior occurring in the internet application comprises accumulated actions over time within the internet application and wherein the assigning step comprises assigning negative fraud points to the user account when a received event message indicates that the particular user has accumulated actions over time within the internet application.

22. The method of claim 19 wherein the particular user behavior occurring in the internet application comprises a past suspension from the internet application and wherein the assigning step comprises assigning negative fraud points to the user account when a received event message indicates that a reactivated user was previously suspended from the internet application.

23. The method of claim 19 wherein the particular user behavior occurring in the internet application comprises a suspension from the internet application and wherein the assigning step comprises assigning positive fraud points to the user account when a received event message indicates that a user was suspended from the internet application.

24. The method of claim 19 wherein the particular user behavior occurring in the internet application comprises a disputes to total purchases ratio and wherein the assigning step comprises assigning positive fraud points to the user account when a received event message indicates that a user has dispute to total purchases ratio that indicates a higher risk than other users of the internet application.

25. The method of claim 19 wherein the particular user behavior occurring in the internet application comprises a chargebacks to disputes ratio and wherein the assigning step comprises assigning positive fraud points to the user account when a received event message indicates that a user has a chargebacks to dispute ratio that indicates a higher risk than other users of the internet application.

26. The method of claim 19 the user account further comprises a wallet and wherein the assigning step comprises assigning negative fraud points to the user account when a commerce event indicates a successful transaction occurs in the wallet.

27. The method of claim 19 the user account further comprising a step of receiving a third party payment partners error response associated with a transaction on the user account and wherein the assigning step comprises assigning negative fraud points to the user account based on the received error response.

28. The method of claim 19 the user account further comprising a step of assigning a particular risk class to the user account based on the fraud score.

29. The method of claim 28 the user account further comprising a step of limiting the user account based on the assigned risk class to a limited number of particular payment forms.

30. The method of claim 28 the user account further comprising a step of limiting the user account based on the assigned risk class to a particular user role.

31. The method of claim 28 the user account further comprising a step of limiting the user account based on the assigned risk class to one of:

wallet transaction limits, particular storefront offers, and particular content available in the internet application.

32. The method of claim 19 wherein the user account further comprises a wallet with a personal threshold for spending that the user is allowed to spend in advance before the system clears the wallet and further comprising a step of updating the personal threshold based on changes to the fraud score for the user account.

33. The method of claim 32 further comprising steps of:

receiving a transaction request with an amount for a micropayment on a shopper order in the in-application e-commerce system; and

debiting the wallet based on a determining that the received transaction request amount is below the personal threshold.

34. The method of claim 32 further comprising steps of:

receiving a transaction request with an amount for a micropayment on a shopper order in the in-application e-commerce system; and

notifying the user that the personal threshold would be exceeded based on a determining that the received transaction request amount is above the personal threshold.

35. The method of claim 34 further comprising a step of loading the wallet with an amount that exceeds the personal threshold based upon the user responding to a notification that the personal threshold would be exceeded.

36. The method of claim 32 further comprising a step of clearing the wallet once spending in the wallet has exceeded the personal threshold.