Versions Compared

Old Version 1

changes.mady.by.user Praveen Ponnumony

Saved on

compared with

New Version Current

changes.mady.by.user Praveen Ponnumony

Saved on

Key

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


Panel
titleColorBlack
borderStyledashed
titleOB Standards

This Section applies to ASPSPs that have impletemented implemented OB Standards


Page Properties
iconfalse
idOB Standards


-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? version 4.0 in 2025.The current Open Banking standard, version 3.1.6, will be updated to version 4.0 in 2025.

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
Dynamic Client Registration is supported and described in the TPP Developer Portal of The Bank of London:  https://priora.saltedge.com/docs/open_banking/tbol/v3.1/tpp_onboarding#tpp-register
DCR - Which date are you planning to implement your latest version? 2025.The latest DCR version will be implemented along with the latest Open Banking standard version in 2025.

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

Not applicable

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?

Are Have you planning to implement implemented TRIs (Transactional Risk Indicator enhancements included in v3.1.10Indicators), if sonot, implementation date planned to Implement?

Not planning 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)  
Not applicable



...

Panel
borderStyledashed
titleSCA-RTS 90-day reauth Implementation


Page Properties
idSCA-RTS


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

SCA reauthentication is not implemented.

Following the FCA recommendation under PS21/19, this dedicated interface enables the SCA exemption under SCA-RTS Article 10A for AISPs.

 If the AISP creates a consent longer than 90-days, then AISP must reconfirm PSU consent, and must not access information without the PSU actively requesting it unless the PSU has reconfirmed their consent within the previous 90 days.

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

Not applicable

Not applicable as SCA reauthentication is not implemented.

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
The dedicated interface enables the SCA exemption under SCA-RTS Article 10A for AISPs, allowing them to create consents that last longer than 90 days. However, AISPs must reconfirm customer consent under Article 36(6) of the SCA-RTS. AISPs must not access information without the customer actively requesting it unless the customer has reconfirmed consent within the previous 90 days.
SCA-RTS implementation status (updated by OBIE OBL PS team only)

Status
colourGreen
titleImplemented

Planned / In-progress / Implemented / TBC



...

Panel
titleColorBlack
borderStyledashed
titleSecurity Profile


Page Properties
idID-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
not applicable
CIBA Profile - Next Planned Version Implementation Date
as part of version 4.0 in 2025.
Next planned version of Security Profile will be implemented together with the updated version of Open Banking standard (4.0) in 2025.
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 OBIE 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?version 4.0 in 2025.

The latest version of CEG will be implemented together with the updated 4.0 version in 2025.

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



...

Panel
titleColorBlack
borderStyledashed
titlePSD2


Page Properties
idTC-PSD2


  •  Yes
  •  No
-Which Directory are you using as your Trust Framework?Open Banking Directory
Are you caching the Directory?Yes
Transaction IDs SupportedYes
  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

Are you enrolled to Dispute Management System?

Are you Seeking Fallback Exemption?

  •  Yes
  •  No

The Bank of London will be applying for Exemption from providing a fallback mechanism.

Article 10 - Maximum time period after authenticationThe maximum time period for fetching account information after authentication is indicated in the `ExpirationDateTime` parameter included in the /consent request.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

AIS endpoints

Accounts:
- https://priora.saltedge.com/docs/open_banking/tbol/v3.1/ais#accounts-index
Balances:
- https://priora.saltedge.com/docs/open_banking/tbol/v3.1/ais#accounts-balances

 Transactions:
https://priora.saltedge.com/docs/open_banking/tbol/v3.1/ais#accounts-transactions


Major MilestonesTransition to updated version of Open Banking standard 4.0 in 2025
Brand(s)The Bank of London Group Limited



...