US 12,131,389 B2
Application programming interface for providing common user interface access to data from separate systems
Jason Pedone, Raleigh, NC (US); Sudhakar Swaminathan, Duluth, GA (US); and Raghavendra P. Narasimhan, Cary, NC (US)
Assigned to Truist Bank, Charlotte, NC (US)
Filed by TRUIST BANK, Charlotte, NC (US)
Filed on Feb. 28, 2022, as Appl. No. 17/682,304.
Application 17/682,304 is a continuation of application No. 17/592,001, filed on Feb. 3, 2022.
Claims priority of provisional application 63/167,790, filed on Mar. 30, 2021.
Prior Publication US 2022/0318927 A1, Oct. 6, 2022
This patent is subject to a terminal disclaimer.
Int. Cl. G06Q 40/12 (2023.01); G06F 9/54 (2006.01)
CPC G06Q 40/12 (2013.12) [G06F 9/547 (2013.01)] 16 Claims
OG exemplary drawing
 
1. A server comprising:
a processor device; and
a non-transitory computer-readable memory that is executable by the processor device to perform operations comprising:
outputting a common user interface that provides integrated labeling for accessing data and performing functions relating to a first financial account data system and a second financial account data system, the integrated labeling being generic with respect to the first financial account data system and the second financial account data system, the integrated labeling representing an integration of the first financial account data system and the second financial account data system at a future time, the first financial account data system having first account data stored thereon and being configured to perform (i) at least one function according to a first process and using the first account data, and (ii) a first authentication process to authenticate, based on received data, a request to perform the first process, the second financial account data system having second account data stored thereon that is unintegrated with the first account data, the second financial account data system being configured to perform (i) at least one function according to a second process and using the second account data, and (ii) a second authentication process to authenticate, based on the received data, a request to perform the second process, the second process being different than the first process and the second authentication process being different than the first authentication process, the integrated labeling representing a process different than and generic to the first process and the second process and an authentication process different than and generic to the first authentication process and the second authentication process;
receiving, via the integrated labeling, input data from an entity, the input data including a request to perform a function;
comparing the input data with data included in a plurality of existing user profiles to identify, among the plurality of existing user profiles, a user profile associated with the input data by:
receiving, from the first financial account data system, a first set of user profiles, wherein each user profile of the first set of user profiles includes indications of known devices and known behaviors of a first corresponding entity having an account associated with the first financial account data system;
receiving, from the second financial account data system, a second set of user profiles, wherein each user profile of the second set of user profiles includes indications of known devices and known behaviors of a second corresponding entity having an account associated with the second financial account data system; and
determining, among the first set of user profiles and the second set of user profiles, the user profile associated with the input data by comparing the input data with the first set of user profiles and the second set of user profiles to identify historical data associated with the entity;
providing, via the common user interface and to an application programming interface (API) on a system configured to communicatively couple to the first financial account data system and the second financial account data system, the request for the function to be executed, the API configured to determine a data system, among the first financial account data system and the second financial account data system, with which to execute the function based on the historical data;
receiving, from the API, a result from executing the function using the first process or the second process; and
outputting the result via the common user interface.