Skip to main content
This topic explains why and when a card is renewed, reissued, and replaced:

A card is renewed when the existing card is about to expire. The card number (PAN) and the PIN remain the same. The expiry date and the CVV2/CVC2 are regenerated.

Enfuce automatically generates a card renewal request before the current one expires. You can configure the renewal timing with your customer onboarding manager. For example, you can configure 30 days before expiry as your renewal time.
A new card version created by renewal starts in INITIAL or ACTIVE_LIMITED status, depending on programme configuration. See Card Version Status for details.

A card is reissued when the existing card has either worn out or broken. The card number (PAN) remains the same. The expiry date and the CVV2/CVC2 are updated.

By default, the PIN remains the same. However, you can modify this behaviour via the pinStatus parameter:

  • Specify GENERATED to set a random PIN.
  • Specify WAITING to set the PIN later.

Related API Endpoint: Reissue card

When a new version is created, the currently ACTIVE version remains ACTIVE. It transitions to CLOSED only when a newer version is activated. See Card Version Status for the coexistence rules and a worked example.

A card is replaced when it is lost, stolen, or compromised for fraudulent activity. The card number (PAN), the expiry date, and the CVV2/CVC2 are updated.

By default, the replaced card has a system-generated PIN. However, you can modify this behaviour via the pinStatus parameter. To manually set the PIN later, specify WAITING.

Related API Endpoint: Replace card