Account to account batch transfer4

Activation data3

Authentication Response Callback1

Authorization Holds4

Card Hierarchy Group Management5

Card Hierarchy Management6

Card Management in Card Hierarchy Groups7

Create a customer2

Create an account6

Create card11

Create fees2

Create price lists2

Create purchase details1

Create repricing agreements3

Create transactions3

Customer hierarchy3

Forward authorisation webhook1

Get account information2

Get application1

Get card8

Get customer information2

Get ECB exchange rate1

Get ECB supported currencies1

Get EMV scripts1

Get Fraud Case2

Get FX exchange rates2

Get invoice information1

Get plastic1

Get price lists5

Get purchase details2

Get repricing agreements7

Get tokens1

Get transaction data6

Instalment Operations6

OOB Webhook Notification1

PIN Control handling3

PIN operations using PKI6

PIN operations with pre-shared key3

Post account to account transfer1

Post card to card transfer1

Push Provision4

Receive a notification1

Rule Sets Endpoints7

Rules Endpoints9

Spend Control Test Endpoint1

STIP External Account Balance Endpoints2

STIP Spend Control Test Endpoint1

Test authorizations1

Test transactions1

test-auth-request-templates2

test-authorizations2

Trigger repricing1

Update a customer3

Update an account6

Update an invoice2

Update application1

Update card12

Update Fraud Case1

Update plastic1

Update price lists4

Update purchase details2

Update repricing agreements6

Visa Click2Pay Enrol and Manage9

Warm up authorisation control webhook1

Push Provision

Samsung Pay push provisioning

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.

post/v1/{cardId}/provision/samsungpay

Request

Base URL
https://integration-api-cat2.{{environment}}.ext.{{realm}}.cia.enfuce.com/transfer
Auth
none required
TypeScript
https://skmtc.dev/enfuce/apis/transfer-api/docs/v1/:cardId/provision/samsungpay/post.ts
A function with typed inputs. Its response is checked against the schema.

Path parameters

cardIdinteger required

CardId for the card that should be provisioned (returned from card operation)

Query parameters

auditUserstring required

The audit user to log the request

Request body

clientAppIDstring

Only applicable for VTS customers

clientDeviceIDstring

clientWalletAccountIDstring

Response

digitizationDatastring

Base64 encoded json structure containing needed data for MDES/VTS

googleOpaquePaymentCardstring

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.

Changes

No recorded changes to this operation across all 1 revision of this API.