Response codes

There are two places in the payment flow when Netaxept may respond with the response code OK. Be mindful that these two responses should not be confused.

After the customer has entered their payment method information in the payment window and passed the possible 3D Secure authentication successfully, they are redirected to the redirectURL specified by the merchant in the Register call. At the end of this URL you will find a responseCode parameter which includes either "OK", "Cancel" or some error code. This specifies whether the terminal process has been completed successfully. It doesn't contain information about the completeness of the actual payment.

Example of a URL for a completed terminal phase: http://localhost/Test/?transactionId=6c5e402a4ee445ba9f19411f55c75b91&responseCode=OK

Example of a URL for a payment where the customer clicked “Cancel” button on the payment window: http://localhost/Test/?transactionId=6c5e402a4ee445ba9f19411f55c75b91&responseCode=Cancel

The response code OK is also returned to the merchant when the transaction has been processed (for example authorized, captured or credited) successfully without errors by using the Process call. In that case, OK parameter can be found in the ResponseCode parameter in the ProcessResponse.

Despite of the successfully authorized and captured transaction, it is recommended to make the Query call before sending goods to the customer to verify that the money has actually been captured. This is due to the response times Netaxept from time to time see from third-party payment methods, such as direct bank payments.

Example of a response for a successfully processed payment:

<ProcessResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <AuthorizationId>258460</AuthorizationId>
  <BatchNumber>642</BatchNumber>
  <ExecutionTime>2017-01-24T07:47:28.1900126+01:00</ExecutionTime>
  <MerchantId>[MERCHANTID]</MerchantId>
  <Operation>AUTH</Operation>
  <ResponseCode>OK</ResponseCode>
  <TransactionId>6c5e402a4ee445ba9f19411f55c75b91</TransactionId>
</ProcessResponse>

If something goes wrong when communicating between your system and Netaxept or in the middle of the payment process, Netaxept declines the transaction and returns an exception. All exceptions are wrapped in the outer Exception tag, with an Error tag inside. The type (xsi:type) of the Error tag indicates which exception it is. Read more about exceptions

All exceptions include the message that provides a textual description of what failed. Besides the message, one commonly used exception "BBSException" includes also error code, error source and error message which are available in English.

Example of an error response for a payment that is already processed:

<Exception xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <Error xsi:type="BBSException">
    <Message>Unable to sale</Message>
      <Result>
        <IssuerId>3</IssuerId>
        <ResponseCode>98</ResponseCode>
        <ResponseText>Transaction already processed</ResponseText>
        <ResponseSource>Netaxept</ResponseSource>
        <TransactionId>6c5e402a4ee445ba9f19411f55c75b91</TransactionId>
        <ExecutionTime>2017-01-24T09:56:24.8329041+01:00</ExecutionTime>
        <MerchantId>[MERCHANTID]</MerchantId>
        <MaskedPan/>
      <MessageId>8ba8ccadbffa4f2ba7c6f286bbcada68</MessageId>
    </Result>
  </Error>
</Exception>

The error codes are divided into groups according to the source. The source is a textual description of which part of the system generated the error code. The source should not be used to drive code; instead, it should only be logged and used as a diagnostic tool if it is unclear why a transaction failed.

• "Netaxept" or "NTS" (or "01" in the old Netaxept; version 1), if the error occurred in the Netaxept solution.
• "Issuer" (or "02" in the old Netaxept; version 1), if the error came from the card Issuer or other payment method service provider.
• "Module" (or "03" in the old Netaxept; version 1)) or "Transport" (or "04" in the old Netaxept; version 1), if the error occurred internally at Nets.
• "Terminal" (or "05" in the old Netaxept; version 1), if the error occurred as a result of the customer input in the payment window.

Note! Occasionally, you can see other sources as well, for example the name of a Netaxept’s integration partner, like "Klarna"

Netaxept displays error messages to the customer in the payment window, to guide the customer in cases where error situations can be resolved by fixing errors for example in data fields. These error messages will be translated to the language specified by the merchant in the Register call. The error messages may also specify the data field where the error is happening, to direct the customer to resolve the error. The following are the most common error messages shown in the payment window for card payments.

• Too few digits
• Expired card
• Missing bank agreement
• Too many digits
• The cardnumber belongs to another card company
• Contains illegal characters
• Wrong cardnumber
• Format error
• Illegal value
• Is missing and required
• Not legal length
• Refused by Issuer (Several payment methods may return this error message. In these cases, the Issuer bank or payment method service provider has refused the payment, and the customer can be advised to contact their card Issuer or payment method service provider to resolve the issue).
• 17: Cancelled by customer
• 30: Missing customer input

• Pan Hash not in file: panHash (token) used in subsequent payment has been deleted due to retention criteria described on the tokenization page.

Error messages from Netaxept’s integration partners are documented at their own developer site.

When the merchant uses their own hosted payment window, Netaxept will compose the responseCode parameter returned to the merchant via Query call from the following field names and messages. At the same time, the Operation parameter and the ResponseSource parameter will be set to "Terminal". In the responseCode parameter the field names and messages are concatenated with a ":", and if there are multiple errors, they will be comma-separated.

Field name:

• Cardnumber
• ExpiryMonth
• ExpiryYear
• SecurityCode

Message:

• TooFewDigits
• TooManyDigits
• ContainsIllegalCharacters
• HasWrongCheckDigit
• FormatError
• IllegalValue
• Required
• IllegalLength
• ExpiredCard

In some cases, the responseCode will be set to "30" when the ResponseSource is set to "Terminal". This is in the situations where Netaxept tries to look up the payment card in its BIN servers but is unable to find it. This can be communicated to the customer as "Illegal card". This case will be extremely seldom in the production environment as the production BIN servers have larger datasets than the ones in the test environment.

Example of the error message returned to the merchant via Query response:

<Error>
  <DateTime>2017-08-04T09:46:09.947</DateTime>
  <Operation>Terminal</Operation>
  <ResponseCode>Cardnumber:Required</ResponseCode>
  <ResponseSource>Terminal</ResponseSource>
  <ResponseText/>
</Error>

Examples of the ResponseCode values:

Multiple response codes can also be combinated. In that case, the codes are separated with a comma. For example:

<ResponseCode>Cardnumber:HasWrongCheckDigit,ExpiryMonth:FormatError</ResponseCode>

This a combination of wrong check digit on the card number and expiry month being formally incorrect.

Below you can find error codes from version 1 of Netaxept API. The error response consists of a three-digit number indicating data field, combined with a code indicating the error. For example, if MasterCard CVC2 is missing, the response is 144:7.

3-digit numbers indicating the data field where the error occur are listed in the table below:

Codes indicating the exact error are listed in the table below: