Card issuing
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 COS uses i2c as the payment processor, with the ability to adapt to other card processors.
Find these APIs in the cardmanagement module of our COS sandbox.
Get started with Cross River APIs.
This table presents APIs that we describe in detail.
Action | API Call | Description |
POST /cardmanagement/v1/cards | Requests creation of a new card | |
POST /cardmanagement/v1/cards/{id}/activate | Activates a card for a customer. This is the preferred way to activate a card. | |
PUT /cardmanagement/v1/cards/{id}/pin | Sets the customer PIN | |
GET /cardmanagement/v1/cards/{id} | Returns the details of a specific debit card based on its ID | |
GET /cardmanagement/v1/transactions | Returns information about card transactions based on various query criteria such as payment date or a range of dates, card type or account number |
To create a card, you must supply a valid deposit account number along with other card-specific information. The initial card status of a newly submitted card is unactivated. When the card is successfully created the order status is OrderPending.
Cards can only be used once they are activated. After creation, the card status is Unactivated. Once you are ready to activate the card for use, call the Activate Card ID endpoint. This is the preferred way to activate a card.
Response attributes
The response attributes for this call are the same as for Create a new card.
Set an initial debit card personal identification number (PIN) number for withdrawing funds from an ATM and other uses.
To set a card PIN number, the card cannot already have a PIN number set. This means that the card's isPinSet must have a value of false.
Response attributes
The response attributes for this call are the same as for Create a new card.
Returns the details of a specific debit card based on its ID.
Response attributes
The response attributes for this call are the same as for Create a new card.
Returns details about card transactions. The response values below are repeated for each transaction.
Add query parameters to filter the response the API returns to all GET calls.
Use pagination to control presentation of your results.
Event Name | Description |
Cards.Card.Activated | Debit card activated |
Cards.Card.Closed | Debit card closed |
Cards.Card.Created | Debit card created |
Cards.Card.Failed | Debit card creation failed |
Cards.Card.Pin.Set | PIN set for debit card |
Cards.Card.Profile.Changed | Profiled of cardholder changed |
Cards.Card.Replaced | New card created to replace an existing card |
Cards.Card.Suspended | Debit card use temporarily suspended |
Cards.Card.Unsuspended | Suspension removed from debit card |
Cards.Transaction.Cleared | Card transaction successfully completed |
Cards.Transaction.Authorized | Card transaction approved |
Cards.Transaction.Declined | Card transaction not approved |
Cards.Transaction.Failed | Card transaction did not succeed |
Cards.Transaction.Reversed | Payment credited to the originating account |
Cards.Card.Status.Changed | Card state has changed |