FRAUD MONITORING SYSTEM WITH DISTRIBUTED CACHE

• US 20140379561A1
• Filed: 01/23/2014
• Published: 12/25/2014
• Est. Priority Date: 06/25/2013
• Status: Active Grant

• Current Assignee: Quisk, Inc.
• Original Assignee: Quisk, Inc.
• Inventors: Amancherla, Praveen, Kartikeya, Kumar
• Granted Patent: US 9,519,902 B2
• Time in Patent Office: Days
• US Class Current: 705/39
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 13/4243 with synchronous protocol
• CPC Class Codes: G06F 16/24552 Database cache management
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06F 2201/80 Database-specific techniques
• CPC Class Codes: G06F 2201/82 Solving problems relating to consistency ensuring consistency in mirrored systems G06F11/2064
• CPC Class Codes: G06F 2212/254 Distributed memory
• 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 20/4016 involving fraud or risk level assessment in transaction processing
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

Systems and methods for fraud monitoring in a payment service are disclosed. An exemplary system includes a first server being located at a first locale and routing a first series of transaction requests. The system includes a second server being located at a second locale and routing a second series of transaction requests. The transactions requests may or may not be associated with a single payment service user account. The system includes a distributed cache storing a set of transaction details of the two series of transaction requests. The system includes a risk service having access to the set of transaction details from the distributed cache. The risk service generates a fraud warning based on a result of a comparison of at least one transaction detail in the set of transaction details and at least one transaction detail of a new transaction request received by the first server.

Claims

1. A system comprising:

a first server located at a first locale and routing a first series of transaction requests for a payment service;

a second server located at a second locale and routing a second series of transaction requests for said payment service;

a distributed cache storing a set of transaction details of said first and second series of transaction requests; and

a risk service operating at said first locale and having access to said set of transaction details from said distributed cache;

wherein said risk service generates a fraud warning based on a result of a comparison of at least one transaction detail in said set of transaction details and at least one transaction detail of a new transaction request received at said first server.

2. The system of claim 1, wherein:

said first and said second series of transaction requests comprise purchase transaction requests associated with a set of purchases made by a single account;

said set of transaction details include a cumulative amount of money spent in said set of purchases; and

said comparison compares a sum of said cumulative amount of money and a purchase amount of said new transaction against a predetermined amount.

3. The system of claim 1, further comprising:

a load balancer dividing a third series of transaction requests into said first and second series of transaction requests;

wherein said first server and said second server are both located in a single data center.

4. The system of claim 1, wherein:

said first and said second series of transaction requests comprise purchase transaction requests associated with a single account;

said set of transaction details include a geographical distance between a transaction in said second series of transactions and said new transaction; and

said risk service generates said fraud warning when said geographical distance is greater than a predetermined distance.

5. The system of claim 1, wherein said risk service is located in said distributed cache.

6. The system of claim 1, wherein said risk service comprises a set of configurable fraud monitoring rules.

7. The system of claim 6, wherein:

said first and said second series of transaction requests comprise purchase transaction requests for a set of purchases; and

said set of fraud monitoring rules vary based on an identity of a financial institution serving as a funding source for said purchases.

8. The system of claim 1, further comprising:

a reaper having access to said distributed cache;

wherein;

said set of transaction details include a time stamp of when a particular transaction in said first series of transaction requests was processed;

a subset of transaction details in said set of transaction details describe said particular transaction; and

when initiated, said reaper conducts a reaper process in which said subset of transaction details are cleared from said distributed cache if said time stamp indicates said particular transaction was processed more than a predetermined length of time in the past.

9. The system of claim 8, wherein:

said reaper is initiated according to a configurable reaper period defining how often said reaper process is initiated;

said predetermined length of time is a configurable reaper window; and

said configurable reaper period and said configurable reaper window vary based on an identity of a financial institution associated with said particular transaction.

10. The system of claim 8, wherein said reaper is located in said distributed cache.

11. A computer-implemented process comprising:

processing a first series of transaction requests at a first server;

processing a second series of transaction requests at a second server;

storing historical transaction information concerning transactions associated with said first and said second series of transaction requests in a distributed cache;

receiving a transaction request;

conducting a comparison of information regarding said transaction request with said historical transaction information; and

issuing a fraud warning based on results of said comparison;

wherein said first and said second series of transactions are associated with a single user account; and

wherein said first and second servers are in different locales.

12. The process of claim 11, further comprising:

processing said first and second series of transactions;

wherein said historical transaction information includes a cumulative amount of money expended via the processing of said first and second series of transaction requests.

13. The process of claim 11, wherein:

said historical transaction information includes a first geographical location of a transaction from said first series of transactions; and

said transaction request is received via said second server.

14. The process of claim 11, further comprising:

dividing a third series of transactions requests into said first and second series of transaction requests using a load balancer;

wherein said first server and said second server are both located in a single data center.

15. The system of claim 12, wherein said comparison is conducted using a risk service that is programmable to set fraud monitoring rules by a user.

16. The system of claim 14, wherein said fraud monitoring rules:

(i) are based on an identity of the user requesting a transaction, or (ii) are based on a financial institution administering a funding source involved in said transaction request.

17. The process of claim 11, further comprising:

setting a predetermined reaper period; and

initiating a reaper process when said reaper period has elapsed, said reaper process removing a portion of said historical transaction information from said distributed cache;

wherein said portion comprises historical transaction information that has been stored in said distributed cache for longer than a predetermined reaper window.

18. The process of claim 17, further comprising:

receiving a configuration message from a financial institution;

wherein said configuration message determines said predetermined reaper window; and

said portion consists of historical transaction information that has been stored in said distributed cache for longer than said predetermined reaper window and contains information regarding transactions that create an obligation for said financial institution to transfer or receive funds.

19. The process of claim 18, wherein said fraud warning comprises restricting said transaction.

20. A system comprising:

a first server located at a first locale and routing a first series of transaction requests for a payment service;

a second server located at a second locale and routing a second series of transaction requests for said payment service;

a distributed cache storing a set of transaction details of said first and said second series of transaction requests; and

a risk service having access to said set of transaction details from said distributed cache;

wherein said risk service generates a fraud warning based on a result of a comparison of at least one transaction detail in said set of transaction details and at least one transaction detail of a new transaction request received by said first server; and

wherein said first and second series of transaction requests are associated with a single payment service user account.