---
title: "Create fleet account"
method: POST
path: "/v4/FLEET/customer/{customerId}"
tags: ["Create an account"]
---

# Create fleet account

`POST /v4/FLEET/customer/{customerId}`

This operation will create a fleet account

## Path parameters

- `customerId` string, biginteger, required

## Query parameters

- `auditUser` string, required

## Request body

- CreateFleetResourceBody
  - `expiration` Expiration
    - `year` integer — Expiration year in format YYYY
    - `month` integer — Expiration month in format MM
  - `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
  - `digitalLayoutCode` string — Id used for digital wallet artwork and other related assets. Use of this need to be agreed with Enfuce separately
  - `scheduledClosing` ScheduledClosing — Scheduled closing of the card. Use of this object should be aligned with Enfuce prior to use.
    - `type` 'TIMEBASED' — This field is used when there is a need to setup the scheduled closing of the card. Use of this field should be aligned with Enfuce prior to use.
    - `time` string, date-time — This field is used to determine the date for closing of the card. Card will be closed on that date which is selected. The time specified in the closing time must adhere to the UTC time zone. Use of this field should be aligned with Enfuce prior to use.
  - `additionalValues` KeyValuePair[] — The additionalValues array is used to store information in the form of key-value pairs. Enfuce does not perform any validation on these key-value pairs beyond ensuring they adhere to the character limit constraints. The primary purpose of these key-value pairs is to store data without further processing. In newer versions of the card personalization files, these key-value pairs are included in the file. However, this inclusion is version-dependent. We recommend consulting the specific version details of your card personalization files to confirm whether these values will be added to the card personalization file in your case.
    - `key` string, required
    - `value` string, required
  - `encryptedData` string — JWE encrypted card number, see details above
  - `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.
  - `productCode` string — This field is used when the institution has multiple card products setup. The productCode is used to determine the specific card product. Use of this field as well as the values of the field, is dependent on institution setup and should be aligned with Enfuce prior to use.
  - `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
  - `allowedPurchaseCategories` 'UNRESTRICTED' | 'ALL_FUELS_INCL_VEHICLE_GOODS_AND_SERVICES' | 'ALL_FUELS' | 'RESTRICTED_FUELS' | 'NO_PRODUCTS'
  - `branchId` string — Field that can be populated in order to group cards together
  - `branchName` string — Field that can be populated in order to group cards together
  - `extraTerminalInformation` 'NONE' | 'VEHICLE_ID_AND_ODOMETER' | 'VEHICLE_ID' | 'ODOMETER'

## Response `201`

Successful creation of the account

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