Cards

Learn how to receive and/or update cards and card information using DECTA API


The Card Information request allows users to receive a list of client cards. This request returns partial information about cards; if the user needs to receive detailed information about a certain card, please use a specific GET card request. Some use cases might require that the cardholder change their PIN number or passphrase, or even replace a stolen or lost card and, if necessary, update their delivery address.

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.

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

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.

Use the request GET/v1/api/cards/{ppan}/card-data2 or GET/v1/api/cards/{ppan}/card-data5to 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.

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 to send to the token service provider.

If you are cooperating with a third-party data service provider, you should use the request GET/v1/api/cards/{ppan}/card-data4 to get selected card data including a clear pan, cardholder name, and expiry date for the third-party data service provider.

To keep the data transfer safe with token service provider, you will be required to use a OTP. To get it make the request GET/v1/api/cards/{ppan}/otp-secret

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.

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.

The Client and/or partner can suspend cards to temporarily prevent payment processing. If a card is suspended, the client can activate the card again at any time. If a client wants to permanently cancel a card, it needs to be blocked. The request PATCH /v1/api/cards/{ppan}/state allows users to block, unblock and activate cards by pseudo-pan. Once the card is BLOCKED_PERMANENTLY it can't be unblocked.

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.

If your cardholder has lost, stolen or damaged a card, you should either suspend or block it. 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.

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

Blocking a card is a permanent action and cannot be reversed. To block a card permanently, make PATCH /v1/api/cards/{ppan}/state request and set the state to BLOCKED_PERMANENTLY.

Jump to
  • Get Cards
  • Retrieve Card information
  • Retrieve Card data 1
  • Retrieve Card data 2 and 5
  • Retrieve Card data 3
  • Retrieve Card data 4
  • Get a One-Time Password (OTP)
  • Assign PIN code
  • Replace a card
  • Card Status Change
  • Activate Card
  • Suspend Card
  • Reactivate Suspended Card
  • Block Card Permanently