Securely communicating data between an application associated with an entity and a third-party system

{
  "publication_number": "US2026106870A1",
  "country": "US",
  "kind": "A1",
  "title": "Securely communicating data between an application associated with an entity and a third-party system",
  "abstract": "A webview associated with a third-party system is provided in an application context associated with an entity. It is determined that a user has been authenticated by the third-party system based on data comprising a page displayed via the provided webview. In response to a determination that the user has been authenticated by the third-party system, one or more tasks to perform a function with the third-party system on behalf of the entity are automated.",
  "claims": [
    "1. (canceled) 2. A system, comprising: a communication interface; and a processor, coupled to the communication interface, configured to: provide, by code associated with a second entity in an application context of an application corresponding to a first entity associated with a user, a webview associated with a third-party system selected from a plurality of third-party systems, wherein the webview associated with the selected third-party system displays a native login page corresponding to the selected third-party system, wherein the user's login credentials are directly provided from the application associated with the application context, via the webview associated with the selected third-party system, to the selected third-party system; determine by executing the code associated with the second entity that the user has been authenticated by the selected third-party system, using data comprising a response page displayed via the provided webview associated with the selected third-party system by determining that the data comprising the response page includes data indicative of the user being authenticated, wherein the code associated with the second entity is embedded in code of the application corresponding to the first entity associated with the user; and in response to the determination that the data comprising the response page includes data indicative of the user being authenticated, automate one or more tasks needed to perform a function, requested by the user, with the selected third-party system on behalf of the entity, including by executing further code associated with the second entity to determine a parameter and a request structure associated with the function requested by the user as implemented by the selected third-party system and use the parameter and the request structure to generate and send to the selected third-party system an application programming interface request that includes the parameter and conforms to the request structure. 3. The system of claim 2, wherein the processor is configured to provide, via a user interface, the plurality of third-party systems. 4. The system of claim 3, wherein the processor is configured to receive, via the user interface, the selection of the third-party system selected from the plurality of third-party systems. 5. The system of claim 4, wherein the processor is configured to obtain from the selected third-party system the native login page associated with the selected third-party system. 6. The system of claim 4, wherein the user's login credentials are not accessed by code associated with the second entity. 7. The system of claim 4, wherein the user's login credentials are entered into the native login page associated with the selected third-party system via a password manager. 8. The system of claim 2, wherein the data comprising or otherwise associated with the response page includes a uniform resource locator. 9. The system of claim 2, wherein the data comprising or otherwise associated with the response page is analyzed using machine learning. 10. The system of claim 2, wherein the request comprises the application programming interface request. 11. The system of claim 2, wherein the processor is configured to perform the function with the third-party system by initiating bidirectional communication via remote procedure calls with a backend server. 12. The system of claim 11, wherein data transferred in the remote procedure call with the backend server is encrypted using elliptic curve cryptography. 13. The system of claim 2, wherein the request structure includes an application programming interface request body and a header as the request structure associated with the function requested by the user. 14. A method, comprising: providing, by code associated with a second entity in an application context of an application corresponding to a first entity associated with a user, a webview associated with a third-party system selected from a plurality of third-party systems, wherein the webview associated with the selected third-party system displays a native login page corresponding to the selected third-party system, wherein the user's login credentials are directly provided from the application associated with the application context, via the webview associated with the selected third-party system, to the selected third-party system; determining, by executing the code associated with the second entity, that the user has been authenticated by the selected third-party system, using data comprising a response page displayed via the provided webview associated with the selected third-party system by determining that the data comprising the response page includes data indicative of the user being authenticated, wherein the code associated with the second entity is embedded in code of the application corresponding to the first entity associated with the user; and in response to determining that the data comprising the response page includes data indicative of the user being authenticated, automating one or more tasks needed to perform a function, requested by the user, with the selected third-party system on behalf of the entity, including by executing further code associated with the second entity to determine a parameter and a request structure associated with the function requested by the user as implemented by the selected third-party system and use the parameter and the request structure to generate and send to the selected third-party system an application programming interface request that includes the parameter and conforms to the request structure. 15. The method of claim 14, further comprising providing, via a user interface, the plurality of third-party systems. 16. The method of claim 15, further comprising receiving, via the user interface, the selection of the third-party system selected from the plurality of third-party systems. 17. The method of claim 16, further comprising obtaining from the selected third-party system the native login page associated with the selected third-party system. 18. The method of claim 16, wherein the user's login credentials are entered into the native login page associated with the selected third-party system via a password manager. 19. The method of claim 14, wherein the data comprising or otherwise associated with the response page includes a uniform resource locator. 20. A computer program product embodied in a non-transitory computer readable medium and comprising computer instructions for: providing, by code associated with a second entity in an application context of an application corresponding to a first entity associated with a user, a webview associated with a third-party system selected from a plurality of third-party systems, wherein the webview associated with the selected third-party system displays a native login page corresponding to the selected third-party system, wherein the user's login credentials are directly provided from the application associated with the application context, via the webview associated with the selected third-party system, to the selected third-party system; determining, by executing the code associated with the second entity, that the user has been authenticated by the selected third-party system, using data comprising a response page displayed via the provided webview associated with the selected third-party system by determining that the data comprising the response page includes data indicative of the user being authenticated, wherein the code associated with the second entity is embedded in code of the application corresponding to the first entity associated with the user; and in response to determining that the data comprising the response page includes data indicative of the user being authenticated, automating one or more tasks needed to perform a function, requested by the user, with the selected third-party system on behalf of the entity, including by executing further code associated with the second entity to determine a parameter and a request structure associated with the function requested by the user as implemented by the selected third-party system and use the parameter and the request structure to generate and send to the selected third-party system an application programming interface request that includes the parameter and conforms to the request structure."
  ],
  "description_excerpt": "An employer may utilize a third-party system, such as a payroll provider or other employment-related third-party system, to perform tasks, such as to initiate the deposit of wages associated with a user (e.g., employee, independent contractor) to an account maintained by an entity associated with the user (e.g., a financial institution, a financial technology company, a financial service organization, a benefit provider, an institution, an enterprise, a government, a business, a corporation, etc.), to maintain and provide access to employment, income, tax, payroll, or other employment-related business records, etc.\n\nIn a prior approach, the user may utilize a third-party application, which the user accesses through an integration with an application, such as an application associated with an entity, to connect the user's payroll provider to the entity and/or alter settings in the payroll that indicate how the user would like their wages to be dispersed. The user provides their login credentials associated with the payroll provider to the application, which then provides the login credentials associated with the payroll provider to an intermediary service. The intermediary service utilizes the login credentials associated with the payroll provider to establish a communication session between the payroll provider and a device associated with the user on which the application is installed.",
  "cpc": [
    "H04L 63/0884",
    "G06Q 20/08",
    "G06Q 20/0855",
    "G06Q 20/40",
    "H04L 63/00",
    "H04L 63/083"
  ],
  "ipc": [
    "G06Q 20/08",
    "G06Q 20/40",
    "H04L 9/40"
  ],
  "assignees": [
    "Atomic FI Inc"
  ],
  "inventors": [
    "Scott Nielsen Weinert, JR.",
    "Sean Michael Hill",
    "Michael Contreras"
  ],
  "filing_date": "2025-09-17",
  "publication_date": "2026-04-16",
  "priority_date": "2022-12-22",
  "application_number": "US-202519331158-A",
  "family_id": "93018398",
  "cited_by_count": 0
}