---
title: "Create card"
method: POST
path: "/v3/customer/{customerId}/account/{accountId}/{cardRole}"
tags: ["Create card"]
deprecated: true
---

# Create card

`POST /v3/customer/{customerId}/account/{accountId}/{cardRole}`

> **Deprecated.**

This operation will create an credit card media connected to given customer. An account id needs to be provided as well so we know to which account the card should be connected to.

## Path parameters

- `customerId` string, biginteger, required
- `accountId` string, biginteger, required
- `cardRole` 'MAIN' | 'SUPPLEMENTARY', required — A role needs to be provided for the connection to the account. Role is one way to categorize between primary and supplementary card holders. Role MAIN will always create a card to have same account holder and card holder. For a supplementary card there is a possibility to differ between account and card holder.

## Query parameters

- `auditUser` string, required

## Request body

- CreateV3ResourceBody
  - `cardTemplate` string, required — Card template of the new card to be created
  - `embossing` Embossing, required — Default set of allowed characters for fields embossed onto the card: A-Z, a-z, Áá, Ää, Åå, Ææ, Éé, Íí, Ðð, Óó, Öö, Øø, Úú, Üü, Ýý, Þþ, 0-9, symbols -/.,&+' and space. For printed cards allowed characters are: (including the above) ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõöøùúûüý þÿĀāĂ㥹ĆćĈĉĊċČčĎďĐđĒēĔĕĖėĘęĚěĜĝĞğĠġĢģĤĥĦħĨĩĪīĬĭĮįİıIJijĴĵĶķĸĹ ĺĻļĽľĿŀŁłŃńŅņŇňʼnŊŋŌōŎŏŐőŒœŔŕŖŗŘřŚśŜŝŞşŠšŢţŤťŦŧŨũŪūŬŭŮůŰűŲųŴŵ ŶŷŸŹźŻżŽžſǪǫȘșȚțȪȫȮȯȲȳḐḑṢṣẞỌọ Printed or others characters sets must be agreed in advance.
    - `additionalField1` string — Field value is forwarded to embossing house in order to be used as additional embossing lines. In order to use this field selected embossing house must in advance agree where this is put.
    - `additionalField2` string — Field value is forwarded to embossing house in order to be used as additional embossing lines. In order to use this field selected embossing house must in advance agree where this is put.
    - `additionalField3` string — Field value is forwarded to embossing house in order to be used as additional embossing lines. In order to use this field selected embossing house must in advance agree where this is put.
    - `additionalField4` string — Field value is forwarded to embossing house in order to be used as additional embossing lines. In order to use this field selected embossing house must in advance agree where this is put.
    - `additionalField5` string — Field value is forwarded to embossing house in order to be used as additional embossing lines. In order to use this field selected embossing house must in advance agree where this is put.
    - `companyName` string
    - `externalLayoutCode` string — Code forwarded to embossing house in order to select which plastic layout to use. In order to use this field selected embossing house must in advance agree on name for each layout.
    - `firstName` string — The length of firstName should not exceed 26 characters length. A combined length of firstName and lastName should not exceed 26 characters length.
    - `lastName` string — The length of lastName should not exceed 26 characters length. A combined length of firstName and lastName should not exceed 26 characters length.
    - `additionalEmbossingName` string — Optional additional embossing name to be printed on the card as a second line, alongside the primary embossing name. Usage of this field and its placement on the card must be agreed with the relevant card bureau.
    - `manufacturer` string — Name of manufacturer for the card. This has to be agreed in advance with Enfuce in order to support multiple embossing houses.
    - `physical` boolean — This tag will indicate will there be a physical representation of the card. If true, the card will be placed for card personalisation and end user will receive a physical plastic. If false, the card will not be placed for card personalisation and end user will not receive a physical plastic.
  - `expiration` Expiration
    - `year` integer — Expiration year in format YYYY
    - `month` integer — Expiration month in format MM
  - `pinAddress` Address
    - `address1` string, required
    - `address2` string
    - `address3` string
    - `address4` string
    - `city` string, required
    - `country` string, required — A valid ISO 3166-1 alpha-3 country code, except for QZZ (UNMIK in Kosovo) and ROM for Romania.
    - `region` string
    - `zipCode` string, required
  - `cardAddress` Address
    - `address1` string, required
    - `address2` string
    - `address3` string
    - `address4` string
    - `city` string, required
    - `country` string, required — A valid ISO 3166-1 alpha-3 country code, except for QZZ (UNMIK in Kosovo) and ROM for Romania.
    - `region` string
    - `zipCode` string, required
  - `segment` 'SEGMENT_A' | 'SEGMENT_B' | 'SEGMENT_C' | 'SEGMENT_D' | 'SEGMENT_E' | 'SEGMENT_F' — Field enables to group an entity into a segment. This field will be exported but no logic is applied to this in Enfuce API
  - `pinStatus` 'D' | 'W' | 'S' — This flag will indicate current status for PIN generation. If not specified system will automatically assign D as default and make sure a PIN is calculated during next embossing process. If set to W, then card will be excluded from embossing process until a PIN has been set and status has been updated to S. It is also possible to revert to D, in order for system to generate PIN. Note that system will update to status S automatically when a PIN is set successfully. ### New card In order for a new card to not get a system generated PIN then pinStatus flag must be set to W when created, this will then halt the embossing process for given card until a PIN has been set. ### Reissue card When reissuing a card it is possible to set pinStatus to W in order to hold embossing process for given card until a PIN has been set. Update pinStatus is done on same card id that is reissued. ### Replace card When replacing a card it is possible to set pinStatus to W in order to hold embossing process for given card until a PIN has been set. Update pinStatus is done on new card id that is returned when replacing. - D - default and a random PIN will be generated - W - waiting for PIN to be manually set - S - PIN has been set successfully

## Response `201`

Successful creation of the product

- ResourceResponse
  - `description` string — Short description of the result of the action
  - `id` string — Will contain the ID of the resource that has been created or updated

## Other responses

- `401` — Unauthorized
- `403` — Forbidden
- `404` — Customer does not exist
- `500` — Internal server error

---

[API](https://skmtc.net/enfuce/apis/transfer-api.md) · [All operations](https://skmtc.net/enfuce/apis/transfer-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/enfuce/transfer-api/versions/dc4a41118f80/schema)