DOCSEARCHbyAlgolia
Submit Docs

FDC3 (Financial Desktop Connectivity and Collaboration)

website·Indexed 37 days ago

https://fdc3.finos.org

Documentation for the FDC3 standard, including API references, context schemas, and intent definitions for interoperability between financial applications. Covers versions 2.0, 2.1, 2.2, and 'Next', with details on agent bridging, app directory specifications, and conformance frameworks.

Tokens
308K
Snippets
1.2K
Records
2K
Agent score
65%

What's inside FDC3

  1. Overview of the FDC3 Desktop Agent Communication Protocol (DACP)

    The Desktop Agent Communication Protocol (DACP) is a standardized set of JSON messages (a 'wire protocol') used to implement the interface to a Desktop Agent. It encompasses all API calls and events defined in the Desktop Agent API. It is used by the @finos/fdc3 npm module to communicate with Browser-Resident Desktop Agents or via the FDC3 Web Connection Protocol (WCP).

  2. Overview of Browser-Resident Desktop Agents (DAs)

    Browser-Resident Desktop Agents are an experimental FDC3 2.2 feature that allow FDC3 applications running in a browser to participate in interop. Unlike 'Preload DAs' (which use Electron or browser extensions to inject interfaces), Browser-Resident DAs run as code within a browser page (iframe or window). They enable a 'Write Once Run Anywhere' (WORA) approach where apps use the getAgent() function from the @finos/fdc3 npm module to retrieve a DesktopAgent interface regardless of the specific DA implementation.

  3. Overview of the FDC3 Interoperability Standard

    FDC3 (Financial Desktop Connectivity and Collaboration Consortium) is an open standard designed to allow desktop applications in financial workflows to interoperate in a plug-and-play fashion without requiring prior bi-lateral agreements. The standard codifies common patterns used for cross-application workflows between web and native applications.

  4. Overview of FDC3 PrivateChannel

    A PrivateChannel is an object used for secure communication between two applications. It extends the Channel interface and provides event handlers to monitor the connection state of both parties. This ensures that Desktop Agents do not need to queue messages sent before a listener is added and allows applications to stop broadcasting when the other party disconnects.

    Desktop Agent implementation requirements:

    • SHOULD restrict external apps from listening or publishing on this channel.
    • MUST prevent PrivateChannels from being retrieved via fdc3.getOrCreateChannel.
    • MUST provide the id value for the channel as required by the Channel interface.

  5. Overview of the FDC3 Standard

    FDC3 is an open-source standard (Apache 2.0 license) hosted by the Fintech Open Source Foundation (FINOS). Its primary goal is to define protocols and taxonomies that enable desktop applications used in financial workflows to interoperate in a plug-and-play manner, eliminating the need for prior bi-lateral agreements between different software vendors.

  6. Overview of the FDC3 Standard

    FDC3 is an open standard designed for interoperability on the financial desktop. It enables cross-application workflows by providing standardized verbs for actions (intents), a common data format for passing identifiers (context data), an OpenAPI-based app directory, and standardized API operations.

  7. Overview of FDC3 PrivateChannel

    The PrivateChannel interface extends the standard Channel to support secure communication between two specific applications. It provides event handlers that notify a participant about the connection state of the other party. This ensures that messages are not queued or retained before a listener is active and allows applications to stop broadcasting when the remote party disconnects.

    Desktop Agent requirements for PrivateChannel:

    • MUST prevent retrieval via fdc3.getOrCreateChannel.
    • SHOULD restrict external apps from listening or publishing on the channel.
    • MUST provide a unique id for the channel.

  8. Overview of FDC3 API Standards

    The FDC3 API standards provide a consistent developer interface designed to enable interoperability between applications and Desktop Agents. The primary goals of these standards are to standardize interfaces for reference implementations and ensure a baseline level of interoperability across different platforms. The API is intentionally kept small and consistent to prioritize ease of adoption over exhaustive functional completeness.

  9. Overview of the FDC3 Desktop Agent Communication Protocol (DACP)

    The Desktop Agent Communication Protocol (DACP) is an experimental wire protocol (introduced in FDC3 2.2) consisting of standardized JSON messages. It allows an application to communicate with a Desktop Agent (DA) to perform API calls and receive events. It is used by the @finos/fdc3 npm module for Browser-Resident Desktop Agents and the FDC3 Web Connection Protocol (WCP).

  10. Overview of the FDC3 Standard

    FDC3 is an open standard designed for interoperability on the financial desktop. It enables cross-application workflows through standardized verbs (intents), a common data format, an OpenAPI app directory standard, and standardized API operations. The standard is composed of five complementary parts:

    1. Desktop Agent API: The interface for the Desktop Agent, which serves as the launcher and message router (broker) for applications.
    2. Intents: A set of verbs used with context data (nouns) to trigger common workflows between applications.
    3. Context Data: A standardized message format for passing identifiers and data between apps.
    4. App Directory: A structured repository containing information about FDC3-enabled applications.
    5. Agent Bridging: An experimental API interface that allows applications running under different Desktop Agents to interoperate.

  11. Overview of FDC3 2.0 Key API Elements

    The FDC3 2.0 API provides a standardized interface for interoperability between desktop agents and applications. The core components include:

    • window.fdc3: The global object used to access FDC3 operations.
    • fdc3Ready: An event triggered when FDC3 operations become available globally.
    • DesktopAgent: The interface that exposes FDC3 operations.
    • Channel: An interface used for subscribing to specific context channels.
    • Listener: An interface used to manage and unsubscribe from intent or context listeners.

  12. Overview of FDC3 Security and Identity Model

    FDC3 Security provides a framework for application identity verification, encrypted communications, and user identity sharing. Because Desktop Agents are treated as untrusted intermediaries, the model relies on asymmetric cryptography: each application maintains a private key (kept secret) and publishes a public key at a stable HTTPS endpoint. This allows applications to independently verify digital signatures and encrypt data without relying on the Desktop Agent for trust.