Processing the response data

Here is an example of analysis to guide you through processing the response data.

  1. Identify the mode (TEST or PRODUCTION) that was used for creating the transaction by analyzing the value of the vads_ctx_mode field.
  2. Identify the order by retrieving the value of the vads_order_id field if you have transmitted it to the payment gateway.
    Make sure that the order status has not already been updated.
  3. Retrieve the payment result transmitted in the vads_trans_status field.
    Its value allows you to define the order status.
    Valeur Description
    ABANDONED Abandonné

    Paiement abandonné par l’acheteur.

    La transaction n’est pas créée et n’est donc pas visible dans le Merchant Back Office.

    AUTHORISED

    Waiting for capture

    La transaction est acceptée et sera remise en banque automatiquement à la date prévue.

    CANCELLED

    Canceled

    La transaction est annulée par le marchand.

    CAPTURED

    Captured

    La transaction est remise en banque.

    REFUSED

    Declined

    La transaction est refusée.

    SUSPENDED Suspended

    La remise de la transaction est temporairement bloquée par l'acquéreur (AMEX GLOBAL ou SECURE TRADING). Une fois la remise traitée correctement, le statut de la transaction deviendra CAPTURED.

  4. Retrieve the payment reference transmitted in the vads_trans_id field.
  5. Retrieve the value of the vads_trans_date field to identify the payment date.
  6. Retrieve the value of the vads_capture_delay field to identify the number of days before the capture in the bank.
    It will allow you to identify whether the payment is an immediate or a deferred payment.
  7. Retrieve the used amount and currency. To do this, retrieve the values of the following fields:
    Table 1. Analysis of the payment amount and currency
    Field name Description
    vads_amount Payment amount in the smallest currency unit.
    vads_currency Code of the currency used for the payment.
  8. Retrieve the value of the vads_auth_result field to identify the result of the authorization request.
    The complete list of returned codes can be viewed in the data dictionary.
  9. Retrieve the 3D Secure authentication result. To do this:
    1. Retrieve the value of the vads_threeds_enrolled field to identify the status of the card enrollment.
      Table 2. Values of the vads_threeds_enrolled field
      Value Description
      Empty Incomplete 3DS authentication process (3DS disabled in the request, the merchant is not enrolled or the payment method is not eligible for 3DS).
      Y Authentication available, cardholder enrolled.
      N Cardholder not enrolled.
      U Impossible to identify the cardholder or authentication is not available for the card (e.g. commercial or prepaid cards).
    2. Retrieve the result of 3D Secure authentication by retrieving the value of the vads_threeds_status field.
      Table 3. Values of the vads_threeds_status field
      Value Description
      Empty Incomplete 3DS authentication (3DS disabled in the request, the cardholder is not enrolled or the payment method is not eligible for 3DS).
      Y Cardholder authentication success.
      N Cardholder authentication error.
      U Authentication impossible.
      A Authentication attempted but not completed.
  10. Retrieve the result of fraud checks by identifying the value of the vads_risk_control field. This field is sent only if the merchant has:
    • subscribed to the "Risk management" service
    • enabled at least one verification process in the Merchant Back Office (Settings > Risk management menu).
    It is populated with the list of values separated by ";" with the following syntax: vads_risk_control = control1=result1;control2=result2
    the possible values for control are:
    Table 4. List of fraud verification processes
    Value Description
    CARD_FRAUD Verifies whether the cardholder's card number is on the card greylist.
    SUSPECT_COUNTRY Checks whether the issuing country of the buyer’s card is on the list of forbidden countries.
    IP_FRAUD Verifies whether the cardholder's IP address is on the IP greylist.
    CREDIT_LIMIT Checks the purchase frequency and amounts for the same card number, or the maximum amount of an order.
    BIN_FRAUD Checks whether the BIN code of the card is on the BIN code greylist.
    COMMERCIAL_CARD Checks whether the buyer’s card is a commercial card.
    SYSTEMATIC_AUTO Checks whether the buyer’s card is a MAESTRO or VISA ELECTRON card.
    INCONSISTENT_COUNTRIES Checks whether the country of the IP address, the country of the payment card and the buyer’s country of residence match.
    SUSPECT_IP_COUNTRY Checks whether the buyer’s country, identified by their IP address, is on the list of forbidden countries.
    The possible values for result are:
    Table 5. List of fraud verification processes
    Value Description
    OK OK.
    WARNING Informational control failed.
    ERROR Blocking control failed.
  11. Retrieve the type of the card used for the payment.
    Table 6. Analysis of the card used for the payment
    Field name Description
    vads_card_brand Brand of the card used for the payment, e.g.: , VISA, VISA_ELECTRON, MASTERCARD, MAESTRO, VPAY
    vads_card_number Card number used for the payment.

    vads_expiry_month Expiry month between 1 and 12 (e.g.: 3 for March, 10 for October).
    vads_expiry_year Expiry year in 4 digits (e.g.: 2023).
    vads_bank_code Code of the issuing bank
    vads_bank_product Product code of the card
    vads_card_country Country code of the country where the card was issued (alpha ISO 3166-2 code, e.g.: "IN" for India, "US" for the United States).
  12. Store the value of the vads_trans_uuid field. It will allow you to assign unique identification to the transaction if you use the Web Service APIs.
  13. Retrieve all the order, buyer and shipping details.
    These details will be provided in the response only of they have been transmitted in the payment form.
    Their values are identical to the ones submitted in the form.
  14. Proceed to order update.