Thanks to everyone’s support, FAPI Part 2 has become an Implementer’s Draft. We were concerned that we might not reach quorum because more people than expected were on vacation, but we managed to meet the quorum and it was duly approved as an Implementer’s Draft.
I would like to express my sincere gratitude to everyone who helped.
With this, both FAPI Parts 1 and 2 are now available.
The top 9 banks in the UK are currently coding profiles based on this, aiming for a cutover on January 13. 1 but the overall framework is now settled. One area where I currently expect revisions will probably be needed is the JWS cryptographic suite. At present, it specifies PS256 and ES256, but I anticipate cases in which the HSMs (Hardware Security Modules) used by banks support only RS256. If so, based on that feedback, I expect wording will be added to permit the use of RS256 when an HSM supports only RS256 or below.
Footnotes
Related posts
OpenAI Launches Sign in with ChatGPT (Based on OpenID Connect)
(Work in progress; last updated 2026-10-02 12:39 JST) On September 29, at DevDay 2026, OpenAI officially announced Sign in with ChatGPT (SIWC). I would like to…
We Submitted Public Comments on the FSA’s Proposed Partial Amendments to the “Comprehensive Guidelines for Supervision of Financial Instruments Business Operators, etc.”
The U.S.-based OpenID Foundation submitted the following public comments on the Proposed Partial Amendments to the “Comprehensive Guidelines for Supervision of Financial Instruments Business Operators, etc.”…
When Software Becomes Staff: Governance, Security, and Safety for Agentic AI
Below is the transcript of my keynote speech at EIC 2026 on May 19, 2026. The slides are provided as a PDF at the end of…