Coverage
Live bank connections in nine markets
Direct connections to banks in Austria, Belgium, France, Germany, Lithuania, Latvia, the Netherlands, Spain and the United Kingdom — every one of them monitored around the clock, and all of them behind the same API. Choose a market to see how payment initiation works there and what a licensed PISP needs in place, or see every individual bank, read live from the registry, on the Bank connections page.
Markets at a glance
Regulator, interface standard and payment rail for each market. The regulator matters to you as a passporting PISP; the standard and the rail are our problem.
| Market | Regulator | Interface standard | Rail |
|---|---|---|---|
| Austria | Finanzmarktaufsicht (FMA) | Berlin Group NextGenPSD2 | SEPA Instant Credit Transfer |
| Belgium | National Bank of Belgium (NBB) | Berlin Group NextGenPSD2 and STET, by bank | SEPA Instant Credit Transfer |
| France | Autorité de contrôle prudentiel et de résolution (ACPR) | STET PSD2 API | SEPA Instant Credit Transfer |
| Germany | Bundesanstalt für Finanzdienstleistungsaufsicht (BaFin) | Berlin Group NextGenPSD2 | SEPA Instant Credit Transfer |
| Lithuania | Bank of Lithuania (Lietuvos bankas) | Berlin Group NextGenPSD2 | SEPA Instant Credit Transfer |
| Latvia | Latvijas Banka | Berlin Group NextGenPSD2 | SEPA Instant Credit Transfer |
| Netherlands | De Nederlandsche Bank (DNB) | Berlin Group NextGenPSD2 and bank-specific APIs | SEPA Instant Credit Transfer |
| Spain | Banco de España | Redsys PSD2 hub (Berlin Group profile) | SEPA Instant Credit Transfer |
| United Kingdom | Financial Conduct Authority (FCA) | UK Open Banking Standard | Faster Payments |
Many standards, one integration
One API
The same create-payment request works in every market. The rail is chosen from the currency, and the bank's standard never reaches your code.
One status model
Every bank's statuses map to the same small set, and every payment reaches a final state. Where a bank stops reporting early, the API tells you that bank's ceiling up front.
One watch
Every connection in every market is measured every five minutes, with a dedicated AI agent per bank. How monitoring works.
Coverage questions
- Which countries does MVP Payments cover?
- MVP Payments has live bank connections in nine markets: Austria, Belgium, France, Germany, Lithuania, Latvia, the Netherlands, Spain and the United Kingdom. Coverage grows continuously — if the market you need is not listed, ask us where it sits on the roadmap.
- Are the connections direct or through an aggregator?
- Direct. Every connection goes to the bank’s own PSD2 interface or to the national hub the bank itself uses, such as Redsys in Spain. There is no third-party aggregator in the payment path.
- Which API standards are supported?
- Berlin Group NextGenPSD2, STET, the Redsys hub, the UK Open Banking Standard and bank-specific APIs. All of them are normalised to one REST API, one payment status model and one signed webhook format, so your integration is identical in every market.
- Do we need a licence in every country?
- Within the EU and EEA, no: one PISP authorisation plus passport notifications covers every member state, and your eIDAS certificates are valid in all of them. The United Kingdom is separate and requires authorisation or registration with the Financial Conduct Authority.
- How do we find out which banks are covered in a country?
- The Bank connections page lists every bank the platform connects to, read live from the registry that the banks endpoint serves, with each bank’s expected final status. Filter it by country to see a single market.
Need a market that isn't listed?
New connections are added continuously, and client demand sets the order. Tell us where your merchants' customers bank.