We are already returning Account name as per the definition in 3.1.1 as that is what is being displayed in our own channels. We do not show the name of the party (ie customer) in our own channel so we are not mandated to return this information.
Supported identification method?
OBIE certificates
eIDAS
Previously with OBIE certificates the identification method was tls_client_auth (i.e. the certificate was the identification). Now, with eIDAS certificates, during DCR we require the identification method is private_key_jwt (i.e. a TPP provides a JWT signed with a ‘seal’ certificate).
Major Milestones
V1.1 deprecation V3.1 roadmap
SEPA MTS Bulk / Batch Payments - Q1 2020
Bulk / Batch Payments: SEPA MTS Q1 2020
Bulk / Batch Payments (All payment types) Q1 2020
P2 Two Way Notice of Revocation - Q1 2020
P8 SCA Exemptions- Q1 2020
API specification v3.1.4 & CEG v3.1.4- Q1 2020
Uplift to PS256 encryption standard- Q2 2020
P15 Access Dashboards - TBC
Security Profile?
Open Banking
Security Profile Certification?
No
We are conformant against the OB standards and the errors that are viewed in the logs are outside of the requirements
CIBA
No
Using Open Banking as your eIDAS Trust Framework?
Yes
Are you caching the Directory?
No
Directory Caching will be delivered by 24 February 2020 as part of PSD2 onboarding
Transaction IDs
Yes - August 2019
Transaction id's are provided against each booked transaction that are returned on the transactions endpoint