Skip to content

Order a job file

To format project cards, you need a job file containing the project-specific data to program onto the card. Please order your ready-to-use job file from us.

Below, you'll learn which card types and features we support and which information to provide with your order.

The service fee is €500 per file. For MIFARE DESFire cards purchased from us, this fee is waived if you order a BALTECH standard card structure.

Supported card types

Card type Supported features
MIFARE DESFire
  • All EV1 features supported plus EV2 programming of Delegated Application Management (DAM) keys
  • AES key diversification (optional)
  • Format new blank cards with entire card structure including multiple applications, files, key sets, etc.
  • Add new applications to pre-formatted cards (existing applications are preserved)
  • Add files to existing applications
  • Erase and re-format cards (existing applications are deleted)
  • Copy files from one application to another
MIFARE Classic
  • All features supported
  • Format new blank cards with entire card structure
  • Add new application data to existing cards including keys
  • Exchange keys of existing applications
  • Program static MIFARE Application Directory (MAD)
  • Copy files from one application to another
MIFARE Plus
  • Level 1: all MIFARE Classic features
  • Level 2 and Level 3: full feature support on request
  • Copy files from one application to another
HITAG
  • Program plain data structure without encryption
  • Copy files from one application to another

Support for further ISO 14443-4 cards is available on request. Billing according to expenditure.

Information to provide

To create your job file, we need the following information about your project as well as the security features you want to have implemented.

Project details

Information to provide Description
Card type MIFARE DESFire, MIFARE Classic, or HITAG
Current encryption keys (
only needed for MIFARE cards and if different from factory keys)		 MIFARE DESFire:
  • Keys such as PICC Masterkey, Application Masterkey, Change Key, and other key(s) from key table (depending on card configuration)
  • Is existing data on card to be erased?
MIFARE Classic
  • Keys for the relevant memory sectors
    Please ask your project owner/card issuer. In case of several keys, you can identify the required ones by analyzing the card structure.
PCN range Range of programmed card numbers (PCNs) e.g. 1-999
Card structure
  • Keys for your application (MIFARE cards only)
  • AID (MIFARE cards only)
  • Permissions
  • Location and length of PCN
  • Encoding of PCN, i.e. ASCII, binary, BCD, etc.
  • Any additional constant data or fields incl. position

BALTECH standard card structure

If you have MIFARE DESFire cards and no requirements regarding the card structure, we recommend you order a BALTECH standard card structure (learn more).

You can still determine individual aspects yourself if needed, e.g. the AID. Just let us know when placing the order.

Security features

As needed, we enable the following features when creating the job file. We highly recommend them if Card Formatter is operated in a non-secured environment (i.e. by various users or in an exposed location).

All features can be used independently of each other. However, the higher the desired security level, the more consistently all options should be used.

Advanced key security

  • Store DESFire card keys in a Secure Access Module (SAM) or the reader configuration instead of the job file:

    Benefits

    Job file and the correspondingly configured reader can only be used in combination.
    Job file protection requirements are reduced, e.g. during transmission, while the protection level of the keys is increased. In particular, SAM storage fulfils very high security requirements.

  • Encrypt the USB interface between reader and Card Formatter.

    Benefits

    Job file and the correspondingly configured reader can only be used in combination. In particular, this protects keys stored in the reader in the event of reader theft.

  • Require a password to access the job file in Card Formatter.

    Benefits

    Job file protection requirements are reduced, e.g. during transmission. It's protected against unauthorized decryption, even if Card Formatter is reverse engineered.

Control over programmed card numbers (PCNs) issued

  • Log file in CSV format to keep track of each formatted card (enabled by default). Entries include date & time (system clock), UID, programmed card number (PCN), and content of custom entry fields.

    Please provide the desired storage location for the log.

  • Predefined range of PCNs per job file

  • Enforce consecutive assignment of PCNs: Users can't skip PCNs.
  • Prevent multiple assignment of PCNs: Users can assign each PCN only once.
Title