---
title: "In-app activation"
method: POST
path: "/v3/{cardId}/activate"
tags: ["Activation data"]
---

# In-app activation

`POST /v3/{cardId}/activate`

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.

## Path parameters

- `cardId` integer, required

## Query parameters

- `auditUser` string, required

## Response `200`

OK

- ResponseActivation
  - `activationData` string, required

## Other responses

- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found

---

[API](https://skmtc.net/enfuce/apis/transfer-api.md) · [All operations](https://skmtc.net/enfuce/apis/transfer-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/enfuce/transfer-api/revisions/dc4a41118f80/schema)