Using the MCI

Modified Client Interface (MCI)

To access the Modified Client Interface for the Metro Bank Commercial Banking and Retail Banking channels, Metro Bank has published the MCI API. We also provide a Test Facility for Commercial Banking and Retail Banking channels using the same onboarding and validation processes.

To access the Commercial Banking and Retail Banking channels via the MCI API, please follow the steps below:

  1. Obtain Certificate (QWAC) and Onboard with Open Banking - As a first step towards accessing MCI API, please obtain a valid QWAC certificate from a recognised QTSP and follow the onboarding guide here.
  2. Access Commercial Banking and Retail Banking Channels - Once you have the QWAC and are registered, the MCI API provides the ability to access our Commercial Banking and Retail Banking channels. On successful validation of the client details and QWAC, you will be redirected towards the channel requested.

Modified Client Interface API

Metro Bank requires that API requests are made over a connection secured with mutual TLS. Please use your QWAC to establish the mutual TLS connection with our APIs available at the host https://api.metrobankonline.co.uk

Access Commercial Online Banking Channel

Note: When using the MCI API to access commercial online banking (/open-banking/v3.1/mci/commercial) after successful TPP registration, we request that the TPPs ensure the Authorisation Header information is removed and is not being passed in the redirected commercial online banking channel URL

The following is a sample of the API Request and Response

API Request:

HOST https://api.metrobankonline.co.uk 
GET /open-banking/v3.1/mci/commercial 
HTTP/1.1 Authorization: Basic {base64 encoded value of {client_id}:{client_secret}}

API Response:

HTTP/1.1 302 Found 
Location: https://commercial.metrobankonline.co.uk/portalserver/business-login?X-TPP-Id={software_id from SSA}&X-TPP-Name={software_client_name from SSA}&X-TPP-Role={software roles for UK from SSA}

Access Retail Banking Channel

The following is a sample of the API Request and Response

API Request:

HOST https://api.metrobankonline.co.uk 
GET /open-banking/v3.1/mci/retail HTTP/1.1 
Authorization: Basic {base64 encoded value of {client_id}:{client_secret}}

API Response:

HTTP/1.1 302 Found 
Location: https://personal.metrobankonline.co.uk/MetroBankRetail?X-TPP-Id={software_id from SSA}&X-TPP-Name={software_client_name from SSA}&X-TPP-Role={software roles for UK from SSA}

Access Commercial Online Banking Test Facility Channel

The following is a sample of the API Request and Response

API Request:

HOST https://api.metrobankonline.co.uk 
GET /open-banking/v3.1/mci/commercial-test HTTP/1.1 
Authorization: Basic {base64 encoded value of {client_id}:{client_secret}}

API Response:

HTTP/1.1 302 Found 
Location: https://commercial-tf.metrobankonline.co.uk/portalserver/business-login?X-TPP-Id={software_id from SSA}&X-TPP-Name={software_client_name from SSA}&X-TPP-Role={software roles for UK from SSA}

Access Retail Banking Test Facility Channel

The following is a sample of the API Request and Response

API Request:

HOST https://api.metrobankonline.co.uk 
GET /open-banking/v3.1/mci/retail-test HTTP/1.1 
Authorization: Basic {base64 encoded value of {client_id}:{client_secret}}

API Response:

HTTP/1.1 302 Found 
Location: https://personal-tf.metrobankonline.co.uk/MetroBankRetail?X-TPP-Id={software_id from SSA}&X-TPP-Name={software_client_name from SSA}&X-TPP-Role={software roles for UK from SSA}

 

Updates

 

COB general improvements inc. compatability (PDF)

New feature ‘Sweeps’ added to COB (PDF)  

Change to Bacs payment cycle description (PDF)

Available balance technical update (PDF)

Cross border currency payment regulation update (PDF)

Cross border currency payment regulation update - Day 2 (PDF)

Strong Customer Authentication (PDF)

Update: Amendments to Open Banking Identification Requirements (eiDAS)

From 10th December 2020, our MCI Test Facility for our Retail Online Banking channel and Commercial Online Banking channel will be updated to enable TPPs to test using both eIDAS (QWAC) and OBWAC certificates for authentication purposes.

From 01 January 2021, our MCI Production environment will accept both eiDAS (QWAC) certificates for EU based TPPs and OBWAC certificates for UK based TPPs in line with the recent changes made to the UK-RTS.

This is in consideration that in the post Brexit landscape, UK based TPPs will have had their eIDAS (QWAC) certificates revoked by QTSPs. It should be highlighted that EU based TPPs will continue to be able to use eIDAS (QWAC) certificates.

Please note that we will not be looking to accept any other form of certificates (which do not meet criteria specified in Article 34 of the UK-RTS such as OB legacy certificates) during the transition period. For any TPPs who wish to rely on these certificates during the transition period, please do contact us for further information.