Releases 2026

Release 2.20. - 06.05.2026

Added

• New endpoint GET/v2/api/cards/{ppan} This request allows users to get card information with available balance. This endpoint will replace existing v1 Get Card Information, which will be deprecated starting from 2.21. release.

• New endpoint GET/v2/api/clients/{clientID} The request allows users to receive clients data by using a specific client ID number. This endpoint will replace existing v1 Search client by ID, which will be deprecated starting from 2.21. release.

• Improved Swagger documentation for the Order Card and Create Card V2 endpoints to clearly indicate which field data is not stored in the database.

Deprecated Endpoint

The following endpoint has been marked as Deprecated in Swagger that shouldn’t be used:

• POST/v1/api/cards/card-data1 Get sensitive card information 1

Release 2.19. - 25.03.2026

Added

• New endpoint GET/v2/api/cards/{ppan}/card-data7 This request allows users to retrieve sensitive card information, such as the PIN code for a specific PPAN in encrypted format. This endpoint will replace the existing Get Sensitive Information 1 endpoint, which will be deprecated starting from 2.20. release.

• New endpoint GET/v2/api/accounts/{cardAccount} The request allows users to retrieve detailed information about a specific client's account, including its current balance, status and currency.

• New endpoint POST/v2/api/accounts/{cardAccount}/state The request allows users to manage the transition of the card account from an active state to permanent closure.

Release 2.18. - 11.02.2026

Added

• New endpoint POST/v2/api/cards/{ppan}/duplicate The request allows users to duplicate a virtual card to create a physical card while retaining the same card details for eligible card products.

• New endpoint GET/v2/api/limits/{ppan}/used The request allows users to get used values for the corresponding limit on the card.