Sign in
card-credit

Create a new credit card request.

post/user/{userID}/card-credit

Path parameters

userIDinteger required

Headers

Cache-Controlstring

The standard HTTP Cache-Control header is required for all signed requests.

User-Agentstring required

The User-Agent header field should contain information about the user agent originating the request. There are no restrictions on the value of this header.

X-Bunq-Languagestring

The X-Bunq-Language header must contain a preferred language indication. The value of this header is formatted as a ISO 639-1 language code plus a ISO 3166-1 alpha-2 country code, separated by an underscore. Currently only the languages en_US and nl_NL are supported. Anything else will default to en_US.

X-Bunq-Regionstring

The X-Bunq-Region header must contain the region (country) of the client device. The value of this header is formatted as a ISO 639-1 language code plus a ISO 3166-1 alpha-2 country code, separated by an underscore.

X-Bunq-Client-Request-Idstring

This header must specify an ID with each request that is unique for the logged in user. There are no restrictions for the format of this ID. However, the server will respond with an error when the same ID is used again on the same DeviceServer.

X-Bunq-Geolocationstring

This header must specify the geolocation of the device. The format of this value is longitude latitude altitude radius country. The country is expected to be formatted of an ISO 3166-1 alpha-2 country code. When no geolocation is available or known the header must still be included but can be zero valued.

X-Bunq-Client-Authenticationstring required

The authentication token is used to authenticate the source of the API call. It is required by all API calls except for POST /v1/installation. It is important to note that the device and session calls are using the token from the response of the installation call, while all the other calls use the token from the response of the session-server call

Request body

first_linestring

The first line of text on the card, used as name/description for it. It can contain at most 17 characters and it can be empty.

second_linestring required

The second line of text on the card, used as name/description for it. It can contain at most 17 characters and it can be empty.

name_on_cardstring required

The user's name as it will be on the card. Check 'card-name' for the available card names for a user.

preferred_name_on_cardstring

The user's preferred name that can be put on the card.

typestring required

The type of card to order. Can be MASTERCARD.

product_typestring required

The product type of the card to order.

monetary_account_id_fallbackinteger

ID of the MA to be used as fallback for this card if insufficient balance. Fallback account is removed if not supplied.

order_statusstring

The order status of this card. Can be CARD_REQUEST_PENDING or VIRTUAL_DELIVERY.

Response

With bunq it is possible to order credit cards that can then be connected with each one of the monetary accounts the user has access to (including connected accounts).

Changes

Changed in 2 of the 50 revisions of this API.18

  • 818f9a4297e29See the full diff
    • ○

      the request optional property pin_code_assignment/items/routing_type became not write-only

      request-optional-property-became-not-write-only

    • ○

      the request optional property monetary_account_id_fallback became write-only

      request-optional-property-became-write-only

    • ○

      the request optional property order_status became write-only

      request-optional-property-became-write-only

    • ○

      the request optional property pin_code_assignment became write-only

      request-optional-property-became-write-only

    • ○

      the request optional property preferred_name_on_card became write-only

      request-optional-property-became-write-only

    • ○

      the request required property name_on_card became write-only

      request-required-property-became-write-only

    • ○

      the request required property product_type became write-only

      request-required-property-became-write-only

    • ○

      the request required property second_line became write-only

      request-required-property-became-write-only

    • ○

      the request required property type became write-only

      request-required-property-became-write-only

  • 8dfb44c77ea09See the full diff
    • ○

      the request optional property monetary_account_id_fallback became not write-only

      request-optional-property-became-not-write-only

    • ○

      the request optional property order_status became not write-only

      request-optional-property-became-not-write-only

    • ○

      the request optional property pin_code_assignment became not write-only

      request-optional-property-became-not-write-only

    • ○

      the request optional property preferred_name_on_card became not write-only

      request-optional-property-became-not-write-only

    • ○

      the request optional property pin_code_assignment/items/routing_type became write-only

      request-optional-property-became-write-only

    • ○

      the request required property name_on_card became not write-only

      request-required-property-became-not-write-only

    • ○

      the request required property product_type became not write-only

      request-required-property-became-not-write-only

    • ○

      the request required property second_line became not write-only

      request-required-property-became-not-write-only

    • ○

      the request required property type became not write-only

      request-required-property-became-not-write-only

    This revision also has 75 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog