Card Info API V2 -> V4 migration guide


The following guide will help you migrate from Card Info API V2 to CardInfo API V4. We advise you to do so, as V2 won't be maintained anymore.

A list of all migration guides can be found here: Go to migration guides


Note: Everything colored with red was removed in API V4, while the new functionalities added in V4 are colored with green.

Endpoints

Endpoint V2 Endpoint V4 HTTP method V2 HTTP method V4 V2 V4
Get Card Info By card number Get card information by bin POST GET api/card-info/v2 api/v4/cardinfo/bin/:cardBin
Get Card Info By Merchant Token Get card information by card token POST GET api/card-info/v2 api/v4/cardinfo/token/:token


Get Card Info By Bin

Request parameters mapping
V2 V4 Details
merchant it was moved in X-Header-Merchant, see authentication section
dateTime it was moved in X-Header-Date header (date format changed), see authentication section
signature it was moved in X-Header-Signature header, see authentication section
cc_cvv
cc_owner
exp_year
exp_month
cc_number
extraInfo
cardBin

Response parameters mapping
V2 V4 Details
meta.code code
meta.message status
message A text message with details about processing result or with some message error
cardInfo.binNumber binNumber
cardInfo.cardBrand cardScheme
cardInfo.issuerBank issuerBank
cardInfo.issuerCountry issuerCountryCode Values migrated from being the entire name to ISO 3166-1 alpha-2
cardInfo.cardType cardType
cardInfo.cardProfile cardProfile
cardInfo.cardProgram cardProgram
cardInfo.installmentOptions.installmentNumber installmentOptions.installmentNumber
cardInfo.installmentOptions.installmentAditionalCostPercent
paymentMethod
cardInfo.cardMask
loyaltyPoints.type
loyaltyPoints.number
loyaltyPoints.moneyValue.amount
loyaltyPoints.moneyValue.currency


Get Card Info By Merchant Token

Request parameters mapping
V2 V4 Details
token token Path parameter
merchant it was moved in X-Header-Merchant header, see authentication section
timestamp it was moved in X-Header-Date header (date format changed), see authentication section
signature it was moved in X-Header-Signature header, see authentication section

Response parameters mapping
V2 V4 Details
meta.code code
meta.message status
message A text message with details about processing result or with some message error
cardInfo.binNumber binNumber
cardInfo.cardBrand cardScheme
cardInfo.issuerBank issuerBank
cardInfo.issuerCountry issuerCountryCode Values migrated from being the entire name to ISO 3166-1 alpha-2
cardInfo.cardType cardType
cardInfo.cardProfile cardProfile
cardInfo.cardProgram cardProgram
cardInfo.installmentOptions.installmentNumber installmentOptions.installmentNumber
cardInfo.installmentOptions.installmentAditionalCostPercent
cardInfo.paymentMethod paymentMethod
cardInfo.cardMask
loyaltyPoints.type
loyaltyPoints.number
loyaltyPoints.moneyValue.amount
loyaltyPoints.moneyValue.currency
fxInfo.selectedCurrency


Authentication

Deprecated V4
Can be done in two ways:
  • Header authentication: Authorization and X-timestamp headers
  • Request parameter authentication: merchant, timestamp and signature parameters
The signature is passed in the requests X-Header-Signature header, that has to be sent together with X-Header-Date and X-Header-Merchant headers. Read more about how its calculated here