Create a MasterCard branded card

The customer id of which customer you want to create the card on

The account id that the card should be connected to

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.

The audit user to log the request

Field enables to group an entity into a segment. This field will be exported but no logic is applied to this in Enfuce API

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

Id used for digital wallet artwork and other related assets. Use of this need to be agreed with Enfuce separately

Scheduled closing of the card. Use of this object should be aligned with Enfuce prior to use.

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.

JWE encrypted card number, see details above

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.

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.

Address used to deliver pin

Address used to deliver card

Short description of the result of the action

Will contain the ID of the resource that has been created or updated