v1

latestOpenAPI 3.1.0Copyright Pismo2026-07-247702,7523.1 MB

PCI

Update PIN from PINblock

Update the card PIN (Personal Identification Number) from its PINBlock. PINlBocks are 64-bit strings that encode a PIN ready for encryption and secure transmission in banking networks.

For more information, refer to the PIN/PINBlock tutorial.

Note: This does not change the password recorded on an embossed card's chip. If the card is configured for offline password verification, you need to change the password on the physical card. To do that, you can use a card script.

This endpoint generates a Card password changed event.

Notes:

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

put/pcicards/v1/pcicards/{cardId}/pinblock

Path parameters

cardIdstring required

Pismo card ID

Request body

pinblockstring

PINBlock to update

key_idstring

ID of key used to generate the PINBlock.

A Zone PIN Key (ZPK) identifier. The ZPK is a data encrypting or decrypting key for PIN transfer between parties. For example, between issuers and processors or acquirers and networks or networks and processors, and so on.

In a sandbox environment, a fixed ZPK is used:

key_id: 7d14ca2e-1057-11ee-8cee-060f666de710

HSM key: 0404F2543B1C6E70AB61586E1304B6A7

For production, open a Jira ticket with type = Configuration. Request you need the key to use endpoints with PIN management such as PINBLOCK.

sync_offline_pinboolean

Synchronize the offline PIN with the current online PIN value?

If true, the platform generates a script with the new online PIN, sends the script in the response to the next authorization made with a chip (contact), and generates the Card issuer script notification received event.

Default is false.

Example request

{
  "pinblock": "4E49BF480C44A36C",
  "key_id": "32a147ec-b2d9-4b0d-8c5b-557e6cf41e0e",
  "sync_offline_pin": true
}

Response

No Content