Audience:
Digital card statuses
The lifecycle of a digital card, from provisioning to cancelation. For the model behind the flow, refer to digital cards.
Statuses
The API splits digital card statuses across two enums, depending on how far the digitization has progressed: PendingDigitalCardStatus (returned in PendingDigitalCard.statusInfo) covers the provisioning phase, and CompleteDigitalCardStatus (returned in CompleteDigitalCard.statusInfo) covers the card's life after provisioning.
Provisioning phase (PendingDigitalCardStatus)
| Digital card status | Explanation |
|---|---|
ConsentPending | Request to add a digital card was sent with the addDigitalCard or addDigitalCards mutation and is waiting for the cardholder's consent.Next steps:
|
Pending | Cardholder added the card to their digital wallet manually, or they provided consent after you added the card with the API. Next steps:
|
Declined | Card was declined during the provisioning process. |
After provisioning (CompleteDigitalCardStatus)
| Digital card status | Explanation |
|---|---|
Enabled | Digital card is available for use. Next steps:
|
Suspended | Digital card is suspended and not available for use. Cards can be suspended for various reasons, including a request from you or the cardholder, or a Swan action in the case of suspicious activity. Next steps:
|
Canceled | Card is canceled, no longer available for use, and can't be reactivated. |
If a digital card is stuck in Pending status after manual provisioning (for example, the cardholder didn't complete OTP verification), you can use the activateDigitalCard mutation to help them complete the process without restarting. Learn more in the transitioning from manual to in-app provisioning guide.