v1

latestOpenAPI 3.1.0Copyright Pismo2026-07-247702,7523.1 MB

Token lifecycle

Perform token operation

Perform token operation.

Notes:

This is a PCI endpoint, use the https://gw-pci.pismolabs.io/cards-tokenization environment.
This endpoint takes an account token - an access token encoded with a Pismo account ID

post/v1/cards/{cardId}/network-tokens/{tokenId}

Request body

operation_reasonstring required

Operation reason. Be descriptive, it should be clear what the customer needs to do. For a suspended token, for example, the reason could say "Suspended due to lost device."

Operation type:

DELETE - Delete token
SUSPEND - Suspend token
RESUME - Resume suspended token
CALL_CENTER_ACTIVATION - Call center verification
CARDHOLDER_STEPUP_APP_TO_APP - App2App verification
TOKEN_DEVICE_BIDING_APPROVE - Device verification, approve and activate the most recently inactive device (only Visa)
TOKEN_DEVICE_BINDING_APPROVE_CALL_CENTER - Device verification with call center activation, approve and activate the most recently inactive device (only Visa)
TOKEN_DEVICE_BINDING_APPROVE_BANK_APP - Device verification with bank app approval, approve and activate the most recently inactive device (only Visa)

Note: For App2App token activation, set this field to CARDHOLDER_STEPUP_APP_TO_APP (Mastercard) and CALL_CENTER_ACTIVATION (Visa).

activation_codestring

REQUIRED if operation_type is CALL_CENTER_ACTIVATION. These codes are known only to the issuer/caller.

operator_idstring

Client-generated ID for person or system performing the operation. This is for client monitoring and internal record-keeping.

Example request

{
  "operation_reason": "Suspended due to lost device",
  "operation_type": "DELETE",
  "activation_code": "94"
}

Response

Success