For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

Banking as a Service

bunq is a fully licensed European bank — and we're opening the entire stack to developers and businesses who want to build financial products without starting from scratch.

With bunq's Banking as a Service (BaaS) APIs, you get direct access to the same core infrastructure that powers millions of bunq accounts: real IBANs, payment rails, card issuing, and identity verification. No middleware, no workarounds — just clean REST APIs backed by a real bank.

BaaS APIs are available to approved partners. Get in touch to discuss access.


What you can build

Whether you're embedding financial services into an existing product or building a fintech from the ground up, bunq BaaS gives you the building blocks to do it:

  • KYC as a Service — verify your users' identities using bunq's regulated onboarding flow, without building your own compliance infrastructure.

  • Monetary Accounts — open and manage euro bank accounts (with real IBANs) on behalf of your users, programmatically.

  • Payments — initiate SEPA credit transfers, handle incoming payments, and manage payment flows end-to-end.

  • Cards — issue and manage virtual and physical Mastercard debit cards linked to bunq accounts.


How it works

bunq BaaS is built on the same public bunq API that powers our consumer and business products. It uses standard REST over HTTPS, with signed requests for security.

The key paradigm to understand is the user hierarchy: every account, card, and payment lives under a user object. When you use BaaS, you act on behalf of sub-users that your platform creates and manages — giving you full programmatic control while bunq handles the regulatory and banking layer underneath.

Authentication follows the same installation → session pattern used across the bunq API. You'll set up your API credentials once, then use session tokens for all subsequent calls.

For the full authentication flow, see Basics → Getting Started.


BaaS vs the standard bunq API

Standard bunq API
BaaS

Use case

Automate your own bunq account

Build white label financial products for others

User model

Your own bunq user

Sub-users managed by your platform

KYC

bunq handles it for your account

You trigger it via API for your users

Card issuing

Manage your own cards

Issue cards on behalf of sub-users

Typical integrator

Developer, fintech, accountancy tool

Neobank, SaaS platform, marketplace


Next steps

Pick the capability you want to integrate and follow the dedicated guide:

Bank Accounts - As a ServiceCards - As a ServicePayments - As a ServiceKnow Your Customer - As a Service

Last updated

Was this helpful?