Radial Payments can return a number of fault response codes when credit card processing encounters an exception that should be handled at the web store or the client layer. This page lists the codes and provides recommendations for handling each scenario. Web store developers integrating with Radial Payments can use this list as a guideline.

Fault Response Message

The fault response is an XML message. The following example shows the XML structure of the message.

Copy this code sample.
<?xml version="1.0" encoding="UTF-8"?>
<Fault xmlns="http://api.gsicommerce.com/schema/checkout/1.0">
   <CreateTimestamp>2018-06-26T09:35:07.573Z</CreateTimestamp>
   <Code>{Error Code} </Code>
   <Description>{Error Description} </Description>
</Fault>

Codes and Descriptions

The following table lists fault response codes with recommended actions for each code.

Error Code

Description

Recommended Handling

PanDoesNotPassLuhnCheckException/

PanFailsLuhnCheckException

This payment account number is invalid because it does not pass the Luhn check

(For more information, see https://en.wikipedia.org/wiki/Luhn_algorithm)

Prompt the customer to correct the credit card number.

A maximum number of attempts can be configured. After that number of attempts has been reached, the order should be rejected.

UnknownPanBinRangeException

This payment account number is invalid because it does not fall within a recognized bin range for the tender type

Prompt the customer to correct the credit card number.

A maximum number of attempts can be configured. After that number of attempts has been reached, the order should be rejected.

InvalidTenderTypeException

The tender type passed is not CC

Prompt the customer to choose the correct tender type and ensure the checkout schema contains the correct tender type

TenderGatewayConfigurationException

The Store ID is not configured for the tender type and country code

Store ID should be mapped with the corresponding tender type and country code

TokenNotFoundException

The token passed in with the service request was not found

Prompt the customer to pass a valid token in the request in order to process the transaction.

PanNotFoundException

The pan passed in with the service request is invalid

Prompt the customer to pass a valid token in the request in order to process the transaction.

A maximum number of attempts can be configured. After that number of attempts has been reached, the order should be rejected.

InvalidCreditCardExpirationDateException

Invalid expiration date

Prompt the customer to pass a valid expiration date.

A maximum number of attempts can be configured. After that number of attempts has been reached, the order should be rejected.

InvalidCountryCodeException Country code is incorrect

Prompt the customer to pass a valid country code.

A maximum number of attempts can be configured. After that number of attempts has been reached, the order should be rejected.

PanTooShortException

PAN passed is too short.

Prompt the customer to correct the credit card number.

A maximum number of attempts can be configured. After that number of attempts has been reached, the order should be rejected.

PanTooLongException PAN passed is too long.

Prompt the customer to correct the credit card number.

A maximum number of attempts can be configured. After that number of attempts has been reached, the order should be rejected.

NonNumericDataException

PAN submitted for encryption is not numeric

Prompt the customer to pass a credit card number that contains only numeric values.

A maximum number of attempts can be configured. After that number of attempts has been reached, the order should be rejected.