Versions Compared

Old Version 27

changes.mady.by.user Praveen Ponnumony

Saved on

compared with

New Version 28

changes.mady.by.user Praveen Ponnumony

Saved on

Key

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


Method of Identification
Panel
titleColorBlack
borderStyledashed
titleOB Standards
borderStyledashed
titledetails

This Section applies to ASPSPs that have impletemented OB Standards


Info
iconfalse
idStandards-Production
Implement Open Data v2.2TBCImplement Read/Write API Specification v3.1TBCImplement Customer Experience Guidelines v1.1TBCImplement App-to-App RedirectionTBCImplement OB Security Profile Implementer's Draft v1.1.2TBCImplement FAPI Profile Implementers Draft 2TBCImplement CIBA Profile Implementers Draft 1N/AImplement Dynamic Client Registration v1.1TBCImplement Dynamic Client Registration v3.1TBCDecommission Read/Write API Specification v1.x/2.x Decommission OB Security Profile Implementer's Draft v1.xTBC
Panel


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

Read/Write API - Which date are you planning to implement your latest version?

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 

PISP - Single Payment Limit£
PISP - Daily Payment Limit£
How many months of transaction do you provide?




Panel
titleColorBlack
borderStyledashed
titleSecurity Profile


Page Properties
idID-Production
Commence support for eIDAS QWAC certificates Commence support for eIDAS QSEAL certificates
 N/A

Commence support for OBIE QWAC-like certificates

N/ACommence support for OBIE QSEAL-like certificatesN/ACease support for OBIE non eIDAS-like certificates for transportN/ACease support for OBIE non eIDAS-like certificates for signingN/ASupport for MTLS token endpoint authentication Support for private_key_jwt token endpoint authentication 


Which Security profile have you Implemented or planning to implement?

(Lowest version = Current, Highest version = Planned)

  •  OB Security Profile (Legacy)
  •  FAPI
  •  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
TBC






titleColor
Panel
White
titleBGColor#6180c3
borderStyledashed
titlePost Brexit Certificate Implementation


PRE-BREXIT - Certificates Accepted (until 31st Dec 2020)
Page Properties
idStandards-Production


  •  eIDAS QWAC
  •  eIDAS QSealC
  •  OB legacy (obtransport, obsigning)
  •  OBWAC
  •  OBSeal
  •  Other (Please define) 
POST-BREXIT TRANSITION - Certificates Accepted (1st Jan 2021 - 30th Jun 2021)
  •  eIDAS QWAC
  •  eIDAS QSealC
  •  OB legacy (obtransport, obsigning)
  •  OBWAC
  •  OBSeal
  •  Other (Please define) 

POST-BREXIT POST TRANSITION - Certificates Accepted (from 1st Jul 2021)
  •  eIDAS QWAC
  •  eIDAS QSealC
  •  OB legacy (obtransport, obsigning)
  •  OBWAC
  •  OBSeal
  •  Other (Please define) 

Planned Implementation Date to Satisfy FCA's Post TransitionFrom 10/12/2020, Metro Bank will accept OBWAC certificates in our Test Facility. From 01/01/2021 we will accept OBWAC certificates in Production. 
TPP PSU Migration Outcomes Supported (see eIDAS Migration Playbook)

N/A


POST-BREXIT Certificate Implementation Status (updated by OBIE IES team)

statusReadycolour





Yellow
Panel
titleColor
titlePLANNED
ASPSP accept eIDAS certs and working towards accepting OB certs(OBWAC/OBSeal)
Panel
Black
borderStyledashed
titleImplementationCustomer Journey


Name of Account Holder Implementation DateFuture Certificates used for Signing?
Page Properties
idTC-IMP

Directory?

MCI

Location of Well Known Endpoints?

N/A

API Standard Implemented?

N/A
CJ


What is your approach to Implementing OBIE 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

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?

N/A for MCI
Date of Current eIDAS Implementation? eIDASCurrent Certificates used for Identification?

QWAC

Current Certificates used for Transport?QWACCurrent Certificates used for Signing?QWACDate of Future eIDAS Implementation?No future update currently planned.Future Certificates used for Identification?Future Certificates used for Transport?
The concept of 90 day re-authentication is not applicable to MCI channel




Panel
titleColorBlack
borderStyledashed
titlePSD2


Page Properties
idTC-PSD2


Which Directory are you using as your Trust Framework?Open Banking
Are you caching the Directory?No
Transaction IDs SupportedOption 1Metro Bank provide a Unique, Immutable TransactionID from our core system

Are you enrolled to Dispute Management System?

  •  Yes
  •  No

Are you Seeking Fallback Exemption?

  •  Yes
  •  No


Article 10 - Maximum time period after authenticationN/A
Article 10 - Endpoints exempt of SCA

N/A


Major Milestones

Metro will be delivering our Modified Customer Interface (MCI) as our long term TPP access solution on 12th March 2020.  To be compliant with the PSD2 regulations we will be using eIDAS (QWAC) certificates to authenticate TPPs and will no longer use OBWAC based authentications.

We’d love for you to start using our MCI solution to help bring the Banking Revolution to customers.  To register your app to use the MCI, please follow the "Dynamic Client Registration"  link.  For instructions on how to use the MCI once your app is registered, please follow the "Using the MCI" link.

Our MCI Test Facility is already live – you can find loads of useful information on our Developer Portal: developer.metrobankonline.co.uk.

We previously let you know that we were developing a suite of APIs as our long term strategic solution. We are no longer working on PSD2 APIs (Account API v1, Account API v3.1.1, Payment API v3.1.1) and intend to use the MCI solution as our TPP access interface for the foreseeable future.  Our current v1.0 APIs are being deprecated and will be withdrawn on 12 March 2020.

(Inc Other Products, API Updates, API Deprecations, etc)


Brand(s)Metro Bank
Security Profile?Security Profile Certification?

CIBA

NoUsing Open Banking as your eIDAS Trust Framework?YesAre you caching the Directory?NoTransaction IDsOption 1

Metro Bank provide a Unique, Immutable TransactionID from our core system

Panel
borderStyledashed
titleCustomer Journey
No
Page Properties
idTC-CJ

Implementing Customer Experience Guidelines?

YesCurrent CEG Version?Next CEG Version?Next Version Implementation Date

Implementing Bespoke User Journeys?

No

Implementing App to App?

App to App Implementation Date?N/A

Options on 90 day re-authentication?

N/A for MCI

The concept of 90 day re-authentication is not applicable to MCI channel

Support Embedded Flow?

No




Panel
titleColorBlack
borderStyledashed
titlePSD2ASPSP Dev Portal and Contact Details


FCA Adjustment Period - Maintaining Screen Scraping?Adjusted or Fallback URL
Page Properties
idTC-PSD2

Dispute Management System?

Yes
CJ


?

Location of Well Known Endpoints

N/A

Seeking Fallback Exemption?

No

Adjusted or Fallback Interface?

Yes

Modified Customer Interface URL (if applicable)

https://developer.metrobankonline.co.uk/dcr
Contact Email or Phone Number?

psd2support@metrobank.plc.uk


Dev Portal URL
?
https://developer.metrobankonline.co.uk/home
Test Facility
Implementation Date?TBCProduction Interface Implementation Date?TBCContingency MeasuresArticle 10 - Maximum time period after authentication?N/AArticle 10 - Endpoints exempt of SCAN/A

Authentication Method - Open Banking Channel (Browser)?

Browser Linking plus Risk Score and Username/Password

Authentication Method - Open Banking Channel (APP)?

N/A

Authentication Method - Private Channel (Browser)?

Browser Linking plus Risk Score and Username/Password

Authentication Method - Private Channel (APP)?

Device Binding and PiN/Device Side Biometric

Authentication Method Implementation Date (Open Banking Channel)?

TBC

Authentication Method Implementation Date (Private Channel)?

TBC

SCA Implementation Date?

TBC

SCA Scope? (will it inhibit non PSD2 accounts)

The scope includes: Customer Logon, Non-exempt payment journeys and high risk journeys for all accountsScope of solution only supports Payment Accounts.  Non PSD2 accounts are not affected by this implementation.
URL

ASPSP Support Desk Email or Phone Number

psd2support@metrobank.plc.uk




Panel
titleColorBlack
borderStyledashed
titleKey Implementations


TBC

Page Properties
idTC-HCC


High Cost Credit

TBC

View file
nameHCC.xlsx
height250

Page Properties
idTC-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