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

User

At bunq, everything revolves around the User—it's the foundation of our app, services, and API. That’s why almost every endpoint you’ll use starts with /user.

There are three types of users, each with its own endpoints, permissions, and properties:

  • user-person – for individual users (/user-person)

  • user-company – for business users (/user-company)

  • user-payment-service-provider – for PSD2-certified third-party providers (/user-payment-service-provider)

The general /user endpoint acts as a smart wrapper over all these types. So when you make a GET /user request after opening a session, you’ll receive your specific user ID and type—this is usually one of the first steps in any integration.

👤 user-person and user-company

These are regular bunq users with subscriptions. If you're a bunq customer, you'll fall into one of these categories. As a user, you can:

  • Create monetary accounts (our term for bank accounts)

  • Order cards

  • Make and receive payments

These objects work together and have subtypes, which we’ll explain in the next sections.

🏦 user-payment-service-provider

This type of user is for companies certified under PSD2 regulations. When a company registers a valid eIDAS certificate, we create a user-payment-service-provider account and return an API key.

These users:

  • Don’t have access to the bunq app

  • Can only operate via the API

  • Can act on behalf of bunq users, within the scope of their PSD2 role:

    • AISP (Account Information Service Provider)

    • PISP (Payment Initiation Service Provider)

    • CBPII (Card-Based Payment Instrument Issuer)

Example:

Last updated

Was this helpful?