Card Verification¶
Performs card verification and creates a payment token if the verification was successful and the account
parameter was provided. If 3D-Secure customer authentication is used, the token is returned in the successful response to Complete 3DS on card verification request.
For additional information, please see “Card Verification“
Request¶
PUT /payin/v1/sites/{siteId}/validation/card/requests/{requestUid}
Path Parameters¶
Parameter | Required | Type | Description |
---|---|---|---|
siteId | Yes | string | Merchant site identifier |
requestId | Yes | string | Unique request identifier in the merchant’s system |
Headers¶
Header | Required | Type | Description |
---|---|---|---|
Authorization | Yes | string | API access key. Bearer [access-token] |
Content-type | Yes | string | Request content. application/json |
Accept | No | string | Response content. application/json |
Body Parameters¶
Parameter | Required | Type | Description |
---|---|---|---|
cardData | Yes | object | Bank card data |
tokenizationData | No | object | Data for payment token generation |
Request Example¶
Vard verification and payment token generation
PUT /partner/payin/v1/sites/test-01/validation/card/requests/acd7bf20-22e2-4cbf-a218-38d90e9f29b9 HTTP/1.1
Accept: application/json
Authorization: Bearer 5c4b25xx93aa435d9cb8cd17480356f9
Content-type: application/json
Host: b2b-api.qiwi.com
{
"cardData": {
"pan": "1111222233334444",
"expiryDate": "12/34",
"cvv2": "123",
"holderName": "Super Man"
},
"tokenizationData": {
"account": "cat_girl"
}
}
Response¶
See also HTTP error codes
Successful Response Parameters¶
Parameter | Required | Type | Description |
---|---|---|---|
requestUid | Yes | string | Request identifier. Same as in the request |
status | Yes | string | Card verification status |
checkOperationDate | No | string | Verification date and time |
isValidCard | No | boolean | Verification result.true — the card is valid for payments |
threeDsStatus | No | string | 3D-Secure status |
cardInfo | No | object | Bank card information |
requirements | No | object | Requirements for customer’s addtional verification |
createdToken | No | object | Payment token data. Returns if the additional authentication 3D-Secure is not requieed, isValidCard=true and the account parameter was provided |
Error Parameters¶
Parameter | Required | Type | Description |
---|---|---|---|
serviceName | Yes | string | Name of the service that produced the error |
errorCode | Yes | string | Error code |
description | Yes | string | Error description for the merchant |
userMessage | Yes | string | Error description for the customer |
dateTime | Yes | string | Error date and time |
traceId | Yes | string | Error Log unique ID |
Response Examples¶
{
"requestUid": "acd7bf20-22e2-4cbf-a218-38d90e9f29b9",
"status": "SUCCESS",
"isValidCard": true,
"threeDsStatus": "WITHOUT",
"checkOperationDate": "2025-03-25T12:55:12+03:00",
"cardInfo": {
"issuingCountry": "643",
"issuingBank": "Gazprombank",
"paymentSystem": "MIR",
"fundingSource": "DEBIT",
"paymentSystemProduct": "details"
},
"createdToken": {
"token": "1a77343a-dd8a-11eb-ba80-0242ac130004",
"name": "111122******4444",
"expiredDate": "2034-12-31T00:00:00+03:00",
"account": "cat_girl"
}
}