Electronic payment and authentication system with debit and identification data verification and electronic check capabilities

• US 7,752,132 B2
• Filed: 02/25/2002
• Issued: 07/06/2010
• Est. Priority Date: 02/23/2001
• Status: Active Grant

• Current Assignee: Fidelity Information Services, LLC (Fidelity National Information Services Incorporated)
• Original Assignee: Efunds Corporation (Fidelity National Information Services Incorporated)
• Inventors: Gallmeier, Brian John, Crews, Teresa Marie, Hill, Robert Lawrence, Nipe, Mark Andrew, Haire, James Michael, Petersen, Matthew Lacey, Stewart, Whitney Hilton, Bates, Michael Richard
• Primary Examiner(s): Colbert; Ella
• Assistant Examiner(s): Tran; Hai
• Application Number:
  US10/082,677
• Publication Number:
  US 20020120846A1
• Time in Patent Office: 3,053 Days
• Field of Search: 705/40, 705/35, 705/38, 705/39, 705/42, 705/44
• US Class Current: 705/40
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/0425 the cheque being electronic only
• CPC Class Codes: G06Q 20/085 involving remote charge determination or related payment systems
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/108 Remote banking, e.g. home banking
• CPC Class Codes: G06Q 20/28 Pre-payment schemes, e.g. "pay before"
• 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/401 Transaction verification
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/03 Credit; Loans; Processing thereof

Abstract

An electronic payment and authentication system that includes features to verify the authenticity of a payer, validate debit data, and facilitate debit (as opposed to credit) payment transactions. The electronic payment system allows a consumer to purchase items and services via a network while utilizing a debit transaction. The invention provides merchants with the ability to verify the identity of the consumer, determine if the consumer is a good debit transaction risk, and retrieve debit data associated with a particular consumer.

Claims

1. A computer-implemented debit data validation system for a network, the system comprising:

a calling application configured on a computer to receive a request to validate debit data from a merchant, and to receive transactional debit data to be validated;

a debit data search engine including a keying module configured on a computer to perform a keying process and a matching module configured on a computer to perform a matching process, the debit data search engine being configured on a computer to receive the transactional debit data from the calling application, and to process the transactional debit data to identify a consumer key, the consumer key being based on at least a portion of the transactional debit data; and

a debit data warehouse including stored debit data, the debit data warehouse being configured on a computer to retrieve the stored debit data associated with the consumer key, the stored debit data being representative of at least one consumer, and the consumer key being configured on a computer to link the stored debit data gathered from a plurality of data sources;

the calling application being further configured on a computer to process the stored debit data, to determine whether to allow the debit transaction, and to generate a response message to the merchant with the determination.

2. A system as claimed in claim 1, wherein the keying process includes a standardization component, a validation component, and a matching component.

3. A system as claimed in claim 2, further comprising a converter adapted to be coupled to at least one of the debit data search engine and the debit data warehouse, wherein the converter is coupled to at least one data source, and further wherein the at least one data source includes raw debit data representative of the at least one consumer.

4. A system as claimed in claim 3, wherein the converter performs parsing of the raw debit data, wherein parsing includes breaking a single data field into a number of representative data fields.

5. A system as claimed in claim 3, wherein the converter performs bursting of the raw debit data, wherein bursting includes separating a joint account name into at least two representative names.

6. A system as claimed in claim 3, wherein the converter includes a geographic coder adapted to correct at least one of a street name, a city, a state, a zip code.

7. A system as claimed in claim 3, wherein the raw debit data includes data from at least one of a checking account opening, a checking account closing, a savings account opening, a savings account closing, a checking account collection, an overdraft, a check order, a returned check transaction, a check printing order, an account inquiry, a retail transaction, an ATM transaction, an automated clearinghouse transaction, and an Internet transaction.

8. A system as claimed in claim 3, wherein the raw debit data includes attributes associated with the at least one consumer, and further wherein the attributes include at least one of a name, an address, a SSN, a driver'"'"'s license number, a driver'"'"'s license state, a bank account number, a home phone number, a work phone number, and an MICR.

9. A system as claimed in claim 8, wherein the raw debit data from the at least one data source is utilized only if it includes at least two of the attributes.

10. A system as claimed in claim 2, wherein the at least one data source includes raw debit data representative of the at least one consumer, and wherein the standardization component standardizes the raw debit data into a consistent format.

11. A system as claimed in claim 2, wherein the at least one data source includes raw debit data representative of the at least one consumer, and wherein the validation component checks the raw debit data against existing reference files to detect at least one of bad data and incorrect data.

12. A system as claimed in claim 2, wherein the at least one data source includes raw debit data representative of the at least one consumer, and wherein the matching component matches the raw debit data against the stored debit data to determine one of a first condition and a second condition, wherein the first condition is a match between the raw debit data and the stored debit data, and further wherein the second condition is no match between the raw debit data and the stored debit data.

13. A system as claimed in claim 12, wherein the raw debit data is linked to the stored debit data and thereby becomes stored debit data when the first condition is determined.

14. A system as claimed in claim 12, wherein the stored debit data and the raw debit data are representative of the same at least one consumer when the first condition is determined.

15. A system as claimed in claim 12, wherein the raw debit data is stored in the debit data warehouse and is not linked to the stored debit data and thereby becomes stored debit data not linked to existing stored debit data when the second condition is determined.

16. A system as claimed in claim 12, wherein the stored debit data and the raw debit data are not representative of the same at least one consumer when the second condition is determined.

17. A system as claimed in claim 1, wherein the at least one consumer key is thirteen bytes long with the first three bytes including a partitioning key, wherein the partitioning key determines the physical partition the stored debit data the at least one consumer key is representative of is located in.

18. A system as claimed in claim 1, wherein the at least one consumer key is identified by at least one of a name and an address.

19. A system as claimed in claim 1, wherein the matching process includes a standardization component, a validation component, and a matching component.

20. A system as claimed in claim 19, wherein the standardization component standardizes the transactional debit data into a consistent format.

21. A system as claimed in claim 19, wherein the validation component checks the transactional debit data against existing reference files to detect at least one of bad data and incorrect data.

22. A system as claimed in claim 19, wherein the matching component matches the transactional debit data against the stored debit data to determine one of a first condition and a second condition, wherein the first condition is a match between the transactional debit data and the stored debit data, and further wherein the second condition is no match between the transactional debit data and the stored debit data.

23. A system as claimed in claim 22, wherein the matching component matches the transactional debit data against the stored debit data to determine one of a first condition and a second condition using at least one matching search, and further wherein the at least one matching search include at least one of a name/address search, a name/previous address search, a name/driver'"'"'s license number search, a name/phone search, a name/MICR search, a MICR/phone search, and a MICR/address search.

24. A system as claimed in claim 23, wherein the matching module is configured on a computer to generate an order of matching searches performed when at least two matching searches are performed.

25. A system as claimed in claim 23, wherein the at least one matching search is performed using a fuzzy matching process.

26. A system as claimed in claim 23, wherein the at least one matching search is performed using a hardkey matching process.

27. A system as claimed in claim 22, wherein the calling application is further configured to receive the at least one consumer key representative of the consumer the stored debit data the transactional debit data was matched to is representative of when the first condition is determined.

28. A system as claimed in claim 22, wherein the calling application is configured on a computer to receive the stored debit data the transactional debit data was matched to when the second condition is determined.

29. A system as claimed in claim 1, wherein the consumer key is configured on a computer to represent a debit worthiness of the at least one consumer.

30. A system as claimed in claim 2, wherein the keying module is configured on a computer to perform the keying process every time debit data is acquired from a data source.

31. A system as claimed in claim 19, wherein the matching module is configured on a computer to generate an order of matching searches performed when at least two matching searches are performed.

32. A system as claimed in claim 31, wherein the order of matching searches is defined in the request to validate debit data.

33. A computer-implemented method of conducting a debit data validation of a consumer involved in a debit transaction, the method comprising:

receiving a request from a merchant to validate debit data of the consumer involved in a debit transaction;

receiving transactional debit data that is to be validated;

on a computer, retrieving a consumer key based on at least a portion of the transactional debit data, the consumer key linking debit data from a plurality of data sources;

on a computer, analyzing the debit data associated with the consumer key; and

on a computer, generating a response message to the merchant, the response message being indicative of one of a first condition and a second condition, the first condition being a validation of the debit data, and the second condition being a lack of validation of the debit data of the consumer.