Method and apparatus for detecting and investigating fraudulent transactions in debit and charge card activations

• US 6,488,206 B1
• Filed: 10/20/2000
• Issued: 12/03/2002
• Est. Priority Date: 10/22/1999
• Status: Expired due to Term

• Current Assignee: Fidelity Information Services, LLC (Fidelity National Information Services Incorporated)
• Original Assignee: Efunds Corporation (Fidelity National Information Services Incorporated)
• Inventors: Clark, Robert T., Shea, Gary T., Flaig, Mark S., Wojak-Puranen, Sally A., Odishoo, George J.
• Primary Examiner(s): LE, THIEN MINH
• Application Number:
  US09/694,042
• Time in Patent Office: 774 Days
• Field of Search: 235/379, 235/375, 235/383, 235/381, 235/495, 235/449, 235/380, 379/265.01, 379/91.01, 379/93.03, 379/265, 379/266, 379/309, 379/113, 379/114
• US Class Current: 235/380
• CPC Class Codes: G06Q 20/341 Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
• CPC Class Codes: G07F 7/10 together with a coded signal , e.g. in the form of personal identification information, like personal identification number [PIN] or biometric data
• CPC Class Codes: G07F 7/1008 Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
• CPC Class Codes: G07F 7/1083 Counting of PIN attempts

Abstract

A method and apparatus for the detection and investigation of fraudulent debit and charge card activation transactions. Cardholder information on file is matched with information provided at activation time. Where matching does not occur, fraud is a possibility. All activation activity is captured and summarized. Absolute failures are highlighted. Subsequent fraudulent use of fraudulently activated cards can be investigated resulting in possible identification of the alleged fraudulent card user.

Claims

1. A method of activating a payment card, the method comprising

creating a cardholder record based on information from a cardholder application, the cardholder record including card identity and cardholder information;

receiving a card activation request;

starting a session and issuing a first query in response to the activation request;

receiving card identity information in response to issuing a first query;

starting a card identity information attempt tracking mechanism;

verifying the validity of the card identity information;

reissuing the first query if the card identity information is invalid and a limit of the card identity tracking mechanism has not been exceeded;

issuing an error message and ending the session if a limit of the card identity tracking mechanism has been exceeded; and

if the card identity information is valid

issuing a second query requesting cardholder information;

starting a cardholder information attempt tracking mechanism;

verifying the validity of the cardholder information;

reissuing the second query if the cardholder information is invalid and a limit of the cardholder information attempt tracking mechanism has not been exceeded; and

issuing an error message and ending the session if the limit of the cardholder information tracking mechanism has been exceeded; and

if the cardholder information is valid, issuing a card activation message.

2. A method as claimed in claim 1, further comprising

starting a session tracking mechanism;

issuing an error message and ending the session if a limit of the session tracking session has been exceeded.

3. A method as claimed in claim 1, further comprising logging a first message if the card identity information is valid.

4. A method as claimed in claim 1, further comprising logging a second message if the card identity information is invalid or the limit of the card identity tracking mechanism has been exceeded.

5. A method as claimed in claim 4, further comprising logging a third message if the cardholder information is valid.

6. A method as claimed in claim 5, further comprising logging a fourth message if the cardholder information is invalid.

7. A method as claimed in claim 6, further comprising logging a fifth message if a limit of the cardholder information attempt tracking mechanism has been exceeded.

8. A method as claimed in claim 7, further comprising generating a report based on one or more of the first through fifth messages.

9. A method as claimed in claim 1, further comprising:

before issuing a second query, querying a database;

determining whether the card identity information matches an entry in the database;

logging a match message if the card identity information matches an entry in the database; and

if the card identity information does not match an entry in the database logging a non-match message.

10. A method of capturing card activation activity, the method comprising

receiving a card activation request;

starting a session, incrementing a session tracking mechanism; and

issuing a first query in response to the activation request;

issuing an error message and ending the session if a limit of the session tracking mechanism has been exceeded;

receiving card identity information in response to issuing a first query;

starting a card identity information attempt tracking mechanism;

verifying the validity of the card identity information;

logging a message if the card identity information is invalid;

reissuing the first query if the card identity information is invalid and a limit of the card identity tracking mechanism has not been exceeded;

issuing an error message, logging a second message, and ending the session if a limit of the card identity tracking mechanism has been exceeded; and

if the card identity information is valid

logging a third message;

issuing a second query;

starting a cardholder information attempt tracking mechanism;

verifying the validity of the cardholder information;

logging a fourth message and reissuing the second query if the cardholder information is invalid and a limit of the cardholder information attempt tracking mechanism has not been exceeded; and

logging a fifth message, issuing an error message, and ending the session if the limit of the cardholder information tracking mechanism has been exceeded.

11. A method as claimed in claim 10, further comprising logging a sixth message if the cardholder information is valid.

12. A payment card activation system comprising:

a network;

a cardholder terminal coupled to the network; and

a call center coupled to the network, the call center having

a report generation unit,

a response unit,

a cardholder database,

a set of validation rules, and

a database of logged messages, each message representing a card activation activity,

wherein the report generation unit is operable to generate a report including information based on one or more of the logged messages in the database of logged messages.

13. A system as claimed in claim 12, wherein the cardholder database includes one or more records, each record including an account number, a card number, a cardholder name, and security information.

14. A system as claimed in claim 12, wherein the network is a packet-switched network.

15. A system as claimed in claim 14, wherein the call center includes a web site.

16. A system as claimed in claim 15, wherein the cardholder terminal is an Internet appliance.

17. A system as claimed in claim 12, wherein the network is a circuit-switched network.

18. A system as claimed in claim 17, wherein the cardholder terminal is a telephone.

19. A system as claimed in claim 12, wherein the set of validation rules are set for groups of cards at a bank identification number level.

20. A payment card activation report generation system comprising

a response unit programmed to respond to an inquiry, generate card activation queries, and log messages based on responses to the queries;

a database of logged messages, each message representing a card activation activity;

a cardholder database;

a set of validation rules; and

a report generation unit programmed to sort the database of logged messages by card issuer and to generate a report including information based on one or more of the logged messages in the database of logged messages.

21. A system as claimed in claim 20, wherein the cardholder database includes one or more records, each record including an account number, a card number, a cardholder name, and security information.

22. A system as claimed in claim 21, wherein the queries generated by the response unit are based on the records in the cardholder database.

23. A system as claimed in claim 20, wherein the set of validation rules are set for groups of cards at a bank identification number level.

24. A payment card activation report comprising:

a card issue name block having a name of a card issuer;

card number and cardholder name information;

an account number;

a session number representing the number of times a purported cardholder has attempted to activate a particular card;

a purported cardholder identifier;

an indication of activation criteria;

an indication of activation status;

an indication of an agent processing an activation attempt; and

an eye catcher that indicates a failed card activation.

25. A report as claimed in claim 24, further comprising a coverage period block that includes the date of entries in the report, the run date of the report, and the run time of the report.

26. A report as claimed in claim 24, further comprising a date and a time of an activity listed in the report.

27. A report as claimed in claim 24 further comprising identifying data submitted by a purported cardholder.

28. A report as claimed in claim 24, further comprising an indication representing whether a request for card activation made by a purported cardholder was transferred to a human being for processing.

29. A method of monitoring card activation activity, the method comprising

logging activity of a purported cardholder in activating a payment card, where the impetus of activity is one or more queries generated by a response unit;

creating a report from the logged activity; and

reviewing the report for indications of failed activation, erroneous responses to queries, or both.

30. A method as claimed in claim 29, further comprising reviewing the report for activation failure eye catchers.

31. A method as claimed in claim 29, further comprising reviewing a number of sessions amount in the report.

32. A method as claimed in claim 29, further comprising:

creating a database of actual cardholders;

reviewing the report for an indication of activation success;

determining a card associated with the activation success;

contacting the actual cardholder of the card; and

determining whether the actual cardholder is aware that the card has been activated.

33. A method as claimed in claim 32, further comprising

determining identifying information of a purported cardholder associated with the activation success;

and

contacting the purported cardholder if the actual cardholder is unaware that the card has been activated.