Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Arkos

can support

Payments Solution supports devices that are either part of the payment terminal (

integrated devices)

eg. barcode scanner)

or outside of the payment terminal (

peripheral devices

eg. check reader).

The payment terminal may

 The payments terminal can allow a sales system to use

its devices

: the

. The services are currently supported

via the

based on nexo Retailer V3.0

specification.

Check Reading Command

Message

specifications.




Panel

In this article:

Table of Contents
maxLevel3
printablefalse


Check Data Reading

This command is inititated by the sales system to read check data.

Request

<?xml version="1.0"?>
<SaleToPOIRequest>
    <MessageHeader MessageClass="Device" MessageCategory="Input" MessageType="Request" DeviceID="001" SaleID="SalesA" POIID="87654321"/>
    <InputRequest>
        <InputData Device="CashierInput" InfoQualify="Document" InputCommand="TextString"/>
    </InputRequest>
</SaleToPOIRequest>

Message

Response

<?xml version="1.0"?>
<SaleToPOIRequest>
    <MessageHeader MessageClass="Device" MessageCategory="Input" MessageType="Response" DeviceID="001" SaleID="SalesA" POIID="87654321"/>
    <InputResponse>
        <InputResult Device="CashierInput" InfoQualify="Document" >
               <Response Result="Success"/>
               <Input InputCommand="TextString">
                    <TextInput>CheckData<TextInput/>
              </Input>
        </InputResult>
    </InputResponse>
</SaleToPOIRequest>

Error Cases

When the request is successfully processed

,

:

  • the response message gets the value “Success” in the data element Response.Result,
  • and the check data in CMC-7 format in the data element TextInput.


In case of error, the response message gets the value

“Failure” in

“Failure” in the data element Response.Result.

 These

<Response Result="Failure" ErrorCondition="DeviceOut"/>


These errors are enumerated below, listed by value of the ErrorCondition data element.


DeviceOut

The payment terminal cannot process the request because of a temporary error on the check reader device.

Cancel

The payment terminal cannot process the request because of a timeout from the check reader device or the check data are invalid.

panel

In this article:

Table of Contents
maxLevel3
printablefalse



Check Writing Command

Message

Check Data Writing

This command is inititated by the sales system to write check data.

Request

SalesBA

<?xml version="1.0"?>
<SaleToPOIRequest>
    <MessageHeader MessageClass="Device" MessageCategory="Print" MessageType="Request" DeviceID="002" SaleID="

SalesA" POIID="87654321"/>
    <PrintRequest>
       <PrintOutput DocumentQualifier="Document" ResponseMode="PrintEnd">
          <OutputContent OutputFormat="Text">
             <OutputText>
                <Text>TextToPrint</Text>
             </OutputText>
          </OutputContent>
       </PrintOutput>
    </PrintRequest>
</SaleToPOIRequest>

Message

Response

ArkosSales
<?xml version="1.0"?>
<SaleToPOIRequest>
    <MessageHeader MessageClass="Device" MessageCategory="Print" MessageType="Response" DeviceID="002" SaleID="
SalesA" POIID="87654321"/>
    <PrintResponse  DocumentQualifier="Document"  >
       <Response Result="Success"/>
    </PrintRequest>
</SaleToPOIRequest>

Error Cases

When the request is successfully processed

,

:

  • the response message gets the value “Success” in the data element Response.Result.

In case of error, the response message gets the value

“Failure” in

“Failure” in the data element Response.Result.

<Response Result="Failure" ErrorCondition="DeviceOut"/>


 These errors are enumerated below, listed by value of the ErrorCondition data element.

DeviceOut

The payment terminal cannot process the request because of a temporary error on the check reader device.

Cancel

The payment terminal cannot process the request because of a timeout from the check reader device or the data could not be printed on the check.