Cards
Card lifecycle
3 min
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, partner managed 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, integrated card actions are managed by the partner using cross river’s infrastructure, specifically, cos cards or cos explorer 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 card apis card closure permanently deactivates a card closed cards cannot be reactivated refer to the close card api webhooks webhook events integrations enable real time event driven updates for card lifecycle events, transaction activity, and status changes you need to banking and payments to receive webhooks find out more integrated status and states details on how lifecycle events affect transaction authorization