Configuring the Paymentech plug-in

The Paymentech plug-in allows the Payment plug-in controller to communicate directly with the Paymentech gateway using the plug-in. The Paymentech plug-in replaces the WebSphere Commerce Payments using the Paymentech Cassette.

About this task

Follow this procedure to enable the Paymentech plugin with WebSphere Commerce.

Procedure

Follow the directions provided by Paymentech to set up network connection between WebSphere Commerce and the Paymentech gateway.
Configure a merchant for the store.
Schedule Paymentech jobs.

Configure payment methods in the PaymentMethodConfigurations XML file.

For example:

<PaymentMethodConfiguration 
name="CreditCardOnline"
paymentSystemName="Paymentech" 
systemEditable="true"
humanEditable="true"
refundAllowed="true"
minimumAmount="0"
maximumAmount="Unbounded"
priority="MEDIUM"
partiallyConsumable="true"/>

Configure payment rules and payment mappings in the PaymentMappings XML file.

For example:

<Mapping paymentMethod="VISA" 
paymentConfiguration="CreditCardOnline"
paymentActionRule="Early Approval"/>

Configure settings in the RefundMethodConfigurations XML file.

For example:

<RefundMethodConfiguration 
name="CreditCardOnline"
paymentSystemName="Paymentech" />

Configure refund methods in the RefundMappings XML file. For example:

<RefundMapping refundMethod="VISA" refundConfiguration="CreditCardOnline"/>

Configure the PaymentSystemPluginMapping XML file to specify Paymentech.

For example:


<PaymentSystemName name="Paymentech" >
<Mapping paymentConfigurationId="default" pluginName="PaymentechPlugin" >
<!-- ====================================================================================================
(Optional) 
<name> The name of the plug-in property that should be used in transactions for this particular payment method. 
A plug-in can require additional parameters, or a payment configuration can have unique needs. 
<value> The value of the named plug-in property.
==================================================================================================== -->
<Property name="SupportsOnlineTransaction" value="yes"/>
<Keyword name="cc_cvc" mask ="-" plain="0" removeAfterApproval ="true"/>
<Keyword name="cc_nameoncard" mask ="*" plain="0" removeAfterApproval ="true"/>
<Keyword name="account" mask ="*" plain="-5" searchable="true"/>
</Mapping>
</PaymentSystemName>

Note: By default, there is a configuration where the PaymentSystemName is "Paymentech" but pluginName is "WCPaymentsPlugin" such as:

<PaymentSystemName name="Paymentech" >
<Mapping paymentConfigurationId="default" pluginName="WCPaymentsPlugin" >

Delete this configuration if a new Paymentech Plug-in with the same name is added. If you are using the WCPaymentsPlugin, refer to the topic Migrating from the Paymentech cassette to Paymentech plugin.

Set Paymentech parameters.
1. Open the file WC_eardir/xml/config/payments/ppc/plugins/PaymentechPlugin/PluginDeployment.xml
2. Set the minBatchSize.
  For example:
```
<PluginProperty name="minBatchSize" value="1"/>
```
  minBatchSize represents the minimum number of transactions in a batch. When the scheduler processes the job, if the number of deposit or credit transactions is less than the minBatchSize, the scheduler will not run the job. If the number of deposit or credit transactions is equal to or more than the minBatchSize, then a batch is created and processed.
3. Set the RFRDelayTime, for example:
```
<PluginProperty name="RFRDelayTime" value="1"/>
```
  RFRDelayTime is the delay time between the batch request sent to Paymentech and the RFR (Request For Response) sent to Paymentech to receive a batch response. The recommended value is 15.
4. Change the IP address to connect to the Paymentech gateway.
  For example:
```
<PluginProperty name="onlineHost" value="198.147.142.176"/>
 <PluginProperty name="onlinePort" value="8526"/>
 <PluginProperty name="batchHost" value="198.147.142.176"/>
 <PluginProperty name="batchPort" value="8527"/>
 <PluginProperty name="doDNSLookup" value="false"/>
```
Create a partial ZIP file that contains the changed files using the same structure as the EAR file. For example:
- xml/config/payments/edp/groups/default/PaymentMappings.xml
- xml/config/payments/edp/groups/default/PaymentMethodConfigurations.xml
- xml/config/payments/edp/groups/default/RefundMappings.xml
- xml/config/payments/edp/groups/default/RefundMethodConfigurations.xml
- xml/config/payments/ppc/plugins/PaymentSystemPluginMapping.xml
- xml/config/payments/edp/groups/default/PaymentMethodConfigurations.xml
- xml/config/payments/ppc/plugins/PaymentechPlugin/PluginDeployment.xml
Package your assets as a partial application and deploy them.