Payment with the token creation option for the cardholder
In order to understand the result, analyze the following fields:
Field name | Description |
---|---|
vads_page_action | Completed action. The returned value is ASK_REGISTER_PAY. |
vads_identifier_status | Token creation status. The field will not be sent if the buyer has not given the approval to register their card details. Possible values are:
|
vads_trans_status | Status of the transaction. Possible values are:
|
vads_identifier | Token ID. The field will not be sent if the buyer has not given the approval to register their card details. The returned value is:
Note If you have activated the token uniqueness check and the payment method is already registered with another token, then this token will be returned. The field vads_identifier will not be returned:
|
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. |
To view the payment details, see the parameters below:
Transaction details:
Field name | Description |
---|---|
vads_operation_type | Transaction type Its value is DEBIT. |
vads_amount | Transaction amount. The returned value is the same as the one submitted in the form. |
vads_currency | Code of the currency used for the payment. |
vads_trans_id | Transaction identifier. The returned value is the same as the one submitted in the form. |
vads_trans_uuid | Unique transaction ID. Its value is generated by the payment gateway. |
vads_initial_issuer_transaction_identifier | Unique transaction identifier generated by the issuer. |
vads_contract_used | MID associated with the transaction. |
vads_auth_mode | Type of request made via authorization servers:
|
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_control | Result of the risk assessment. If at least one verification process returns the ERROR value, the transaction is rejected. See the description of the vads_risk_analysis_result field for more information. |
vads_risk_assessment_result | List of actions made with the transaction, following the activation of the advanced risk assessment rules. 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_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.