Updating token details
In order to understand the result, analyze the following fields:
Field name | Description |
---|---|
vads_page_action | Completed action. The returned value is REGISTER_UPDATE. |
vads_identifier_status | Token update status. Possible values are:
|
vads_identifier | Token ID to be updated. The returned value is the same as the one submitted in the form. |
vads_initial_issuer_transaction_identifier | Unique transaction identifier generated by the issuer. The issuer transaction identifier is stored by the payment gateway at the level of the alias. Depending on how you use the alias (1-click payment, 0-click payment, recurring payment, etc.) the issuer transaction ID will be used as a chaining reference if necessary. |
vads_cust_email | Buyer’s e-mail address transmitted in the request. |
vads_site_id | Shop ID The returned value is the same as the one submitted in the form. |
vads_ctx_mode | Operating mode. The returned value (TEST or PRODUCTION) is the same as the one submitted in the form. |
A “token update” request results in the creation of a VERIFICATION transaction, visible in the Merchant Back Office.
The purpose of this transaction is to help the merchant, via their Back Office, understand the reasons for refusal of token creation.
Here are its characteristics:
Field name | Description |
---|---|
vads_operation_type | Transaction type Its value is VERIFICATION. |
vads_trans_status | Status of the transaction. Possible values are:
|
vads_occurrence_type | Transaction occurrence type. Its value is UNITAIRE. |
vads_amount | Possible values:
|
vads_trans_id | Transaction identifier. Its value is generated by the payment gateway. |
vads_trans_uuid | Unique transaction ID. Its value is generated by the payment gateway. |
vads_auth_mode | Type of request made via authorization servers. Its value is MARK. |
vads_auth_number | Authorization number returned by the authorization server. Empty if the authorization has failed. |
vads_auth_result | Return code of the authorization request returned by the issuing bank. See chapter Managing the return codes of the authorization request. Empty in case of an error prior to the authorization. |
vads_risk_assessment_result | List of actions made with the transaction, following the activation of the advanced risk assessment rules. The rules related to the amount, or whose action is “Validate manually”, do not apply in case of a VERIFICATION type transaction. Possible values are:
|
Field name | Note |
---|---|
vads_acquirer_network | Acquirer network code. |
vads_bank_code | Code of the issuing bank. |
vads_bank_label | Name of the issuing bank of the payment card. |
vads_bank_product | Product code of the used card. |
vads_brand_management | Allows to know the brand that was used, the list of available brands as well as whether the buyer has changed the default brand chosen by the merchant. |
vads_card_brand | Used payment method. See chapter Compatible payment methods to see the list of possible values. |
vads_card_country | Country code of the card used in compliance with the ISO 3166 standard. |
vads_card_number | Truncated/masked card number or IBAN and BIC used for the payment separated by “_” in case of a one-off debit payment. Since the BIC is optional, it may be left out. . |
vads_expiry_month | Expiry month of the used card. It is advisable to use this data to check the expiration date of the token. |
vads_expiry_year | Expiry year of the used card. It is advisable to use this data to check the expiration date of the token. |
Field name | Note |
---|---|
vads_threeds_auth_type | Cardholder authentication type. Strong cardholder authentication is mandatory when registering a card. The field will therefore always be populated with CHALLENGE. |
vads_threeds_enrolled | Enrollment status of the buyer to the 3D Secure program. Possible values are:
|
vads_threeds_status | 3D Secure authentication result. Possible values are:
|
The optional fields transmitted in the request are returned in the response with unmodified values.