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:

Obtain Certificate (QWAC) and Onboard with Open Banking for non UK based TPPs - As a first step towards accessing MCI API, please obtain a valid QWAC certificate from a recognised QTSP and follow the onboarding guide here.
Obtain an Open Banking website authentication certificate (OBWAC) for UK based TPPs – As a first step towards accessing MCI API, please obtain a valid OBWAC certificated from Open Banking and follow the onboarding guide here.
Access Commercial Banking and Retail Banking Channels - Once you have the QWAC or OBWAC 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 or OBWAC as relevant, 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 or OBWAC 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}