FAQs
What is the MCI?
The MCI is our Modified Customer Interface and is Metro Bank's initial PSD2 compliant solution for Third Party Providers (TPPs). The MCI will be available until it is superseded by our API services (v3.1.1). The MCI and v3.1.1 API services will coexist for a period of time to enable TPPs to migrate to the API Services.
What can be accessed through the MCI solution?
The MCI allows TPPs to screen scrape on both our Retail and Business Banking or Business Online Plus and Commercial Online Banking platforms. When making a call to use the MCI, the TPP must identify the relevant platform to enable an automatic redirection.
What about the MCI Test Facility?
The MCI Test Facility works in the same way as the MCI Production service will once it's available but uses non-production versions of our Retail and Business Banking or Business Online Plus and Commercial Online Banking platforms. If you wish to make use of the Test Facility, please contact us here. Our support team will issue you with login credentials and test data that will enable you to utilise all PSD2-related services available through those platforms.
Why do I have to register separately for MCI and API Services?
At present, the MCI is the only service connected to the new Open Banking Dynamic Client Registration process. We are working to support registration for Open Banking APIs through Dynamic Client Registration so you will only need to register once to access all our services.
How do I register my application using the Dynamic Client Registration (DCR) API?
Our documentation here provides further information on the steps to take to register your application.
How do I consume the MCI API?
Our documentation here provides further information on the steps to take to register your application.
What is the production host for DCR and MCI API?
The host for accessing the both DCR and MCI is "https://api.metrobankonline.co.uk".
The resource URLs for MCI are specified in the MCI API documentation here.
Is there a sandbox environment for DCR and MCI API?
No. We have not published a sandbox environment for this API as it is very much straightforward. However, you can consume the test facility URLs specified in the MCI API documentation here.
Is the DCR API following a banking standard (e.g. Open Banking)?
Yes. The DCR API is defined as per the OBIE standards defined here.
Can I update or remove an existing application?
We are working towards bringing the update (PUT) and removal (DELETE) APIs for an existing client application. Please visit our developer portal at regular intervals for updates.
What certificates do I need to use to consume the DCR and MCI API?
A valid OBWAC from OB or a valid QWAC from QTSP is required to access the API endpoints for DCR and MCI API. We are supporting QWACs from QTSPs mentioned here.
What certificates do I need to use to sign the JWT?
A valid OBWAC from OB or a valid QWAC from QTSP is required. We are supporting QWACs from QTSPs mentioned here.
What are the operating and support hours for the MCI Test Facility?
The MCI Test Facility is available 24/7/365 except for scheduled maintenance. Support is available from 09:00 to 17:00 Monday to Friday, except public holidays.
Are there any functions available to customers that TPPs cannot access via the MCI Test Facility?
Statement PDFs are available to download in the TPP test facility, but their structure can vary from production. If you need sample PDFs with the same structure as production please contact PSD2 Support here.
Can the MCI Test Facility be used for performance testing?
The MCI Test Facility is not a replica of our production environment so it is unsuitable for performance testing.
As a UK based TPP, can the eIDAS Certificate be used to access DCR and MCI API post-Brexit?
No, the eIDAS Certificates issued to UK based TPPs are invalidated by the issuing QTSP post Brexit and hence OBWAC from Open Banking is to be obtained prior to that.