This example illustrates the new command ADJUSTMENT that can modify an original Sale transaction specific to tip adjustment. This is applicable to all restaurant supported processors. This sample starts with an original sale amount with no tip added in the Ext Data field using HTTP POST.

Response
<?xml version=”1.0″ encoding=”utf-8″ ?>

– <Response xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns=”ArgoFire”>

<Result>0</Result> <RespMSG>Approved</RespMSG> <Message>NO MATCH</Message> <AuthCode>TAS770</AuthCode> <PNRef>27722</PNRef> <HostCode>704623500829</HostCode> <GetAVSResult>N</GetAVSResult> <GetAVSResultTXT>No Match</GetAVSResultTXT> <GetStreetMatchTXT>No Match</GetStreetMatchTXT> <GetZipMatchTXT>No Match</GetZipMatchTXT> <GetCommercialCard>False</GetCommercialCard> <ExtData>CardType=MASTERCARD</ExtData>

</Response>

 

To add a tip to this original Sale transaction, the command ADJUSTMENT is used along with the username,login, PNREF of the original sale and tip amount in the extended data field as shown below. Currently only the tip amount is adjustable. Please observe the screenshot below there is no need to resend all the credit card information data to perform a tip adjustment.

Response
<?xml version=”1.0″ encoding=”utf-8″ ?>

– <Response xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns=”ArgoFire”>

<blockquote> <Result>0</Result> <RespMSG>Approved</RespMSG> <Message>APPROVAL</Message> <PNRef>27723</PNRef> <GetCommercialCard>False</GetCommercialCard> </Response>