Bring your own PISP licence
Open Banking infrastructure for licensed PISPs
You hold the licence. We run everything underneath it — direct bank connections in nine markets, AI-driven connectivity monitoring, one API and a hosted payment page in your merchants' branding.
- Austria Live
- Belgium Live
- France Live
- Germany Live
- Lithuania Live
- Latvia Live
- Netherlands Live
- Spain Live
- United Kingdom Live
Your licence, your merchants, your margin. Payments are initiated under your PISP authorisation with your own eIDAS certificates. MVP Payments is the technical provider — we never hold funds, and we never stand between you and your customers. Read how bring-your-own-licence works.
Why infrastructure
A PISP licence is the hard part. Connectivity shouldn't be the second one.
Every bank implements PSD2 its own way — different standards, different signing rules, different authentication journeys — and changes them without much notice. Building that estate yourself takes years, and keeping it working takes a team for good.
Live sooner
Integrate one API, hand us your certificates, and initiate payments across nine markets under your own licence — without writing a single bank connector.
Direct, not aggregated
Every connection goes straight to the bank or its national hub. No third-party aggregator in the payment path, so no one else's outage, margin or roadmap between you and the bank.
Watched, not assumed
Each connection's health is measured every five minutes, and each bank has its own AI agent that knows that bank's history — so a degrading connection is found early and explained, not guessed at.
How it works
Three steps from licence to live payments
Bring your licence
We record your authorisation — regulator, licence number, home country — and install your QWAC and QSealC in an encrypted secrets vault, under supervised, audited upload.
Integrate once
One REST API and one set of payment statuses across every bank and standard. Use our hosted payment page in your merchants' branding, or keep every screen with the API-only path.
Go live under your name
Banks see your certificates and your authorisation number. You receive signed webhooks at every final status, and a dashboard your operations team can run the business from.
The platform
Everything under the licence, already built
Direct bank connections
Berlin Group NextGenPSD2, STET, the Redsys hub, the UK Open Banking Standard and bank-specific APIs — normalised to one API, one status model and one webhook format.
AI-driven connectivity monitoring
Success rate and latency per bank, evaluated every five minutes, with a dedicated AI agent per bank that diagnoses changes against that bank's own history.
Hosted payment page, white-labelled
Bank picker, approval hand-off and outcome screen in 20 languages. Any number of merchant brands per account, stamped onto each payment when you create it.
API, webhooks and dashboard
A payment in one request. Final statuses arrive as webhooks signed with a key that is yours alone, and every action in the dashboard leaves an audit record.
Coverage
Live bank connections in nine markets
Austria, Belgium, France, Germany, Lithuania, Latvia, the Netherlands, Spain and the United Kingdom — each with its own regulator, API standard and banking habits. Each country page explains how payment initiation works there and what a licensed PISP needs in place.
Developers
A payment in one request
Sandbox and live behave identically — same statuses, same signed webhooks, same errors. Your team starts in the sandbox today and goes live without changing a line.
curl https://api.mvp-payments.com/v1/payments \
-H "x-api-key: $MVP_API_KEY" \
-H "x-mvp-client-id: $MVP_CLIENT_ID" \
-H "x-mvp-client-secret: $MVP_CLIENT_SECRET" \
-H "content-type: application/json" \
-d '{
"amount": "12.00",
"currency": "EUR",
"beneficiary": { "name": "Your Merchant Ltd", "iban": "DE89..." },
"callbackUrl": "https://your-merchant.example/return"
}'
# Pounds settle over UK Faster Payments — sort code and account number, never an IBAN:
# "currency": "GBP",
# "beneficiary": { "name": "Your Merchant Ltd", "sortCode": "000000", "accountNumber": "00000001" },Questions licensed PISPs ask us
- What does "bring your own PISP licence" mean?
- You hold the regulatory authorisation to provide payment initiation services; MVP Payments provides the technology. Payments are initiated under your licence, identified to each bank by your own eIDAS certificates, for your own merchants. MVP Payments acts as your technical service provider: we build, run and monitor the bank connections, the API and the hosted payment page.
- Who is MVP Payments for?
- Authorised payment institutions, e-money institutions and banks that hold — or are obtaining — permission to provide payment initiation services, and would rather put their engineering effort into their own product than into building and maintaining connections to hundreds of bank APIs.
- Does MVP Payments ever hold funds?
- No. Payment initiation moves money directly from the payer’s bank account to the beneficiary’s. MVP Payments never enters into possession of funds — there is no wallet, no float and no settlement account in the middle.
- Where are bank connections live?
- MVP Payments has live bank connections in nine markets: Austria, Belgium, France, Germany, Lithuania, Latvia, the Netherlands, Spain and the United Kingdom. Every connection is direct to the bank or its national hub — there is no third-party aggregator in the payment path.
- How is this different from an Open Banking aggregator?
- An aggregator sells you payments under its own licence and sits between you and your merchants’ money flow as the regulated party. MVP Payments is infrastructure: you remain the regulated PISP, you own the merchant relationship and the economics, and the bank sees your certificates — not ours.
Put your licence to work
Tell us where you are authorised, which markets you want to reach and roughly what you expect to put through. We'll show you the platform against your own use case.