MToken Error Messages

Document created by matthew.milner on May 10, 2016Last modified by Chris Jennings on Jun 1, 2016
Version 2Show Document
  • View in full screen mode

MToken Errors Responses

 

There are four categories of MToken error responses: Connectivity, Merchant Check, Invalid Fields and Corrupted Data errors.

 

Connectivity Errors 

A connection failure to the tokenization server will return an “Unavailable” response.

 

The following response occurs if the Decryption service is unavailable:

<CmdResponse> 
<ResponseOrigin>Server</ResponseOrigin> 
<DSIReturnCode>004118</DSIReturnCode> 
<CmdStatus>Error</CmdStatus> 
<TextResponse> Decryption Service Unavailable. - Status Code Not 200 - 503</TextResponse> 

 

If the Token service is unavailable, the following response occurs:

<CmdResponse> 
<ResponseOrigin>Server</ResponseOrigin> 
<DSIReturnCode>004119</DSIReturnCode> 
<CmdStatus>Error</CmdStatus> 
<TextResponse>Token Service Unavailable.- 200 Response With Status:Error Message:Error generating token</TextResponse> 

 

Merchant Table Token Setup Error

For a tokenization request to be validated, merchants must send both the required tokenization data elements AND be set up in the merchant tokenization tables.  Only the credit TranCodes listed above are checked.  Debit, EBT, Gift/PrePaid and ADMIN transactions are ignored.

 

Merchant Token Setup Errors

If a merchant is setup for tokenization AND both RecordNo and Frequency elements are in the request, then MercuryPay 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:

a. RecordNo and Frequency elements are in the request, but the merchant is not setup for tokenization:  
<CmdResponse> 
<ResponseOrigin>Server</ResponseOrigin> 
<DSIReturnCode>004117</DSIReturnCode> 
<CmdStatus>Error</CmdStatus> 
<TextResponse>Merchant Setting Does Not Accept RecordNo and Frequency.</TextResponse> 
<UserTraceData></UserTraceData> 
</CmdResponse>

 

b. If the merchant is setup for tokenization in the merchant tables, but the request does not contain RecordNo and Frequency elements:

<CmdResponse> 
<ResponseOrigin>Server</ResponseOrigin> 
<DSIReturnCode>004116</DSIReturnCode> 
<CmdStatus>Error</CmdStatus> 
<TextResponse>Merchant Setting Requires RecordNo and Frequency.</TextResponse> 
</CmdResponse> 

 

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.

 

<CmdResponse> 
<ResponseOrigin>Server</ResponseOrigin> 
<DSIReturnCode>004116</DSIReturnCode> 
<CmdStatus>Error</CmdStatus> 
<TextResponse>Merchant Setting Requires RecordNo.</TextResponse> 

 

b. Frequency is missing in the data element field.

  <CmdResponse> 
<ResponseOrigin>Server</ResponseOrigin> 
<DSIReturnCode>100256</DSIReturnCode> 
<CmdStatus>Error</CmdStatus> 
<TextResponse>Invalid Field-Frequency</TextResponse> 

 

Corrupt RecordNo

a. There is corrupted data in the RecordNo element, there is a mismatch in token frequency, or the token has expired:

<CmdResponse> 
<ResponseOrigin>Server</ResponseOrigin> 
<DSIReturnCode>004119</DSIReturnCode> 
<CmdStatus>Error</CmdStatus> 
<TextResponse>Token Service Unavailable. – 200 Response With Status:Failure Message:Parse token failure</TextResponse> 

 

b. Corrupt Frequency error:

 <CmdResponse> 
<ResponseOrigin>Server</ResponseOrigin> 
<DSIReturnCode>100256</DSIReturnCode> 
<CmdStatus>Error</CmdStatus> 
 <TextResponse>Invalid Field-Frequency</TextResponse> 
<UserTraceData></UserTraceData> 
</CmdResponse> 

Attachments

    Outcomes