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.


Method of Identification
Panel
titleColorBlack
borderStyledashed
titleOB Standards
borderStyledashed
title

This Section applies to ASPSPs that have implemented OB Standards

Page Properties
iconfalse
idTC-OB Standards-Production
Implement Open Data v2.2Implement Read/Write API Specification v3.1Implement 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.xArticle 10 SCA Exemption (for 90 days)Resources covered (delete as appropriate): Accounts, Balances, Transactions, Beneficiaries, Direct Debits, Standing Orders, Products, Offers, Parties, Scheduled Payments, Statements
Panel


-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
  •  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
titleSCA-RTS 90-day reauth Implementation


Page Properties
idSCA-RTS


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

Sept 2022

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

Long lived refresh token. It would be for 999 days initially and will be replaced/refreshed with no further authentication from the customer.

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)

Status
colourGreen
titleImplemented

Planned / In-progress / Implemented / TBC




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

eIDAS QWAC and QSeal for EU TPPs

and 

OBWAC and OBSeal for UK based TPPs




Panel
titleColorBlack
borderStyledashed
titleImplementationCustomer Journey


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

Options on 90 day re-authentication?

90 Day Re-Authentication for AISP




Panel
titleColorBlack
borderStyledashed
titlePSD2


IMP
Page Properties
idTC-
PSD2
Page Properties
idTC-CJ


API Standard Implemented?

Open Banking v3.1

Name of Account Holder Implementation Date?

Supported identification method?QWAC
-Which Directory are you using as your Trust Framework?Preta

Location of Well Known Endpoints?

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

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 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
  1. 13th February 2019.
  2. AIS - Open Banking API Standards 3.1
planned for - 14th September
  1. Live - 14th September 2019.
  • Wide Usage – Underway –
    1. Open Banking Functional Conformance Testing
    2. TPP Testing
    1. PIS - Open Banking API Standards 3.1 Live - 15th May 2020
    2. PRETA directory Maintenance and Validation
    services planned for - 14th September
    1. services  - 14th September 2019.
    SCA via 2- Factor authentication – Password (knowledge) and Token (possession) and consent Flow as outlined in OBIE Customer Experience
    Guidelines planned for - 14th September 2019.

    FAPI Compliant?

    Yes

    CIBA

    N/AUsing Open Banking as your eIDAS Trust Framework?NoAre you caching the Directory?Yes - PretaTransaction IDsOption 2
    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

    Implementing Customer Experience Guidelines?

    Yes

    Implementing Bespoke User Journeys?

    		Yes

    Implementing App to App?

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

    Support Embedded Flow?

    		No
    Guidelines  - 14th September 2019.
    Brand(s)




    Panel
    titleColorBlack
    borderStyledashed
    titlePSD2ASPSP Dev Portal and Contact Details


    Contact Email or Phone Number?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?

    		Yes

    Adjusted or Fallback Interface?

    		NoAdjusted or Fallback URL?N/A
    C


    Location of Well Known Endpoints

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

    Modified Customer Interface URL (if applicable)



    Dev Portal URL
    ?
    https://developer.wellsfargo.com/apis
    Test Facility
    Implementation Date?
    		 Production Interface Implementation Date? 

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






    Panel
    titleColorBlack
    borderStyledashed
    titleKey Implementations


    Page Properties
    idTC-HCC


    High Cost Credit

    		TBC

    View file
    nameHCC.xlsx
    height250