Account linking index structure in a network
Abstract
A computer-implemented method for constructing an index structure in a real-time payment network includes: receiving a first set of transaction information comprising data field entries relating to a user; creating a data record in the index structure for the user; inserting the data field entries in the first set of transaction information into the data record; receiving a second set of transaction information comprising data field entries; determining if the second set of transaction information is associated with the user, wherein at least one data field entry in the second set of transaction information is different to a corresponding data field entry in the first set of transaction information; and inserting the data field entries in the second set of transaction information into the data record if the second set of transaction information is determined to be associated with the user.
Claims
exact text as granted — not AI-modified1 . A computer-implemented method for constructing an index structure in a real-time payment network, the method comprising:
receiving a first set of transaction information, wherein the first set of transaction information comprises one or more data field entries relating to a user; creating a data record in the index structure for the user, the data record comprising a plurality of data fields for data field entries; inserting the one or more data field entries in the first set of transaction information into the data record; receiving a second set of transaction information, wherein the second set of transaction information comprises one or more data field entries; determining if the second set of transaction information is associated with the user, wherein at least one data field entry in the second set of transaction information is different to a corresponding data field entry in the first set of transaction information; and inserting the one or more data field entries in the second set of transaction information into the data record if the second set of transaction information is determined to be associated with the user.
2 . The method of claim 1 , wherein determining if the second set of transaction information is associated with the user comprises matching at least a portion of one data field entry in the second set of transaction information to a corresponding data field entry portion in the first set of transaction information.
3 . The method of claim 1 , wherein the one or more data field entries includes one or more of: a name; an email address; a primary account number, PAN; mobile device information; account number; IP address; MAC address; billing address information; merchant identifier; transaction location; transaction amount; transaction date information; and time information.
4 . The method of claim 3 , wherein matching further comprises calculating a likelihood score of the second set of transaction information being associated with the user, wherein the likelihood score being above a predetermined value indicates that the second set of transaction information is associated with the user, and wherein the likelihood score being below the predetermined value indicates that the second set of transaction information is not associated with the user.
5 . The method of claim 4 , wherein the likelihood score is below the predetermined value if the billing address information in the second set of transaction information is the only data field entry which matches with the corresponding data field entry in the first set of transaction information.
6 . The method of claim 4 , wherein the likelihood score is above the predetermined value if at least two of: an IP address associated with a user device, a user address, a user account identifier, and user device information match.
7 . The method of claim 6 , wherein the likelihood score is further increased above the predetermined value if a time information of the second set of transaction information is within a predetermined time period of a time information of the first set of transaction information.
8 . The method of claim 1 , further comprising:
linking a first primary account number, PAN, in the first set of transaction information with a second PAN in the second set of transaction information in the data record, wherein linking the first PAN and the second PAN indicate that the first and second PANs are associated to the user.
9 . The method of claim 8 , further comprising:
receiving a risk score calculation request for a new transaction comprising a third set of transaction information; identifying a third PAN in the third set of transaction information; comparing the third PAN to the first and second PANs in the data record belonging to the user; calculating a risk score based on the comparison; setting the risk score for the new transaction; and transmitting the risk score for the new transaction to an issuer server.
10 . The method of claim 1 , further comprising:
identifying one or more user accounts from the data record; monitoring the one or more user accounts for one or more further transactions to or from the one or more user accounts; identifying one or more additional user accounts from the one or more further transactions; determining if the one or more additional user accounts belong to the user; and inserting account information of the one or more additional user accounts which belong to the user into the data record.
11 . The method of claim 1 , further comprising:
searching the index structure for the user; and outputting the data record of the user as a report.
12 . A system for constructing an index structure in a real-time payment network, the system configured to:
receive a first set of transaction information, wherein the first set of transaction information comprises one or more data field entries relating to a user; create a data record in the index structure for the user, the data record comprising a plurality of data fields for data field entries; insert the one or more data field entries in the first set of transaction information into the data record; receive a second set of transaction information, wherein the second set of transaction information comprises one or more data field entries; determine if the second set of transaction information is associated with the user, wherein at least one data field entry in the second set of transaction information is different to a corresponding data field entry in the first set of transaction information; and insert the one or more data field entries in the second set of transaction information into the data record if the second set of transaction information is determined to be associated with the user.
13 . The system of claim 12 , wherein the one or more data field entries includes one or more of: a name; an email address; a primary account number, PAN; mobile device information; account number; IP address; MAC address; billing address information; merchant identifier; transaction location; transaction amount; transaction date information; and time information, wherein the system is configured to:
determine if the second set of transaction information is associated with the user by:
matching at least a portion of one data field entry in the second set of transaction information to a corresponding data field entry portion in the first set of transaction information; and
calculating a likelihood score of the second set of transaction information being associated with the user, wherein the likelihood score being above a predetermined value indicates that the second set of transaction information is associated with the user, and wherein the likelihood score being below the predetermined value indicates that the second set of transaction information is not associated with the user;
wherein the likelihood score is below the predetermined value if the billing address information in the second set of transaction information is the only data field entry which matches with the corresponding data field entry in the first set of transaction information; wherein the likelihood score is above the predetermined value if at least two of: an IP address associated with a user device, a user address, a user account identifier, and user device information match.
14 . The system of claim 12 , wherein the system comprises a first server configured to receive the sets of transaction information from one or more additional servers, wherein the first server is separate from the one or more additional servers.
15 . A non-transitory computer-readable storage medium storing instructions thereon which, when executed by a processor, cause the processor to perform a method for constructing an index structure in a real-time payment network, the method comprising:
receiving a first set of transaction information, wherein the first set of transaction information comprises one or more data field entries relating to a user; creating a data record in the index structure for the user, the data record comprising a plurality of data fields for data field entries; inserting the one or more data field entries in the first set of transaction information into the data record; receiving a second set of transaction information, wherein the second set of transaction information comprises one or more data field entries; determining if the second set of transaction information is associated with the user, wherein at least one data field entry in the second set of transaction information is different to a corresponding data field entry in the first set of transaction information; and inserting the one or more data field entries in the second set of transaction information into the data record if the second set of transaction information is determined to be associated with the user.Join the waitlist — get patent alerts
Track US2025053978A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.