Append update PIN script

post

https://sandbox.pismolabs.io/pcicards/v1/pcicards/{cardId}/scripts/pin-update

Append issuer script to update the card PIN that will be applied at the next authorization.

You must work with Pismo to pre-register a script and get its script ID. For information on generating a PINBlock and key ID, refer to the PIN/PINBlock tutorial guide.

For more information, refer to the Card scripts guide.

Note: This is a PCI endpoint, use the https://gw-pci.pismolabs.io/ environment."

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

cardId

string

required

Pismo card ID

Body Params

Request body*

script_id

string

required

Issuer script ID. Pismo configures a script according to your needs. Contact your Pismo representative to create a script. Once created, Pismo gives you the script ID.

pin_block

string

New PIN encrypted as a PINblock using the Zone Pin Key (ZPK) key_id field that was pre-registered.

key_id

string

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.

string

length between 4 and 6

New card Primary Identification Number (PIN)- 4 or 6 digits.

Headers

x-account-id

string

required

Account ID

x-tenant

string

required

Organization/tenant ID

Responses

400

Bad Request

401

Access token is missing or invalid

403

You don't have permission to access this resource

404

The specified resource was not found

500

Internal server error

Append update PIN script

Changelog

Support

Pismo is here to help

200Response for success append issuer scripts