Versions Compared

Version Old Version 1 New Version Current
Changes made by

Adam Pretlove (Unlicensed)

Praveen Ponnumony

Saved on

Key

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


Panel
titleColorBlack
borderStyledashed
titleImplementationOB Standards

This Section applies to ASPSPs that have implemented OB Standards

  • ASPSPs provide a Unique, Immutable TransactionID from their core system
  • ASPSPs generate a Unique TransactionID from a set of Immutable fields
  • ASPSPs specify field(s) for TPP to generate a Unique Transaction Identifier
    • ASPSPs provide neither a TransactionID nor the method by which TPPs can generate one
    Page Properties
    iconfalse
    idTC-IMP
    Page Properties
    idTC-IMP

    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?

    		 Supported identification method?eIDAS QWAC

    Major Milestones

    		-

    Security Profile?

    		Security Profile Certification?

    CIBA

    		N/AUsing Open Banking as your eIDAS Trust Framework?YesAre you caching the Directory?NoTransaction IDs
    OB Standards


    -Have you Implemented OB Standards?
    •  Yes
    •  No
    		Other (PSD2/SCA-RTS compliant API)
    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
    •  V3.1.9
    •  V3.1.10
    •  V3.1.11
    •  V4.0

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

    Have you implemented v4.0 information flows, if not date planned to Implement?

    •  Already Implemented
    •  Planning to implement
    •  Not planning to implement 

    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 

    Have you implemented ECA Standard?

    •  Already Implemented
    •  Planning to implement
    •  Not planning to implement 

    ECA Implementation details


    Contact: [enter contact details for the relevant person(s) at your organisation]

    [You can use this space to provide your status with respect to the Standard]

    Have you implemented Bulk/File Payments?

    •  Already Implemented
    •  Planning to implement
    •  Not planning to implement 

    Have you implemented VRP – Sweeping, if not date planned to Implement?

    •  Already Implemented
    •  Planning to implement
    •  Not planning to implement 

    Have you implemented VRP non-Sweeping, if not date planned to Implement?

    •  Already Implemented
    •  Planning to implement
    •  Not planning to implement 

    Contact: [enter contact details for the relevant person(s) at your organisation]

    [You can use this space to provide implementation details relevant to VRP]
    PISP - Single Payment Limit£
    PISP - Daily Payment Limit£
    How many months of transaction do you provide?

    Have you implemented TRIs (Transactional Risk Indicators), if not, date planned to Implement?

    What is your approach to Implementing TRIs?
    •  Accept payload with TRI fields – Process all fields
    •  Accept payload with TRI fields – Ignore all fields
    •  Reject payload with TRI fields – Error back to TPP
    •  Accept payload with TRI fields – Process few fields (Provide list of accepted fields)  




    Panel
    borderStyledashed
    titleCustomer JourneySCA-RTS 90-day reauth Implementation


    No
    Page Properties
    idTCSCA-CJ

    Implementing Customer Experience Guidelines?

    Yes

    Implementing Bespoke User Journeys?

    		Yes

    Implementing App to App?

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

    Support Embedded Flow?

    RTS


    Which date are you planning on implementing the SCA reauthentication exemption?



    What is your approach to token management to enable application of the reauthentication exemption? (see link to FCA guidance)


    Example approach:
    Issue a long-lived refresh token during one final SCA, with refresh token rotation implemented.

    [Please use this space to provide more details on your approach]

    Article 10A - Endpoints exempt of SCA-RTS
    •  

      Accounts

    •  

      Transactions (90days)

    •  

      Balances

    •  

      Standing orders

    •  

      Direct debits

    •  

      Beneficiaries

    •  

      Products

    •  

      Offers

    •  

      Parties

    •  

      Scheduled Payments

    •  

      Statements


    Article 10A - Endpoints not exempt of SCA-RTS
    •  

      Transactions (more than 90days)

    •  

      Standing orders

    •  

      Direct debits

    •  

      Beneficiaries

    •  

      Products

    •  

      Offers

    •  

      Parties

    •  

      Scheduled Payments

    •  

      Statements


    Article 10A - Maximum time period after authentication
    		Please specify the time period in minutes
    SCA-RTS implementation status (updated by OBL PS team only)


    		Planned / In-progress / Implemented / TBC




    Panel
    titleColorBlack
    borderStyledashed
    titlePSD2Security Profile


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

    Dispute Management System?

    		YesFCA Adjustment Period - Maintaining Screen Scraping?

    Seeking Fallback Exemption?

    		Yes

    Adjusted or Fallback Interface?

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

    Test Facility Implementation Date?

    		 - TBCProduction Interface Implementation Date? - TBCContingency MeasuresPlease 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 requireArticle 10 - Maximum time period after authentication?
    ID-Production


    -Which Security profile have you Implemented or planning to implement?

    (Lowest version = Current, Highest version = Planned)

    •  OB Security Profile (Legacy)
    •  FAPI (ID2)
    •  FAPI 1 Advanced
    •  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 
    POST-BREXIT POST TRANSITION - Certificates Accepted (from 1st Jul 2021)
    •  eIDAS QWAC
    •  eIDAS QSealC
    •  OB legacy (obtransport, obsigning)
    •  OBWAC
    •  OBSeal
    •  Other (Please define) 




    Panel
    titleColorBlack
    borderStyledashed
    titleCustomer Journey


    Page Properties
    idTC-CJ


    -What is your approach to Implementing OBL 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
    •  V3.1.9
    •  V3.1.10
    •  V3.1.11
    •  V4.0

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

    Redirection Model
    •  App to App redirection
    •  Decoupled authentication
    •  Embedded Flow
    •  Bespoke User Journeys




    Panel
    titleColorBlack
    borderStyledashed
    titlePSD2


    SCA will be applied for all online accounts. 

    APIs will be exposed for PSD2 accounts only
    Page Properties
    idTC-PSD2


    -Which Directory are you using as your Trust Framework?Open Banking
    Are you caching the Directory?No
    Transaction IDs Supported

    Are you Seeking Fallback Exemption?

    •  Yes
    •  No


    Article 10 - Maximum time period after authentication

    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)?

    		 - TBC

    Authentication Method Implementation Date (Private Channel)?

    		N/A

    SCA Implementation Date?

     - TBC

    		SCA Scope? (will it inhibit non PSD2 accounts)



    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




    Panel
    titleColorBlack
    borderStyledashed
    titleASPSP Dev Portal and Contact Details


    Page Properties
    idTC-C


    Location of Well Known Endpoints

    Dev Portal:

    https://developer.token.io/

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

    Modified Customer Interface URL (if applicable)



    Dev Portal URLhttps://developer.token.io/
    Test Facility URL

    Brand Landing Pages URL
    		[You can use this space to explain your guidance on using Brand logos]

    ASPSP Support Desk Email or Phone Number

    (including queries about consent success rates) 

    		Us@unity.co.uk




    Panel
    titleColorBlack
    borderStyledashed
    titleKey Implementations


    Page Properties
    idTC-HCC


    High Cost Credit

    		TBC

    View file
    nameHCC.xlsx
    height250