Card Credit

post

Create a new credit card request.

Path parameters

userIDintegerRequired

Header parameters

Cache-ControlstringOptional

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

User-AgentstringRequired

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-LanguagestringOptional

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-RegionstringOptional

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-IdstringOptional

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-GeolocationstringOptional

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-AuthenticationstringRequired

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

Body

first_linestringWrite-onlyOptional

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_linestringWrite-onlyRequired

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_cardstringWrite-onlyRequired

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_cardstringWrite-onlyOptional

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

typestringWrite-onlyRequired

The type of card to order. Can be MASTERCARD.

product_typestringWrite-onlyRequired

The product type of the card to order.

monetary_account_id_fallbackintegerWrite-onlyOptional

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

order_statusstringWrite-onlyOptional

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

Responses

200

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).

application/json

400

This is how the error response looks like for 4XX response codes

application/json

post

HTTPcURLJavaScriptPython

POST /v1/user/{userID}/card-credit HTTP/1.1
Host: public-api.sandbox.bunq.com
User-Agent: text
X-Bunq-Client-Authentication: text
Content-Type: application/json
Accept: */*
Content-Length: 361

{
  "first_line": "text",
  "second_line": "text",
  "name_on_card": "text",
  "preferred_name_on_card": "text",
  "alias": {
    "type": "text",
    "value": "text",
    "name": "text",
    "service": "text"
  },
  "type": "text",
  "product_type": "text",
  "pin_code_assignment": [
    {
      "type": "text",
      "routing_type": "text",
      "pin_code": "text",
      "monetary_account_id": 1
    }
  ],
  "monetary_account_id_fallback": 1,
  "order_status": "text"
}

{
  "Id": {
    "id": 1
  }
}