Activation data
In-app activation
This 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.
POST
In-app activation
Path Parameters
CardId for the card that should be tokenised
Query Parameters
The audit user to log the request
Response
200
application/json
OK
The response is of type object.
Previous
TAV for MDES (Deprecated)This operation will read the card data, generate activation data according to MDES specification and respond. The activation data should in most cases be used when the card holder as added the card manually and not via the push / in-app provisioning, especially in flow that has done into none-green flow. This data is used to ensure the card schema 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
In-app activation