Skip to main content

mPOS

Card details

Code

  • For reading MiFare Classic

    <Custom_Card>

<Type>MF_Classic</Type>

<Key>CDAEEFFBCEEE</Key>

<Key>ABCDEFABCDEF</Key>

<Key>SG_KEY_1</Key>

</Custom_Card>

  • For reading MiFare Desfire

    <Custom_Card>

<Type>MF_DESFire</Type>

<Key>CDAEEFFBCEEE</Key>

<Key>ABCDEFABCDEF</Key>

<Key>SG_KEY_1</Key>

</Custom_Card>

  • For reading MiFare Ultralight

    <Custom_Card>

<Type>Ultra</Type>

<Key>CDAEEFFBCEEE</Key>

<Key>ABCDEFABCDEF</Key>

<Key>SG_KEY_1</Key>

</Custom_Card>

Enter custom keys for each of the pre-defined card types.

Important to know:

  • For Desfire and UltraLight cards, the key length is 32 characters.

  • In each of the card types, 3 custom key options are provided.

    The first two provide an option for entering the custom keys of the card, which can be entered by the customer Admin or CSE.

    Whereas, the third key refers to the static key available in the backend and does not require to be changed.

Warning

Generally, for Recreatex cards, the custom keys and the static key will be available in the backend and the data will be fetched as per the configuration of the parameter NFC scan type.

However, for third-party cards, the customer Admin or CSE will be required to enter the custom keys so that the mPOS app can read such cards.

When it is used

When a customer's card is scanned, the values defined in the code for Card details enable the mPOS app to identify whether it is a Recreatex card or a third-party card.

In this section: