Implement OB Security Profile Implementer's Draft v1.1.2
COMPLETE
Implement FAPI Profile Implementers Draft 2
Phased migration to FAPI 2 by Q1 2020
Update 22/05 - TPPs are reminded that notifications were sent in December 2019 / March 2022020 that Barclays would enforce FAPI rules from 31st March 2020. This was delayed due to COVID however there are still some TPPs that have not movmigrated and so we request that this is completed as soon as possible. If there are issues / blockers then please reach out to the team.
Implement CIBA Profile Implementers Draft 1
TBC
Plans to be confirmed
Implement Dynamic Client Registration v1.1
Not Delivered
Implement Dynamic Client Registration v3.1
TBC
Plans to be confirmed
Decommission Read/Write API Specification v1.x/2.x
Plans to decommission AIS v1 / v2 in May - however this has been delayed due to COVID
Decommission OB Security Profile Implementer's Draft v1.x
TBC - No Plans
...
Panel
borderStyle
dashed
title
Implementation
Page Properties
id
TC-IMP
Directory?
Open Banking
Location of Well Known Endpoints?
OB Technical Directory
API Standard Implemented?
Open Banking
Name of Account Holder Implementation Date?
Completed - September 2019
Date of Current eIDAS Implementation?
September 2019
Current Certificates used for Identification?
OB Transport + ClientID + Secret OBWAC
Current Certificates used for Transport?
OB Transport / OBWAC
Current Certificates used for Signing?
OB Signing / OBSEAL
Date of Future eIDAS Implementation?
March 2020
As of the 14th of March, TPP’s will be able to onboard via two routes with Barclays inclusive of, uploading QWAC and QSEAL certificates directly to the OB directory, and will be required to use existing manual / BDN APP to onboarding using the SSA generated on OB directory. The second route is to directly onboard to Barclays by invoking the Barclays Dynamic Client Registration APIs using eIDAS certificates. Please refer to Barclays Developer Network for further information on Barclays implementation of DCR.
Future Certificates used for Identification?
OBWAC / QWAC
Future Certificates used for Transport?
OBWAC / QWAC
Future Certificates used for Signing?
OBSEAL / QSEAL
Major Milestones
v3.1 –
v3.1.1 –
Implementation of all AIS / PIS / CoF end points COMPLETE
AIS / PIS / CoF journeys supported for following payment account types:
Current Accounts (Personal and Business)
Current Accounts (Corporate)
Savings Accounts (Personal and Business)
Personal Credit Cards (Barclaycard)
Corporate Credit Cards
Currency Accounts (Personal and Business)
Currency Accounts (Corporate)
Pingit E-Wallets
Please see Note for Important Information *
Future Delivery Dates
P2 2WR / Event Notification API –
P7 Refunds (Payments v3.1.4) – TBC
Waiver 007 (Payment Signing, v3.1.4) – - No changes are needed before this date. Once this is completed, it’s important to note validation will be completed against all v3 payment requests, to avoid payment failures you’ll need to make your changes from our implementation date
Note that Account Holder Name for PCA / BCA / Pingit customers is available through PARTIES end point and through ACCOUNTS end point for Barclaycard UK, Barclaycard Commercial Payment and Barclays Corporate customers
IMPORTANT INFORMATION
In order to complete Open Banking journeys, you will need to establish the Identity Provider (IDP) authentication method for your implementation.
An IDP is a system to authenticate and gain permission from an end user - such as a customer, to access their resources e.g. their account data. For Open Banking, this is used to authenticate the customer providing the consent to the Third Party.
Examples of an IDP in Open Banking includes Barclays app (Personal and Business Banking customers) and iPortal (Barclays Corporate clients), but we have a number of methods depending on the customer type and digital channel that they use. This needs to be considered in your development.
The latest OpenID configuration (OIDC) URLs available are shown below
TPPs are reminded that latest URLS MUST be used and where a legacy URL is still being used then TPP MUST migrate to URLs below
Note - some Business Banking clients will require the Corporate Banking IDP as they use Corporate Banking services to fulfil their business requirements and some Corporate clients will require the Business Banking IDP as they use Business Banking services to fulfil their business requirements
Brand(s)
Security Profile?
Currently Open Banking Security Profile
Phased migration to FAPI 2 by Q1 2020
Update 22/05 - TPPs are reminded that notifications were sent in December 2019 / March 2022020 that Barclays would enforce FAPI rules from 31st March 2020. This was delayed due to COVID however there are still some TPPs that have not movmigrated and so we request that this is completed as soon as possible. If there are issues / blockers then please reach out to the team.
Security Profile Certification?
Yes
CIBA
TBC - No plans
Using Open Banking as your eIDAS Trust Framework?
TBC
Are you caching the Directory?
Transaction IDs
March 2019 - Option 3 Supported
3 (longer term commitment to option 1)
Panel
borderStyle
dashed
title
Customer Journey
Page Properties
id
TC-CJ
Implementing Customer Experience Guidelines?
Yes
Implementing Bespoke User Journeys?
No
Implementing App to App?
Yes
App to App Implementation Date?
Live
Options on 90 day re-authentication?
90 day re-authentication required across all Open Banking flows