GENERATING INTEGRATED DATA RECORDS BY CORRELATING SOURCE DATA RECORDS FROM DISPARATE DATA SOURCES

• US 20170053357A1
• Filed: 09/11/2015
• Published: 02/23/2017
• Est. Priority Date: 08/18/2015
• Status: Active Grant

• Current Assignee: Fiserv Incorporated
• Original Assignee: Fiserv Incorporated
• Inventors: Ruhe, Timothy Allen, Bowman, Mark Edward, Gupta, Vikram, Schroder, Phillip Andrew, Smelker, Gregory David, Sunderji, Amirali, Lawson, Mary Elizabeth
• Granted Patent: US 10,459,935 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2471 Distributed queries
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06Q 20/22 Payment schemes or models
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

Systems, methods and computer-readable media are disclosed for generating integrated data records by correlating source data records stored at different registry source data repositories. A set of source data records is retrieved based on execution of one or more search queries against a set of registry source data repositories. A data record matching rule is selected for execution on the set of source data records. The matching rule specifies one or more input properties, each of which specifies at least one data field designator, and optionally, a matching algorithm and an input property match threshold value. The matching rule is executed on pairwise combinations of source data records to obtain a set of matched source data records. An integrated data record is generated and populated with respective data from each of one or more of the matched source data records. The integrated data record is linked to each source record.

Claims

1. A system, comprising:

at least one memory storing computer-executable instructions; and

at least one processor operatively coupled to the at least one memory and configured to execute the computer-executable instructions to;

determine a first source data record populated with first data associated with an entity, wherein the entity is a payor or a payee of a financial transaction, and wherein the first source data record is stored in a first source data repository associated with a first payment system;

determine a second source data record populated with second data associated with the entity, wherein the second source data record is stored in a second source data repository not associated with the first payment system, and wherein the first source data record does not include the second data;

select a data record matching rule that is eligible for execution on the first source data record and second source data record;

determine that the data record matching rule specifies an input property, a matching algorithm corresponding to the input property, and a rule match threshold value;

execute the data record matching rule on the first source data record and the second source data record, wherein executing the data record matching rule comprises executing the matching algorithm to obtain a result value;

determine an input property match confidence value associated with the input property based at least in part on the result value;

determine a final cumulative match confidence value based at least in part on the input property match confidence value;

determine that the final cumulative match confidence value satisfies the rule match threshold value;

determine that the first source data record matches the second source data record based at least in part on determining that the final cumulative match confidence value satisfies the rule match threshold value;

generate an integrated data record, wherein the at least one processor is configured to generate the integrated data record by executing the computer-executable instructions to populate the integrated data record with the first data populated in the first source data record and the second data populated in the second source data record;

store the integrated data record in an integrated data repository;

link the integrated data record to the first source data record stored in the first source data repository;

link the integrated data record to the second source data record stored in the second source data repository;

receive, on behalf of the first payment system, an entity information request associated with the entity, wherein the entity information request comprises at least a portion of the first data; and

transmit, to the first payment system, a response to the entity information request, the response comprising at least a portion of the second data, wherein the at least a portion of the second data enables initiation of a debit or a credit associated with a financial transaction involving the entity.

2. The system of claim 1, wherein the second source data repository is associated with a second payment system.

3. The system of claim 2, wherein the at least a portion of the second data included in the response to the entity information request comprises an indication of a financial account associated with the payee, and wherein the at least one processor is further configured to execute the computer-executable instructions to:

transmit, by one of;

i) the first payment system or ii) a money movement engine operating on behalf of the first payment system, to one of iii) the second payment system or iv) a notification engine, a credit notification instruction, the credit notification instruction comprising an identifier of the payee and a payment amount,

wherein one of i) the first payment system or ii) the money movement engine operating on behalf of the first payment system initiates the credit to the financial account associated with the payee using the indication of the financial account.

4. The system of claim 3, wherein the at least one processor is further configured to execute the computer-executable instructions to:

determine a notification identifier associated with the payee based at least in part on the identifier of the payee, wherein the notification identifier is associated with a notification mechanism;

generate a credit notification message indicating the credit and the payment amount; and

transmit the credit notification message to the notification identifier using the notification mechanism.

5. The system of claim 2, wherein the first payment system is configured to identify the second payment system for initiating at least one of the debit or the credit associated with the financial transaction based at least in part on the at least a portion of the second data included in the response to the entity information request.

6. The system of claim 2, wherein the entity is a payee, and wherein the at least one processor is further configured to execute the computer-executable instructions to:

transmit, on behalf of the first payment system to one of;

i) the second payment system or ii) a money movement engine, a credit instruction to direct the credit to a financial account associated with the payee, wherein the credit instruction comprises at least a portion of the at least a portion of the second data.

7. The system of claim 6, wherein the at least one processor is further configured to execute the computer-executable instructions to:

determine a notification identifier associated with the payee, wherein the notification identifier is associated with a notification mechanism;

generate a notification message indicating availability of the credit, the notification message comprising at least one of i) a selectable mechanism for accepting the credit or ii) a selectable mechanism for registering with the second payment system; and

transmit the notification message to the notification identifier using the notification mechanism.

8. The system of claim 7, wherein the payee is registered with the second payment system, and wherein the at least one processor is further configured to execute the computer-executable instructions to:

receive an indication that the credit has been accepted via selection of the selectable mechanism for accepting the credit, wherein the second payment system initiates the credit to the financial account associated with the payee based at least in part on receiving the indication that the credit has been accepted; and

transmit, on behalf of the second payment system, a response to the credit instruction to the first payment system, the response to the credit instruction indicating successful initiation of the credit to the financial account associated with the payee.

9. The system of claim 7, wherein the payee is not registered with the second payment system, and wherein the at least one processor is further configured to execute the computer-executable instructions to:

receive an indication that the payee has registered with the second payment system via selection of the selectable mechanism for registering with the second payment system, wherein the second payment system initiates the credit to the financial account associated with the payee based at least in part on receiving the indication that the payee has registered with the second payment system; and

transmit, on behalf of the second payment system, a response to the credit instruction to the first payment system, the response to the credit instruction indicating successful initiation of the credit to the financial account associated with the payee.

10. The system of claim 7, wherein the financial account associated with the payee is a first financial account, and wherein the at least one processor is further configured to execute the computer-executable instructions to:

determine, on behalf of the first payment system, a duration of a timeout period, wherein the credit instruction specifies the duration of the timeout period;

initiate, on behalf of the second payment system, the timeout period;

determine that the duration of the timeout period has elapsed without having received an indication of an acceptance of the credit or registration of the payee with the second payment system; and

transmit, on behalf of the second payment system, a response to the credit instruction to the first payment system, the response to the credit instruction indicating absence of receipt of the acceptance of the credit or the registration of the payee with the second payment system,

wherein the first payment system initiates the credit to the payee responsive to receiving the response to the credit instruction without using the at least a portion of the second data included in the response to the entity information request.

11. The system of claim 10, wherein the at least one processor is further configured to execute the computer-executable instructions to determine, on behalf of the first payment system, that a payment lead time associated with the financial transaction is sufficient to permit interaction with the payee prior to determining the duration of the timeout period.

12. The system of claim 1, wherein at least one processor is further configured to execute the computer-executable instructions to:

initiate, by one of;

i) the first payment system or ii) a money movement engine operating on behalf of the first payment system, the debit to a financial account associated with the payor, wherein at least one of i) the first source data record or ii) the second data comprises an indication of the financial account.

13. The system of claim 1, wherein the at least one processor is further configured to execute the computer-executable instructions to:

initiate, by one of;

i) the first payment system or ii) a money movement engine operating on behalf of the first payment system, the credit to a financial account associated with the payee, wherein at least one of i) the first source data record or ii) the second data comprises an indication of the financial account.

14. The system of claim 1, wherein the at least one processor is further configured to execute the computer-executable instructions to generate a search query comprising a search parameter value that corresponds to an entity identifier of the entity included in the first data and submit the search query against the second source data repository.

15. A method, comprising:

determining a first source data record populated with first data associated with an entity, wherein the entity is a payor or a payee of a financial transaction, and wherein the first source data record is stored in a first source data repository associated with a first payment system;

determining a second source data record populated with second data associated with the entity, wherein the second source data record is stored in a second source data repository not associated with the first payment system, and wherein the first source data record does not include the second data;

selecting a data record matching rule that is eligible for execution on the first source data record and second source data record;

determining that the data record matching rule specifies an input property, a matching algorithm corresponding to the input property, and a rule match threshold value;

executing the data record matching rule on the first source data record and the second source data record, wherein executing the data record matching rule comprises executing the matching algorithm to obtain a result value;

determining an input property match confidence value associated with the input property based at least in part on the result value;

determining a final cumulative match confidence value based at least in part on the input property match confidence value;

determining that the final cumulative match confidence value satisfies the rule match threshold value;

determining that the first source data record matches the second source data record based at least in part on determining that the final cumulative match confidence value satisfies the rule match threshold value;

generating an integrated data record, wherein generating the integrated data record comprises populating the integrated data record with the first data populated in the first source data record and the second data populated in the second source data record;

storing the integrated data record in an integrated data repository;

linking the integrated data record to the first source data record stored in the first source data repository;

linking the integrated data record to the second source data record stored in the second source data repository;

receiving, on behalf of the first payment system, an entity information request associated with the entity, wherein the entity information request comprises at least a portion of the first data; and

transmitting, to the first payment system, a response to the entity information request, the response comprising at least a portion of the second data, wherein the at least a portion of the second data enables initiation of a debit or a credit associated with a financial transaction involving the entity.

16. The method of claim 15, wherein the second source data repository is associated with a second payment system.

17. The method of claim 16, wherein the at least a portion of the second data included in the response to the entity information request comprises an indication of a financial account associated with the payee, the method further comprising:

transmitting, by one of;

i) the first payment system or ii) a money movement engine operating on behalf of the first payment system, to one of iii) the second payment system or iv) a notification engine, a credit notification instruction, the credit notification instruction comprising an identifier of the payee and a payment amount,

wherein one of i) the first payment system or ii) the money movement engine operating on behalf of the first payment system initiates the credit to the financial account associated with the payee using the indication of the financial account.

18. The method of claim 16, wherein the entity is a payee, the method further comprising:

transmitting, on behalf of the first payment system to one of;

i) the second payment system or ii) a money movement engine, a credit instruction to direct the credit to a financial account associated with the payee, wherein the credit instruction comprises at least a portion of the at least a portion of the second data;

determining a notification identifier associated with the payee, wherein the notification identifier is associated with a notification mechanism;

generating a notification message indicating availability of the credit, the notification message comprising at least one of i) a selectable mechanism for accepting the credit or ii) a selectable mechanism for registering with the second payment system; and

transmitting the notification message to the notification identifier using the notification mechanism.

19. The method of claim 18, further comprising:

receiving a first indication that the credit has been accepted via selection of the selectable mechanism for accepting the credit or a second indication that the payee has registered with the second payment system via selection of the selectable mechanism for registering with the second payment system, wherein the second payment system initiates the credit to the financial account associated with the payee based at least in part on receiving the first indication or the second indication; and

transmitting, on behalf of the second payment system, a response to the credit instruction to the first payment system, the response to the credit instruction indicating successful initiation of the credit to the financial account associated with the payee.

20. The method of claim 18, wherein the financial account associated with the payee is a first financial account, the method further comprising:

determining, on behalf of the first payment system, a duration of a timeout period, wherein the credit instruction specifies the duration of the timeout period;

initiating, on behalf of the second payment system, the timeout period;

determining that the duration of the timeout period has elapsed without having received an indication of an acceptance of the credit or registration of the payee with the second payment system; and

transmitting, on behalf of the second payment system, a response to the credit instruction to the first payment system, the response to the credit instruction indicating absence of receipt of the acceptance of the credit or the registration of the payee with the second payment system,

wherein the first payment system initiates the credit to the payee responsive to receiving the response to the credit instruction without using the at least a portion of the second data included in the response to the entity information request.