• France
status page
Demo shops
assistance
FAQContact support
Search
Categories
Tags
Europe (English)
France
Spain
Europe (English)
India
Homepage
Use cases
Create a payment
Create an installment payment
Create a multi-card (split) payment
Create a payment by Alias (Token)
Create a payment link
Create a recurring payment
Manage subscriptions
Manage your transactions (refund, cancel...)
Analyze your reports
API docs
Embedded Form
REST API
Hosted payment
Mobile payment
File exchange
SDD mandates by REST API
Snippets
Payment methods
Plugins
Marketplace
Guides
Merchant Back Office
Back Office Expert
Functional guides

Installment payment

In order to understand the result, analyze the following fields:

Field name Description
vads_page_action Completed action.

The returned value is PAYMENT.

vads_trans_status Status of the transaction.

Possible values are:

  • AUTHORISED

    The authorization request has been accepted.

  • AUTHORISED_TO_VALIDATE

    The authorization request has been accepted.

    The merchant must manually validate the transaction.

  • CAPTURED

    The authorization request has been accepted.

    The transaction is visible in the “Captured transactions” tab of the Back Office.

  • REFUSED

    The authorization request has been declined.

vads_identifier Token ID.
vads_cust_email Buyer’s e-mail address.
vads_site_id Shop ID
vads_ctx_mode Operating mode.

To see the recurring payment details, see the parameters below:

Field name Note
vads_subscription Recurring payment token
vads_recurrence_number Recurrence number of the recurring payment.

To view the payment details, see the parameters below:

Transaction details:

Field name Description
vads_operation_type Transaction type

Its value is DEBIT.

vads_occurrence_type Transaction occurrence type.
Possible values:
  • RECURRENT_INITIAL: First installment.
  • RECURRENT_INTERMEDIAIRE: Nth installment. View the vads_recurrence_number field to know the installment number.
  • RECURRENT_FINAL: Last installment.
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_contract_used MID associated with the transaction.
vads_auth_mode Type of request made via authorization servers:
  • MARK: corresponds to an authorization of EUR 1 (or information request about the CB network if the acquirer supports it).

    Value also used if the period between the requested capture date and the current date is strictly greater than the authorization validity period.

  • FULL: corresponds to an authorization of the total transaction amount.

    Value also used if the period between the requested capture date and the current date is strictly shorter than the authorization validity period.

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:

  • ENABLE_3DS: 3D Secure enabled.
  • DISABLE_3DS: 3D Secure disabled.
  • CHALLENGE_REQUESTED:
    • 3DS1 card: The risk module has requested 3DS authentication.
    • 3DS2 card: The risk module has requested an authentication with cardholder interaction (challenge).
  • CHALLENGE_MANDATE:
    • 3DS1 card: The risk module has requested 3DS authentication.
    • 3DS2 card: The risk module has requested an authentication with cardholder interaction (challenge for regulatory reasons) for regulatory reasons.
  • MANUAL_VALIDATION: The transaction has been created via manual validation.

    The payment capture is temporarily blocked to allow the merchant to perform all the desired verification processes.

  • REFUSE: The transaction is refused.
  • RUN_RISK_ANALYSIS: Result of the external risk analyzer.

    See the description of the vads_risk_analysis_result field for more information.

  • INFORM: A warning message appears.

    The merchant is notified that a risk has been identified via one or several notification center rules.

Details of the used payment method:
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.
Jobs
Legal
GDPR
25.18-1.11