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 Implementer’s Draft.
An Implementer’s Draft is a draft that implementers can use with confidence in terms of both intellectual property and technical stability. It is the stage immediately before the final version.
The specification being voted on is available at http://openid.net/specs/openid-financial-api-part-2.html.
Voting is open until 7/24 at https://openid.net/foundation/members/polls/126.
We kindly ask you to vote early.
Related posts
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…
Financial-grade API (FAPI) Security Profile Parts 1 and 2, and JWT Secured Authorization Response Mode (JARM), Have Entered Public Review Prior to the Implementer’s Draft Vote.
The OpenID Financial-grade API Working Group has recommended that the following draft specifications be approved as OpenID Implementer's Drafts. Financial-grade API - Part 1: Read-Only API…
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…