Format Type

Purpose

There are two basic formats that the viaConex request message can be constructed for submission to the Elavon Host for processing. The messages can be formatted in either a Value-Pair or XML structure.

Value-Pair Request Example

Request=Credit  Card.Sale

Version=4033

HD.Application_ID=HZ9999GC

HD.Terminal_ID=1234567890123456789012

HD.Device_Tag=123456

01.POS_Entry_Capability=02

01.Account_Entry_Mode=01

01.Partial_Auth_Indicator=0

01.Account_Data=400000******0002=1230

01.Transaction_Amount=1000

01.Last_Record_Number=1

10.Postal_ZIP_Code=30328

10.Street_Address=1234 Any Street

Value-Pair Response Example

RD.Device_Tag=123456

02.Response_Code=AA

02.Issuer_Response_Code=00

02.Authorization_Source=2

02.Capture_Code=1

02.Approval_Code=CVI333

02.Authorization_Date=012512

02.Authorization_Time=173451

02.Batch_Number=898

02.Record_Number=2

02.Authorization_Response=APPROVAL

02.Trace_Number=103163

02.Transaction_Reference_Nbr=125223451

80.Amex_Capture_Code=2

80.AVS_Response=A

80.CVV2_Response=

80.PS2000_Data=V112025981291331DD8BG

80.MSDI=1

87.Authorized_Amount=1000

87.Account_Balance_1=1000

87.Account_Balance_2=0

XML Request Example

<?xml version="1.0" encoding="ISO-8859-1"?>

<Request id="Credit Card.Sale">

<Version>4033</Version>

<Block id="HD">

   <Application_ID>HZ9999GC</Application_ID>

   <Terminal_ID>1234567890123456789012</Terminal_ID>

   <Device_Tag>123456</Device_Tag>

</Block>

<Block id="01">

   <POS_Entry_Capability>02</POS_Entry_Capability>

   <Account_Entry_Mode>01</Account_Entry_Mode>

   <Partial_Auth_Indicator>0</Partial_Auth_Indicator>

   <Account_Data>400000******0002=1230</Account_Data>

   <Transaction_Amount>1000</Transaction_Amount>

   <Last_Record_Number>2</Last_Record_Number>

</Block>

<Block id="10">

   <Postal_ZIP_Code>30328</Postal_ZIP_Code>

</Block>

</Request>

XML Response Example

<?xml version="1.0" ?>

<Response>

<Block id="RD">

   <Device_Tag>123456</Device_Tag>

</Block>

<Block id="02">

   <Response_Code>AA</Response_Code>

   <Issuer_Response_Code>00</Issuer_Response_Code>

   <Authorization_Source>2</Authorization_Source>

   <Capture_Code>1</Capture_Code>

   <Approval_Code>CVI334</Approval_Code>

   <Authorization_Date>012512</Authorization_Date>

   <Authorization_Time>173510</Authorization_Time>

   <Batch_Number>898</Batch_Number>

   <Record_Number>3</Record_Number>

   <Authorization_Response>APPROVAL</Authorization_Response>

   <Trace_Number>203162</Trace_Number>

   <Transaction_Reference_Nbr>125223510</Transaction_Reference_Nbr>

</Block>

<Block id="80">

   <Amex_Capture_Code>2</Amex_Capture_Code>

   <AVS_Response>A</AVS_Response>

   <CVV2_Response> </CVV2_Response>

   <PS2000_Data>V112025981310332DD9EG</PS2000_Data>

   <MSDI>1</MSDI>

</Block>

<Block id="87">

   <Authorized_Amount>1000</Authorized_Amount>

   <Account_Balance_1>1000</Account_Balance_1>

   <Account_Balance_2>0</Account_Balance_2>

</Block>

</Response>

error_outline
note

The response types are determined by the inbound request type.  An XML request will return an XML response and a Value-Pair Request will return a Value-Pair response.

The XML examples above have been formatted for human readability and are returned as a continuous stream of data.  Sensitive data in each example was also masked.