Card lifecycle
Card lifecycle management
All card programs must support a complete lifecycle for each issued card, from creation to closure. The lifecycle governs the card’s operational state. This card’s operational state determines whether the card can be used for transactions, requires replacement, or must be suspended or closed due to fraud, customer request, or expiration.
In partner-managed programs, lifecycle actions are handled by the partner and their processor. The partner is responsible for triggering lifecycle events, maintaining card status, and communicating relevant updates to Cross River via daily reporting.
In integrated issuing programs, lifecycle actions are managed by the partner using Cross River’s infrastructure, specifically, COS APIs or COS Explorer.
Lifecycle events
Typical lifecycle events include:
- Card creation: A physical or virtual card is generated and linked to a customer account.
- Refer to the create new card API.
- Card activation: The card transitions from Unactivated to Active status and becomes eligible for transactions.
- Refer to the activate card by ID API.
- Replacement or reissue: A new card is issued due to expiration, damage, or being reported lost or stolen.
- Refer to replace and reissue for more details.
- Suspension and unsuspension: Temporarily disables or re-enables a card, often due to fraud or customer request.
- Refer to the suspend card and unsuspend a card APIs.
- Card closure: Permanently deactivates a card. Closed cards cannot be reactivated.
- Refer to the close card API.
Webhooks
WebhookWebhook integrations enable real-time event-driven updates for card lifecycle events, transaction activity, and status changes. You need to register to receive webhooks.
Find out more
- Integrated status and states - details on how lifecycle events affect transaction authorization.
Read more