This Section applies to ASPSPs that have implemented OB Standards
Page Properties
icon
false
id
TC-OB Standards-Production
Implement Open Data v2.2
N/A
Implement Read/Write API Specification v3.1
Conformance certificates being explored.
Implement Customer Experience Guidelines v1.1
Conformance certificates being explored.
Implement App-to-App Redirection
N/A
Browser based redirection only.
Implement OB Security Profile Implementer's Draft v1.1.2
Implement FAPI Profile Implementers Draft 2
Implement CIBA Profile Implementers Draft 1
N/A
Implement Dynamic Client Registration v1.1
N/A
Implement Dynamic Client Registration v3.1
Conformance certificates being explored.
Decommission Read/Write API Specification v1.x/2.x
N/A
Decommission OB Security Profile Implementer's Draft v1.x
N/A
-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
borderStyle
dashed
title
Method of IdentificationSCA-RTS 90-day reauth Implementation
Page Properties
id
ID-Production
Commence support for eIDAS QWAC certificates
Commence support for eIDAS QSEAL certificates
Commence support for OBIE QWAC-like certificates
Commence support for OBIE QSEAL-like certificates
Cease support for OBIE non eIDAS-like certificates for transport
No Plans
We will continue to accept the OB Certificate at the end of the adjustment period in March provided the TPP has identified itself to OBIE using an eIDAS certificate
Cease support for OBIE non eIDAS-like certificates for signing
No Plans
We will continue to accept the OB Certificate at the end of the adjustment period in March provided the TPP has identified itself to OBIE using an eIDAS certificate
Support for MTLS token endpoint authentication
N/A
Only supporting private_key_jwt
Support for private_key_jwt token endpoint authentication
Cease support for client id and client secret token endpoint authentication
N/A
Only supporting private_key_jwt
Panel
titleColor
White
titleBGColor
#6180c3
borderStyle
dashed
title
Post Brexit Certificate Implementation
Page Properties
id
Standards-Production
PRE-BREXIT - Certificates Accepted (until 31st Dec 2020)
eIDAS QWAC
eIDAS QSealC
OB legacy (obtransport, obsigning)
OBWAC
OBSeal
SCA-RTS
Which date are you planning on implementing the SCA reauthentication exemption?
What is your approach to token management to enable application of the reauthentication exemption?(see link to FCA guidance)
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
titleColor
Black
borderStyle
dashed
title
Security Profile
Page Properties
id
ID-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)
POST-BREXIT TRANSITION - Certificates Accepted (1st Jan 2021 - 30th Jun 2021)
eIDAS QWAC
eIDAS QSealC
OB legacy (obtransport, obsigning)
OBWAC
OBSeal
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 authentication
N/A
POST-BREXIT POST TRANSITION - Certificates Accepted (from 1st Jul 2021)
eIDAS QWAC
eIDAS QSealC
OB legacy (obtransport, obsigning)
OBWAC
OBSeal
Other (Please define)
The capability to accept eIDAS certificates is under review and may come into scope at a later date.
Planned Implementation Date to Satisfy FCA's Post Transition
Following the FCA Adjustment Period announcement, SCA has not yet been applied on the bank’s primary online channel / customer interface, and access remains available via screen-scraping. As access is still available through the customer interface, no contingency mechanism is required.
Article 10 - Maximum time period after authentication?
90 days
Article 10 - Endpoints exempt of SCA
Accounts, Balances, Transactions, Products
Authentication Method - Open Banking Channel (Browser)?
When the PSU’s browser reaches the HL web page for authentication they undergo the same authentication process they would coming to HL page directly, namely two steps consisting of:
Identification of the client through validation of a client number and Date of Birth:
Authentication of the client through validation of a online password and secure number
When the RTS come in force in September this will be supplemented, in line with direct client log in, with the validation of a One Time Passcode (OTP) that would have been issued to a clients registered telephone number by SMS or Call Back.
Hybrid flow as described within the Security Implementer guide v1.1.2, with redirect via browser
Authentication Method - Open Banking Channel (APP)?
When the PSU’s browser reaches the HL web page for authentication they undergo the same authentication process they would coming to HL page directly, namely two steps consisting of:
Identification of the client through validation of a client number and Date of Birth:
Authentication of the client through validation of a online password and secure number
When the RTS come in force in September this will be supplemented, in line with direct client log in, with the validation of a One Time Passcode (OTP) that would have been issued to a clients registered telephone number by SMS or Call Back.
Hybrid flow as described within the Security Implementer guide v1.1.2, with redirect via browser
Authentication Method - Private Channel (APP)?
TBC
Authentication Method Implementation Date (Open Banking Channel)?
Proposed
Authentication Method Implementation Date (Private Channel)?
Existing
SCA Implementation Date?
Provisional date depending on developments during the FCA transition period.
SCA Scope? (will it inhibit non PSD2 accounts)
SCA only offered for PSD2 Account and HLSL clients who are linked to SCA accounts.
URL
Brand Landing Pages URL
[You can use this space to explain your guidance on using Brand logos]
