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

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



TPP PSU Migration Outcomes Supported



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



Implementation

Directory?

Open Banking

Location of Well Known Endpoints?

Dev Portal:

https://developer.token.io/

https://www.unity.co.uk/psd2/

API Standard Implemented?

Other

(PSD2/SCA-RTS compliant API)

Name of Account Holder Implementation Date?

Completed -  

Date of Current eIDAS Implementation?
eIDAS QWAC
Current 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

Test platform available via Token.io from  

Production platform available via Token.io from  

For more information, please visit www.unity.co.uk/PSD2



Brand(s)Unity Trust Bank

Security Profile?




Security Profile Certification?


CIBA

N/A

Using Open Banking as your eIDAS Trust Framework?Yes

Are you caching the Directory?No

Transaction IDs
  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?

Yes

Implementing App to App?

Yes
App to App Implementation Date? 
Options on 90 day re-authentication?Not supported. Max consent = 90 days

Support Embedded Flow?

No
PSD2

Dispute Management System?

Yes
FCA Adjustment Period - Maintaining Screen Scraping?No

Seeking Fallback Exemption?

Granted exemption  

Adjusted or Fallback Interface?

No
Adjusted or Fallback URL?N/A
Contact Email or Phone Number?Us@unity.co.uk
Dev Portal URL?https://developer.token.io/

Test Facility Implementation Date?

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

Decoupled

Authentication Method - Open Banking Channel (APP)?

Decoupled

Authentication Method - Private Channel (Browser)?

N/A


Authentication Method - Open Banking Channel (APP)?

N/A

Authentication Method Implementation Date (Open Banking Channel)?

 


Authentication Method Implementation Date (Private Channel)?

N/A

SCA Implementation Date?

 


SCA Scope? (will it inhibit non PSD2 accounts)

SCA will be applied for all online accounts. 

APIs will be exposed for PSD2 accounts only


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

TBC


  • No labels