Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

OB Standards
Implement Open Data v2.2N/A
Implement Read/Write API Specification v3.114 Sept 2019 
Implement Customer Experience Guidelines v1.114 Sept 2019 
Implement App-to-App Redirection30 Nov 2020
Implement OB Security Profile Implementer's Draft v1.1.214 Sept 2019 
Implement FAPI Profile Implementers Draft 2N/A
Implement CIBA Profile Implementers Draft 1N/A
Implement Dynamic Client Registration v1.1N/A
Implement Dynamic Client Registration v3.114 Sept 2019 
Decommission Read/Write API Specification v1.x/2.xN/A
Decommission OB Security Profile Implementer's Draft v1.xN/A
Method of Identification
Commence support for eIDAS QWAC certificatesN/AAs per agreement between OBIE and FCA we will allow TPP's to register with OBIE Directory using eIDAS and swap these out for OBIE certs for communications with us. This is referred to as the Open Banking eIDAS Trust Framework. 
Commence support for eIDAS QSEAL certificates
N/A
As per agreement between OBIE and FCA we will allow TPP's to register with OBIE Directory using eIDAS and swap these out for OBIE certs for communications with us. This is referred to as the Open Banking eIDAS Trust Framework.

Commence support for OBIE QWAC-like certificates

14 Sept 2019 
Commence support for OBIE QSEAL-like certificates14 Sept 2019 
Cease support for OBIE non eIDAS-like certificates for transportN/AWill cease support for OBIE non eIDAS-like certificate for transport when OBIE cease support for non eIDAS-like certificate
Cease support for OBIE non eIDAS-like certificates for signingN/AWill cease support for OBIE non eIDAS-like certificate for signature when OBIE cease support for non eIDAS-like certificate
Support for MTLS token endpoint authenticationN/A
Support for private_key_jwt token endpoint authentication14 Sept 2019 
Cease support for client id and client secret token endpoint authenticationNot Planned
Post Brexit Certificate Implementation
PRE-BREXIT - Certificates Accepted (until 31st Dec 2020)
  • eIDAS QWAC
  • eIDAS QSealC
  • OB legacy (obtransport, obsigning)
  • OBWAC
  • OBSeal
  • Other (Please define) 

POST-BREXIT TRANSITION - Certificates Accepted (1st Jan 2021 - 30th Jun 2021)
  • eIDAS QWAC
  • eIDAS QSealC
  • OB legacy (obtransport, obsigning)
  • OBWAC
  • OBSeal
  • Other (Please define) 

POST-BREXIT POST TRANSITION - Certificates Accepted (from 1st Jul 2021)
  • eIDAS QWAC
  • eIDAS QSealC
  • OB legacy (obtransport, obsigning)
  • OBWAC
  • OBSeal
  • Other (Please define) 

Planned Implementation Date to Satisfy FCA's Post Transition



TPP PSU Migration Outcomes Supported



POST-BREXIT Certificate Implementation Status (updated by OBIE IES team)



Implementation

Directory?

Open Banking

Location of Well Known Endpoints?

OB Technical Directory

API Standard Implemented?

Open Banking

Name of Account Holder Implementation Date?

Completed -  

Date of Current eIDAS Implementation?14 Sept 2019 OBWAC/OBSeal, As per agreement between OBIE and FCA we will allow TPP's to register with OBIE Directory using eIDAS and swap these out for OBIE certs for communications with us. This is referred to as the Open Banking eIDAS Trust Framework.
Current Certificates used for Identification?

OBWAC / OB Transport Certificate



Current Certificates used for Transport?OBWAC / OB Transport Certificate

Current Certificates used for Signing?OBSeal / OB Signing Certificate

Date of Future eIDAS Implementation?N/A

Future Certificates used for Identification?N/A

Future Certificates used for Transport?

N/A



Future Certificates used for Signing?N/A

Major Milestones




Brand(s)


Security Profile?




Security Profile Certification?
Yes  

CIBA

No

Using Open Banking as your eIDAS Trust Framework?Yes

Are you caching the Directory?No

Transaction IDsOption 2
  1. ASPSPs provide a Unique, Immutable TransactionID from their core system
  2. ASPSPs generate a Unique TransactionID from a set of Immutable fields
  3. ASPSPs specify field(s) for TPP to generate a Unique Transaction Identifier
  4. ASPSPs provide neither a TransactionID nor the method by which TPPs can generate one

Customer Journey

Implementing Customer Experience Guidelines?

Yes

Implemented as of 14th of June 2019

Current CEG Version?

Next CEG Version?

Next Version Implementation Date

Implementing Bespoke User Journeys?

No

Implementing App to App?

Yes
App to App Implementation Date?30 Nov 2020
Options on 90 day re-authentication?Yes

Support Embedded Flow?

No
PSD2

Dispute Management System?

Yes
FCA Adjustment Period - Maintaining Screen Scraping?

Seeking Fallback Exemption?

Yes

Adjusted or Fallback Interface?

No
Adjusted or Fallback URL?N/A
Contact Email or Phone Number?

Phone : +442075973000

Email : openbankingsupport@kleinworthambros.com


Dev Portal URL?https://www.kleinworthambros.com/en/our-services/banking-and-deposits/open-banking/

Test Facility Implementation Date?

 
Production Interface Implementation Date? 
Contingency Measures
Please specify the location of the guidance that explains your strategy and plans for when your dedicated interface is unavailable.  This should be a URL to your dev portal or artefact that provides TPPs with the information they require
Article 10 - Maximum time period after authentication?

Please specify how long the AISP has from the time when they receive the access token (after PSU authentication).  This is the period the AISP must submit their first request before SCA will be re-applied to endpoints NOT exempt of SCA under Article 10.  ASPSPs should consider that this timeline is consistent with the time limit applied by the ASPSP in the existing online PSU interface (i.e. before the PSU is logged out)

Article 10 - Endpoints exempt of SCA
Please specify which AIS endpoints will be exempt from SCA under Article 10. (delete as appropriate): Accounts, Balances, Transactions, Beneficiaries, Direct Debits, Standing Orders, Products, Offers, Parties, Scheduled Payments, Statements

Authentication Method - Open Banking Channel (Browser)?

Device binding, OTP-based PIN/Biometric 14/06/2019

Device binding, notification-based PIN/Biometric 31/10/2019


Authentication Method - Open Banking Channel (APP)?

Device binding, OTP-based PIN/Biometric 14/06/2019

Device binding, notification-based PIN/Biometric 31/10/2019


Authentication Method - Private Channel (Browser)?

Device binding, notification-based PIN/Biometric 14/09/2019


Authentication Method - Open Banking Channel (APP)?

Device binding, notification-based PIN/Biometric 14/09/2019


Authentication Method Implementation Date (Open Banking Channel)?

 

Authentication Method Implementation Date (Private Channel)?

 

SCA Implementation Date?

 
SCA Scope? (will it inhibit non PSD2 accounts)

PSD2 Only


Key Implementations

High Cost Credit

TBC

After Waiver 7 Expiry (16/06/20) option supported: Option 1 - The parameter b64 being set to FALSE OR Option 2 - The b64 claim not being in the header

-

  Functional Certificate (PIS): SG Kleinwort Hambros Bank 2019
  • No labels