Frequently Asked Questions
- How do I register my application?
- What kind of data is available to developers?
- Is there a sandbox environment?
- Are the Metro Bank APIs following a banking standard (e.g. Open Banking)?
- Does Metro Bank support payments by API?
- What is the on-boarding process for Metro Bank's fans that use my application?
- Can I partner with Metro Bank?
- How do I get help troubleshooting issues?
- What is the production URL?
- What is the URL to access Metro Bank's secure authentication portal?
- Which Account API should I use, previous or OB conformant?
- Which host URL I should use to obtain SSA and trigger register endpoint?
Our documentation here provides further information on the steps to take to register your application.
We have published AISP and PISP APIs closely inline with version 3.1.1 API specification of Open Banking Implementation Entity (OBIE). We are also continuing with our previously published Account APIs.
Details of the overall process to consume the APIs can be found at our overview page. Detail information of the API contract can be found at our Our APIs section.
Yes. We have published the APIs on our Sandbox environment.
The host URL to access the account and payment APIs on sandbox is https://sandbox.metrobankonline.co.uk.
The host URL for strong customer authentication on sandbox is https://sandbox.metrobankonline.co.uk/identity/v1/authorize.
Metro Bank is on its way to be registered with Open Banking Implementation Entity (OBIE). Our new Account and Payment API portfolios are closely inline with version 3.1.1 of OBIE's read write API specification.
Please play with the smartdocs APIs of account API and payment API resources.
Yes. We are supporting the payments by API. The different API resources on the payment API can be found at payment API.
The on-boarding process is fully automated.
When your application makes a request to the /authorize resource, the customer is redirected to Metro Bank's secure authentication portal.
The customer shall provide any necessary account consent and payment initiation consent via the portal. When that process is complete your application can make further account information and payment initiation requests. The details of the authentication and authorization set up process can be found at the Authorisation and Authentication section.
To discuss API partnerships and propositions please contact us through our support team here.
Please contact our support team here.
The team are ready to assist you with any queries you may have.
The host URL for strong customer authentication on production is https://scapip.metrobankonline.co.uk/portalserver/psd2/authorize.
The host URL to access the account and payment APIs on production is https://api.metrobankonline.co.uk.
The sandbox API can be reached using the URL https://sandbox.metrobankonline.co.uk/identity/v1/authorize.
The production URL is https://scapip.metrobankonline.co.uk/portalserver/psd2/authorize.
If you are not yet registered with us, we would encourage you to use the account apis which are inline with version 3.1.1. read write specification of OBIE. You need to specifically request this service with our support team during registration process and they would guide you through the process.
If you are already registered with us, we would encourage you to plan to migrate to our new APIs. However, are not deprecating the existing APIs at the moment.
The detailed information about app registration is documented at our registration page for sandbox and production, including URLs to be used. In nutshell you need to use our production host URL https://api.metrobankonline.co.uk to trigger APIs required for different phases of registration process.