Directory? | Other |
|
|
|---|
Location of Well Known Endpoints? | Developer Portal |
|
|
|---|
API Standard Implemented? | The Berlin Group | PSD2 compliant XS2A |
|
|---|
Name of Account Holder Implementation Date? | Completed - |
|
|
|---|
| Date of Current eIDAS Implementation? |
| QWAC |
|
|---|
| Current Certificates used for Identification? |
|
|
|
|---|
| Current Certificates used for Transport? |
|
|
|
|---|
| Current Certificates used for Signing? |
|
|
|
|---|
| Date of Future eIDAS Implementation? | No future update currently planned. |
|
|
|---|
| Future Certificates used for Identification? |
|
|
|
|---|
| Future Certificates used for Transport? |
|
|
|
|---|
| Future Certificates used for Signing? |
|
|
|
|---|
Major Milestones |
|
|
|
|---|
| Brand(s) |
|
|
|
|---|
| Security Profile? |
| The Open ID Foundation's Financial Grade API (FAPI) is not used |
|
|---|
| Security Profile Certification? |
|
|
|
|---|
CIBA | No | The Open ID Foundation's Financial Client Initiated Back-Channel Authentication is not used) |
|
|---|
| Using Open Banking as your eIDAS Trust Framework? | No |
|
|
|---|
| Are you caching the Directory? | No |
|
|
|---|
| Transaction IDs |
| - ASPSPs provide a Unique, Immutable TransactionID from their core system
- ASPSPs generate a Unique TransactionID from a set of Immutable fields
- ASPSPs specify field(s) for TPP to generate a Unique Transaction Identifier
- ASPSPs provide neither a TransactionID nor the method by which TPPs can generate one
|
|
|---|