Replace or renew a card

When a physical card is replaced (for example, after loss) or renewed (for expiration), the issuer backend must send the updated FPAN and expiration date to Tokenization Service. Tokenization Service then updates the funding card information with the payment network TSP.

Use the UpdateCard API. Provide both the old and new FPAN and expiration date.

Update FPAN and expiration date

Here is an example of a valid request:

{
  "issuerCardRefId": "string",
  "fpanDetails": "string (base64)"
}

fpanDetails contains the encrypted old and new FPAN and expiration date. It is a base64-encoded PKCS#7 encrypted JSON payload.

JSON payload format:

{
  "oldFPAN": "[0-9]{16,19}",
  "oldExpDate": "MMYY",
  "newFPAN": "[0-9]{16,19}",
  "newExpDate": "MMYY"
}

Some payment networks require the old FPAN and expiration date to process the update.

The detailed flow:

UpdateCard flow for card replacement or renewal.

Update the card profile on renewal

In rare cases, the card is renewed because the end user changes card program (for example, from Classic to Gold).

In this case, you can also update the card profile using newProductId. This value is the card profile ID configured in the payment network TSP.

Request body example:

{
  "issuerCardRefId": "string",
  "fpanDetails": "string (base64)",
  "newProductId": "string"
}

Update issuerCardRefId

issuerCardRefId uniquely identifies the card. You can also update it during this process using newIssuerCardRefId.

Request body example:

{
  "issuerCardRefId": "string",
  "fpanDetails": "string (base64)",
  "newProductId": "string",
  "newIssuerCardRefId": "string"
}