Versions Compared

Version Old Version 2 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
titleOBIE OB Standards

This Section applies to ASPSPs that have implemented OB Standards

Page Properties
iconfalse
idTC-OB Standards9Standards-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.xN/ADecommission OB Security Profile Implementer's Draft v1.xN/AArticle 10 SCA Exemption (for 90 days)
Panel
titleColorBlack
borderStyledashed
titleMethod of Identification
Cease support for client id and client secret token endpoint authentication
Page Properties
id9ID-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
-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£10,000[Personal Account]
£50,000[Business Account]
PISP - Daily Payment Limit£10,000[Personal Account]
£50,000[Business Account]
How many months of transaction do you provide?12
Have you implemented TRIs (Transactional Risk Indicators), if not, date planned to Implement?No Plan at this time
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?

Q2 2024[Implementation of 3.1.10]

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

Approach to Article 10A implementation work in progress. Planned for Q2 2024.

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

Approach to Article 10A implementation work in progress. Planned for Q2 2024.
Article 10A - Endpoints not exempt of SCA-RTS
  •  

    Transactions (more than 90days)

  •  

    Standing orders

  •  

    Direct debits

  •  

    Beneficiaries

  •  

    Products

  •  

    Offers

  •  

    Parties

  •  

    Scheduled Payments

  •  

    Statements

Approach to Article 10A implementation work in progress. Planned for Q2 2024.
Article 10A - Maximum time period after authentication  Implemented60 minutes
SCA-RTS implementation status (updated by OBL PS team only)


Planned / In-progress / Implemented / TBC




Panel
titleColorBlack
borderStyledashed
titleImplementationSecurity Profile


Page Properties
idTCID-IMP

Directory?

Open Banking

Location of Well Known Endpoints?

Open Banking technical directory and Cynergy Bank Developer Portalhttps://openbanking.cynergybank.co.uk/

API Standard Implemented?

Open Banking v3.1.1 &
Open Banking v3.0

Name of Account Holder Implementation Date?

N/A

Supported identification method?

eIDAS, OBWAC/OBSEAL

Major Milestones

Testing interface Open Banking API standard v3.0 13/03/2019
Wide usage interface Open Banking API Standard v3.0 13/03/2019
Stress testing (Open Banking API standard v3.0) 30/06/2019
Open Banking API standard v3.1.1 13/09/2019
Infrastructure upgrades 05/08/2019
eIDAS 13/09/2019

FAPI Compliant?

Yes

CIBA

N/AThe Bank does not offer a mobile banking app
Using Open Banking as your eIDAS Trust Framework?NoAre you caching the Directory?NoTransaction IDsTBC
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 authenticationN/A
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


Implementing Bespoke User Journeys?

N/A

-What is your approach to Implementing OBL Customer Experience Guidelines (CEG)?

Yes

No

Implementing App to App?

N/AApp to App Implementation Date?N/A 

Options on 90 day re-authentication?

90 day consent model as per SCA-RTS

Support Embedded Flow?

(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
Cynergy Bank does not offer a mobile banking app




Panel
titleColorBlack
borderStyledashed
titlePSD2


Page Properties
idTC-PSD2

Dispute Management System?

No


-Which Directory are you using as your Trust Framework?Cynergy Bank will utilise an independent eIDAS solution provider(Banfico). Cynergy Bank will also offer OBIE's Dynamic Client Registration
Are you caching the Directory?No
Transaction IDs SupportedImmutable Transaction ID from Cynergy's Core Banking System

Are you Seeking Fallback Exemption?

  •  Yes

Adjusted or Fallback Interface?

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

Test Facility Implementation Date?

  •  No


Article 10 - Maximum time period after authentication

If 90 days has elapsed since SCA was applied, the customer will need to re-authenticate.

The 90 day period is specific to each AISP and must be distinguished to the 90 day period which applies to customers.

Application of SCA to initiate a payment (via a PISP or customer) does not restart the 90 day period.


Article 10 - Endpoints exempt of SCA

No


Major Milestones

Testing interface Open Banking API standard v3.0  

Production Interface Implementation Date?

Wide usage interface Open Banking API Standard v3.0  

Authentication Method - Open Banking Channel (Browser)?

AISP: Username + Password (as knowledge factors) + hard token/soft token (as possession factors)/One time password (to be deprecated)
PISP: Username + Password (as knowledge factors) + hard token/soft token (as possession factors)/One time password (to be deprecated)

Authentication Method - Open Banking Channel (APP)?

N/AThe Bank does not offer a mobile banking app

Authentication Method - Private Channel (Browser)?

AISP: Username + Password (as knowledge factors) + hard token/soft token (as possession factors)/One time password (to be deprecated)
PISP: Username + Password (as knowledge factors) + hard token/soft token (as possession factors)/One time password (to be deprecated)

Authentication Method - Private Channel (APP)?

N/AThe Bank does not offer a mobile banking app

Authentication Method Implementation Date (Open Banking Channel)?

 

Authentication Method Implementation Date (Private Channel)?

 

SCA Implementation Date?

 

SCA Scope? (will it inhibit non PSD2 accounts)

Applicable for all payment account holders with Customer Channel (Online Banking) access

Stress testing (Open Banking API standard v3.0)  
Open Banking API standard v3.1.1  
Infrastructure upgrade  

eIDAS  


Brand(s)




Panel
titleColorBlack
borderStyledashed
titleASPSP Dev Portal and Contact Details


Page Properties
idTC-C


Location of Well Known Endpoints

Open Banking technical directory and Cynergy Bank Developer Portal

https://openbanking.cynergybank.co.uk/API/.well-known/openid-configuration


Modified Customer Interface URL (if applicable)



Dev Portal URLhttps://openbanking.cynergybank.co.uk
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) 

obaccadmin@cynergybank.co.uk




Panel
titleColorBlack
borderStyledashed
titleKey Implementations


Page Properties
idTC-HCC


High Cost Credit

Implemented 30 Nov 2019 

View file
nameHCC.xlsx
height250