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

{cardId}

activate

In-app activation

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

{
  "activationData": "<string>"
}

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

In-app activation

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

{
  "activationData": "<string>"
}