Gestionar el ciclo de vida de la tarjeta

Card life cycle and operations

The diagram below shows the different life cycle states of a card.

Card life cycle state diagram.

In addition to the state, each card exposes an ongoingOperation property. This property indicates whether a card renewal has been initiated and activation of the reissued card is expected. The ongoingOperation property is available both in the D1 API and in the D1 SDK.

Card life cycle operations

Card life cycle operations can be performed through the following channels:

• D1 REST API

• D1 SDK

Life cycle operation reasons

A reason must be provided every time you perform a card life cycle operation. The tables below summarize, for each operation type, the available reasons, their meaning, and the impact on the card.

Suspend reasons

Reason	Description
CARD_LOST	The card has been reported as lost. You can: - resume the card using the reason CARD_FOUND. - request a replacement.
CARD_STOLEN	The card has been reported as stolen. The card remains suspended until you explicitly request a replacement.
CARD_BROKEN	The card is damaged and no longer works. The card remains suspended until you explicitly request a replacement.
FRAUD	The card is compromised. The card remains suspended until you explicitly request a replacement.
USER_DECISION	The end user has decided to temporarily suspend the card. The card can be resumed with the reason USER_DECISION or ISSUER_DECISION.
ISSUER_DECISION	The issuer has decided to temporarily suspend the card. The card can be resumed with the reason ISSUER_DECISION.

Resume reasons

Reason	Description
CARD_FOUND	The card has been found and was previously suspended with the reason CARD_LOST.
ISSUER_DECISION	The issuer has decided to resume the card.
USER_DECISION	The end user has decided to resume the card and the card was previously suspended with USER_DECISION.

Delete reasons

Reason	Description
CLOSED_ACCOUNT	The end user has closed the account and the card must be deleted/canceled.
CLOSED_CARD	The card must be deleted/canceled.
CARD_LOST	The card has been reported as lost and must be deleted/canceled.
CARD_STOLEN	The card has been reported as stolen and must be deleted/canceled.
CARD_BROKEN	The card is damaged and must be deleted/canceled.
FRAUD	The card is compromised and must be deleted/canceled.
USER_DECISION	The end user has decided to delete the card.
ISSUER_DECISION	The issuer has decided to delete the card.

Replacement reasons

Reason	Description
CARD_LOST	The card has been reported as lost.
CARD_STOLEN	The card has been reported as stolen.
CARD_BROKEN	The card is damaged and no longer works.
FRAUD	The card is compromised.
ISSUER_DECISION	The issuer has decided to replace the card.

Renewal reasons

Reason	Description
USER_DECISION	The end user has decided to renew the card.
ISSUER_DECISION	The issuer has decided to renew the card.
CARD_EXPIRED	The card has been renewed because it has expired or is about to expire.

D1 REST API

Renewal and replacement flows

Automatic renewal

Automatic renewal is available only for cards created with D1. D1 monitors the expiry date of each card created with D1 and can automatically trigger renewal a few weeks before expiration.

Manual renewal

Manual renewal is available for cards created with D1 and for registered cards. Manual renewal is triggered using the renew API.

If the card is registered (not created with D1), the new PAN and/or expiry date must be provided so that D1 stays up to date with the new card credentials.

Manual replacement flow

Manual replacement is available for cards created with D1 and for registered cards. Manual replacement is triggered using the replace API.

If the card is registered (not created with D1), the new PAN and/or expiry date must be provided so that D1 stays up to date with the new card credentials.

New card activation

Depending on the card product configuration, after renewal or replacement the new card may be created in the INACTIVE state. There are three ways to activate the card:

• Activation at first card-present transaction with a valid PIN. This is available only if the card was created via D1.

• Manual activation using the D1 REST API (Not yet available).

• Manual activation from the issuer application using the D1 SDK (Not yet available).