---
title: "Samsung Pay push provisioning"
method: POST
path: "/v1/{cardId}/provision/samsungpay"
tags: ["Push Provision"]
---

# Samsung Pay push provisioning

`POST /v1/{cardId}/provision/samsungpay`

This endpoint is only used for Samsung Pay push provisioning.

Response is a JSON that must be passed to Samsung and onwards to MDES/VTS.

## Path parameters

- `cardId` integer, required

## Query parameters

- `auditUser` string, required

## Request body

- SamsungParametersRequest
  - `clientAppID` string — Only applicable for VTS customers
  - `clientDeviceID` string
  - `clientWalletAccountID` string

## Response `200`

OK

- ExternalResponseIssuerInitiatedDigitizationData
  - `digitizationData` string — Base64 encoded json structure containing needed data for MDES/VTS
  - `googleOpaquePaymentCard` string — Base64-encoded (RFC 4648 §4, non-URL-safe) PGP signed and encrypted Google Opaque Payment Card. Present only on Google Pay provisioning responses when the request included a serverSessionId.

## Other responses

- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `500` — Internal server error

---

[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)