Response

Description

<xmp>
	<response>
		<Message>Error</Message>
		<ResultCode>2</ResultCode>
		<RespMSG>Terminal not connected to SPIn Proxy server</RespMSG>
	</response>
</xmp>

Terminal is not connected to SPIn Proxy server. It may be temporary not connected while terminal is reconnecting ack usually it takes a few seconds or terminal may be offline and turned off.

Check that the terminal is connected to network and repeat the request one more time

<xmp>
	<response>
		<Message>Error</Message>
		<ResultCode>2</ResultCode>
		<RespMSG>Terminal in use, please wait</RespMSG>
		<StatusCode>2008</StatusCode>
	</response>
</xmp>

The requested terminal is in use by a previous request. SPIn Proxy waits for terminal response to provide it to a register.

Before to send the next request wait for 120 seconds from original request.

<xmp>
	<response>
		<Message>Error</Message>
		<ResultCode>2</ResultCode>
		<RespMSG>busy</RespMSG>
	</response>
	<error>busy
		<code>2</code>
	</error>
</xmp>

Service or terminals is busy processing previous SPIn request.

Repeat request later.

<xmp>
	<response>
		<Message>Error</Message>
		<ResultCode>2</ResultCode>
		<RespMSG>The operation has timed out</RespMSG>
	</response>
</xmp>

The current operation was timed out, try again. A Default timeout is 120 seconds. Reister gets this error if a terminal does not provide a response back during 120 seconds after requets. It may happen in two cases:

  • terminal still handle a transaction. Like user looking for a card, entiring pin-code, adding signature, etc.

  • terminal lost connection during a transaction

After such response need to do Status request to check if transaciton was operated.

<xmp>
	<response>
		<Message>Error</Message>
		<ResultCode>2</ResultCode>
		<RespMSG>Terminal was disconnected</RespMSG>
	</response>
	<error>Terminal was disconnected
		<code>2</code>
	</error>
</xmp>

During a transaction time a connection to terminal was closed in case of detected network issues or used application was terminated(closed).

After such response need to do Status request to check if transaciton was operated.

<xmp>
	<response>
		<Message>Error</Message>
		<ResultCode>503</ResultCode>
		<RespMSG>Service busy</RespMSG>
	</response>
	<error>Service busy
		<code>503</code>
	</error>
</xmp>

This error comes from terminal level and terminal reports that it cannot get a new request. It happens in two cases:

  1. The terminal in SPIn bypass mode. Turn it to the SPIn mode and send a request one more time.

  2. The requested terminal operates previuos transaction (prints receipt, uploads data to DeNovo, waits for signature, waits for pin-code, communicates to the host, etc).
    If the terminal not in SPIN bypass mode do Status request in a few seconds to check if terminal completed previous transaction.

<xmp>
	<response>
		<Message>Error</Message>
		<ResultCode>2</ResultCode>
		<RespMSG>reconnected</RespMSG>
	</response>
	<error>reconnected
		<code>2</code>
	</error>
</xmp>

While processing SPIN request device faced internet connection problem and restored connection.

After such response need to do Status request to check if transaciton was operated.

<xmp>
	<response>
		<Message>Error</Message>
		<ResultCode>2</ResultCode>
		<RespMSG>Route not found</RespMSG>
	</response>
</xmp>

Terminal does not have any paired connection. Create it on DeNovo and try again.

<xmp>
	<response>
		<Message>Error</Message>
		<ResultCode>2</ResultCode>
		<RespMSG>Register not found</RespMSG>
	</response>
</xmp>

Terminal was not found by its RegisterId or TPN. Check that you use correct RegisterID or TPN in the request and try again

<xmp>
	<response>
		<Message>Error</Message>
		<ResultCode>0</ResultCode>
		<RespMSG>Wrong payment or transaction type</RespMSG>
	</response>
	<error>Wrong payment or transaction type
		<code>0</code>
	</error>
</xmp>

The transaction request uses incorrect or inapplicable payment or transaction type

<xmp>
	<response>
		<Message>Error</Message>
		<ResultCode>2</ResultCode>
		<RespMSG>Not pars request</RespMSG>
	</response>
</xmp>

SPIN Proxy cannot pars incoming request, check their body and try again

<xmp>
	<response>
		<Message>Error</Message>
		<ResultCode>2</ResultCode>
		<RespMSG>Active route not found</RespMSG>
	</response>
</xmp>

A terminal does not have active Paired Connection. The Connection is created, but was disabled.

Activate it and try again.

It may happen:

  • If SPIN Proxy or DeNovo services were canceled

  • If two devices use the same TPN. SPIn proxy block the connection becasue cannot send one request on a few devices.

<xmp>
	<response>
		<Message>Error</Message>
		<ResultCode>0</ResultCode>
		<RespMSG>Request format error</RespMSG>
	</response>
	<error>Request format error
		<code>0</code>
	</error>
</xmp>

The SPIN request uses an unsupported markup language or the request is malformed

<xmp>
	<response>
		<Message>Error</Message>
		<ResultCode>0</ResultCode>
		<RespMSG>Authentication failed</RespMSG>
	</response>
	<error>Authentication failed
		<code>0</code>
	</error>
</xmp>

Authentication failed (auth key mismatch)

Check Auth key in request that it matches to AuthKey on DeNovo for this terminal.

The terminal may not download the last settings with configuration for SPIn Proxy for this save paired connect one more time on DeNovo and do partial update on a terminal.

<xmp>
  <response>
    <Message>Error</Message>
    <ResultCode>2</ResultCode>
    <RespMSG>Communication error. Send request one more time</RespMSG>
    <StatusCode>2010</StatusCode>
  </response>
</xmp>

Something unpredicted happened, try to send request one more time