Error Handling for Decryptx Parser

Error Response Handling

The Decryptx Parser's error response object will always contain a success property that is set to false. It will also contain a human readable errMessage and a machine friendly errCode. If a reference value is included in the API request, it will be included in the response object. Some error responses will include a messageId which can be used to view the decryption record on the P2PEManager. API calls that fail validation are not recorded on the P2PE Manager and will not include a messageId.

{
    "success"   : false,
    "errCode"   : 2800,
    "errMessage": "PAN not found in decrypted data",
    "reference" : "myref",
    "messageId" : "1201804091311071001318556"
}

Sample 2800 "PAN not found in decrypted data" error response.

Error Categories

The following table categorises the errCodes ranges that can be returned from /api/decrypt/parser API call.

Specific Error Messages

The following tables outline the error codes, their descriptions, and the steps required to generate the error condition. Where applicable the table will also contain a sample body for a /api/decrypt/parser REST request.

Internal server error

API constrain violations

API constrain violations

Device specific errors (Generic Devices)

Device specific errors (IDTECH Devices)

Device specific errors (Ingenico RA1 Devices)

Device specific errors (Ingenico RBA Devices)

Device specific errors (Miura Devices)

Device specific errors (Infinite Peripherals Prima Devices)

Device specific errors (Verifone Devices)

Device specific errors (WisePad Devices)

Device specific errors (WisePad 2 Devices)

KSN errors

Decryption errors

Decryption errors