v1

latestOpenAPI 3.1.0Copyright Pismo2026-07-247702,7523.1 MB

PCI

Get PIN as PINblock

Get the card PIN (Personal Identification Number) as a PINblock. PINblocks 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 is a PCI endpoint, use the https://gw-pci.pismolabs.io environment.

get/pcicards/v1/pcicards/{cardId}/pinblock

Path parameters

cardIdstring required

Pismo card ID

Query parameters

key-idstring required

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.

Response

Get card PIN as PINBlock success object

card_idinteger

Pismo card ID

account_idinteger

Account ID

org_idstring

Organization ID

correlation_idstring

The Correlation identifier field is used to link related API requests and events. The CID can help the Pismo engineering team track everything related to a call. If not passed, a random one is generated. You can find the CID in the response header.

pinblockstring

PINBlocks are 64-bit strings that encode a PIN ready for encryption and secure transmission in banking networks. It contains both the PIN and additional data needed to encrypt it for transmission. The PIN block is typically encrypted using a secure cryptographic algorithm to prevent unauthorized access or tampering during transmission.

panstring

Card's Primary Account Number (PAN)

key_idstring

Generated key ID.

A Zone PIN Key (ZPK) identifier. The ZPK is a data encrypting or decrypting key for PIN transfer between parties. Ffor 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.

password_updatedboolean

Has password been updated?

Example response

{
  "account_id": 6912345,
  "org_id": "TN-cc8f8b89-233a-4582-9f36-63ee85278d6d",
  "correlation_id": "c737895c-8159-4c0c-a92a-a4f8600bff37",
  "pinblock": "4E49BF480C44A36C",
  "pan": "123456******789",
  "key_id": "32a147ec-b2d9-4b0d-8c5b-557e6cf41e0e"
}