The Cards API contains all the endpoints necessary to create nominated and innominated cards, activate them, perform searches, obtain information about a particular card, and more.
The endpoint /cards/v1/
allows you to create a new nominated card that can be physical or virtual.
We will validate that you meet the requirements detailed in the documentation.
The endpoint /cards/v1/
allows you to search for a group of cards based on the attributes you specify.
You will be able to filter and sort the cards following this documentation.
The attributes for sorting are:
card_type
user_id
status
affinity_group_id
status_detail
shipment_id
innominate
start_date
.The endpoint /cards/v1/{id}
allows you to obtain information about a particular card.
This functionality allows access to sensitive card data such as the full number (PAN), security code (CVV), cardholder name, and expiration date.
By requirement of the PCI DSS standard, you may only use this functionality if:
If you do not meet these requirements, you may use our secure data Web.
The endpoint /cards/v1/{id}
allows you to update the status of a card, its affinity group, and the PIN.
You must specify a reason from the following list to update the status of a card:
New status. | Valid reason |
---|---|
BLOCKED / DISABLED | CLIENT_INTERNAL_REASON |
BLOCKED / DISABLED | USER_INTERNAL_REASON |
DISABLED | LOST |
DISABLED | STOLEN |
DISABLED | BROKEN |
DISABLED | UPGRADE |
The endpoint /cards/v1/activation
allows you to activate a physical card and also set a PIN.
We will validate that you meet the requirements detailed in the documentation..
Add this endpoint to your service so we can communicate updates about your cards in real time.
If you have questions about how to set up a webhook, visit our documentation.
We expect a response of type 2XX to ensure that you received the notification. Otherwise, we will resend it.
CREATION
: We will notify you each time a new card is created.ACTIVATION
: We will notify you each time a card is activated.EMBOSSMENT
: We will notify you each time we send a card for embossing.BLOCK
: We will notify you each time a card is blocked.UNBLOCK
: We will notify you each time a card is unlocked.DISABLEMENT
: We will notify you each time a card is deactivated.api-secret
to use in case multiple pairs of api-key
and api-secret
have been configured.The endpoint /cards/v1/{id}/shipment
allows you to update the shipping address of a card.
The card must be a physical nominated card and have a status of CREATED
.
The endpoint /cards/{id}/cvv/refresh
allows you to refresh the dynamic CVV of a card, invalidating the current CVV and generating a new one.
You will be able to obtain the new CVV with the endpoint Get Card.
This endpoint only applies to virtual cards of an affinity group with dynamic CVV functionality enabled.
The endpoint /cards/v1/batches
allows you to create a batch of innominated cards.
We will validate that you meet the requirements detailed in the documentation.
CLIENT
.The endpoint /cards/v1/batches/bulk
allows you to create up to 15 batches of innominated cards at the same time.
We will validate that you meet the requirements detailed in the documentation.
CLIENT
.The endpoint /cards/v1/batches/shipments/{shipmentId}
allows you to update the shipping address of a batch of cards.
The batch of cards must be a physical innominated card and have a status of CREATED
.
/config/affinity-groups/{id}
allows you to obtain information about a particular affinity group.