fapi /

Filename Size Date modified Message
27.5 KB
resolves Issue #192 by rewording authorization_signed_response_alg client metadata parameter to more clearly suggest that the default is applied when doing the signing and not that the default needs to be applied and persisted with client config or registration
20.5 KB
Lodging Intent: Minor edits and Security Considerations
35.1 KB
First attempt at the intro to the FAPI spec
25.2 KB
Merged in josephheenan/fapi/key-sizes (pull request #96)
31.4 KB
Merged in josephheenan/fapi/restrict-aud (pull request #95)
18.8 KB
Replace references to RFC6736 with RFC7636
30.0 KB
Replace references to RFC6736 with RFC7636
11.6 KB
Replace references to RFC6736 with RFC7636
16.4 KB
Merged in dgtonge/fapi/ciba-signed-request (pull request #91)
9.1 KB
Added Markdown to HTML instructions
1.4 KB
README.md edited online with Bitbucket
17.9 KB
TR-Cross_browser_payment_initiation_attack.md edited online with Bitbucket
583.3 KB
Add the Cross Browser Payment Initiation Attack document
126.2 KB
Update markdown of CBPI-Attack
94.3 KB
Update markdown of CBPI-Attack
78.7 KB
refactored document to focus on OAuth-based solution, generic mitigation has been moved to appendix
109.2 KB
refactored document to focus on OAuth-based solution, generic mitigation has been moved to appendix
126.0 KB
Update markdown of CBPI-Attack
113.4 KB
added Products entities and endpoints
1.7 KB
index.html created
112.0 KB
rename "logincal model.png" to logical_model.png
104.5 KB
added diagrams

README

This is the official repository for OpenID Foundation Financial API (FAPI) Working Group.

What is this repository for?

  • Financial API
  • Version 0.1

OpenID Foundation FAPI Working Group is creating a Financial API standard that is applicable internationally. It is taking requirements from Open Banking Standard document, and has started working on based on the contributed FS-ISAC Durable Data API.

You can find the overview and rationale of the working group at the WG page.

Contribution guidelines

  • You MUST Execute Contributor Agreement either by
    • Electronic Signature and notify openid-specs-fapi-owner@lists.openid.net; OR
    • print this PDF and fill, sign, scan, and send it to openid-specs-fapi-owner@lists.openid.net.
  • You MUST file an issue to the issue tracker before contributing a code.
  • You MUST test that the contributed code compiles without error.

Who do I talk to?

  • The chairs of the WG can be reached at openid-specs-fapi-owner@lists.openid.net