Directory? | Open Banking |
|
|
|---|
Location of Well Known Endpoints? | OB Technical Directory and Dev Portal |
|
|
|---|
API Standard Implemented? | Open Banking |
|
|
|---|
Name of Account Holder Implementation Date? | TBC | No confirmed date in short or medium term |
|
|---|
| Date of Current eIDAS Implementation? | |
|
|
|---|
| Current Certificates used for Identification? | OB Transport + ClientID + Secret
OBWAC / OBSEAL/ QWAC |
|
|
|---|
| Current Certificates used for Transport? | OB Transport / OBWAC / QWAC |
|
|
|---|
| Current Certificates used for Signing? | OB Signing / OBSEAL / QSEAL |
|
|
|---|
| Date of Future eIDAS Implementation? | |
|
|
|---|
| Future Certificates used for Identification? | N/A - No further updates planned |
|
|
|---|
| Future Certificates used for Transport? | N/A - No further updates planned |
|
|
|---|
| Future Certificates used for Signing? | N/A - No further updates planned |
|
|
|---|
Major Milestones | N/A | (Inc Other Products, API Updates, API Deprecations, etc) |
|
|---|
| Brand(s) |
|
|
|
|---|
Security Profile? | Open Banking V1.X |
|
|
|---|
| Security Profile Certification? | No |
|
|
|---|
CIBA | N/A |
|
|
|---|
| Using Open Banking as your eIDAS Trust Framework? | Yes, JWKS for TPP’s and the EC trusted list for eIDAS QTSP’s |
|
|
|---|
| Are you caching the Directory? | Yes |
|
|
|---|
| Transaction IDs | Date TBC - Option 4 Supported | 4. ASPSPs provide neither a TransactionID nor the method by which TPPs can generate on |
|
|---|