FAPI Part 2 passed the Implementer's Draft vote

Thanks to you, FAPI Part 2 has become an Implementer's Draft. There were many people on vacation, so we were worried whether we could meet the quorum, but we managed to meet the quorum and the Implementer's Draft was happily approved.

We would like to express our deepest gratitude to everyone who helped us.

Now, FAPI Part 1 and Part 2 are complete.

• FAPI Part 1 – Read Only Security Profile
• FAPI Part 2 – Read Write Security Profile

Implementation Feedback¹There will probably be some slight adjustments in response to this, but the general outline is now set. One area that we are thinking of that will likely require adjustment is the JWS cipher suite. Currently, it is PS256 and ES256, but we suspect that there will be cases where the HSMs (Hardware Security Modules) used by banks only support RS256. In that case, based on that feedback, we will insert a statement that allows the use of RS256 if the HSM only supports RS256 or lower.

1. The top nine UK banks are currently coding profiles based on this, with the cutover scheduled for January 9th next year.