---
title: "Update a debit Mastercard branded card"
method: PATCH
path: "/v4/DEBIT_MC/{id}"
tags: ["Update card"]
---

# Update a debit Mastercard branded card

`PATCH /v4/DEBIT_MC/{id}`

This operation will update given fields given a card id

## Path parameters

- `id` string, biginteger, required

## Query parameters

- `auditUser` string, required

## Request body

- PatchStandardResourceBody
  - `accountId` string — The account id card is linked to
  - `customerId` string — The customer id card is linked to
  - `embossing` Embossing — 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.
  - `reason` string — Reason for contract status change
  - `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
  - `status` 'CARD_OK' | 'CARD_BLOCKED' | 'SUSPECTED_FRAUD' | 'CARD_CLOSED_DUE_TO_FRAUD' | 'CARD_NO_RENEWAL' | 'CARD_LOST' | 'CARD_STOLEN' | 'CARD_CLOSED'
  - `usageLimits` UsageLimit[] — Usage limits Use cases: 1. No spend or usage limits If spend and usage should not be limited, then the default configuration is applied. By default, both the singleAmount and sumAmount are set to 0, indicating that no spend limit is set. The count is set to 9999999 indicating that a high (almost unlimited) number of transactions are allowed without any usage limit set. usageLimits.values.singleAmount = 0 usageLimits.values.sumAmount = 0 usageLimits.values.count = 9999999 2. Spend limit per transaction If the maximum spend should be limited for the defined transaction type, set the singleAmount to the desired maximum. If only the singleAmount is set, then both the singleAmount and the count will default to 0 indicating that there is no cumulative spend limit and the number of allowed transactions are not limited. Example: Maximum allowed spend per transaction is 1000 usageLimits.values.singleAmount = 1000 usageLimits.values.sumAmount = 0 usageLimits.values.count = 0 3. Cumulative spend limit If the amount spent under a time period should be limited, set the sumAmount to the desired maximum. If only the sumAmount is set, then both the singleAmount and the count will default to 0 indicating that there is no limit on the number of allowed transactions or on single amounts. Example: Maximum allowed spend under a certain period of time is 1200 usageLimits.values.singleAmount = 0 usageLimits.values.sumAmount = 1200 usageLimits.values.count = 0 4. Usage limit If the number of allowed transaction under a time period should be limited, set the count to the desired maximum. If only the count is set, then both the singleAmount and the sumAmount will default to 0 indicating that there is no limit on the allowed amounts. Example: Maximum number of allowed transactions under a certain period of time is 5 usageLimits.values.singleAmount = 0 usageLimits.values.sumAmount = 0 usageLimits.values.count = 5 5. Combinations of usage and spend limits If multiple limits should apply, set each applicable limit to the desired value. Any unset limiter will default back to 0. Example: Limit the allowed number of transactions to 5 and the allowed amount to 1000 under a certain period of time usageLimits.values.singleAmount = 0 usageLimits.values.sumAmount = 1000 usageLimits.values.count = 5 6. Restrict Usage To disable a specific use case for the card—such as ATM transactions—set all corresponding values for that usage type to 0. Example: Disable ATM usage by setting all limits to 0 usageLimits.values.singleAmount = 0 usageLimits.values.sumAmount = 0 usageLimits.values.count = 0
    - `code` '24H' | 'DAILY' | 'MONTHLY' | 'WEEKLY' | 'ANNUAL_YEARLY' | 'ROLLING_YEARLY' — Usage Limiter Time Periods Available usage limiters include: * __24H__ - A sliding window limiter covering the last 24 hours. * __WEEKLY__ - Limits usage for the current week, starting on Monday. * __MONTHLY__ - Limits usage for the current month, starting on the 1st. __Note:__ The following usage limiters are not part of the standard usage limiter setup. The use of these fields and their values depends on the institution's configuration and must be coordinated with Enfuce before use. * __DAILY__ - Limits usage for the current day, starting at 00:00. * __ANNUAL_YEARLY__ - Limits usage for the current year, starting on 1st January. * __ROLLING_YEARLY__ - A sliding window limiter covering the year until now. (DAILY, WEEKLY, MONTHLY and ANNUAL_YEARLY are reset at midnight UTC)
    - `values` LimitValues[]
      - `code` 'ATM' | 'RETAIL' | 'ALL' — Note that all values must be present when set. Usage limiter values are: * __ATM__ - ATM max withdrawal limit * __RETAIL__ - Retail max purchase limit * __ALL__ - All usage max limit
      - `reset` boolean — If set to true this specific usage limit will be reset to product default and any other values sent in to the request will be ignored. Example: If __usageLimits.values.reset__ = true then all values below will be ignored and the default configuration will apply. usageLimits.values.singleAmount = 1000 usageLimits.values.sumAmount = 1200 usageLimits.values.count = 5
      - `singleAmount` number — The max allowed amount of a single transaction. Example: Maximum allowed spend per transaction is 1000 usageLimits.values.singleAmount = 1000 usageLimits.values.sumAmount = 0 usageLimits.values.count = 0
      - `count` integer — The max number of transactions allowed under a time period. Example: Maximum number of allowed transactions under a certain period of time is 5 usageLimits.values.singleAmount = 0 usageLimits.values.sumAmount = 0 usageLimits.values.count = 5
      - `sumAmount` number — The max allowed amount under a time period. Example: Maximum allowed spend under a certain period of time is 1200. usageLimits.values.singleAmount = 0 usageLimits.values.sumAmount = 1200 usageLimits.values.count = 0
  - `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
  - `cardAddress` UpdateAddress
    - `address1` string
    - `address2` string
    - `address3` string
    - `address4` string
    - `city` string
    - `country` string — A valid ISO 3166-1 alpha-3 country code, except for QZZ (UNMIK in Kosovo) and ROM for Romania.
    - `region` string
    - `zipCode` string
  - `cardDeliveryType` 'CUSTOM_1' | 'CUSTOM_2' | 'CUSTOM_3' | 'CUSTOM_4' | 'CUSTOM_5' | 'MAIL' | 'COURIER' — Valid card delivery types in API
  - `pinAddress` UpdateAddress
    - `address1` string
    - `address2` string
    - `address3` string
    - `address4` string
    - `city` string
    - `country` string — A valid ISO 3166-1 alpha-3 country code, except for QZZ (UNMIK in Kosovo) and ROM for Romania.
    - `region` string
    - `zipCode` string
  - `pinDeliveryType` 'CUSTOM_1' | 'CUSTOM_2' | 'CUSTOM_3' | 'CUSTOM_4' | 'CUSTOM_5' | 'MAIL' | 'COURIER' | 'EPIN' — Valid pin delivery types in API
  - `regionAndEcommBlocking` RegionAndEcommBlocking — Card ecomm and geo-region blocking
    - `ecomm` boolean — Block e-comm usage
    - `africa` boolean — Block Africa region
    - `asia` boolean — Block Asia region
    - `europe` boolean — Block Europe region
    - `home` boolean — Block home region
    - `northAmerica` boolean — Block North-America region
    - `oceania` boolean — Block Oceania region
    - `southAmerica` boolean — Block South-America region
  - `cardUsageBlocks` CardUsageBlocks — Card usage blocks
    - `cardPresent` boolean — Card-present environment transactions. true = the transaction type is blocked false = the transaction type is allowed
    - `atmCashDisbursement` boolean — ATM cash disbursement transactions. true = the transaction type is blocked false = the transaction type is allowed

## Response `200`

Successful update of the card

- 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

- `400` — Bad request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Entity 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)