Cards

Learn how to create/manage cards, receive and/or update card’s information

A set of functionalities allows to manage important aspects of the card lifecycle, to retrieve, update and oversee key card details.

---

Create Card t-dapi only

Use POST/v2/api/cards Create card V2 to create a physical or virtual card for a new private or business client, as well as to create a supplementary card to existing card account. To create a card, you should submit all mandatory fields as indicated in Swagger documentation. Create card endpoint has the same card creating scenarios as for Card order endpoint and can be found here. If the Create card request was submitted successfully then you will receive PPAN, card account and client ID in response. This endpoint requires additional access rights and is proposed for TPP clients only. To start using it, please contact your DECTA manager.

---

Get Cards

When you want to retrieve information about all your issued cards, you should use the request GET/v1/api/cards to get a list of cards with detailed information.

---

Retrieve Card information

To receive detailed information about a specific card and client, use the request GET/v1/api/cards/{ppan} and select necessary PPAN.

---

Retrieve Card data 1

Use request GET/v1/api/cards/{ppan}/card-data1 to get sensitive card information, like PIN code for a specific PPAN. DECTA takes data security seriously, so please contact your DECTA Manager to learn more about the availability of this additional feature.

---

Retrieve Card data 2 and 5

Use the request GET/v1/api/cards/{ppan}/card-data2 or GET/v1/api/cards/{ppan}/card-data5 to get sensitive card information, like full PAN and CVV2 or CVC2 for a specific PPAN. DECTA takes data security seriously, so please contact your DECTA Manager to learn more about the availability of this additional feature.

---

Retrieve Card data 3

If you are cooperating with a token service provider, you should use request GET/v1/api/cards/{ppan}/card-data3 to get selected card data including a clear pan, cardholder name, and expiry date for the specific card. As an additional layer of security, it is necessary to use the OTP Secret in the request. OTP secret allows card issuers to delegate permissions for a token service provider to fetch sensitive data for a specific PPAN.

---

Retrieve Card data 4

If you are cooperating with a third-party data service provider, it should use request GET/v1/api/cards/{ppan}/card-data4 to get selected card data including a clear pan, cardholder name, CVV2/CVC2 and expiry date for the the specific card. As an additional layer of security, it is necessary to use the OTP secret in the request. OTP secret allows card issuers to delegate permissions for a token service provider to fetch sensitive data for a specific PPAN.

---

Retrieve Card data 6 t-dapi only

If you are cooperating with a third-party data service provider, it should use request GET/v2/api/cards/{ppan}/card-data6 to get PIN in encrypted format for a selected card. As an additional layer of security, it is necessary to use the OTP secret in the request. OTP secret allows card issuers to delegate permissions for a third-party data service provider to fetch sensitive data for a specific PPAN.

---

Get a One-Time Password (OTP)

Use request GET/v1/api/cards/{ppan}/otp-secret if you are cooperating with a token service provider or a third-party data service provider to allow them to retrieve a sensitive data for a specific PPAN.

---

Assign PIN code

You have the option to offer your clients the possibility to change their PIN code by using the request POST/v1/api/cards/{ppan}/assign-pin. The PIN code length is 4 digits. To find out more about this option and how you can start using it, contact your Account Manager.

---

Replace a card

When your client needs to replace a damaged or stolen/lost card, use the request POST/v1/api/cards/{ppan}/replace. The clients previous card should be permanently blocked.

---

Renew a card

When your client needs to renew the plastic card that expires within 2 months use the request POST/v1/api/cards/{ppan}/renew. This request allows to mark the card by selected PPAN which should be renewed and included in embossing file during the next file generation session. This request is intended only for plastic cards which are in status UNBLOCKED or BLOCKED_BY_HOLDER. If the card is in status BLOCKED_BY_HOLDER, then it will be automatically changed to status UNBLOCKED and marked for renewal. Use PATCH/v1/api/cards/{ppan}/state to set again BLOCKED_BY_HOLDER for the old card.

Renewed cards are made with the same account and card conditions configured in card product setting using the same PAN or a new PAN.

For renewed cards with the same PAN:

• The old card should be used until it expires and then the renewed card can be activated;
• Card token is updated.
• CVV/CVC is updated.

For renewed cards with a new PAN:

• The old card can be closed any time upon activating the renewed card;
• Card token is updated.
• CVV/CVC is updated.

---

Card Status Change

To change the card status, you should request PATCH/v1/api/cards/{ppan}/state that allows to activate, block or unblock a card by selected pseudo-pan.

---

Activate Card

To activate a physical card that has been received by the cardholder and has the status 1- Suspended, make a PATCH/v1/api/cards/{ppan}/state request and set the state to ACTIVE. In this request the cardholder should indicate the last 6 digits of the card.

---

Suspend Card

To suspend a card make a PATCH/v1/api/cards/{ppan}/state request and set the state to BLOCKED_BY_HOLDER or BLOCKED_BY_PARTNER. A suspended card can still be unblocked or blocked permanently.

Card statuses with converted card blocking reason codes to Visa/Mastercard systems:

---

Reactivate Suspended Card

To activate a card that was suspended, make a PATCH/v1/api/cards/{ppan}/state request and set the state to UNBLOCKED.

---

Card Closure

Closing a card is equal to blocked permanently card status and can’t be reversed. Make PATCH/v1/api/cards/{ppan}/state request and set the state to BLOCKED_PERMANENTLY or BLOCKED_TERMINATED or BLOCKED_NOT_RECEIVED.

Card statuses with converted card blocking reason codes to Visa/Mastercard systems:

---

Change card user defined fields

If you want to change userDefinedField7, then use this request PATCH/v1/api/cards/{ppan}/user-defined-fields. UserDefinedField7 is a free custom use field which allows to store specific information/conditions associated with card in the database.