Managing errors (JS client)

This page describes the processing of integration errors.

If you would like to customize how you handle errors that occur when a transaction is rejected, see the following article:

KR.onError()

How are errors displayed?

For JavaScript form, errors are automatically displayed in the kr-form-error div:

    <!-- error zone -->
    <div class="kr-form-error"></div>

    <!-- error zone -->
    <div class="kr-form-error"></div>

All you need to do is add it to your code.

Managing errors manually

To handle errors manually, simply intercept the default error message and customize it. In the following example, the custom error message will be placed in the customerror class div:

          <script type="text/javascript">
    $(document).ready(function() {
          KR.onError( function(event) {
            var code = event.errorCode;
            var message = event.errorMessage;
            var myMessage = code + ": " + message;

            try {
              /* if client answer exists, a refused transaction has been created */
              /* it's not always the case. For example, if the form is empty,    */
              /* error is raised before transaction creation                     */

JS error codes

The REST API has many error codes described here:

• ACQ
• AUTH
• INT
• PSP

The error codes that start with CLIENT_ correspond to errors occurring in the Buyer's browser. They occur before the payment data is sent to our servers. This concerns, for example, local form data validation errors or JavaScript client integration errors.

Warning codes

The error codes comprised between CLIENT_700 and CLIENT_799 are warning messages. They help you integrate the JavaScript client:

Error code details

CLIENT_004

The public key defined in kr-public-key is not valid, it must have the following format: [NUMBER]:[STRING]

for example: 69876357:testpublickey_DEMOPUBLICKEY95me92597fd28tGD4r5

For more information, go to: Retrieving my keys.

CLIENT_100

The formToken that you have defined in kr-form-token is invalid. For more information on creating a formToken, go to: Integration guide.

CLIENT_101

Transaction abandoned by the buyer. This error occurs, for example, when the Buyer closes the 3D Secure pop-in before authenticating him/herself.

If the Buyer does not make another attempt, a rejected transaction is automatically created when the formToken expires.

CLIENT_300

When several form fields are invalid, a general CLIENT_300 error is returned. The detailed list of all detected errors will be presented in the children field:

{
    "errorCode": "CLIENT_300",
    "errorMessage": "Invalid form data",
    "children": [{
        "errorCode": "CLIENT_301",
        "errorMessage": "Invalid card number",
        "field": "pan",
        (...)
    }, {
        "errorCode": "CLIENT_302",
        "errorMessage": "Invalid expiry date",
        "field": "expiryDate",
        (...)
    }, {
        "errorCode": "CLIENT_303",
        "errorMessage": "Invalid security code",
        "field": "securityCode",
        (...)
    }],
    "detailedErrorCode": null,
    "detailedErrorMessage": null,
    (...)
}

CLIENT_301

The kr-pan field (card number) of the payment form is invalid.

CLIENT_302

The kr-expiry field (expiry date) of the payment form is invalid.

CLIENT_303

The kr-security-code field (security number or CVV) of the payment form is invalid.

CLIENT_304

An additional field declared as mandatory is empty. For more information, go to: Custom form fields.

CLIENT_305

Le formToken n'existe pas ou n'est pas conforme. Pour plus de détails, rendez-vous ici : undefined.

CLIENT_500

No payment form buttons have been found in the HTML code. Check if the required tags are present, or if there are no syntax errors.

CLIENT_501

The public key is not defined in kr-public-key.

CLIENT_502

The application has detected that the Buyer returned to the payment page using the return button in their Internet browser. The payment form has been locked.

Note that this information can be detected only in some browsers.

CLIENT_505

Le thèmematerialn'est pas supporté par le formulairesmartForm.
Il fautimpérativementchanger et choisir entre le thèmenéonou le thèmeclassic. Voir :"Themes".

CLIENT_508

Make sure you have an active card payment contract that is associated with your shop.

CLIENT_704

An additional field uses icons with the Awesome font but the library has not loaded. For more information, go to: Custom form fields.

CLIENT_705

The <meta> tag, via the "viewport" directive tells the browser how to control the dimensions and scale of the page to be displayed. It is recommended to use it on all HTML5 pages.

CLIENT_997

The formToken has been created via a gateway different from the one where the JavaScript client has been downloaded. The URL of the call to the REST Web Service must be the same as the one of the JavaScript client.

CLIENT_998

The payment form uses a demo formToken that does not allow to interact with the server. Use a valid formToken: Charge/CreatePayment.

CLIENT_999

Unknown error, please contact tech support and give them the following information:

• Shop number
• URL of the form
• Name and version of the browser
• Type and version of the operating system
• Device used (iPhone 6S, PC, iPad Pro, etc.)
• Date and time of the error.