This operation makes it possible to check the card’s validity. It consists in sending the card data (such as the primary account number and the expiration date) to Axerve Ecommerce Solutions and receiving the result after the checks.
The WSs2s web service method to use for this purpose is CallVerifycardS2S.
CallVerifycardS2S will also try to authorize the card using a very small amount.
This is the list of mandatory fields needed to verify the card:
shopLogin - merchant code
shopTransactionID - transaction identification code
cardNumber - credit card account number
expMonth - card expiration month
expYear - card expiration Year
CVV2 - String containing the Card Verification Value printed on the credit card, as specified in the chapter Handling of CVV field.
The CallVerifyCardS2S method sends to Axerve Ecommerce Solutions all previously assigned data, which uses to make a transaction request without affecting the account and returns the result of the operation.
After the CallVerifyCardS2S method has been performed, it is possible to know the outcome of the operation by using the values in the relevant XML return:
First it is possible to use the TransactionResult field which will return the string OK if the transaction was authorised or the string KO if the transaction was not authorised.
If TransactionResult returns the string KO, then it is possible to know whether the failure was due to a negative response from the credit card network, using the ErrorCode method:
If ErrorCode returns a value which is <> 0, the transaction was denied due to technical problems; the value returned will vary according to the specific reason for the failure. The ErrorDescription method will return a description of the reason for the failure (in the language set within the Back Office environment).
If ErrorCode returns the value 0, the transaction did not fail due to technical problems. By using the ErrorCode it is possible to know the error code associated with the failure; the description of the error will be shown in the language set within the Back Office environment by using the ErrorDescription method.
If TransactionResult returns the value OK, the transaction was authorised and the card is considered valid.