Migrate tokens

post https://gw-pci.pismolabs.io/migrations/v1/migrations/tokens

Start migration of tokens.

This endpoint generates the following events:

Body Params

Start migration of tokens

line_number

string

File line number (when batch file import migration is used) Indicates the line number in the file of the entity being migrated.

migration

object

required

Applicant additional migration information

payment_application_instance_id

string

length between 48 and 48

Identifier of payment application installed on device

card_holder_name

string

Identifies bearer name. In the wallet, the client is allowed to change the name.

token_type

string

Identifies the token type

token

string

length ≤ 255

Identifies card token generated by MASTERCARD/VISA

tc_date_time

string

Identifies date-time of token confirmation message (token creation)

token_unique_ref

string

length ≤ 255

Identifies unique token reference code (sent by flag)

pan_unique_ref

string

length between 1 and 255

Identifies unique PAN reference code (from-to by flag)

expiry_date

date

Identifies token expiration date

status

string

Identifies token status

wallet_identifier

string

length between 1 and 50

Digital wallet identifier (from-to flag requestor token)

network

string

length between 1 and 10

Product code of tokenization of flag

event_date_time

string

Date-time of event

metadata

object

Token extra data

Responses

202

Accepted

Language

Credentials

Bearer

JWT

URL


xxxxxxxxxx
1
curl --request POST \
2
     --url https://gw-pci.pismolabs.io/migrations/v1/migrations/tokens \
3
     --header 'accept: application/json' \
4
     --header 'content-type: application/json'

Click Try It! to start a request and see the response here! Or choose an example:

application/json

Migrate tokens

Changelog

Support

Pismo is here to help

400Bad request

500Internal error