Search

US-12626300-B1 - Cross-system integration platform

US12626300B1US 12626300 B1US12626300 B1US 12626300B1US-12626300-B1

Abstract

A system includes an intermediate mortgage integration platform as a service (MiPaas). Specifically, an MiPaas layer may facilitate integration between a loan origination system (LOS) and supporting services. The MiPaas layer may provide integration flexibility by enabling integration of the supporting services with each other and with different LOSs. Indeed, a number of MiPaas integration formats (e.g. REST API, OpenAPI, GRPC, GraphQL, Industry Standard interface, etc. may be provided to facilitate ease of integration between the LOS and the supporting services. Further, the MiPaas may provide processing efficiencies by adapting workflows based upon particular retrieved data. In this manner, efficient processing may be performed in an intermediate data processing layer, resulting in more efficient turnaround times and reduced processing requirements at traditionally over-burdened systems.

Inventors

  • Hrishikesh Madhukar Godse
  • Jason Christopher Bostic
  • Elizabeth Poland Smith

Assignees

  • UNITED SERVICES AUTOMOBILE ASSOCIATION (USAA)

Dates

Publication Date
20260512
Application Date
20240829

Claims (16)

  1. 1 . A system, comprising: a mortgage integration platform as a service (MiPaas) comprising: a computer processor and communication circuitry, the MiPaas communicatively integrated with a loan origination system (LOS) via a first integration supported by the communication circuitry and communicatively integrated with a vendor service via a second integration supported by the communication circuitry; and one or more interface translators configured to provide vendor service data to the LOS via one or more particular interface formats specified by the one or more interface translators, wherein the one or more interface translators comprise: a representational state transfer (REST) API interface translator providing a REST API interface to the MiPaas; an OpenAPI interface translator providing an OpenAPI interface to the MiPaas; a Google Response Procedure Call (gPRC) interface translator providing a gPRC interface to the MiPaas; a GraphQL interface translator providing a GraphQL interface to the MiPaas; or any combination thereof; and wherein the MiPaas is configured to: receive the vendor service data from the vendor service in a first integration format; generate formatted vendor data from the received vendor service data in a second integration format; and integrate the LOS and the vendor service, by providing the formatted vendor data to the LOS, independent of a direct integration between the vendor service and the LOS, wherein the LOS and the vendor service are unable to directly integrate with each other.
  2. 2 . The system of claim 1 , comprising: a second LOS communicatively integrated with the MiPaas, wherein the MiPaas is configured to provide the vendor service data from the vendor service to the second LOS without a second LOS-specific integration of the vendor service.
  3. 3 . The system of claim 1 , wherein the one or more interface translators comprise an Industry Standard interface translator providing an Industry Data Standards interface to the MiPaas.
  4. 4 . The system of claim 1 , comprising: a second vendor service communicatively integrated with the MiPaas, independent of an LOS-specific integration.
  5. 5 . The system of claim 1 , comprising: a second vendor service directly communicatively integrated with the LOS via a third integration, wherein the MiPaas is configured to integrate the LOS, the vendor service, and the second vendor service via the first integration, the second integration, and the third integration.
  6. 6 . The system of claim 5 , wherein the vendor service and the second vendor service provide at least a partial overlap in provided data and the MiPaas is configured to identify a prioritized integration of the second integration and the third integration to receive the partial overlap in provided data.
  7. 7 . The system of claim 1 , wherein the MiPaas comprises: a first data processing engine implemented in a cloud-based infrastructure, configured to perform first data processing on first data from one or more integrated services; and a second data processing engine implemented in an on-Premise infrastructure, configured to perform second data processing on second data from one or more integrated services.
  8. 8 . The system of claim 7 , wherein the MiPaas is configured to: identify non-private information as the first data and route the first data to the first data processing engine; and identify private information as the second data and route the second data to the second data processing engine.
  9. 9 . The system of claim 1 , wherein the MiPaas is configured to: identify, from data fields provided by the vendor service, anti-money laundering (AML) data fields that provide AML data; automatically register the LOS as a subscriber to the AML data fields; provide initial data, modified data, or both of the AML data fields to the LOS; determine whether the initial data, modified data, or both indicates an AML data issue; and when the initial data, modified data, or both indicates an AML data issue, provide an AML alert with an indication of the AML data issue, specifying the initial data, modified data, or both that resulted in the AML data issue.
  10. 10 . The system of claim 1 , wherein the MiPaas is configured to: receive an indication of a data capture trigger event occurring; request data associated with the data capture trigger event; determine whether the requested data is received; in response to determining that the requested data is not received, re-request the data; in response to determining that the requested data is received, identify data requirements of the received data and determine whether the data requirements of the received data are met; when the data requirements are met, provide an indication of satisfaction of the data requirements; and otherwise, when the data requirements are not met, provide a data requirement alert indicating that the data requirements are not satisfied.
  11. 11 . The system of claim 10 , wherein the MiPaas is configured to: in response to determine that the requested data is not received, re-request the data only up to a threshold number of re-requests, only up to a threshold amount of allotted passed time, or both.
  12. 12 . A tangible, non-transitory, computer-readable medium, comprising computer-readable instruction that, when executed by one or more processors of a computer, cause the computer to: implement a mortgage integration platform as a service (MiPaas) comprising a computer processor and communication circuitry, the MiPaas communicatively integrated with a loan origination system (LOS) via a first integration supported by the communication circuitry and communicatively integrated with a vendor service via a second integration supported by the communication circuitry; provide an interface for the LOS to access vendor service data received from the vendor service via an interface translator configured to provide the vendor service data to the LOS via a particular interface format specified by the interface translator, wherein the interface translator comprises: a representational state transfer (REST) API interface translator providing a REST API interface to the MiPaas; an OpenAPI interface translator providing an OpenAPI interface to the MiPaas; a Google Response Procedure Call (gPRC) interface translator providing a gPRC interface to the MiPaas; a GraphQL interface translator providing a GraphQL interface to the MiPaas; an Industry Standard interface translator providing an Industry Data Standards interface to the MiPaas; or any combination thereof; and wherein the MiPaas is configured to: receive the vendor service data from the vendor service in a first integration format; generate formatted vendor data from the received vendor service data in a second integration format; and integrate the LOS and the vendor service, by providing the formatted vendor data to the LOS, independent of a direct integration between the vendor service and the LOS, wherein the LOS and the vendor service are unable to directly integrate with each other.
  13. 13 . The tangible, non-transitory, computer-readable medium of claim 12 , comprising computer-readable instruction that, when executed by one or more processors of the computer, cause the computer to: integrate the LOS, the vendor service, and a second vendor service integrated with the MiPaas via a third integration via the first integration, the second integration, and the third integration.
  14. 14 . A computer-implemented method, comprising: implementing a mortgage integration platform as a service (MiPaas) comprising a computer processor and communication circuitry, the MiPaas communicatively integrated with a loan origination system (LOS) via a first integration supported by the communication circuitry and communicatively integrated with a vendor service via a second integration supported by the communication circuitry; providing an interface for the LOS to access vendor service data received from the vendor service via an interface translator configured to provide the vendor service data to the LOS via a particular interface format specified by the interface translator, wherein the interface translator comprises: a representational state transfer (REST) API interface translator providing a REST API interface to the MiPaas; an OpenAPI interface translator providing an OpenAPI interface to the MiPaas; a Google Response Procedure Call (gPRC) interface translator providing a gPRC interface to the MiPaas; a GraphQL interface translator providing a GraphQL interface to the MiPaas; an Industry Standard interface translator providing an Industry Data Standards interface to the MiPaas; or any combination thereof; and receiving the vendor service data from the vendor service in a first integration format; generating formatted vendor data from the received vendor service data in a second integration format; and integrating the LOS and the vendor service, by providing the formatted vendor data to the LOS, independent of a direct integration between the vendor service and the LOS, wherein the LOS and the vendor service are unable to directly integrate with each other.
  15. 15 . The computer-implemented method of claim 14 , comprising: identifying, from data fields provided by the vendor service, anti-money laundering (AML) data fields that provide AML data; automatically registering the LOS as a subscriber to the AML data fields; providing initial data, modified data, or both of the AML data fields to the LOS; determining whether the initial data, modified data, or both indicates an AML data issue; and when the initial data, modified data, or both indicates an AML data issue, providing an AML alert with an indication of the AML data issue, specifying the initial data, modified data, or both that resulted in the AML data issue.
  16. 16 . The computer-implemented method of claim 14 , comprising: receiving an indication of a data capture trigger event occurring; requesting data associated with the data capture trigger event; determining whether the requested data is received; in response to determining that the requested data is not received, re-requesting the data; in response to determining that the requested data is received, identifying data requirements of the received data and determine whether the requirements of the received data are met; when the data requirements are met, providing an indication of satisfaction of the data requirements; and otherwise when the data requirements are not met, providing a data requirement alert indicating that the data requirements are not satisfied.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS This application is a continuation of U.S. patent application Ser. No. 17/858,683, entitled “CROSS-SYSTEM INTEGRATION PLATFORM”, filed on Jul. 6, 2022, which is incorporated by reference herein in its entirety for all purposes. BACKGROUND The present disclosure relates generally to systems and methods related to integration of cross-platform standards. More specifically, the present disclosure relates to an integration platform that provides effective data transfer across disparate third-party systems. Third-party devices may include smart devices that use sensors to monitor the environment of a customer and that send data to a third-party. For example, the customer may own multiple third-party devices (e.g., smart home devices, wearables, security systems) that generate data in real-time or near real-time and store the data in a remote server that is accessible by a manufacture of the third-party device. While third-party devices may empower the owner to better understand their environment, the aggregation of data from multiple third-party devices may create privacy and security risks. As such, improved systems and methods for managing and protecting the data of third-party customers or owners are desired. This section is intended to introduce the reader to various aspects of art that may be related to various aspects of the present techniques, which are described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art. BRIEF DESCRIPTION A summary of certain embodiments disclosed herein is set forth below. It should be understood that these aspects are presented merely to provide the reader with a brief summary of these certain embodiments and that these aspects are not intended to limit the scope of this disclosure. Indeed, this disclosure may encompass a variety of aspects that may not be set forth below. Embodiments provided herein relate to a mortgage integration platform as a service (MiPaas). Specifically, an MiPaas layer may facilitate integration between a loan origination system (LOS) and 3rd party vendor supporting services for originating and servicing loans. The MiPaas layer may provide integration flexibility by enabling integration of the supporting services with each other and with different LOSs. Indeed, a number of MiPaas integration formats (e.g., REST API, OpenAPI, GRPC, GraphQL, File Transfer Protocols, Industry Data Standards based integration, etc.) may be provided to facilitate ease of integration between the LOS and the supporting services. Further, the MiPaas may provide processing efficiencies by adapting workflows based upon particular retrieved data. In this manner, efficient processing may be performed in an intermediate data processing layer, resulting in more efficient turnaround times and reduced processing requirements at traditionally over-burdened systems. BRIEF DESCRIPTION OF THE DRAWINGS These and other features, aspects, and advantages of the present disclosure will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein: FIG. 1 is a schematic diagram, illustrating a Loan Origination System (LOS) directly coupled to vendor services; FIG. 2 is a schematic diagram, illustrating a Mortgage Integration Platform as a Service (MiPaas) that provides integration between vendor services and a LOS, in accordance with certain embodiments of the current application; FIG. 3 is a schematic diagram of an MiPaas integrating vendor services integrated with an LOS with non-LOS integrations, in accordance with certain embodiments of the current application; FIG. 4 is a flowchart, illustrating a process for implementing hybrid integrations, in accordance with certain embodiments of the current application; FIG. 5 is a block diagram, illustrating a list of components that may be integrated via the MiPaas, in accordance with certain embodiments of the current application; FIG. 6 is a flowchart, illustrating a process for creating a vendor services integration via the MiPaas, in accordance with certain embodiments of the current application; FIG. 7 is a schematic diagram, illustrating a graphical user interface (GUI) for creating a vendor services integration, in accordance with certain embodiments of the current application; FIG. 8 is a schematic diagram, illustrating a graphical user interface (GUI) for creating a mapping between vendor services data and LOS data, in accordance with certain embodiments of the current application; FIG. 9 is a schematic diagram, illustrating data flows of hybrid MiPaas that provides on-premises processing and/or clo