Platform Error Messages

Transcription

1 DSI Server Specific (TCP/IP) Code Description Password Verified Queue Full Password Failed Disconnecting System Going Offline Disconnecting Socket Refused Max Connections Duplicate Serial Number Detected Password Failed (Client / Server) Password failed (Challenge / Response) Internal Server Error Call Provider DSIClientX Specific (TCP/IP) Code Description Code Description General Failure TStream Type Missing Invalid Command Format Could Not Encrypt Response- Call Provider Insufficient Fields Unknown Error Global API Not Initialized Invalid Transaction Type Timeout on Response Invalid Operator ID Empty Command String Invalid Memo In Process with server Invalid Account Number Socket Error sending request Invalid Expiration Date Socket already open or in use Invalid Authorization Code Socket Creation Failed Invalid Authorization Code Socket Connection Failed Invalid Authorization Amount Connection Lost Invalid Cash Back Amount TCP/IP Failed to Initialize Invalid Gratuity Amount Control failed to find branded serial (password lookup failed) Invalid Purchase Amount Time Out waiting for server response Invalid Magnetic Stripe Data Connect Cancelled Invalid PIN Block Data bit CryptoAPI failed Invalid Derived Key Data Threaded Auth Started Expect Response Invalid State Code Page 1 of 5

2 Code Description Code Description Event (Note it is possible the event could fire before the function returns.) Failed to start Event Thread Invalid Date of Birth XML Parse Error Invalid Check Type All Connections Failed Invalid Routing Number Server Login Failed Invalid TranCode Initialize Failed Invalid Merchant ID Global Response Length Error (Too Short) Invalid TStream Type Unable to Parse Response from Global (Indistinguishable) Invalid Batch Number Global String Error Invalid Batch Item Count Weak Encryption Request Not Supported Invalid MICR Input Type Clear Text Request Not Supported Invalid Driver s License Unrecognized Request Format Invalid Sequence Number Error Occurred While Decrypting Request Invalid Pass Data Invalid Check Digit Invalid Card Type Merchant ID Missing Page 2 of 5

3 E2E Error Responses There are four categories of E2E error responses: Connectivity, Merchant Check, Invalid Fields and Corrupted Data errors. 1. Connectivity Errors In the rare event that Mercury s encryption service is unavailable, the following error will be returned: <TextResponse>Decryption Service Unavailable.</TextResponse> 2. Mercury s E2E Merchant Check Mismatch Error If the merchant is not setup for E2E but the E2E encryption data elements (EncryptedFormat, AccountSource, EncryptedBlock, EncryptedKey) are sent in the request, then the transaction will return Merchant setting does not accept Encrypted data. If merchant is setup for E2E but the request does not contain the E2E Encryption elements, then the transaction will return Merchant setting requires Encrypted data. <DSIReturnCode>004115</DSIReturnCode> <TextResponse>Merchant setting requires Encrypted data</textresponse> 3. E2E Invalid Field Errors If one of the E2E Encryption elements is missing in the transaction request, an Invalid Field will be returned qualified by the missing element. <DSIReturnCode>100254</DSIReturnCode> <TextResponse>Invalid Field - Encrypted Block</TextResponse> 4. Decryption Service Unavailable errors: Corrupt, Malformed or Incorrect Data In the event that one of the E2E encryption data elements contains corrupted, malformed or in any way incorrect data, Mercury s encryption service will return a text response containing Decryption Service Unavailable followed by the field detected to contain the failed data. These failure messages vary and are dynamically generated based on the reason for the failure: <DSIXReturnCode>004116</DSIXReturnCode> <TextResponse>Decryption Service Unavailable-200 Response with Status: Failure Message:Invalid EncryptedBlock</TextResponse> Note Merchant setting, Invalid Field and some Decryption Service Unavailable error messages described above are typically determined by Mercury s servers prior to decryption. If an encrypted transaction request passes this initial set of checks it is passed to Mercury s decryption server. There is another set of error messages at this stage of the decryption process: In the event that an incorrect EncryptedKey is sent, or the EncryptedBlock is not decryptable, in the wrong format, or if the decrypted data is invalid, the following error format is used. Note the differences in the failure message for Failed to decrypt, Encrypted block invalid, or Decrypted data invalid : Error # Decryption Service Unavailable Response With Status:Failure Message:Failed to decrypt Error # Decryption Service Unavailable Response With Status:Failure Message:Encrypted block invalid Error # Decryption Service Unavailable Response With Status:Failure Message:Decrypted data invalid Page 3 of 5

4 MToken Errors Responses There are four categories of MToken error responses: Connectivity, Merchant Check, Invalid Fields and Corrupted Data errors. 1. Connectivity Errors A connection failure to the tokenization server will return an Unavailable response. <DSIReturnCode>004118</DSIReturnCode> <TextResponse> Decryption Service Unavailable. - Status Code Not </TextResponse> Figure 1. Connectivity Errors, Service Unavailable <DSIReturnCode>004119</DSIReturnCode> <TextResponse>Token Service Unavailable Response With Status:Error Message:Error generating token</textresponse> Figure 2. Connectivity Errors, Token Service Unavailable 2. Merchant Table Token Setup Error For a tokenization request to be validated, Mercury merchants must send both the required tokenization data elements AND be set up in the Mercury merchant tokenization tables. Only the credit TranCodes listed above in Figure 40 are checked. Debit, EBT, Gift/PrePaid and ADMIN transactions are ignored. If a merchant is setup for tokenization AND both RecordNo and Frequency elements are in the request, then Mercury builds the token record. The token is sent back in the RecordNo element. In the event of a decline/error response, no token is generated. Transactions will decline if: a. RecordNo and Frequency elements are in the request, but the merchant is not setup for tokenization: <DSIReturnCode>004117</DSIReturnCode> <TextResponse>Merchant Setting Does Not Accept RecordNo and Frequency.</TextResponse> <UserTraceData></UserTraceData> b. If the merchant is setup for tokenization in the merchant tables, but the request does not contain RecordNo and Frequency elements: <TextResponse>Merchant Setting Requires RecordNo and Frequency.</TextResponse> Page 4 of 5

5 3. Invalid field or missing field errors a. RecordNo is missing in the data element field. This error returns the Merchant Setting Requires RecordNo message because the absence of a RecordNo is validated by the Merchant Table settings. <TextResponse>Merchant Setting Requires RecordNo.</TextResponse> b. Frequency is missing in the data element field. <DSIReturnCode>100256</DSIReturnCode> <TextResponse>Invalid Field-Frequency</TextResponse> 4. Corrupt RecordNo a. There is corrupted data in the RecordNo element, there is a mismatch in token frequency, or the token has expired: <DSIReturnCode>004119</DSIReturnCode> <TextResponse>Token Service Unavailable. 200 Response With Status:Failure Message:Parse token failure</textresponse> b. Corrupt Frequency error: <DSIReturnCode>100256</DSIReturnCode> <TextResponse>Invalid Field-Frequency</TextResponse> <UserTraceData></UserTraceData> Page 5 of 5