Cards
Card lifecycle
Integrated card actions
card actions cos supports full card lifecycle management, enabling partners to control card operations via cos apis (direct system to system integration) cos explorer (cross river’s operational ui) key lifecycle events include /#card creation physical or virtual /#card activation transition from unactivated to active /#set card pin set intial pin for the card /#card replacement or re issue for lost, stolen, or expired cards suspension and unsuspension temporary blocks card closure permanent deactivation once a card is closed, it cannot be reactivated a new card must be issued if card access is needed again card creation for card creation using our docid\ ejccinvxb0omkja567gum api endpoint , you need a valid deposit account number, the configuration id, and other card specific information such as the name and address of the cardholder a newly created card has the status unactivated when the card is successfully created, the order status is orderpending see our tutorial to learn how to docid\ rzzrd7am62 ktyv9g1n9 card activation cards can only be used once they are activated to activate the card, use the docid\ e u42earziwdzoiixuuni api endpoint with the cos card id see our tutorial to learn how to docid\ wzyv6qgm31ldteagrt2fc set card pin use the docid\ yfzldndp2nxsd7hq2tiku api endpoint to set a customer personal identification number (pin) this will be the customer's atm pin card replacement order a replacement for damaged, lost or stolen cards using the docid\ axi2plsucmhxdn8 vhcoh api endpoint damaged cards remain active until the cardholder activates the replacement card lost or stolen cards are immediately closed and a replacement card is issued important when you replace a card, you must make the replacement card the primary card in the cross river system to avoid issues once the card is supplied