Card lifecycle and statuses

The following graphic shows the card lifecycle and statuses for a nominal (physical - plastic or metal) card. Card termination statuses are on the right.

Termination statuses cannot be changed to an active or temporarily blocked status.

The lifecycle and statuses for noname and reissued cards are slightly different, but similar:

Noname card lifecycle and statuses
Reissued card lifecycle and statuses

Initial/default card statuses

The following table shows the initial (default) statuses for Pismo issued cards.

CardInitial statusNotes
VirtualNORMALDoes not have to be activated.
Physical (plastic/metal)CREATEDCan be overridden in program configuration to be NORMAL. After activation, it changes to NORMAL.
NonameUNBOUNDWhen assigned to a customer its status becomes CREATED. Once activated, it becomes NORMAL.

Card status enums

The following table contains current card status enums. "Type" here is an unofficial grouping, and does not exist as enums in code.

EnumTypeDescription
CREATEDInitialCreated in the system.
UNBOUNDInitialNoname card not yet assigned to customer.
NORMALActiveActive and eligible for transactions. Default for virtual cards. The transition from CREATED to NORMAL is for physical cards and can only be done through the Activate physical card
REISSUEDActiveCard has been reissued.
BLOCKEDTemporary
block
Temporarily blocked until further status changes.
PENDINGTemporary
block
Created and is pending until further processing, such as account verification. Until then, transactions are disabled.
WARNINGTemporary
block
A general alert flag is set and transactions are disabled. After investigation, it could, typically, transition to FRAUD or revert back to `NORMAL.
LOSTTerminatedReported lost
ROBBEDTerminatedReported stolen
EXPIREDTerminatedCard date expiration reached
DAMAGEDTerminatedDamaged
FRAUDTerminatedSuspected fraud
CANCELEDTerminatedCanceled
DELETEDTerminatedDeleted
BROKENTerminatedNo longer physically usable
THEFTTerminatedStolen
DEFECTTerminatedHas defect

Call the Update card status endpoint to change a card's status.

Card reissues

You need to reissue a card once it has a termination status. Similar to your embossing configuration, you need to personalize the card reissuing configuration and process for your brand as every brand has different reissue reasons and associated costs. After setting up your program, meet with your Pismo representative to configure this.

You can call the following APIs to view your reissuing configuration and reissue a card:

Card reissue scenarios and statuses

Scenario 1 - physical:

  1. Card created (CREATED) and activated (NORMAL)
  2. Card reissued with must_block = true(CANCELLED). (The reissue reason object contains the must_block field).
  3. New card created (CREATED) and activated (NORMAL)

Scenario 2 - physical:

  1. Card created (CREATED) and activated (NORMAL)
  2. Card reissued with must_block = false(REISSUED)
  3. New card created (CREATED) and activated (NORMAL)
  4. Old card cancelled (REISSUED > CANCELLED)

Scenario 3 - virtual:

  1. Card created and activated automatically (NORMAL)
  2. Card reissued with must_block = true (CANCELLED). (The must_block flag is a field in the reissue reason object.)
  3. New card created (CREATED) and activated (NORMAL)

Scenario 4 - virtual:

  1. Card created and activated automatically (NORMAL)
  2. Card reissued with must_block = false(REISSUED)
  3. New card created (CREATED) and activated (NORMAL)
  4. Old card cancelled (REISSUED > CANCELLED)

Automatic card reissue updates

This service is offered in partnership with Mastercard to simplify a customer's life. When a new customer card number is issued, it is automatically updated on the various websites, applications, and digital services where the customer already has a record with the old card.