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 18 Next »

OB Standards
Implement Open Data v2.2

Implement Read/Write API Specification v3.1

Implement Customer Experience Guidelines v1.1

Implement App-to-App Redirection

Implement OB Security Profile Implementer's Draft v1.1.2

Implement FAPI Profile Implementers Draft 2

Implement CIBA Profile Implementers Draft 1

Implement Dynamic Client Registration v1.1

Implement Dynamic Client Registration v3.1

Decommission Read/Write API Specification v1.x/2.x

Decommission OB Security Profile Implementer's Draft v1.x

Method of Identification
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

Cease support for OBIE non eIDAS-like certificates for signing

Support for MTLS token endpoint authentication

Support for private_key_jwt token endpoint authentication

Cease support for client id and client secret token endpoint authentication

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

test1

test1
TPP PSU Migration Outcomes Supported (refer: POST-BREXIT Certificate Migration Outcomes)

test

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



Implementation

Directory?

MCI

Location of Well Known Endpoints?

OB Technical Directory

API Standard Implemented?

Open Banking

Name of Account Holder Implementation Date?

TBC

Date of Current eIDAS Implementation?
eIDAS
Current Certificates used for Identification?

2021



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

September 2019 – API delivered by Bank ABC development team to ABC International Bank ABC

October 2019 – Testing commences with 3rd party


Brand(s)


Security Profile?




Security Profile Certification?


CIBA

No

Using Open Banking as your eIDAS Trust Framework?Yes

Are you caching the Directory?No

Transaction IDsOption 1
  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


Current CEG Version?

Next CEG Version?

Next Version Implementation Date

Implementing Bespoke User Journeys?

No

Implementing App to App?

No
App to App Implementation Date?N/A
Options on 90 day re-authentication?90 Day Re-AuthenticationAfter 90 days consent is considered expired.  The customer will have to consent again by accessing via the TPP site and authenticating with ABC and selecting accounts

Support Embedded Flow?

NoWhen customer gives consent through the TPP site the Bank ABC login page (Auth0) is used to authenticate customer consent.  The customer provides username, password and OTP during login.  The system verifies credentials with the bank.
PSD2

Dispute Management System?

Yes
FCA Adjustment Period - Maintaining Screen Scraping?No

Seeking Fallback Exemption?

Yes

Adjusted or Fallback Interface?

Yes
Adjusted or Fallback URL?TBC
Contact Email or Phone Number?

Dev Portal URL?developer.bank-abc.com

Test Facility Implementation Date?

TBC
Production Interface Implementation Date?2021
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)?

Username and Password, and two factor authentication provided by users soft token


Authentication Method - Open Banking Channel (APP)?

N/A

Authentication Method - Private Channel (Browser)?

TBC


Authentication Method - Open Banking Channel (APP)?

N/A

Authentication Method Implementation Date (Open Banking Channel)?

TBC

Authentication Method Implementation Date (Private Channel)?

TBC

SCA Implementation Date?

TBC
SCA Scope? (will it inhibit non PSD2 accounts)

N/A


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

-
  • No labels