Versions Compared

Old Version 11

changes.mady.by.user Praveen Ponnumony

Saved on

compared with

New Version 12

changes.mady.by.user Praveen Ponnumony

Saved on

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


TBUK uses Token.io’s
Page Propertiesinfo
iconfalse
idStandards-Production


Implement Open Data v2.2N/AImplement Read/Write API Specification v3.1N/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
TBUK uses Token.io’s standards which are aligned with Open Banking Standards
Implement Customer Experience Guidelines v1.1TBC

Currently being investigated by our TSP

Implement App-to-App RedirectionN/AImplement OB Security Profile Implementer's Draft v1.1.2N/AImplement FAPI Profile Implementers Draft 2N/AImplement CIBA Profile Implementers Draft 1N/AImplement Dynamic Client Registration v1.1N/AImplement Dynamic Client Registration v3.1N/ADecommission Read/Write API Specification v1.x/2.xN/ADecommission OB Security Profile Implementer's Draft v1.xN/A
Panel
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 certificates Commence support for eIDAS QSEAL certificates
 

Commence support for OBIE QWAC-like certificates

N/A

Commence support for OBIE QSEAL-like certificatesN/ACease support for OBIE non eIDAS-like certificates for transportN/ACease support for OBIE non eIDAS-like certificates for signingN/ASupport for MTLS token endpoint authenticationN/ASupport for private_key_jwt token endpoint authenticationN/A

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
N/A






White
Panel
titleColor
titleBGColor#6180c3
borderStyledashed
titlePost Brexit Certificate Implementation


Page Properties
idStandards-Production


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



TPP PSU Migration Outcomes Supported (see eIDAS Migration Playbook)



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





Panel
borderStyledashed
titleImplementation
Page Properties
idTC-IMP
Page Properties
idTC-IMP

Directory?

Open Banking

Open Banking Directory through Token.io

Location of Well Known Endpoints?

OB Technical Directory

API Standard Implemented?

Open Banking

Sandbox  Environment – App Creation by TPP and after TBUK Approval

Production Environment – App Creation by TPP and after TBUK Approval

Name of Account Holder Implementation Date?

N/ADate of Current eIDAS Implementation?MTLS with eIDAS CertificatesCurrent Certificates used for Identification?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

June 2019 for test facility

October 2019 for production APIs

Brand(s)

Security Profile?

TBC

Security Profile Certification?TBC

CIBA

NoUsing Open Banking as your eIDAS Trust Framework?NoAre you caching the Directory?NoTransaction IDsTBC
  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
titleColorBlack
borderStyledashed
titleCustomer Journey


N/A
Page Properties
idTC-CJ


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

TBC

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

Implementing Bespoke User Journeys?

No

Implementing App to App?

YesApp to App Implementation Date?

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

Options on 90 day re-authentication?

90 day Re-AuthenticationIn line with RTS (If customer logs in after 90 days then they will be prompted to re-authenticate for Consent.)

Support Embedded Flow?

No



No
Panel
titleColorBlack
borderStyledashed
titlePSD2


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
Page Properties
idTC-PSD2


Dispute Management System
Which Directory are you using as your Trust Framework?
NoFCA Adjustment Period - Maintaining Screen Scraping?Yes

Seeking Fallback Exemption?

Yes

Adjusted or Fallback Interface?

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

IThelpdesk@turkishbank.co.uk

Dev Portal URL?

https://turkishbankuk.docs.token.io/

Test Facility Implementation Date?

June 2019

Production Interface Implementation Date?October 2019Contingency MeasuresTBC
Open Banking
Are you caching the Directory?No
Transaction IDs SupportedTBC

Are you enrolled to Dispute Management System?

  •  Yes
  •  No

Are you Seeking Fallback Exemption?

  •  Yes
  •  No


Article 10 - Maximum time period after authentication
?
90 Days
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

Authentication Method - Open Banking Channel (Browser)?

Credentials + OTP

Authentication Method - Open Banking Channel (APP)?

Credentials + OTP

Authentication Method - Private Channel (Browser)?

Credentials + OTP

Authentication Method - Open Banking Channel (APP)?

Credentials + OTP

Authentication Method Implementation Date (Open Banking Channel)?

September 2019

Authentication Method Implementation Date (Private Channel)?

September 2019

SCA Implementation Date?

September 2019SCA Scope? (will it inhibit non PSD2 accounts)
- Endpoints exempt of SCA

Exemption covers all AIS endpoints

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

Major Milestones

June 2019 for test facility

October 2019 for production APIs


Brand(s)




Panel
titleColorBlack
borderStyledashed
titleASPSP Dev Portal and Contact Details


Page Properties
idTC-CJ


Location of Well Known Endpoints

OB Technical Directory

Modified Customer Interface URL (if applicable)



Dev Portal URL

Test Facility URL

ASPSP Support Desk Email or Phone Number






Panel
titleColorBlack
borderStyledashed
titleKey Implementations


TBC

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