Where does this bank list come from?

From the platform’s bank registry — the same published data the banks endpoint serves to integrations. The page reads it when it loads, so a bank appears here once it is enabled and leaves once it is withdrawn. Nothing on the page is kept by hand.

What does a bank’s final status mean for our integration?

It is the furthest a bank reports a payment on the success path. Initiated means the bank confirms final success, so every payment ends Initiated or Failed. Processing means the bank accepts the initiation and then goes quiet: never treat Processing as success, and expect an untouched payment to end Failed with the reason Expired at its expiry time. Failed is possible at every bank.

Whose test data is shown in a test journey?

The bank’s own. A test journey repeats what the bank publishes about its sandbox on a public page — the screens a tester sees, any published test persona, and how to reach each outcome — and links to the page it came from. It never carries real customer credentials, and nothing in it is issued to us privately. The platform’s own mock banks are the exception: their journeys are ours, built from the same magic amounts as the getting-started guide, and carry no source link.

Why is a bank we need not listed?

The list shows the banks enabled on the platform right now: under Sandbox, the banks you can test against; under Production, every bank we connect to. A bank that is temporarily withdrawn, for example during an outage on the bank’s side, leaves the list until it is restored, and banks still being connected join it once they pass testing. If the bank you need is missing, tell us — client demand sets the order in which new connections are added.

Connections

Bank connections

Every bank MVP Payments connects to, read live from the same registry that the banks endpoint serves — so this list is never kept by hand. It has two filters. Sandbox is where you integrate and test against each bank’s own test environment: each bank shows how the payer authenticates, the final status the bank reports, how its sandbox connection has performed over the last 24 hours and, where the bank publishes one, its sandbox test journey with any test-user credentials. Production lists every bank we connect to, market by market, for real payments under your own licence — with no test data. How to read this page.

Loading the bank list…

This list is built in your browser and needs JavaScript. The sandbox list is also public JSON: https://api.mvp-payments.com/v1/banks?environment=sandbox. The Production view needs JavaScript and our partner password.

How to read this page

Sandbox

The default filter: every bank you can test against today, in the bank’s own sandbox. Each card carries the bank’s test journey, including any test-user credentials, its final status and its sandbox health. Nothing under this filter moves real money.

Production

Every bank the platform connects to, grouped by market, with the markets it serves, its SCA model, rails and currencies. Live — the bank’s production connection is live on the platform. A final status is shown once a bank is live, because a bank’s sandbox can report differently from production. No test journeys, credentials or health are shown under this filter. The Production view is behind a simple password for our partners.

Final status

Each bank shows the highest status it reports on the success path — Initiated or Processing. The API reference defines it as follows:

A subset of PaymentStatus: the highest status this bank reports on the success path, for the caller's environment. Compare it directly against a payment's status — when they are equal the bank will report nothing further on the success path. INITIATED — poll or await the webhook to INITIATED | FAILED. PROCESSING — the bank accepts the initiation and then goes quiet; PROCESSING MUST NOT be treated as success, and an untouched payment will end FAILED with failureReason EXPIRED at expiresAt, which is a platform timeout, not a bank rejection. FAILED is reachable for every bank regardless of this value. New values may be added and will only ever be HIGHER than INITIATED (e.g. SETTLED) — treat an unrecognised value as reaching finality; do not switch exhaustively.

Health

Health covers the platform’s calls to each bank’s sandbox over the last 24 hours: the share that succeeded and the 95th-percentile response time (p95). Healthy means at least 90% of calls succeeded, Degraded 50% to 90%, and Down under 50%. Maintenance means operations have paused the connection, for example for a maintenance window the bank has announced; no numbers are shown while it lasts.

No recent traffic means the platform made no calls to that bank’s sandbox in the last 24 hours, so there is nothing current to measure — it says nothing either way about whether the bank is up. A bank without a health badge has not been measured yet. Health is reported for the sandbox environment only.

Verification

Browser-verified — the whole test journey, including the bank’s own screens, has been run end to end in a browser against the bank’s sandbox. API-verified — the platform’s calls to the bank’s sandbox are verified, but the bank’s screens have not been run end to end. Blocked — the bank’s sandbox currently prevents a complete test; the bank’s test journey says why.

SCA model

How the payer approves the payment with their bank. Redirect — the payer is sent to the bank’s own website or app. Embedded — the payer enters the bank’s login and one-time code on the hosted payment page, which passes them to the bank and never stores them. Decoupled — the payer approves in the bank’s app while the hosted payment page waits.

Bank connection questions

Where does this bank list come from?: From the platform’s bank registry — the same published data the banks endpoint serves to integrations. The page reads it when it loads, so a bank appears here once it is enabled and leaves once it is withdrawn. Nothing on the page is kept by hand.
What does a bank’s final status mean for our integration?: It is the furthest a bank reports a payment on the success path. Initiated means the bank confirms final success, so every payment ends Initiated or Failed. Processing means the bank accepts the initiation and then goes quiet: never treat Processing as success, and expect an untouched payment to end Failed with the reason Expired at its expiry time. Failed is possible at every bank.
Whose test data is shown in a test journey?: The bank’s own. A test journey repeats what the bank publishes about its sandbox on a public page — the screens a tester sees, any published test persona, and how to reach each outcome — and links to the page it came from. It never carries real customer credentials, and nothing in it is issued to us privately. The platform’s own mock banks are the exception: their journeys are ours, built from the same magic amounts as the getting-started guide, and carry no source link.
Why is a bank we need not listed?: The list shows the banks enabled on the platform right now: under Sandbox, the banks you can test against; under Production, every bank we connect to. A bank that is temporarily withdrawn, for example during an outage on the bank’s side, leaves the list until it is restored, and banks still being connected join it once they pass testing. If the bank you need is missing, tell us — client demand sets the order in which new connections are added.

One integration for every bank on this list

The same API, the same statuses and the same signed webhooks for every connection — run under your own PISP licence. Start in the sandbox today.

Get started in the sandbox Email sales