US 11,941,652 B2
Automatic linking of loyalty accounts of authorized users to loyalty accounts of primary users
Adrian Bloy, Ottawa (CA); Morgan Klein-MacNeil, Toronto (CA); Syrous Delavari-Maraghi, Vaughan (CA); Trevor Ross Gimbel, Mississauga (CA); Caroline Elizabeth Wilkinson, Mississauga (CA); and Sonali Suresh Nagarkar, Toronto (CA)
Assigned to The Toronto-Dominion Bank
Filed by The Toronto-Dominion Bank, Toronto (CA)
Filed on Aug. 11, 2022, as Appl. No. 17/819,072.
Application 17/819,072 is a continuation of application No. 16/660,248, filed on Oct. 22, 2019, granted, now 11,449,884.
Prior Publication US 2022/0383355 A1, Dec. 1, 2022
Int. Cl. G06Q 30/00 (2023.01); G06Q 20/22 (2012.01); G06Q 20/34 (2012.01); G06Q 20/40 (2012.01); G06Q 30/0207 (2023.01); G06Q 30/0226 (2023.01); G06Q 40/02 (2023.01)
CPC G06Q 30/0215 (2013.01) [G06Q 20/227 (2013.01); G06Q 20/3572 (2013.01); G06Q 20/4012 (2013.01); G06Q 30/0233 (2013.01); G06Q 30/0236 (2013.01); G06Q 40/02 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A financial institution computing system comprising:
a communications module;
at least one memory storing instructions for verifying authorized users of credit accounts, a repository storing a plurality of account profiles associated with a plurality of accounts, each account profile associated with a primary user, wherein at least one of the plurality of account profiles is further associated with at least one authorized user;
at least one hardware processor interoperably coupled with the at least one memory and the communications module, wherein the instructions instruct the at least one hardware processor to:
receive, from a loyalty system managing a plurality of loyalty accounts via a dedicated application programming interface (API), the API hosted on a network by the financial institution computing system, credit account information associated with an authenticated user, wherein the loyalty system is separate and distinct from the financial institution system, wherein an authenticated user is a user who was previously authenticated by the loyalty system, and wherein the credit account information is associated with the financial institution;
in response to receiving the credit account information via the dedicated API, automatically initiate a query of the repository of account profiles for accounts associated with the credit account information;
identify results from the initiated query and automatically compare the received credit account information associated with the authenticated user with the results from queried repository;
determine, by the at least one hardware processor and based on the comparison, whether the authenticated user is an authorized user of a credit account associated with a particular primary user, wherein the particular primary user is different from the authorized user;
in response to determining that the authenticated user is an authorized user of the credit account associated with the particular primary user, automatically generate a success message comprising information necessary to link a loyalty account associated with the authorized user with a loyalty account associated with the particular primary user, wherein the loyalty account associated with the particular primary user is managed by the loyalty system and is different than the credit account associated with the particular primary user; and
return, via the API, the success message to the loyalty system.