Reissuing Cards

After initially issuing a card to a customer, you might need to manually reissue them a new card.

When to reissue

You reissue a card in circumstances such as these:

  • A physical card has been reported damaged, and you want to send a new card to the cardholder.
  • Your product settings do not automatically reissue expiring cards, so you want to reissue manually.
  • You want to reissue or replace a card with the same product ID for other reasons.

When not to reissue

In some similar cases, reissuing a card is not the right course of action, for example, when:

  • You want to reissue a virtual card as a physical card; instead, use Digital First cards for new products or the Switching Products guide for existing virtual cards.
  • A physical card is about to expire and product settings specify automatic reissue; instead, allow the automatic process to run.
  • You want to reissue a virtual-only card that is about to expire; instead, use Add Card to create a replacement virtual card.
  • A card has been reported lost or stolen; instead, use the Lost, Stolen, or Damaged Cards guide.
  • The reissue is the result of the account switching from one product ID to another product ID; instead, use the Switching Products guide.

Reissuing vs. replacing

When you reissue a card, you can specify whether to reissue or replace it:

  • To reissue a card is to make a new version of the card that is associated with the original card account.
    • The PRN, PAN, and CAD stay the same, but a new emboss record with a new expiry date and CVV are created.
    • If you have configured a reissue fee (REI), that fee is applied.
    • Performed when a card is about to expire or when a card is reported damaged.
  • To replace a card is to issue a net-new card.
    • A new card record is created with the same PRN but a new PAN, CAD, expiry, and CVV.
    • If you have configured a replacement fee (REP), that fee may be applied, depending on which reissue method you use.
    • Performed for lost or stolen cards or other times when providing a net-new card for the same product is desired. For lost or stolen cards use the Lost, Stolen, or Damaged Cards guide instead of the replacement methods described in this guide.

๐Ÿ“˜

Note

Virtual cards cannot be reissued; instead, you must replace them by using Add Card.

How to reissue or replace

Galileo provides two methods to reissue and replace cards: using the Reissue Card endpoint and using the Modify Status endpoint. For an explanation of the difference between the methods as well as the instructions for using Modify Status, request the Card Reissue Options PDF from Galileo. The rest of this guide explains how to use Reissue Card, which is the preferred method.

Using the Reissue Card endpoint

This section explains how to use the Reissue Card endpoint to reissue or replace cards.

Result of calling Reissue Card

When Reissue Card has been called successfully, the reissue process is initiated. Depending on how the endpoint parameters are set, the card is set to be embossed with either a new PAN and expiry or the old PAN and new expiry.

  • When the PAN is new, a new card record is created with a new CAD, and a new emboss record is created with a new expiry date and CVV.
  • When the PAN is not new, a new emboss record is created with a new expiry date and CVV.
  • Because new PANs and expiries are generated by subsequent backend processes, the new PAN and expiry are not available in the response to this endpoint call.

According to your arrangements with Galileo, Galileo sends event webhooks to notify when the emboss record is created, when the fee is assessed and when the card is activated. There is no event webhook for card reissue or replacement.

Card reissue product parameters

This product parameter affects card-reissue and replacement behavior when using the Reissue Card endpoint.

ParameterDescription
CANCSUsed in conjunction with CANOC, it specifies the status that a card must be in to be canceled when a new card is activated. Default: N,X,Y,W
CANOCWhen this parameter is set to Y and a new PAN is generated, cards that have the same product ID and cardholder as the newly activated cardโ€”and that are in a status specified in CANCSโ€”are changed to status C (canceled) when the new card is activated. When this parameter is not set, other cards are not canceled.

Set this parameter at the product level so that cards with the same product ID are cancelled.

If you set oldCardStatus to C or D, this parameter is not checked.

๐Ÿ“˜

Note

The Reissue Card endpoint does not check the RISCS parameter, which controls which card statuses are eligible for reissue when using Modify Status to reissue cards.

Endpoint parameters

This table explains the parameters that are specific to the Reissue Card endpoint. See the Reissue Card endpoint reference for details.

ParameterDescription
accountNoThe PRN, PAN or CAD of the card to reissue. If more than one card is associated with the PRN, use the PAN or CAD.
newPanPass Y to generate a new PAN for the card. When this parameter is Y then newExpiryDate: Y is required. Default: N
newExpiryDatePass Y to generate a new expiry date for the new card. Always set this parameter to Y, because otherwise it leaves the reissued card unprotected in transit. Default: N
embossPass Y to send the reissued card to the embosser. The N value is not currently supported, because virtual cards cannot be reissued. Default: Y
oldCardStatusSpecify the status for the card that is being replaced. This parameter is valid only when newPan Y. The status is applied by the emboss process, shortly after reissue. Use D for disabled or C for canceled. Leave blank for the old card to be usable until the new card is activated. Default: Blank

Valid parameter combinations

Only these parameter combinations are valid. See Use cases for instructions on using these combinations.

Use casenewPannewExpiryDateembossoldCardStatus
1: ReissueN or blankYY or blankBlank
2: ReplaceYYY or blankC, D or blank

๐Ÿ‘

Warning

If you set both newPan and newExpiryDate to N or blank, you create an identical copy of the current card. When such a card is mailed to the cardholder, it is active and therefore vulnerable to interception. If you were to set account feature 20 or 21, you would also disable the old card. For this reason, Galileo strongly recommends that you always set newExpiryDate: Y.

Reissue Card workflow

726726
  1. Populate the Reissue Card endpoint and send.
  2. Galileo performs these checks:
    • If the card is virtual, Galileo returns 589-01.
    • If there are pending reissue records for this card, Galileo returns 589-09.
    • If there is a reissue fee, Galileo checks the available balance. If there are insufficient funds, Galileo returns 589-07.
      • Galileo attempts to process the reissue fee. If processing the fee is unsuccessful, Galileo returns 589-08.
    • Galileo attempts to retrieve the data associated with the account and card. If it is unsuccessful, Galileo returns 589-05 or 589-06.
  3. Galileo checks the value of newPan:
    • Y โ€” Galileo checks the value of newExpiryDate:
      • Y โ€” Galileo sets a flag for a new PAN for a net-new card.
      • N or blank โ€” Galileo returns 590-11
    • N or blank โ€” Galileo assigns the old PAN to the reissued card.
  4. Galileo checks the value of newExpiryDate:
    • Y โ€” Galileo sets a flag for a new expiry date for the reissued card.
    • N or blank โ€” This value is not recommended.
  5. Galileo checks the value of oldCardStatus.
    • C or D โ€” Galileo checks the value of newPan:
      • Y โ€” Galileo sets a flag for the old card status to change
      • N โ€” Galileo returns 590-04
    • Blank โ€” The old card is not flagged for a status change.
  6. If the card-reissue process fails, Galileo returns 589-10; otherwise, Galileo sends status: 0.

After the endpoint response

These steps happen after the endpoint call is successful. The emboss process runs once per day in Production for most clients and every 15 minutes in CV.

  1. The emboss process:
    • Generates a new card record with a new CAD and PAN if newPan: Y.
    • Generates a new expiry date and CVV.
    • Generates a new emboss record in status: Y.
    • Includes the emboss record in a batch file to send to the embosser.
    • Sends the SHIP: card_shipped event webhook.
    • If newPan: Y and oldCardStatus is C or D, changes the old card to that status.
    • If applicable, assesses the reissue (REI) fee and sends the BFEE: fee event message.
  2. The emboss vendor creates the card and mails it to the cardholder.
  3. The cardholder activates the new card in one of these ways, according to your setup:
  4. You receive notification that the card has been activated (BACT: card_activated event webhook).
  5. If the card has a new PAN, then the PIN must also be reset using your preferred method.
  6. If newPan: Y and oldCardStaus was blank and CANOC is not Y, then the old card is still active. Perform this step:
    • Call Modify Status with these parameters:
      • accountNo: CAD or PAN of old card; do not use PRN
      • type: 5

๐Ÿ“˜

Note

A reissue is represented in the CST on the Card Info screen under Reissued Card History and Emboss History.

Sample endpoint request and response

Consult the Reissue Card endpoint reference to see how to build the API request and to see the response schema.

Because the emboss process generates new PANs, CADs, expiry dates and CVVs after the Reissue Card endpoint is called, the Reissue Card endpoint cannot return that data. After you receive the SHIP: card_shippedSHIP: card_shipped event webhook, you can retrieve the new information using Get Account Cards or Get Card. You can receive the new PAN, CVV and expiry only if you are PCI compliant.

View the reissued card

Because the emboss process generates new PANs and expiry dates, the Reissue Card endpoint does not return the new PAN and expiry. When you receive the SHIP: card_shipped event webhook, you can call Get Account Cards or Get Card to see the new card information.

Use cases

Use the Reissue Card endpoint for these use cases:

Use case 1: Reissue card with same PAN and new expiry

Your product settings do not reissue cards automatically when they are about to expire, so you reissue them manually. There is no reissue fee. The old card is usable until the new card is activated, and then it is disabled.

  1. You call Reissue Card with these parameters:
    • newPan: N or blank
    • newExpiryDate: Y
    • emboss: Y or blank
    • oldCardStatus: blank
  2. The emboss process:
    • Generates a new expiry date and CVV.
    • Creates a new emboss record in status: Y.
    • Adds the emboss record to the batch file to send to the embosser.
    • Sends the SHIP: card_shipped event webhook.
  3. The embosser mails the cards to the cardholders, who activate them. Galileo sends the BACT: card_activated event webhook.
  4. Because the card has the same PAN, the PIN does not need to be reset.
  5. The old card is deactivated.

Use case 2: Replace card with new PAN and expiry

The cardholder wants a new card with a new PAN for the same product and account. You charge a $5.00 reissue (REI) fee. (To charge a replacement [REP] fee instead, use Modify Status to replace the card. Request the Card Reissue Options PDF from Galileo for instructions.)

This scenario has two methods for cancelling the old card, depending on the timing that you desire:

  • Cancel shortly after reissuing the card โ€” Set oldCardStatus to C or D.
  • Cancel when the new card is activated โ€” Leave oldCardStatus blank.
  1. You call Reissue Card with these parameters:
    • newPan: Y
    • newExpiryDate: Y
    • emboss: Y or blank
    • oldCardStatus: C, D or blank
  2. The emboss process:
    • Creates a new card record with a new PAN and CAD.
    • Creates a new emboss record in status: Y with new expiry date and CVV.
    • Adds the card to a batch file to send to the embosser.
    • Sends the SHIP: card_shipped event webhook.
    • If oldCardStatus is populated, change the old card status to C or D.
    • Assesses the 5.00 reissue fee and sends the BFEE: fee event message.
  3. The embosser mails the card to the cardholder, who activates it. Galileo sends the BACT: card_activated event webhook.
  4. Because the card has a new PAN, the PIN must also be reset, using your preferred method.
  5. If you left oldCardStatus blank and CANOC is not set, then the old card is still active. Perform these steps to set the old card status to C (canceled):
    • Call Modify Status with these parameters:
      • accountNo: CAD or PAN of old card; do not use PRN
      • type: 5

Reissue Card status codes

Status CodeDescriptionNext Steps
589-01Reissue request for virtual card is invalidVerify that prodId is not a virtual card product.
589-02The valid values for newPan and newExpiryDate are Y and N.Verify that the values for those parameters are Y, N or blank
589-03The valid values for oldCardStatus are D and C.Verify that the value is D or C or blank
589-04Trying to update card status without requesting new PANIf oldCardStatus is populated then newPan: Y is required.
589-05Failure getting data associated with account/card. Cannot retrieve CAD, ENP or product ID.Contact Galileo for troubleshooting.
589-06Failure getting data associated with account/card. CAD or XID is null.Contact Galileo for troubleshooting.
589-07Insufficient funds to cover reissue feeFollow your business process for this use case.
589-08Failure, generic error processing reissue fee.Contact Galileo for troubleshooting.
589-09Failure, card has pending reissue records.None. The pending emboss record will be sent to the embosser in the next cycle.
589-10Card reissue cannot be processed.Contact Galileo for troubleshooting.
589-11If new_pan='Y' then new_expiry_date needs to be 'Y' too.Verify that newExpiryDate: Y when newPan: Y.

Did this page help you?