Page Comparison

...

Panel

titleColor	Black
borderStyle	dashed
title	OB Standards

This Section applies to ASPSPs that have implemented OB Standards

Page Properties

icon	false
id	TC-OB Standards-Production

Implement Open Data v2.2

N/A

Implement Read/Write API Specification v3.1

14/09/2019 -AISP

Implement Customer Experience Guidelines v1.1

Yes

Implement App-to-App Redirection

N/A

Implement OB Security Profile Implementer's Draft v1.1.2

N/A

Implement FAPI Profile Implementers Draft 2

Implement CIBA Profile Implementers Draft 1

N/A

Implement Dynamic Client Registration v1.1

N/A

Implement Dynamic Client Registration v3.1

N/A

Decommission Read/Write API Specification v1.x/2.x

N/A

Decommission OB Security Profile Implementer's Draft v1.x

N/A

Panel

borderStyle	dashed
title	Method of Identification

Page Properties

id	ID-Production

Commence support for eIDAS QWAC certificates

14/09/2019

Commence support for eIDAS QSEAL certificates

Commence support for OBIE QWAC-like certificates

N/A

Commence support for OBIE QSEAL-like certificates

N/A

Cease support for OBIE non eIDAS-like certificates for transport

N/A

Cease support for OBIE non eIDAS-like certificates for signing

N/A

Support for MTLS token endpoint authentication

Support for private_key_jwt token endpoint authentication

-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

borderStyle	dashed
title	SCA-RTS 90-day reauth Implementation

Page Properties

id	SCA-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

colour	Green
title	Implemented

Planned / In-progress / Implemented / TBC

Panel

titleColor	Black
borderStyle	dashed
title	Security Profile

Page Properties

id	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)	eIDAS QWAC and QSeal for EU TPPs and OBWAC and OBSeal for UK based TPPs

Panel

titleColor	Black
borderStyle	dashed
title	ImplementationCustomer Journey

QSEAL

Page Properties

id	TC-IMP

Page Properties

id	TC-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 2019

Current Certificates used for Identification?

QWAC + ClientID +Secret

Current Certificates used for Transport?

QWAC

Current Certificates used for Signing?

N/A

Date of Future eIDAS Implementation?

Q4 2020

Future Certificates used for Identification?

QWAC + ClientID +Secret

Future Certificates used for Transport?

QWAC

Future Certificates used for Signing?

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

titleColor	Black
borderStyle	dashed
title	PSD2

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

id	TC-PSD2

Brand
-Which Directory are you using as your Trust Framework?	Preta
Are you caching the Directory?	Yes - Preta
Transaction IDs Supported	Option 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 authentication	90 Days
Article 10 - Endpoints exempt of SCA	Accounts,Balances, Transactions
Major Milestones	Test Facility (Sandbox) Open Banking API Standards 3.1 Live -14^th March 2019 Stress Testing (Sandbox) Open Banking API Standards 3.1 -13^th February 2019. AIS - Open Banking API Standards 3.1 Live - 14^th September 2019. PIS - Open Banking API Standards 3.1 Live - 15^th May 2020 PRETA directory Maintenance and Validation services - 14^th September 2019. SCA via 2- Factor authentication – Password (knowledge) and Token (possession) and consent Flow as outlined in OBIE Customer Experience Guidelines - 14^th September 2019.

(s)

Security Profile?

Security Profile Certification?

CIBA

N/A

Using Open Banking as your eIDAS Trust Framework?

No

Are you caching the Directory?

Yes - Preta

Transaction IDs

Option 2

(s)

for TPP to generate a Unique Transaction IdentifierASPSPs provide neither a TransactionID nor the method by which TPPs can generate one

TC-CJ

Panel

borderStyle	dashed
title	Customer Journey

Page Properties

id

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?

N/A

Options on 90 day re-authentication?

90 Day Re-Authentication for AISP

Support Embedded Flow?

No

Panel

titleColor	Black
borderStyle	dashed
title	PSD2ASPSP Dev Portal and Contact Details

Dev Portal URL?

Page Properties

id	TC-PSD2

Dispute Management System?

No

FCA Adjustment Period - Maintaining Screen Scraping?

No

Seeking Fallback Exemption?

Exemption Granted

Exemption granted on 3rd Jan 2020.

Adjusted or Fallback Interface?

No

Adjusted or Fallback URL?

N/A

Contact Email or Phone Number?

C

Test Facility
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

Implementation Date?

14 Mar 2019

Production Interface Implementation Date?

14 Sep 2019

Contingency Measures

Article 10 - Maximum time period after authentication?

90 Days

Article 10 - Endpoints exempt of SCA

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

14 Sep 2019

Authentication Method Implementation Date (Private Channel)?

14 Sep 2019

SCA Implementation Date?

14 Sep 2019

SCA Scope? (will it inhibit non PSD2 accounts)

Our scope only includes PSD2 accounts. Non PSD2 accounts will not be inhibited.

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

titleColor	Black
borderStyle	dashed
title	Key Implementations

N/A

Page Properties

id	TC-HCC

High Cost Credit	TBC

View file

name	HCC.xlsx
height	250

Page Properties

id	TC-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

Version	Old Version 16	New Version Current
Changes made by	Narayan Tyagarajan	Praveen Ponnumony
Saved on	Sept 07, 2020	Sept 05, 2024

Page Comparison

Versions Compared

Key