Cynergy Bank Limited

OB Standards

Implement Open Data v2.2	N/A	Mandated only for the CMA9
Implement Read/Write API Specification v3.1	14/03/2020
Implement Customer Experience Guidelines v1.1	14/03/2020
Implement App-to-App Redirection	N/A	Cynergy Bank does not offer a mobile banking app
Implement OB Security Profile Implementer's Draft v1.1.2	14/03/2020
Implement FAPI Profile Implementers Draft 2	N/a
Implement CIBA Profile Implementers Draft 1	N/A	Cynergy Bank does not offer a mobile banking app
Implement Dynamic Client Registration v1.1	N/A
Implement Dynamic Client Registration v3.1	14/03/2020
Decommission Read/Write API Specification v1.x/2.x	N/A
Decommission OB Security Profile Implementer's Draft v1.x	N/A

Method of Identification

Commence support for eIDAS QWAC certificates	14/03/2020
Commence support for eIDAS QSEAL certificates	14/03/2020
Commence support for OBIE QWAC-like certificates	14/03/2020
Commence support for OBIE QSEAL-like certificates	14/03/2020
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	14/03/2020
Support for private_key_jwt token endpoint authentication	13/03/2019
Cease support for client id and client secret token endpoint authentication	N/A

Implementation

Directory?	Open Banking
Location of Well Known Endpoints?	Open Banking technical directory and Cynergy Bank Developer Portal	https://openbanking.cynergybank.co.uk/
API Standard Implemented?	Open Banking v3.1.1 Open Banking v3.0
Name of Account Holder Implementation Date?	14/03/2020
Date of Current eIDAS Implementation?		eIDAS, OBWAC/OBSEAL
Current Certificates used for Identification?
Current Certificates used for Transport?
Current Certificates used for Signing?
Date of Future eIDAS Implementation?	No future update currently planned.
Future Certificates used for Identification?
Future Certificates used for Transport?
Future Certificates used for Signing?
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 14/03/2020 Infrastructure upgrade 13/03/2020 eIDAS 14/03/2020	(Inc Other Products, API Updates, API Deprecations, etc)
Brand(s)
Security Profile?	FAPI 14/03/2020
Security Profile Certification?	FAPI 14/03/2020
CIBA	N/A	The Bank does not offer a mobile banking app
Using Open Banking as your eIDAS Trust Framework?	No	Cynergy Bank will utilise an independent eIDAS solution provider. Cynergy Bank will also offer OBIE's Dynamic Client Registration
Are you caching the Directory?	No
Transaction IDs	Immutable Transaction ID from Cynergy's Core Banking System

Customer Journey

Implementing Customer Experience Guidelines?	Yes
Implementing Bespoke User Journeys?	No
Implementing App to App?	N/A	Cynergy Bank does not offer a mobile banking app
App to App Implementation Date?	N/A	Cynergy Bank does not offer a mobile banking app
Options on 90 day re-authentication?	90 day consent model as per SCA-RTS Article 10
Support Embedded Flow?	N/A

PSD2

Dispute Management System?	No
FCA Adjustment Period - Maintaining Screen Scraping?	Yes
Seeking Fallback Exemption?	Yes
Adjusted or Fallback Interface?	N/A
Adjusted or Fallback URL?	N/A
Contact Email or Phone Number?	bsmith1@cynergybank.co.uk
Dev Portal URL?	https://openbanking.cynergybank.co.uk
Test Facility Implementation Date?	14 Mar 2019
Production Interface Implementation Date?	14 Mar 2019
Contingency Measures	N/A
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	Exemption will cover all AISP resources
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/A	The 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/A	The Bank does not offer a mobile banking app
Authentication Method Implementation Date (Open Banking Channel)?	14 Mar 2019	Cynergy Bank is currently rolling out a replacement 2FA service which will be available to all online channels simultaneously at point of deployment
Authentication Method Implementation Date (Private Channel)?	14 Sep 2019	Cynergy Bank will implement the Authentication Method on 13 Jan 2020 however, the Authentication Method won't be switched on until 13 Mar 2020 , once the Bank has provisioned customers for new 2FA services.
SCA Implementation Date?	14 Mar 2020
SCA Scope? (will it inhibit non PSD2 accounts)	Applicable for all payment account holders with Customer Channel (Online Banking) access. Appli

Key Implementations

High Cost Credit	TBC

Waiver 7 Implementation Date	TBC