Payment Engine Merchant Configuration and Setup
The main file for merchant account configuration in the new payment engine
is the Merchants.xml file. This file holds one or more merchant
account configurations. The new payment engine supports the VitalPS
VirtualNet, Verisign Payflow Pro, and Cygnus CEPay gateways.
Each gateway requires its own type of merchant configuration.
First, here are sample configurations for each:
- VitalNet
<![CDATA[
<Merchant id="vital" type="test"
class="com.hteinc.payment.domain.vitalnet.HTEVitalNetMerchantConfig"
name="Test Name"
city="Lake Mary"
state="FL"
zip="55555"
phone="555-5555555"
merchant="999999999911"
store="0011"
terminal="5999"
locationNum="00001"
chain="111111"
agent="000000"
acquirerBIN="999995"
SIC_MCC="5999"
terminalID="70000001"
currency="840"
country="840"
timezone="705">
<TestTender accountNumber="6011111111111117"/>
<TestTender accountNumber="4012000010000"/>
<TestTender accountNumber="40120000100001"/>
<ServiceAccess uid="qhte" pwd="qhte"/>
</Merchant>
]]>
- Verisign
<![CDATA[
<Merchant id="verisign" type="test"
class="com.hteinc.payment.domain.verisign.HTEVerisignMerchantConfig"
partner="verisign"
vendor=""
uid="click2gov"
pwd="yap2g!">
<TestTender accountNumber="6011111111111117"/>
<TestTender accountNumber="4111111111111111"/>
<TestTender accountNumber="4012000010000"/>
<ServiceAccess uid="qhte" pwd="qhte"/>
</Merchant>
]]>
- Cygnus
<![CDATA[
<Merchant id="cygnus" type="test"
class="com.hteinc.payment.domain.cygnus.HTECygnusMerchantConfig"
merchant="888000000359"
url="http://test.ceiris.com/XML/servlet/hte_cepay">
<TestTender accountNumber="6011111111111117"/>
<TestTender accountNumber="4012000010000"/>
<TestTender accountNumber="40120000100001"/>
<ServiceAccess uid="qhte" pwd="qhte"/>
</Merchant>
]]>
Note the above samples pertain to test merchant configurations. For examples
of live configurations, click here.
Each <Merchant> configuration has an id.
The id is used to uniquely identify each
merchant configuration. The id must be unique in each
<Merchant> configuration in the file.
Each <Merchant> configuration also has a
type. There are only two valid values: live and test. If the
type is test, then only credit card numbers listed
as a <TestTender> under that <Merchant>
will be processed by the engine. For example, in the samples above only the
credit card numbers 6011111111111117, 4012000010000, and 40120000100001 will
be processed. All other cards will be ignored. The purpose of this is to
prevent a client from accidentally going live with a test configuration.
When the web application connects to the payment engine and makes a request,
it passes the id for the <Merchant> configuration
that should be used to process the request. Therefore, the web application must
be configured with an id to pass. This is done in the
hte.cfg located in
\bea\c2gdomain\applications\Click2GovXX\cfg. The entry in the
hte.cfg is named PaymentInterface.MerchantId. The
entry must match the PaymentInterface.MerchantId
PaymentInterface.MerchantUid
PaymentInterface.MerchantPwd
LIVE CONFIG
- VitalNet
<![CDATA[
<Merchant id="vital" type="live"
class="com.hteinc.payment.domain.vitalnet.HTEVitalNetMerchantConfig"
name="Test Name"
city="Lake Mary"
state="FL"
zip="55555"
phone="555-5555555"
merchant="999999999911"
store="0011"
terminal="5999"
locationNum="00001"
chain="111111"
agent="000000"
acquirerBIN="999995"
SIC_MCC="5999"
terminalID="70000001"
currency="840"
country="840"
timezone="705">
<ServiceAccess uid="qhte" pwd="qhte"/>
</Merchant>
]]>
- Verisign
<![CDATA[
<Merchant id="verisign" type="live"
class="com.hteinc.payment.domain.verisign.HTEVerisignMerchantConfig"
partner="verisign"
vendor=""
uid="click2gov"
pwd="yap2g!">
<ServiceAccess uid="qhte" pwd="qhte"/>
</Merchant>
]]>
- Cygnus
<![CDATA[
<Merchant id="cygnus" type="live"
class="com.hteinc.payment.domain.cygnus.HTECygnusMerchantConfig"
merchant="888000000359"
url="http://test.ceiris.com/XML/servlet/hte_cepay">
<ServiceAccess uid="qhte" pwd="qhte"/>
</Merchant>
]]>