Will create TAV according to TAV format version 2 with encrypted card data to be sent to MDES.

This operation will read the card data, generate activation data according to MDES specification TAV2 format and respond. Difference betwen v1 is that v2 will also contain the tokenUniqueReferenceId. 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.

POST

{cardId}

activate

mdes

tav2

Will create TAV according to TAV format version 2 with encrypted card data to be sent to MDES.

curl --request POST \
  --url 'https://integration-api-cat2.{{environment}}.ext.{{realm}}.cia.enfuce.com/wallet/v2/{cardId}/activate/mdes/tav2' \
  --header 'Authorization: Bearer <token>'

{
  "activationData": "<string>"
}

Deprecated: This API endpoint is no longer supported.

Authorizations

Authorization

string

header

required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

cardId

integer<int64>

required

CardId for the card that should be tokenised

Query Parameters

auditUser

string

required

The audit user to log the request

Response

activationData

string

required

⌘I

Will create TAV according to TAV format version 2 with encrypted card data to be sent to MDES.

curl --request POST \
  --url 'https://integration-api-cat2.{{environment}}.ext.{{realm}}.cia.enfuce.com/wallet/v2/{cardId}/activate/mdes/tav2' \
  --header 'Authorization: Bearer <token>'

{
  "activationData": "<string>"
}