Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panel
titleColorBlack
borderStyledashed
titleOB Standards

This Section applies to ASPSPs that have implemented OB Standards

N/A
Page Properties
iconfalse
idTC-OB Standards-Production
Implement Open Data v2.2N/AImplement Read/Write API Specification v3.114 Sept 2019 Implement Customer Experience Guidelines v1.114 Sept 2019 Implement App-to-App Redirection30 Nov 2020Implement OB Security Profile Implementer's Draft v1.1.214 Sept 2019 Implement FAPI Profile Implementers Draft 2N/AImplement CIBA Profile Implementers Draft 1N/AImplement Dynamic Client Registration v1.1N/AImplement Dynamic Client Registration v3.114 Sept 2019 Decommission Read/Write API Specification v1.x/2.xN/ADecommission OB Security Profile Implementer's Draft v1.x


-Have you Implemented OB Standards?
  •  Yes
  •  No

Open Data - Which version have you Implemented?
  •  None
  •  V2.2
  •  V2.3
  •  V2.4

Read/Write API Specification Implemented or planning to implement

(Lowest version = Current, Highest version = Planned)

  •  V3.0
  •  V3.1
  •  V3.1.1
  •  V3.1.2
  •  V3.1.3
  •  V3.1.4
  •  V3.1.5
  •  V3.1.6
  •  V3.1.7
  •  V3.1.8
  •  v3.1.9
  •  v3.1.10
  •  V3.1.11
  •  V4.0

Read/Write API - Which date are you planning to implement your latest version?

Have you implemented v4.0 information flows, if not date planned to Implement?

  •  Already Implemented
  •  Planning to implement
  •  Not planning to implement 

Dynamic Client Registration - Which version have you Implemented or planning to implement?

(Lowest version = Current, Highest version = Planned)

  •  None
  •  V3.1
  •  V3.2
  •  V3.3

DCR - Which date are you planning to implement your latest version?

Have you implemented Trusted beneficiaries, if not date planned to Implement?

  •  Already Implemented
  •  Planning to implement
  •  Not planning to implement 

Have you implemented Reverse Payments, if not date planned to Implement?

  •  Already Implemented
  •  Planning to implement
  •  Not planning to implement 

Have you implemented ECA Standard?

  •  Already Implemented
  •  Planning to implement
  •  Not planning to implement 

ECA Implementation details


Contact: [enter contact details for the relevant person(s) at your organisation]

[You can use this space to provide your status with respect to the Standard]

Have you implemented Bulk/File Payments?

  •  Already Implemented
  •  Planning to implement
  •  Not planning to implement 

Have you implemented VRP – Sweeping, if not date planned to Implement?

  •  Already Implemented
  •  Planning to implement
  •  Not planning to implement 

Have you implemented VRP non-Sweeping, if not date planned to Implement?

  •  Already Implemented
  •  Planning to implement
  •  Not planning to implement 

Contact: [enter contact details for the relevant person(s) at your organisation]

[You can use this space to provide implementation details relevant to VRP]
PISP - Single Payment Limit£
PISP - Daily Payment Limit£
How many months of transaction do you provide?

Have you implemented TRIs (Transactional Risk Indicators), if not, date planned to Implement?

What is your approach to Implementing TRIs?
  •  Accept payload with TRI fields – Process all fields
  •  Accept payload with TRI fields – Ignore all fields
  •  Reject payload with TRI fields – Error back to TPP
  •  Accept payload with TRI fields – Process few fields (Provide list of accepted fields)  




panel
Panel
borderStyledashed
titleMethod of IdentificationSCA-RTS 90-day reauth Implementation


Page Properties
idID-Production
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/ASupport for private_key_jwt token endpoint authentication14 Sept 2019 Cease support for client id and client secret token endpoint authenticationNot Planned
Panel
borderStyledashed
titleImplementation
Page Properties
idTC-IMP
Page Properties
idTC-IMP

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 CertificateCurrent Certificates used for Signing?OBSeal / OB Signing CertificateDate of Future eIDAS Implementation?N/AFuture Certificates used for Identification?N/AFuture Certificates used for Transport?

N/A

Future Certificates used for Signing?N/A

Major Milestones

Brand(s)

Security Profile?

Security Profile Certification?Yes  

CIBA

NoUsing Open Banking as your eIDAS Trust Framework?YesAre you caching the Directory?NoTransaction 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
SCA-RTS


Which date are you planning on implementing the SCA reauthentication exemption?

by 31/12/2022

This date has been revised to 31/03/2023 due to other priorities. 


What is your approach to token management to enable application of the reauthentication exemption? (see link to FCA guidance)

AIS consents created after the implementation of the changes will remain valid until the Consent Expiry Date, if set. They will not normally need to be reauthenticated. If Consent does not have expiration date, re-authentication date will be set as virtual infinity date. 

Note that Kleinwort Hambros does not have any live consent and working AISP except internal test TPP.

Example approach:
Issue a long-lived refresh token during one final SCA, with refresh token rotation implemented.

[Please use this space to provide more details on your approach]

Article 10A - Endpoints exempt of SCA-RTS
  •  

    Accounts

  •  

    Transactions (90days)

  •  

    Balances

  •  

    Standing orders

  •  

    Direct debits

  •  

    Beneficiaries

  •  

    Products

  •  

    Offers

  •  

    Parties

  •  

    Scheduled Payments

  •  

    Statements


Article 10A - Endpoints not exempt of SCA-RTS
  •  

    Transactions (more than 90days)

  •  

    Standing orders

  •  

    Direct debits

  •  

    Beneficiaries

  •  

    Products

  •  

    Offers

  •  

    Parties

  •  

    Scheduled Payments

  •  

    Statements


Article 10A - Maximum time period after authentication
Please specify the time period in minutes
SCA-RTS implementation status (updated by OBL PS team only)


Planned / In-progress / Implemented / TBC




Panel
titleColorBlack
borderStyledashed
titleSecurity Profile


Page Properties
idID-Production


-Which Security profile have you Implemented or planning to implement?

(Lowest version = Current, Highest version = Planned)

  •  OB Security Profile (Legacy)
  •  FAPI (ID2)
  •  FAPI 1 Advanced
  •  Other (Please define) 

Security Profile - Next Planned Version Implementation Date

CIBA Profile - Implemented or planning to implement

(Lowest version = Current, Highest version = Planned)

  •  None
  •  CIBA
  •  CIBA FAPI Profile

CIBA Profile - Next Planned Version Implementation Date

Security Profile Certification date?
 

Token Endpoint Authentication Methods Supported
  •  
    client_secret_post
  •  
    client_secret_basic
  •  
    client_secret_jwt
  •  
    tls_client_auth
  •  Private_key_jwt

Planned date to Cease support for client id and client secret token endpoint authenticationNot planned
POST-BREXIT POST TRANSITION - Certificates Accepted (from 1st Jul 2021)
  •  eIDAS QWAC
  •  eIDAS QSealC
  •  OB legacy (obtransport, obsigning)
  •  OBWAC
  •  OBSeal
  •  Other (Please define) 




Panel
titleColorBlack
borderStyledashed
titleCustomer Journey


No
Page Properties
idTC-CJ


-What is your approach to Implementing OBL Customer Experience Guidelines

?Yes

(CEG)?

(tick all that apply)

  •  Already Implemented
  •  Planning to implement or upgrade
  •  Not planning to implement CEG
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?

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

Support Embedded Flow?

Which version have you implemented or planning to implement?

(Lowest version = Current, Highest version = Planned)

  •  V3.1.2
  •  V3.1.3
  •  V3.1.4
  •  V3.1.5
  •  V3.1.6
  •  V3.1.7
  •  V3.1.8
  •  v3.1.9
  •  v3.1.10
  •  V3.1.11
  •  V4.0

Which date are you planning to implement your latest CEG version?

Redirection Model
  •  App to App redirection
  •  Decoupled authentication
  •  Embedded Flow
  •  Bespoke User Journeys




Dev Portal URL?
Panel
titleColorBlack
borderStyledashed
titlePSD2


Page Properties
idTC-PSD2


Dispute Management System?

YesFCA Adjustment Period - Maintaining Screen Scraping?
-Which Directory are you using as your Trust Framework?Open Banking
Are you caching the Directory?No
Transaction IDs SupportedOption 2

2. ASPSPs generate a Unique TransactionID from a set of Immutable fields

Are you Seeking Fallback Exemption?

  •  Yes

Adjusted or Fallback Interface?

NoAdjusted or Fallback URL?N/AContact Email or Phone Number?

Phone : +442075973000

Email : openbankingsupport@kleinworthambros.com

  •  No


Article 10 - Maximum time period after authentication

Article 10 - Endpoints exempt of SCA



Major Milestones

Brand(s)




Panel
titleColorBlack
borderStyledashed
titleASPSP Dev Portal and Contact Details


Page Properties
idTC-C


Location of Well Known Endpoints

OB Technical Directory

Modified Customer Interface URL (if applicable)



Dev Portal URLhttps://www.kleinworthambros.com/en/our-services/banking-and-deposits/open-banking/
Test Facility
Implementation Date?
 Production Interface Implementation Date? Contingency MeasuresPlease 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 requireArticle 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 SCAPlease 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

URL

Brand Landing Pages URL
[You can use this space to explain your guidance on using Brand logos]

ASPSP Support Desk Email or Phone Number

(including queries about consent success rates) 

Phone : +442075973000

Email : openbankingsupport@kleinworthambros.com





Panel
titleColorBlack
borderStyledashed
titleKey Implementations


  Functional Certificate (PIS): SG Kleinwort Hambros Bank 2019

Page Properties
idTC-HCC


High Cost Credit

TBC

View file
nameHCC.xlsx
height250

Page Properties
idTC-W7

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

-