Versions Compared

Key

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


...


panel
Panel
titleColorBlack
borderStyledashed
titleOB Standards
details

This Section applies to ASPSPs that have impletemented OB Standards

Info
iconfalse
idStandards-Production
Implement Open Data v2.2N/AImplement Read/Write API Specification v3.1

14/09/2019 -AIS

15/05/2020 -PIS

Implement Customer Experience Guidelines v1.1YesImplement App-to-App RedirectionN/AImplement OB Security Profile Implementer's Draft v1.1.2N/AImplement FAPI Profile Implementers Draft 2Implement 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


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

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
titleMethod of IdentificationSecurity Profile


Page Properties
idID-Production
Commence support for eIDAS QWAC certificates14/09/2019Commence support for eIDAS QSEAL certificates
 

Commence support for OBIE QWAC-like certificates

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





#6180c3
Panel
titleColorWhite
titleBGColor
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) 

eIDAS QWAC and QSeal for EU TPPs

and 

OBWAC and OBSeal for UK based TPPs

POST-BREXIT POST TRANSITION - Certificates Accepted (from 1st Jul 2021)
  •  eIDAS QWAC
  •  eIDAS QSealC
  •  OB legacy (obtransport, obsigning)
  •  OBWAC
  •  OBSeal
  •  Other (Please define) 

eIDAS QWAC and QSeal for EU TPPs

and 

OBWAC and OBSeal for UK based TPPs

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
titleColorBlack
borderStyledashed
titleImplementationCustomer Journey


QSEAL
Page Properties
idTC-IMP
Page Properties
idTC-IMP

Directory?

Preta

Location of Well Known Endpoints?

Dev Portal – URL : https://developer.wellsfargo.com/apis

API Standard Implemented?

Open Banking v3.1

Name of Account Holder Implementation Date?

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

QWAC + ClientID +Secret

Current Certificates used for Transport?QWACCurrent Certificates used for Signing?N/ADate of Future eIDAS Implementation?Q4 2020Future Certificates used for Identification?QWAC + ClientID +SecretFuture Certificates used for Transport?

QWAC 

Future Certificates used for Signing?
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

Options on 90 day re-authentication?

90 Day Re-Authentication for AISP




Panel
titleColorBlack
borderStyledashed
titlePSD2


  • ASPSPs provide a Unique, Immutable TransactionID from their core system
  • ASPSPs generate a Unique TransactionID from a set of Immutable fields
  • ASPSPs specify field
    Page Properties
    idTC-PSD2


    Which Directory are you using as your Trust Framework?Preta
    Are you caching the Directory?Yes - Preta
    Transaction IDs SupportedOption 2

    2.ASPSPs generate a Unique TransactionID from a set of Immutable fields

    Are you enrolled to Dispute Management System?

    •  Yes
    •  No

    Are you Seeking Fallback Exemption?

    •  Yes
    •  No


    Article 10 - Maximum time period after authentication90 Days
    Article 10 - Endpoints exempt of SCA

    Accounts,Balances, Transactions


    Major Milestones
    1. Test Facility (Sandbox) Open Banking API Standards 3.1 Live -14th March 2019
    2. Stress Testing (Sandbox) Open Banking API Standards 3.1 -13th February 2019.
    3. AIS - Open Banking API Standards 3.1 Live - 14th September 2019.
    4. PIS - Open Banking API Standards 3.1 Live - 15th May 2020
    5. PRETA directory Maintenance and Validation services  - 14th September 2019.
    SCA via 2- Factor authentication – Password (knowledge) and Token (possession) and consent Flow as outlined in OBIE Customer Experience Guidelines  - 14th September 2019.

    Brand
    (s)
    Security Profile?Security Profile Certification?

    CIBA

    N/AUsing Open Banking as your eIDAS Trust Framework?NoAre you caching the Directory?Yes - PretaTransaction IDsOption 2
    (s)
    for TPP to generate a Unique Transaction Identifier
  • ASPSPs provide neither a TransactionID nor the method by which TPPs can generate one





  • id
    Panel
    borderStyledashed
    titleCustomer Journey
    Page Properties
    TC-CJ

    Implementing Customer Experience Guidelines?

    Yes

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

    Implementing Bespoke User Journeys?

    Yes

    Implementing App to App?

    YesApp to App Implementation Date?N/AOptions on 90 day re-authentication?90 Day Re-Authentication for AISP

    Support Embedded Flow?

    No
    Panel
    titleColorBlack
    borderStyledashed
    titlePSD2ASPSP Dev Portal and Contact Details


    Our scope only includes PSD2 accounts. Non PSD2 accounts will not be inhibited.
    Page Properties
    idTC-PSD2

    Dispute Management System?

    NoFCA Adjustment Period - Maintaining Screen Scraping?No

    Seeking Fallback Exemption?

    Exemption Granted Exemption granted on 3rd Jan 2020.

    Adjusted or Fallback Interface?

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


    Location of Well Known Endpoints

    Dev Portal – URL : https://developer.wellsfargo.com/apis

    Test Facility Implementation Date?

     Production Interface Implementation Date? Contingency MeasuresArticle 10 - Maximum time period after authentication?90 DaysArticle 10 - Endpoints exempt of SCAAccounts,Balances, Transactions

    Authentication Method - Open Banking Channel (Browser)?

    Yes. For the API based Dedicated Interface we will be using the Redirect Method of Authentication with OAUTH2.

    Authentication Method - Open Banking Channel (APP)?

    N/A

    Authentication Method - Private Channel (Browser)?

    Yes. For the Direct access channels we will be using the 2FA Authentication which will include (password) Knowledge and (Token) Possession for both Account Information Services and Payment Initiation Services.

    Authentication Method - Open Banking Channel (APP)?

    N/A

    Authentication Method Implementation Date (Open Banking Channel)?

     

    Authentication Method Implementation Date (Private Channel)?

     

    SCA Implementation Date?

     SCA Scope? (will it inhibit non PSD2 accounts)

    Modified Customer Interface URL (if applicable)



    Dev Portal URLhttps://developer.wellsfargo.com/apis
    Test Facility URL

    ASPSP Support Desk Email or Phone Number






    Panel
    titleColorBlack
    borderStyledashed
    titleKey Implementations


    N/A

    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