Secure Electronic Payments API

You must always pass 14 parameters to Transact.ProcessCreditCard. This example shows only the required parameters, e.g. UserName. The rest of the parameters must be passed as empty strings, or can contain optional values. For example, in C#: Transact.ProcessCreditCard(“glob9069”, “7597”, ” Reversal “, “”, “”, “”, “”, “”, “”, ” 413624″, “”, “”, “”, “”)

Given this transaction:

We run a Reversal against it, and get this result returned:

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

<Response xmlns=”http://TPISoft.com/SmartPayments/” xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance“><Result>0</Result><RespMSG>Approved</RespMSG><Message>REVERSED</Message><AuthCode>VI2500</AuthCode><PNRef>413625</PNRef><GetCommercialCard>False</GetCommercialCard></Response>

In the above result, the PNRef 413625 is the transaction id assigned to the Reversal itself, as we see here:

Note: ArgoFire does not support the Reversal TransType on all processors. If you run a Reversal against an unsupported processor, you will get this response:

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

<Response xmlns=”http://TPISoft.com/SmartPayments/” xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance“><Result>14</Result><RespMSG>Transaction Type Not Supported In This Version</RespMSG><AuthCode>Transaction_Type_Not_Supported_In_This_Version</AuthCode><PNRef>413707</PNRef><GetCommercialCard>False</GetCommercialCard></Response>