The “Financial API — Part 1: Read Only Security Profile”, which is being developed by the OpenID Foundation’s Financial API WG (FAPI WG), is undergoing final review before the Implementer’s Draft1 vote. The Implementer’s Draft vote is intended to lock in the technical elements and the related intellectual property. Once it becomes an Implementer’s Draft, implementers will be free to implement it, which makes this an important milestone.
If you are interested, please join the WG (free of charge) and raise any issues in the issue tracker.
The table of contents is provided below.
Financial Services – Financial API – Part 1: Read Only API Security Profile
- Financial Services – Financial API – Part 1: Read Only API Security Profile
- Financial Services – Financial API – Part 1: Read Only API Security Profile
Footnotes
Related posts
Public Review of “Financial API – Part 1: Read Only API Security Profile” Has Begun
The OpenID Foundation’s Financial API (FAPI) Working Group has recommended commencing a public review prior to the vote to approve Financial API – Part 1: Read Only API…
Please Vote on the Implementer’s Draft for FAPI Part 2
The OpenID Financial API (FAPI) Working Group has recommended that “Financial API – Part 2: Read and Write API Security Profile” be approved as an OpenID…
Financial API — Please Vote on the Read-Only Security Profile!
The OpenID Foundation in the United States is currently holding an Implementer's Draft vote, open until February 10, on “Financial API Part 1 -- Read only…