Versions Compared

Key

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


Method of Identification
Panel
titleColorBlack
borderStyledashed
titleOB Standards
borderStyledashed
title

This Section applies to ASPSPs that have impletemented OB Standards


Implement
Page Propertiesinfo
iconfalse
idStandards-Production


Implement Open Data v2.2
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

v3.1
Implement Customer Experience Guidelines v1.1Implement App-to-App RedirectionImplement OB Security Profile Implementer's Draft v1.1.2Implement FAPI Profile Implementers Draft 2Implement CIBA Profile Implementers Draft 1Implement Dynamic Client Registration v1.1Implement Dynamic Client Registration v3.1Decommission Read/Write API Specification v1.x/2.xDecommission OB Security Profile Implementer's Draft v1.x
Panel

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

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

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 

PISP - Single Payment Limit£
PISP - Daily Payment Limit£
How many months of transaction do you provide?




Panel
titleColorBlack
borderStyledashed
titleSecurity Profile


Page Properties
idID-Production


Commence support for eIDAS QWAC certificatesCommence support for eIDAS QSEAL certificates
 

Commence support for OBIE QWAC-like certificates

Commence support for OBIE QSEAL-like certificatesCease support for OBIE non eIDAS-like certificates for transportCease support for OBIE non eIDAS-like certificates for signingSupport for MTLS token endpoint authenticationSupport for private_key_jwt token endpoint authentication

Which Security profile have you Implemented or planning to implement?

(Lowest version = Current, Highest version = Planned)

  •  OB Security Profile (Legacy)
  •  FAPI
  •  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





Panel
titleColorWhite
titleBGColor#6180c3
borderStyledashed
titlePost Brexit Certificate Implementation


  •  eIDAS QWAC
  •  eIDAS QSealC
  •  OB legacy (obtransport, obsigning)
  •  OBWAC
  •  OBSeal
  •  Other (Please define) 
Page Properties
idStandards-Production
PRE-BREXIT - Certificates Accepted (until 31st Dec 2020)


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 (see eIDAS Migration Playbook)



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

Ready





Panel
titleColorBlack
borderStyledashed
titleImplementationCustomer Journey


Yes
Page Properties
idTC-IMP
Page Properties
idTC-IMP

Directory?

MCI

Location of Well Known Endpoints?

OB Technical Directory

API Standard Implemented?

Open Banking

Name of Account Holder Implementation Date?

TBCDate of Current eIDAS Implementation?eIDASCurrent 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

NoUsing Open Banking as your eIDAS Trust Framework?
CJ


What is your approach to Implementing OBIE Customer Experience Guidelines (CEG)?

(tick all that apply)

  •  Already Implemented
  •  Planning to implement or upgrade
  •  Not planning to implement CEG

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

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

Redirection Model
  •  App to App redirection
  •  Decoupled authentication
  •  Embedded Flow
  •  Bespoke User Journeys
When 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.

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




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
Panel
titleColorBlack
borderStyledashed
titlePSD2


Page Properties
idTC-PSD2
Panel
titleColorBlack
borderStyledashed
titlePSD2
Page Properties
idTC-PSD2


Which Directory are you using as your Trust Framework?MCI
Are you caching the Directory?No
Transaction IDs SupportedOption 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
Panel
borderStyledashed
titleCustomer Journey
Page Properties
idTC-CJ

Implementing Customer Experience Guidelines?

Yes

Current CEG Version?Next CEG Version?Next Version Implementation Date

Implementing Bespoke User Journeys?

No

Implementing App to App?

NoApp 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.

Are you enrolled to Dispute Management System?

YesFCA Adjustment Period - Maintaining Screen Scraping?
  •  Yes
  •  No

Are you Seeking Fallback Exemption?

Yes

Adjusted or Fallback Interface?

YesAdjusted or Fallback URL?TBCContact Email or Phone Number?Dev Portal URL?developer.bank-abc.com

Test Facility Implementation Date?

TBCProduction Interface Implementation Date?2021Contingency Measures
  •  Yes
  •  No


Article 10 - Maximum time period after authentication
?

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?

TBCSCA Scope? (will it inhibit non PSD2 accounts)

N/A


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

Major Milestones

Brand(s)




-
Panel
titleColorBlack
borderStyledashed
titleKey ImplementationsASPSP Dev Portal and Contact Details


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

CJ


Location of Well Known Endpoints

OB Technical Directory

Modified Customer Interface URL (if applicable)



Dev Portal URLdeveloper.bank-abc.com
Test Facility URL

ASPSP Support Desk Email or Phone Number