FDX

The Financial Data Exchange (FDX) specifies a common, interoperable, royalty-free standard and operating framework for financial data sharing and secure authentication. It also provides user experience and consent guidelines.

FDX is a nonprofit, independent subsidiary of the Financial Services Information Sharing and Analysis Center (FS-ISAC), an industry consortium with the mission of ensuring resilience and continuity of the global financial services infrastructure. Operating in the US and Canada, FDX is a technical organization which does not involve in policy discussions.

FDX Members

As of August 2021, FDX has approximately 197 members including financial institutions, aggregators, financial industry groups, consumer advocacy groups, permissioned parties, and other financial services organizations.

Data providers that are on the board of both Akoya and FDX are:

• Bank of America
• Capital One
• Citi
• Fidelity Investments
• JPMorgan Chase & Co.
• PNC
• TD Bank
• Truist
• US Bank
• Wells Fargo

Some FDX data recipients:

• American Express
• Experian
• Finicity
• Fiserv
• H&R Block
• MorningStar
• MX
• Plaid
• Quicken
• Truelayer
• Yodlee

If you are interested in joining FDX, you may explore membership options and read the organizational overview: "The Global Industry Standard for Consumer Access to Financial Data".

Benefits

FDX specifications unify financial data sharing implementations which can vary from organization to organization. By adopting the FDX API as an industry standard, data providers and data recipients no longer need to spend extra time and resources resolving problems caused by inconsistent data connectivity, quality, and governance. Consumers will also benefit from a consistent standard across financial services platforms for strengthened control, access, transparency, traceability, and security of their financial data.

📌

Membership not required

While data providers and recipients receive the value of FDX with the Akoya Data Access Network, the Network does not require data providers or data recipients to be FDX members.

Benefits for data providers

The benefits of FDX standards include risk reduction and improved privacy. The FDX API supports Open ID Connect (OIDC) token-based access that eliminates risks posed by “held-away credentials[1].” The consent from the consumer for data sharing is captured both at the application interface (e.g. the fintech app) and the provider's data source. This clear and secure consent flow allows consumers to better manage data that they want to share with third parties[2].

Benefits for data recipients

The interoperability of FDX standards allows recipients to access financial data from providers easily and securely. Akoya, following the FDX standard with some customizations, translates responses from providers through data mapping and API integration to render a unified format for recipients. This unified format ensures consistent data to ease integration efforts. It also reduces time spent with bespoke integrations and disparate data structures.

API specs

Formerly FS-ISAC's Durable Data API (DDA), the FDX API specification is updated twice a year. The specifications provide the introduction and transmission protocol details for implementing with RESTful APIs. Akoya leverages these standards to enable financial data sharing via secure tokenized access.

FDX provides fee-free access to specifications by accepting the intellectual property agreement. Join or request API access here.

Best Practices

The FDX 2020 Fall Release added UX guidelines with widespread acceptance from the FDX API implementers, including major financial institutions. The FDX UX Guidelines[3] specify design recommendations for permissioning. The guidelines also describe the concepts of financial data sharing, data flow, and an end-user grant consent journey for financial data sharing.

According to the guidelines, the financial data flow process from a provider to a recipient has the following steps:

1. The recipient initiates data sharing when the end-user decides to access their accounts.
2. The end-user identifies the provider where they hold their accounts.
3. The provider inspects the request and allows the end-user to grant consent for data sharing.

[1]: Held-away (shared) credentials or screen scraping allows a 3rd party to hold an end-user's credentials.

[2]: If you are interested in learning more about the benefits of FDX, you may explore its member benefits page.

[3]: Financial Data Exchange User Experience (UX) Guidelines v1.0. Dec. 2020, fdx.atlassian.net/wiki/download/attachments/772964368/UX%20Guidelines%20v1_0.pdf?api=v2.