v1
latestOpenAPI 3.0.32026-07-26208618579.9 KBActivation 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 has 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/v3/{cardId}/activate
Path parameters
cardIdinteger required
CardId for the card that should be tokenised
Query parameters
auditUserstring required
The audit user to log the request
Response
OK