IP Library Granted Patent US 12,353,447
Granted Patent B2
US 12,353,447 · App. 18/421,764 · Granted Jul 8, 2025

Account association systems and methods

Inventors: Malcolm Lewis (London, GB); Boris Taratine (London, GB)
Assignee: VISA EUROPE LIMITED
G06F16/288G06F16/951G06Q50/01H04L63/123
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,353,447
App. No.
18/421,764
Granted
Jul 8, 2025
Kind
B2
Abstract

Embodiments of the present disclosure comprise methods, apparatus and computer readable instructions for establishing a relationship between user accounts. A first account association request message in relation to a first user account in an account based system is received. A first source account identifier which corresponds to the first user account and a first target account identifier which corresponds to the second user account are identified. A second account association request message in relation to the second user account is received. Based on the second account association request message, a second source account identifier which corresponds to the second user account and a second target account identifier which corresponds to the first user account are identified. Responsive to a determination of whether the source account identifiers and target account identifiers relate to the same user account, a relationship is established between the first user account and the second user account.

Claims (48)

1. A method, comprising:

performing, by a server computer, a token process with respect to at least one of a first user account or a second user account, the token process comprising:

receiving a token request message associated with one of the first user account and the second user account, and

transmitting a token response message comprising a token corresponding to the one of the first user account or the second user account;

receiving, by the server computer, a first account association request message in relation to the first user account from a first user, the first account association request message comprising account identification data corresponding to the second user account;

identifying, by the server computer, based on the first account association request message, a first source account identifier which corresponds to the first user account and a first target account identifier which corresponds to the second user account;

receiving, by the server computer, a second account association request message in relation to the second user account from a second user, the second account association request message comprising account identification data corresponding to the first user account;

identifying, by the server computer, based on the second account association request message, a second source account identifier which corresponds to the second user account and a second target account identifier which corresponds to the first user account;

determining a first match between the first source account identifier and the second target account identifier;

determining a second match between the second source account identifier and the first target account identifier;

establishing a relationship between the first user account and the second user account based on the first match and the second match, wherein establishing the relationship comprises:

without revealing account information for the first user account to the second user, adding the account information for the first user account to the second user account by adding an entry for the first user account to a list of payees associated with the second user account; and

without revealing account information for the second user account to the first user, adding the account information for the second user account to the first user account by adding an entry for the second user account to a list of payees associated with the first user account.

2. The method of claim 1 , wherein the first account association request message is received from one of a user device associated with the first user account and a service provider entity associated with the first user account.

3. The method of claim 1 , wherein the second account association request message is received from one of a user device associated with the second user account and a service provider entity associated with the second user account.

4. The method of claim 1 , further comprising:

transmitting, in response to the first account association request message, an account association query message, wherein the second account association request message is received in response to transmission of the account association query message, wherein the account association query message is transmitted using the first target account identifier.

5. The method of claim 1 , further comprising:

performing an identity verification process in response to determining the first match and the second match, wherein the relationship between the first user account and the second user account is established after successful completion of the identity verification process.

6. The method of claim 1 , wherein the account identification data corresponding to one of the first user account or the second user account comprises the token.

7. The method of claim 1 , wherein one of the first target account identifier or the second target account identifier is identified based on the token.

8. The method of claim 1 , wherein the token process comprises generating the token in response to the token request message, wherein the token comprises a timestamp relating to at least one of a date and a time that the token was generated.

9. The method of claim 1 , wherein at least one of the account identification data corresponding to the first user account or the second user account includes an alias, an e-mail address or a phone number.

10. A processing system comprising:

one or more processors; and

a computer readable medium storing instructions that, when executed by the one or more processors, cause the processing system to:

performing a token process with respect to at least one of a first user account or a second user account, the token process comprising:

receiving a token request message associated with one of the first user account and the second user account, and

transmitting a token response message comprising a token corresponding to the one of the first user account or the second user account;

receive a first account association request message in relation to the first user account from a first user, the first account association request message comprising account identification data corresponding to the second user account;

identify, based on the first account association request message, a first source account identifier which corresponds to the first user account and a first target account identifier which corresponds to the second user account;

receive a second account association request message in relation to the second user account from a second user, the second account association request message comprising account identification data corresponding to the first user account;

identify, based on the second account association request message, a second source account identifier which corresponds to the second user account and a second target account identifier which corresponds to the first user account;

determine a first match between the first source account identifier and the second target account identifier;

determine a second match between the second source account identifier and the first target account identifier;

establish a relationship between the first user account and the second user account based on the first match and the second match, wherein establishing the relationship comprises:

without revealing account information for the first user account to the second user, adding the account information for the first user account to the second user account by adding an entry for the first user account to a list of payees associated with the second user account; and

without revealing account information for the second user account to the first user, adding the account information for the second user account to the first user account by adding an entry for the second user account to a list of payees associated with the first user account.

11. The processing system of claim 10 , wherein the first account association request message is received from one of a user device associated with the first user account and a service provider entity associated with the first user account.

12. The processing system of claim 10 , wherein the second account association request message is received from one of a user device associated with the second user account and a service provider entity associated with the second user account.

13. The processing system of claim 10 , wherein the instructions, when executed by the one or more processors, further cause the processing system to:

transmit, in response to the first account association request message, an account association query message, wherein the second account association request message is received in response to transmission of the account association query message, wherein the account association query message is transmitted using the first target account identifier.

14. The processing system of claim 10 , wherein the instructions, when executed by the one or more processors, further cause the processing system to:

perform an identity verification process in response to determining the first match and the second match, wherein the relationship between the first user account and the second user account is established after successful completion of the identity verification process.

15. The processing system of claim 10 , wherein the account identification data corresponding to one of the first user account or the second user account comprises the token.

16. The processing system of claim 10 , wherein one of the first target account identifier or the second target account identifier is identified based on the token.

17. The processing system of claim 10 , wherein the token process comprises generating the token in response to the token request message, wherein the token comprises a timestamp relating to at least one of a date and a time that the token was generated.

18. The processing system of claim 10 , wherein at least one of the account identification data corresponding to the first user account or the second user account includes an alias, an e-mail address or a phone number.

Priority Claims (1)
GB 1317311 · Sep 30, 2013 · national
Continuity (3)
Continuation 15079466 · Mar 24, 2016
Continuation PCTGB2014052952 · Sep 30, 2014
Related Publication 20240202217A1 · Jun 20, 2024
References Cited (23)
US 8355955B1 · Mirchandani et al. · 2013 [cited by applicant]
US 8571980B1 · Greenwood · 2013 [cited by examiner]
US 11282139B1 · Winklevoss et al. · 2022 [cited by applicant]
US 20050108155A1 · Gallagher · 2005 [cited by examiner]
US 20070019616A1 · Rantapuska et al. · 2007 [cited by applicant]
US 20090271287A1 · Halpern · 2009 [cited by applicant]
US 20100042538A1 · Dheer · 2010 [cited by examiner]
US 20100262932A1 · Pan · 2010 [cited by applicant]
US 20110060629A1 · Yoder · 2011 [cited by examiner]
US 20110106675A1 · Perlman · 2011 [cited by examiner]
US 20120136781A1 · Fridman · 2012 [cited by examiner]
US 20120271761A1 · Kight et al. · 2012 [cited by applicant]
US 20130036112A1 · Poon · 2013 [cited by applicant]
US 20130060689A1 · Oskolkov · 2013 [cited by examiner]
US 20140058965A1 · Ryan et al. · 2014 [cited by applicant]
US 20140279444A1 · Kassemi · 2014 [cited by examiner]
US 20140280941A1 · Maguire · 2014 [cited by applicant]
US 20150013000A1 · Linnakangas et al. · 2015 [cited by applicant]
US 20150066743A1 · Gerard et al. · 2015 [cited by applicant]
US 20150278919A1 · Stoll et al. · 2015 [cited by applicant]
Application No. EP21160069.7 , Office Action, Mailed On Jun. 29, 2023, 6 pages. [cited by applicant]
International Search Report and Written Opinion dated Jan. 23, 2015 for PCT Application No. PCT/3B2014/052952. [cited by applicant]
UKIPO Search Report dated Mar. 10, 2014 for Application No. GB1317311.7. [cited by applicant]