Cross River card issuing lets you offer customers different types of debit card products. These products, known as instrument types, include contact-less and virtual cards. CR card issuing in our banking core uses i2c as the payment processor, but can adapt to other card processors.

Manage your customer's cards by working with CR to decide what you want to offer, such as physical or virtual cards. This is the card configuration. CR creates a card configuration profile for youfor each instrument type you choose for your customers. Once created, we give you a configurationId for each instrument type you are offering. You needthis configuration ID when asking COS to create a new card for a customer.

To create a card, 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 is not activated.

Cards can only be used once they are activated. To activate the card, use the activate endpoint with the COS card ID.

Cards include different types of status: The status (card status) and the order status. These indicate different things.

The card status also contributes to the card state.

The status attribute is the activation status of the card and if the card can be used by the cardholder:

The orderStatus attribute is the current status of the order:

The status of a newly created card is Unactivated and the order status is OrderPending. The order status updates to Completed when the order is complete. For physical cards, this means the card has been mailed to the customer.

Managing a card program may require you to update card statuses for specific scenarios. For example, you may want to offer your customers added security by allowing them to temporarily suspend a card that has been misplaced.

Update activated card status when necessary to suspend, block, or close a card:

A given card status can be due to more than one reason. For example, a card might be suspended because it was lost, stolen, or blocked due to fraud. Knowing the reason for a given status is important to manage the card life cycle. At CR we call combination of status and other attributes card state.

You see the card state in the Cards.Status.Changed webhook event.



Order a replacement for damaged, lost or stolen cards using the replace 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.

Use the pin endpoint to set a customer personal identification number (PIN). This will be the customer's ATM PIN.

See the card issuing API reference page.