Activation data
Activation data
Endpoints
In-app activation
POST /v3/{cardId}/activate
Will create activationdata according to TAV format version 2 with encrypted card data to be sent to MDES.(Deprecated)
POST /v1/{cardId}/activate/mdes/tav2
Deprecated
Will create TAV according to TAV format version 2 with encrypted card data to be sent to MDES.(Deprecated)
POST /v2/{cardId}/activate/mdes/tav2
Deprecated
Previous
In-app activationThis is common for Apple Pay, Google Pay and Samsung Pay by using either WSD keys for VTS or TAV for MDES.
Note that these keys are handled and exchanged by Enfuce.
Activation data that is returned from this endpoint will in most cases be used when the card holder as added
the card manually and not via push provisioning. It contains encrypted card data and must be sent to MDES/VTS.
Activation data is used to ensure the card schema (Visa/Mastercard) that the issuer in fact has allowed the
card to be tokenized as it contains a digital signature calculated over the PAN of the card.
Next