A card serves as the actual payment instrument. Cards can take many forms: They can be plastic, virtual or tokenised elements that work though a variety of devices, like smart watches, mobile phones and rings.
customerId
) and account to which it is linked to (accountId
)
cardID
is the Enfuce database ID for the card that is used for updates and as the main identifier in API and Data Export Files.PAN
) (maskedCardNumber
)
expiration
)
pinStatus
)
segment
) (optional service)
pinAddress
)
cardAddress
)
status
)
usageLimits
, regionAndEcommBlocking
)
(**customerId**, **accountId**)
**cardRole**
)**firstName, lastName**
)Code | Status | Description |
---|---|---|
00 | Card OK | Card is open and in normal status. Potentially suspended tokens linked to card are activated when status is set. |
05 | Card Blocked | Temporary block on the card that will prevent approval of authorisations. Can be used instead of account level temporary block if the goal is to block only a specific card. Tokens linked to card are automatically suspended when status is set. Card status is automatically updated to “Card blocked” when account status is set to “Account to close”. |
205 | Suspected fraud | Temporary block on the card that will prevent approval of authorisations. Functionality the same as for “Card blocked”, the different code allows to differentiate between the blocks. |
04 | Card closed due to fraud | Used to close a card due to known fraud. Changing card to this status will trigger an EMV script if the physical card is used, which means that the chip will be blocked permanently. It will also close possible tokens and inform merchants automatically that card has been closed (VAU/MABU services). Due to this the status is final and can’t be reverted to Card OK anymore. |
41 | Card lost | Used to close a card in case it is lost. Changing card to this status will trigger an EMV script if the physical card is used, which means that the chip will be blocked permanently. It will also close possible tokens and inform merchants automatically that card has been closed (VAU/MABU services). Due to this the status is final and can’t be reverted to Card OK anymore. |
43 | Card stolen | Used to close a card in case it is stolen. Changing card to this status will trigger an EMV script if the physical card is used, which means that the chip will be blocked permanently. It will also close possible tokens and inform merchants automatically that card has been closed (VAU/MABU services). Due to this the status is final and can’t be reverted to Card OK anymore. |
105 | Card closed | Used to close card by request from customer or issuer. Tokens linked to card are automatically deactivated when status is set. Cards are automatically updated to this status when account is set to Auto-Closed. |
14 | Card invalid | Final card closure status, that blocks also clearing transaction posting. |
50 | Card no renewal | Set to cards that are not expected to be renewed (e.g. passive cards). The existing card is valid until the end of the expiration time. |
Status | Description |
---|---|
Active | The card is active and may be used to perform transactions. |
Inactive | The plastic is not yet produced. |
Closed | Status of old plastic after new plastic has been activated/used. |
Locked | Used if cards are sent with initial status locked and require activation. |
Use case | Plastic status | |||
---|---|---|---|---|
Inactive | Active | Locked | Closed | |
Card embossing process as Enfuce has been completed | N | Y | Y | N/A |
Card can be used for purchases | N | Y | N | Y |
Card can be enrolled to digital wallets | N | Y | N | Y |
physical
flag during card ordering.
This allows you to onboard customers with a digital-first experience and decide per card whether a plastic is needed—without switching between separate products.
For implementation details, including API usage and field-level behavior, refer to the Digital card guide.
VISA_VIRTUAL/MC_VIRTUAL
. These are separate card products that are always digital-only and cannot be configured to include a physical form.
In contrast, the Digital card feature allows dynamic control over physical issuance per card, providing more flexibility and easier product maintenance.
RALLRE
is always triggered regardless of whether a physical plastic is actually produced (physical = true
or false
). Read more around card production event below.physical
field to determine whether a physical representation of the card exists. You can fetch this using the Get Card API.manufacturer
: Enfuce can support a multi-manufacturer setup where some cards are sent to one manufacturer and some to another e.g. based on the geographic location of the customer. Information on who should manufacture the card should be provided in the card creation request.
externalLayoutCode
: If there are multiple card layouts at the embosser, it is possible to store the information and Enfuce will include information of the chosen one in the embossing file. If only one layout is defined, this information is not needed.
companyName
: Name of the company to which the card belongs to. The length is limited to 26 characters to ensure fit on the card. If the name cannot be fit to 26 characters, the issuer should abbreviate the name. There is no standard as to how the name should be abbreviated and issuer can use own consideration.
There is a default set of characters that are supported when card is embossed (i.e. stamped) as well as an extended set of characters available for issuers that use laser overlay that allows for laser printing. Issuer should align with embosser and Enfuce on the supported character set. Enfuce supported characters are available in the API description.
firstName
: First name of the cardholder. The length is limited to 26 characters to ensure fit on the card. If the name cannot be fit to 26 characters, the issuer should abbreviate the name. There is no standard as to how the name should be abbreviated and issuer can use own consideration. One option is to abbreviate first name and keep last name complete e.g. “J. CARSON”.
There is a default set of characters that are supported when card is embossed (i.e. stamped) as well as an extended set of characters available for issuers that use laser overlay that allows for laser printing. Issuer should align with embosser and Enfuce on the supported character set. Enfuce supported characters are available in the API description.
lastName
: Last name of cardholder. The length is limited to 26 characters to ensure fit on the card. If the name cannot be fit to 26 characters, the issuer should abbreviate the name. There is no standard as to how the name should be abbreviated and issuer can use own consideration. One option is to abbreviate first name and keep last name complete e.g. “J. CARSON”.
There is a default set of characters that are supported when card is embossed (i.e. stamped) as well as an extended set of characters available for issuers that use laser overlay that allows for laser printing. Issuer should align with embosser and Enfuce on the supported character set. Enfuce supported characters are available in the API description.
additionalField1 / additionalField2 / additionalField3 / additionalField4 / additionalField5
: These fields can be used instead of the “Name” fields or in addition to them, depending on how many lines are supported on the plastic card. The additional fields have the same logic as the “Name” fields (length, characters supported), but if an actual name is not printed on the card, these fields enable not needing to store e.g. “Vehicle 1” type of information in name fields in the system. Usage of additional fields and the number of lines embossed and possible additional layouts need to be aligned with Enfuce and the card embosser.
Note that the embossing data is only relevant for physical cards and the information is not automatically reflected in virtual card designs.
**manufacturer**
: Enfuce can support a multi-manufacturer setup where some cards are sent to one card manufacturer and some to another e.g. based on the geographic location of the customer. Information on who should manufacture the card should be provided in the card creation request.
externalLayoutCode
: If there are multiple card layouts at the manufacturer, it is possible to store the information and Enfuce will include information of the chosen one in the embossing file. If only one layout is defined, this information is not needed.
**companyName**
: Name of the company to which the card belongs to. The length is limited to 26 characters to ensure it fits on the card. If the name cannot be fit to 26 characters, the name needs to be abbreviated. There is no standard as to how the name should be abbreviated so you and your customer can use your own consideration and preference.
There is a default set of characters that are supported when card is embossed (i.e. stamped) as well as an extended set of characters available for issuers that use laser overlay that allows for laser printing. You need to align with the embosser and Enfuce on the supported character set. Enfuce-supported characters are available in the API description.
**firstName**
: First name of the cardholder. The length is limited to 26 characters to ensure fit on the card. If the name cannot be fit to 26 characters, the name needs to be abbreviated. There is no standard as to how the name must be abbreviated so you and your customer can use your own consideration and preference. One option is to only print the first initial of the first name, e.g. “J. CARSON”.
There is a default set of characters that are supported when card is embossed (i.e. stamped) as well as an extended set of characters available for issuers that use laser overlay that allows for laser printing. You need to align with the embosser and Enfuce on the supported character set. Enfuce-supported characters are available in the API description.
**lastName**
: Last name of cardholder. The length is limited to 26 characters to ensure fit on the card. If the name cannot be fit to 26 characters, the name needs to be abbreviated. There is no standard as to how the name must be abbreviated so you and your customer can use your own consideration and preference. One option is to only print the first initial of the first name, e.g. “J. CARSON”.
There is a default set of characters that are supported when card is embossed (i.e. stamped) as well as an extended set of characters available for issuers that use laser overlay that allows for laser printing. You need to align with the embosser and Enfuce on the supported character set. Enfuce-supported characters are available in the API description.
**additionalField1 / additionalField2 / additionalField3 / additionalField4 / additionalField5**
These fields can be used instead of the “Name” fields or in addition to them, depending on how many lines are supported on the plastic card. The additional fields have the same logic as the “Name” fields (length, characters supported), but if an actual name is not printed on the card, these fields enable not needing to store e.g. “Vehicle 1” type of information in name fields in the system. Using additional fields and the number of lines embossed and possible additional layouts need to be aligned with the card printer.
Note that the embossing data is only relevant for physical cards and the information is not automatically reflected in virtual card designs.
**REPLACE_CARD**
functionality is used. When triggering the replacement, the previous card status will be changed to Card Lost and a new card number will be created automatically. As REPLACE_CARD will change the status to LOST, the issuer is expected to change the previous card status to match what it was (for example Card stolen, Closed due to fraud).
As the card is replaced, it will remain linked to the same account and customer. Enfuce will generate a new card entity, which will get a new card number (PAN), expiration date and CVV2/CVC2. The PIN will be regenerated unless ‘set PIN’ is chosen during replacement.
Name | Code in API and DWH files | Applicable with Instant issuing | Applicable with physical (without instant issuing) | Applicable with virtual only | Description |
---|---|---|---|---|---|
New Card | NCRD | Y | This card production event is created at the same time when a new card is created via API. Only the first plastic of each card will have this production event | ||
New Card – Virtual | NVRT | Y | Y | This card production event is created at the same time as the new virtual card is created | |
New Card – Instead Lost | NLOST | Y | This production event comes with a replacement (REPLACE_CARD). The previous card will be put to lost and a new card will be created with the production event NLOST | ||
New Card – Instead Lost Virtual | NLOSTVRT | Y | Y | Same as the production event “NLOST” but no physical card is produced. | |
Reorder PIN – Renew | ROPIN | Y | Y | This production event comes when a reorder PIN (REORDER_CARD_PIN) has been ordered | |
Replace All – Instead Lost | RALLNLOST | Y | This production event will change the PAN# and replace the PIN. Used for creating the physical card for Instant Issuing when using REPLACE_CARD | ||
Replace All – Renew | RALLRE | Y | This production event comes when the physical form of the card is ordered | ||
Replace Plastic – Expired | RPL | Y | Y | This production event comes automatically when the current plastic has expired for a physical card | |
Replace Plastic – Renew | RPLRE | Y | This production event comes with the reissue (REISSUE_CARD) when only plastic is renewed | ||
Replace Virtual – Expired | RVRT | This production event comes automatically when the current virtual card has expired |