# US 2017/0286959 A1 · Systems and methods for verifying an identity record

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0286959 A1
- Document ID: US20170286959A1
- Status: Published application
- Kind: A1
- Application number: 15/513,585
- Filed: 2015-09-23
- Published: 2017-10-05
- Earliest claimed: 2014-09-23
- Assignees: David Thomas; Juan Furmie
- Inventors: David Thomas; Juan Furmie; Mark Anthony James Chirnside
- Web page: https://patentgrep.com/patent/US20170286959A1

## CPC

- G06Q 20/4014: {Identity check for transactions}
- G06F 21/31: User authentication
- G06Q 50/26: Government or public services (business processes related to the transportation industry G06Q50/40)
- H04L 63/102: {Entity profiles}
- H04L 63/12: {Applying verification of the received information (cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32)}
- H04L 67/04: specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/53: using third party service providers
- G06F 2221/2115: Third party
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 63/0892: {by using authentication-authorization-accounting [AAA] servers or protocols}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system and method for verifying an identity record is provided. The system includes a data server configured to submit first and second data elements associated with an unverified identity record to first and second third party servers, respectively. The data server then receives from the first and second third party servers, at least one additional data element and at least one further data element being associated, at the first and second third party servers respectively, with the first and second data elements. A comparing component then compares the received at least one additional data element and at least one further data element with at least corresponding data elements associated with the identity record and a flagging component flags the identity record as a verified identity record if the received at least one additional and further data elements match the at least one corresponding data element.

## Claims

### Claim 1

A method for verifying an identity record, the method being conducted at a data server and comprising the steps of:
submitting, by a submitting component, a first data element associated with an unverified identity record to a first third party server;
receiving, by a receiving component, from the first third party server, at least one additional data element being associated, at the first third party server, with the first data element;
submitting, by the submitting component, a second data element associated with the unverified identity record to a second third party server;
receiving, by the receiving component, from the second third party server, at least one further data element being associated, at the second third party server, with the second data element;
comparing, by a comparing component, the received at least one additional data element and the received at least one further data element with at least corresponding data elements associated with the unverified identity record; and,
if the received at least one additional data element and the received at least one further data element matches the at least corresponding data elements, flagging, by a flagging component, the identity record as a verified identity record.

### Claim 2 (depends on 1)

The method as claimed in claim 1, wherein the step of comparing the received data elements with corresponding data elements to includes:
associating, by a confidence associating component, a confidence indicator with the identity record, wherein the confidence indicator is related to the extent to which the received data elements match the corresponding data elements; and,
flagging, by the flagging component, the identity record as a verified identity record if the confidence indicator exceeds a predetermined threshold.

### Claim 3 (depends on 1)

The method as claimed in claim 1, wherein the identity record has associated therewith one or more data elements of the group of: a full name; initials; national identity number; a residential address; a communication address; and payment credentials including a bank account number, a branch code and an account type.

### Claim 4 (depends on 1)

The method as claimed in claim 1, wherein the first data element is a national identity number and the received at least one additional data element is one or more of the group of: a full name; initials; living/deceased status; residential address; and marital status.

### Claim 5 (depends on 1)

The method as claimed in claim 1, wherein the second data element is payment credentials and the received at least one further data element includes one or more of the group of: a full name; initials; residential address; national identity number; and a status of an associated financial account.

### Claim 6 (depends on 5)

A method as claimed in claim 5, which includes the steps of:
initiating, by an initiating component, a payment having a specific attribute in favour of the financial account associated with the payment credentials;
receiving, by a receiving component, from a communication device of a user, an indication of an attribute in respect of the payment made in favour of the financial account, the user having obtained the attribute from a bank statement or other transaction record relating to the financial account and accessible by the user ; comparing, by a comparing component, the received attribute to the specific attribute; and,
if the received attribute matches the specific attribute, authenticating the identity record.

### Claim 7 (depends on 6)

A method as claimed in claim 6, wherein the specific attribute is one or both of a specific amount and a specific payment reference and the payment reference is unique to the user.

### Claim 8 (depends on 1)

A method as claimed in claim 1, which includes the steps of:
receiving, by a receiving component, from a utility provider, a utility bill associated with at least one data element of the identity record;
validating, by a validating component, using a residential address provided with the utility bill, the residential address associated with the identity record;
identifying, by an identifying component, utility usage intimating user activity at the residential address; and,
flagging, by a flagging component, for a predefined period, the residential address as active.

### Claim 9

A system for verifying an identity record, the system including a data server comprising:
a submitting component for submitting first and second data elements associated with an unverified identity record to first and second third party servers, respectively;
a receiving component for receiving, from the first and second third party servers, at least one additional data element and at least one further data element being associated, at the first and second third party servers respectively, with the first and second data elements;
a comparing component for comparing the received at least one additional data element and at least one further data element with at least corresponding data elements associated with the identity record; and,
a flagging component for, if the received at least one additional and further data elements match the at least one corresponding data element, flagging the identity record as a verified identity record.

### Claim 10 (depends on 9)

The system as claimed in claim 9, wherein the data server includes an extracting component for extracting the first data element from the identity record.

### Claim 11 (depends on 9, 10)

The system as claimed in claim 9 or claim 10, wherein the comparing component includes a confidence associating component for associating a confidence indicator with the identity record, the confidence indicator being related to the extent to which the received data elements, including at least the additional and further data elements, match corresponding data elements and wherein the flagging component, if the confidence indicator exceeds a predetermined threshold, flags the identity record as a verified identity record.

### Claim 12 (depends on 9)

The system as claimed claim 9, wherein the data server includes an initiating component for initiating a payment having a specific attribute in favour of a financial account associated with payment credentials, an indication receiving component for receiving, from a communication device of a user, an indication of an attribute in respect of the payment made in favour of the financial account, the user having obtained the attribute from a bank statement or other transaction record relating to the financial account and accessible by the user, an attribute comparing component for comparing the received attribute to the specific attribute, and an authenticating component for, if the received attribute matches the specific attribute, authenticating the identity record.

### Claim 13 (depends on 12)

The system as claimed in claim 12, wherein the specific attribute is one or both of a specific amount and a specific payment reference and wherein the payment reference is unique to the user.

### Claim 14 (depends on 9)

The system as claimed in claim 9, wherein the data server further includes a utility bill receiving component for receiving, from a utility provider, a utility bill associated with at least one data element of the identity record, a validating component for validating, using a residential address provided with the utility bill, the residential address associated with the identity record, an identifying component for identifying utility usage intimating user activity at the residential address, and wherein the flagging component flags, for a predefined period, the residential address as active.

### Claim 15

A computer program product for verifying an identity record, the computer program product comprising a computer-readable medium having stored computer-readable program code for performing the steps of:
submitting a first data element associated with an unverified identity record to a first third party server;
receiving, from the first third party server, at least one additional data element being associated, at the first third party server, with the first data element;
submitting a second data element associated with the unverified identity record to a second third party server;
receiving, from the second third party server, at least one further data element being associated, at the second third party server, with the second data element;
comparing the received at least one additional data element and the received at least one further data element with at least corresponding data elements associated with the unverified identity record; and,
if the received at least one additional data element and the received at least one further data element matches the at least corresponding data element, flagging the identity record as a verified identity record.
