Tracking: Implementers of FAPI 1.0 and FAPI 2.0
Open
@danielfett is already working on this.
Since Jul 11, 2026.
component: FAPI2: Security Profile
migrated-from-bitbucket
priority: minor
type: task
- Dominant language
- HTML
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Originally submitted by Daniel Fett (Daniel Fett) on 2022-11-23
As discussed on the call, we should keep track of implementers and adopters of FAPI 1.0 and FAPI 2.0.
Please update the following table with available information (as far as it can be made public):
| Country | Adopting Body | FAPI Version | Statistics (No. of IDPs/End-Users/etc.) |
|---|---|---|---|
| UK | Open Banking UK | 1.0 Advanced (Some/most using ID2) | ~70 IDPs |
| Australia | ACCC/ConsumerDataRights | 1.0 Advanced (2.0 planned) | |
| Brazil | OpenFinance, OpenInsurance | 1.0 Advanced | |
| Germany | yes.com (private-sector open banking ecosystem) | 2.0 with minor differences | ~1100 banks as IDPs |
| USA | FDX ( https://financialdataexchange.org ) | 1.0 Advanced | |
| New Zealand |
Bitbucket status: new
Bitbucket origin: issue 555
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.