RIS Error Codes

The Risk Inquiry Service (RIS) combines data provided by the Device Data Collector (DDC) with the customer order data sent from the merchant to evaluate and score each transaction. The evaluation is sent back to the merchant as a RIS response. One function of the RIS response is to return any warnings or errors that were identified from the RIS post (errors are returned with a MODE=E).

Example of a RIS response error without warnings

    MODE=E ERRO=323 ERROR_0=323 BAD_SITE Field: [SITE],
    Value: [DEFAULT1] ERROR_1=341 BAD_IPAD Field: [IPAD],
    Value: [127.0.0.1234] ERROR_COUNT=2 WARNING_COUNT=0
    

Example of a RIS response error with warnings

    MODE=E ERRO=323 ERROR_0=323 BAD_SITE Field: [SITE],
    Value: [DEFAULT1] ERROR_1=311 BAD_CURR Field: [CURR],
    Value: [US] ERROR_2=341 BAD_IPAD Field: [IPAD],
    Value: [127.0.0.1234] ERROR_COUNT=3 WARNING_0=399 BAD_OPTN Field: [DOB],
    Value: [1980-00-00] WARNING_1=399 BAD_OPTN Field: [GENDER], Value: [K] WARNING_COUNT=2
    

Refer to the RIS Error Codes table below to find error descriptions.

RIS Error Codes

Response Code

Warning/Error Label

Response Code
Description

Suggested Resolution

201

MISSING_VERS

The RIS post is missing the RIS version number.

Sending the RIS version number is built into the SDK, but if you are using the API standalone, the version number must be supplied in the post.
Example:
VERS=0720

202

MISSING_MODE

The mode type for post is missing.

Refer to Risk Inquiry Service (RIS) Modes.

Example: MODE=U

203

MISSING_MERC

The Kount provided six-digit Merchant ID is not in the RIS POST.

 

204

MISSING_SESS

The unique Session ID is not in the RIS POST.

Refer to How to Create a Session ID for the Device Data Collector.

205

MISSING_TRAN

Transaction ID number is not in the RIS POST.

 

211

MISSING_CURR

The currency is not in the RIS POST.

 

212

MISSING_TOTL

The total amount is not in the RIS POST.

 

221

MISSING_EMAL

The email address is not in the RIS POST.

 

222

MISSING_ANID

The caller ID is missing for MODE = P RIS inquiries.

 

223

MISSING_SITE

The website identifier that is created in the AWC is missing.

 

231

MISSING_PTYP

The payment type is missing.

Refer to Accepted Payment Types and Corresponding Codes.

232

MISSING_CARD

The credit card information is missing.

 

233

MISSING_MICR

Missing Magnetic Ink Character Recognition string.

 

234

MISSING_PYPL

The PayPal Payer ID is missing.

 

235

MISSING_PTOK

The payment token is missing.

 

241

MISSING_IPAD

The end user IP address is missing.

 

251

MISSING_MACK

The merchant acknowledgement is missing. Must equal Y or N.

 

261

MISSING_POST

The RIS query submitted to Kount contained no data.

 

271

MISSING_PROD_TYPE

The shopping cart data array attribute for product type is missing.

 

272

MISSING_PROD_ITEM

The shopping cart data array attribute for product items is missing.

 

273

MISSING_PROD_DESC

The shopping cart data array attribute for product description is missing.

 

274

MISSING_PROD_QUANT

The shopping cart data array attribute for product quantity is missing.

 

275

MISSING_PROD_PRICE

The shopping cart data array attribute for product price is missing.

 

301

BAD_VERS

The version of Kount supplied by merchant does not fit the four integer parameter.

 

302

BAD_MODE

The mode type is invalid. Refer to Risk Inquiry Service (RIS) Modes.

Refer to RIS Inquiry Service Modes.

303

BAD_MERC

The six-digit Merchant ID is malformed or incorrect.

Refer to your onboarding emails to make sure you are using the correct 6-digit numeric Merchant ID.

304

BAD_SESS

The unique Session ID is invalid.

Refer to How to Create a Session ID for the Device Data Collector.

305

BAD_TRAN

Transaction ID number is malformed.

 

311

BAD_CURR

The currency is incorrect in the RIS POST.

 

312

BAD_TOTL

The total amount is incorrect. TOTL is the whole numerical amount charged to the customer.

 

321

BAD_EMAL

The email address does not meet required format or is greater than 64 characters in length.

 

322

BAD_ANID

The caller ID is malformed for MODE = P RIS inquiries.

 

323

BAD_SITE

The website identifier that was created in the AWC (DEFAULT is the default website ID) does not match what was created in the AWC.

 

324

BAD_FRMT

The specified format is wrong. Format options are key value pairs: XML, JSON, and YAML.

 

331

BAD_PTYP

The payment type is wrong.

Refer to Refer to Accepted Payment Types and Corresponding Codes.

332

BAD_CARD

The credit card information is malformed or wrong; test cards do not work in the production environment.

 

333

BAD_MICR

Malformed or improper Magnetic Ink Character Recognition string.

 

334

BAD_PYPL

The PayPal Payer ID is malformed or corrupt.

 

335

BAD_GOOG

The Google Checkout Account ID string is malformed or incorrect.

 

336

BAD_BLML

The Bill Me Later account number is malformed or incorrect.

 

337

BAD_PENC

The encryption method specified is wrong.

Refer to Payment Encryption (PENC) Options.

338

BAD_GDMP

The GreenDot payment token is not valid.

 

339

BAD_HASH

When payment = card and enc = KHASH, the PENC (payment encryption) must be 20 characters. If it is not, you will receive a 339.

 

340

BAD_MASK

There are invalid or excessive characters in the PTOK field.

 

341

BAD_IPAD

The IP address is malformed.

 

342

BAD_GIFT

The Gift Card payment token is invalid due to invalid characters, null, or exceeding character length.

 

351

BAD_MACK

Pre-auth – Mode U with Mack should be sending N if no pre-auth, otherwise Y. Blank or malformed (other than N or Y) data will result in 351.

 

362

BAD_CART

There is a discrepancy between the shopping cart key count and the number of items sent in the cart.

 

371

BAD_PROD_TYPE

The shopping cart data array attribute for product type is malformed.

 

372

BAD_PROD_ITEM

The shopping cart data array attribute for product items is malformed.

 

373

BAD_PROD_DESC

The shopping cart data array attribute for product description is malformed.

 

374

BAD_PROD_QUANT

The shopping cart data array attribute for product quantity is malformed.

 

375

BAD_PROD_PRICE

The shopping cart data array attribute for product price is malformed.

 

399

BAD_OPTN

A User Defined Field (UDF) has been mistyped or does not exist in the AWC.

 

401

EXTRA_DATA

RIS keys submitted by merchants are not part of the Kount SDK and cannot be used.

 

404

UNNECESSARY_PTOK

This error occurs if the PTYP equals NONE in the RIS POST but a PTOK is still submitted.

 

413

REQUEST_ENTITY_TOO_ LARGE

The RIS POST sent to Kount exceeds the 4K limit.

 

501

UNAUTH_REQ

API key or certificate does not match production API key or certificate used during submission. MID API key does not match submitted API key.

 

502

UNAUTH_MERC

Invalid Merchant ID is entered.

MID likely disabled as a result of trial ending or payment issues. Contact Customer Service Manager.

601

SYS_ERR

Unspecified system error. Caused when issues are not caught by any other errors. 

Contact your Customer Success Manager.

602

SYS_NOPROCESS

Kount will not process a particular transaction due to the detection of a spam request.

Contact your Customer Success Manager.

701

NO_HDR

No header found with merchantID = [XXXXX], sessionID = [htot2kk5khpamo45f777q455], trans=[122347].

This error occurs when a RIS request goes to the database and there is no data available in the reply. The updated POST has an invalid transaction ID number.

Check all required fields for the updated RIS POST and confirm they are being passed correctly.

If the issue persists, contact your Customer Success Manager.

Missing: When this designation appears, the customer has failed to complete a required field.

Bad: When this designation appears, some data was sent but failed to meet specifications. This could also be explained as malformed data or bad code that did not meet specifications, such as AVS = W instead of AVS = M.

Anomaly – high_errors: When this designation appears, the RIS POST sent to Kount meets one or more of the following criteria:

  • A required POST field is missing
  • The data did not meet specifications
  • The POST contained malformed data

These errors can either be Soft or Hard. Soft errors result in an evaluation by Kount while Hard errors prevent Kount from being able to evaluate a transaction.

Was this article helpful?
0 out of 0 found this helpful