Directory? | Open Banking | Open Banking Directory through Token.io |
|
|---|
Location of Well Known Endpoints? | OB Technical Directory |
|
|
|---|
API Standard Implemented? | Open Banking | Sandbox Environment – App Creation by TPP and after TBUK Approval Production Environment – App Creation by TPP and after TBUK Approval |
|
|---|
Name of Account Holder Implementation Date? | N/A |
|
|
|---|
| Date of Current eIDAS Implementation? |
| MTLS with eIDAS Certificates |
|
|---|
| 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 | June 2019 for test facility October 2019 for production APIs |
|
|
|---|
| Brand(s) |
|
|
|
|---|
Security Profile? | TBC |
|
|
|---|
| Security Profile Certification? | TBC |
|
|
|---|
CIBA | No |
|
|
|---|
| Using Open Banking as your eIDAS Trust Framework? | No |
|
|
|---|
| Are you caching the Directory? | No |
|
|
|---|
| Transaction IDs | TBC | - 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
|
|
|---|