PAS Releases

The SAP Adapter (PAS) is the adapter that connects SAP to the XiPay and XiSecure platforms.

IMPORTANT NOTE: This is a required update. You must update PAS to version 2.11.2 to align with the Worldpay WAF Akamai URLs.
PAS version 2.11.2 is RHEL only.

New Features

Known Issues

Get Transaction Function in PAS is currently not working. This capability is for custom workflows. Please contact Paymetric Support if you use this function.

Problems Addressed

N/A

Compatibility and Requirements

This section highlights the basic compatibility and minimum requirements for this release.

Compatible Operating Systems

  • Red Hat Enterprise Linux (RHEL) 8 (32- and 64-bit)

  • Windows Server 2019 (64-bit)

Additional Windows Server Requirements

  • Microsoft .NET Framework 4.7.2 or higher

  • Visual C++ Runtime 2015-2019 (x86)

General Requirements

  • 1 GB Ram

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging

  • TLS Port 443 and hostnames should be open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment (obtain hostnames from your Implementation Consultant)

  • Deployment:

    • A single instance of PAS can support multiple SAP instances

    • Paymetric best practice is to have one instance of PAS for PROD and a separate instance for non-PROD environments

PCMA Compatibility

  • Backwards compatible with prior PCMA ECC and S/4HANA versions

XiSecure SAP IK Compatibility

  • Backwards compatible with prior XiSecure SAP IK ECC and S/4HANA versions

Install and Configuration Notes

New Installation

New Install Prerequisites:

BEFORE beginning installation, ensure you have met the following prerequisites:

  • Dedicated machine identified on which to install PAS with a User Account that has Administrator rights to the system for Windows

  • 1 GB of RAM

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging

  • TLS Port 443 and IP Address Range 65.163.245.65 - 65.163.245.94 and open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment to test TLS 1.2 connection

  • XiPay Web Service Account (WSA) username assigned by Paymetric and QA password assigned by Paymetric (Merchant can change QA password), PROD password set by the Merchant

  • XiPay Web Service URL for the environment you are configuring

  • XiSecure Web Service URL for the environment you are configuring

  • Signed client certificate (*.pem) file from Paymetric SaaS Operations for configuring XiSecure in PAS. The file is saved on the PAS machine and you know the file path and file name.

  • Private key file and password you generated when creating the CSR for XiSecure.

  • Download and install the Microsoft Redistributable Packages defined in the Compatibility and Requirements section For Windows Machines.

New Install Release-Specific Instructions:

There are no installation notes specific to this release for new installs. Detailed instructions for installation and configuration are included in the PAS Setup Guide.

Upgrade for Windows

BEFORE accessing the new installer, perform the following prerequisite steps to ensure a smooth upgrade process:

  • Validate the credit card system is fully operational:

    • From PAS:

      • Perform a validation of all Program IDs defined in PAS by clicking on the blue button (double arrows) located in the upper portion of PAS configuration console.

      • If the result is a red circle after performing the validation, you can move the cursor above the red circle to reveal the error messages associated with the failure.

    • From SAP:

      • Ensure all RFCs defined in SM59 - TCP connections result in a successful test against PAS.

      • Please engage with Support Services if necessary to address any errors generated from the above validation prior to initiating the upgrade.

  • Clear contents of the boost_interprocess directory.

    • Stop the PAS service (from the PAS Configuration GUI, lower left side of window).

      • Ensure that all processes associated with PAS disappear in Task Manager once PAS service stops.

      • If the PAS service is in a Stopped state and the executables highlighted in the screenshot above of the Task Manager, stop the processes manually (right click the orphaned executable(s) and select End Task).

    • Navigate to \C:\WINDOWS\Temp\boost_interprocess\ and delete all files contained in this directory. If you do not see the directory in the above location, perform a search for "boost_interprocess" on all volumes of the server or workstation on which PAS is installed.

  • Make backup copies of the following files:

    • All *.xml configuration files located in:

      • %ProgramFiles(x86)%\Paymetric\Paymetric Adapters for SAP

        Configuration files should be installed in the PAS folder before you upgrade

    • All certificate files (*.pem). These may reside in the install directory or are commonly saved in c:\certs. Verify these are backed-up to a secure location. The *.pem files are for XiSecure. As part of this release the *.crt file is being replaced with a new one.

  • End prerequisites. Continue with the upgrade steps below.

Perform these steps to run installer and upgrade PAS

  • Stop the PAS Service (if not already).

  • Run the installer and go through the wizard.

  • If a Question dialog box pops-up regarding a Microsoft Visual C++ 2005 Redistributable Package, click [Yes] to skip message and continue.

  • Reboot the server if prompted by the Install Wizard; otherwise just Continue.

  • Restart the Paymetric Endpoint Manager service. (see for Start-Stop the Adapter on Windows in XiAssist for instructions if needed).

  • Validate Program ID connections ValidateProgAllIcon.

  • End procedure. You are now ready to test your workflows and TLS 1.2 connectivity.

Upgrade for Red Hat Enterprise Linux (RHEL)

  • Stop the PAS Service.

  • Run the following command as root to install the package: rpm -Uv pas-<ver#>.i686.rpm

  • Start the Paymetric Endpoint Manager service. (see for Start-Stop the Adapter on Red Hat in XiAssist for instructions if needed).

  • End procedure. You are now ready to test your workflows.

Supporting Integration Documents and Installers

The following are downloadable from the Resources page in Merchant Portal or ask your Implementation Consultant or Support Services.

  • PAS Setup Guide

  • PAS_RHEL_Install_Pgk.zip

IMPORTANT NOTE: This is a required update. You must update PAS to version 2.11.1 to align with the Worldpay WAF Akamai URLs.
This version is Windows only. Any references to Linux Red Hat in this document do not apply to this version and should be ignored.

New Features

Known Issues

Get Transaction Function in PAS is currently not working. This capability is for custom workflows. Please contact Paymetric Support if you use this function.

Problems Addressed

N/A

Compatibility and Requirements

This section highlights the basic compatibility and minimum requirements for this release.

Compatible Operating Systems

  • Windows Server 2019 (64-bit)

Additional Windows Server Requirements

  • Microsoft .NET Framework 4.7.2 or higher

  • Visual C++ Runtime 2015-2019 (x86)

General Requirements

  • 1 GB Ram

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging

  • TLS Port 443 and IP Address Ranges should be open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment (obtain IP ranges from Implementation Consultant)

  • Deployment:

    • A single instance of PAS can support multiple SAP instances

    • Paymetric best practice is to have one instance of PAS for PROD and a separate instance for non-PROD environments

PCMA Compatibility

  • Backwards compatible with prior PCMA ECC and S/4HANA versions.

XiSecure SAP IK Compatibility

  • Backwards compatible with prior XiSecure SAP IK ECC and S/4HANA versions.

Install and Configuration Notes

New Installation

New Install Prerequisites:

BEFORE beginning installation, ensure you have met the following prerequisites:

  • Dedicated machine identified on which to install PAS with a User Account that has Administrator rights to the system for Windows.

  • 1 GB of RAM.

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging.

  • TLS Port 443 and IP Address Range 65.163.245.65 - 65.163.245.94 and open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment to test TLS 1.2 connection.

  • The XiPay Web Service Account (WSA) username assigned by Paymetric and QA password assigned by Paymetric (Merchant can change QA password), PROD password set by the Merchant.

  • The XiPay Web Service URL for the environment you are configuring.

  • The XiSecure Web Service URL for the environment you are configuring.

  • The signed client certificate (*.pem) file from Paymetric SaaS Operations for configuring XiSecure in PAS. The file is saved on the PAS machine and you know the file path and file name.

  • The private key file and password you generated when creating the CSR for XiSecure.

  • Download and install the Microsoft Redistributable Packages defined in the Compatibility and Requirements section For Windows Machines.

New Install Release-Specific Instructions:

There are no installation notes specific to this release for new installs. Detailed instructions for installation and configuration are included in the PAS Setup Guide.

Upgrade for Windows

BEFORE accessing the new installer, perform the following prerequisite steps to ensure a smooth upgrade process:

  • Validate the credit card system is fully operational:

    • From PAS:

      • Perform a validation of all Program IDs defined in PAS by clicking on the blue button (double arrows) located in the upper portion of PAS configuration console.

      • If the result is a red circle after performing the validation, you can move the cursor above the red circle to reveal the error messages associated with the failure.

    • From SAP:

      • Ensure all RFCs defined in SM59 - TCP connections result in a successful test against PAS.

      • Please engage with Support Services if necessary to address any errors generated from the above validation prior to initiating the upgrade.

  • Clear contents of the boost_interprocess directory.

    • Stop the PAS service (from the PAS Configuration GUI, lower left side of window).

      • Ensure that all processes associated with PAS disappear in Task Manager once PAS service stops.

      • If the PAS service is in a Stopped state and the executables highlighted in the screenshot above of the Task Manager, stop the processes manually (right click the orphaned executable(s) and select End Task).

    • Navigate to \C:\WINDOWS\Temp\boost_interprocess\ and delete all files contained in this directory. If you do not see the directory in the above location, perform a search for "boost_interprocess" on all volumes of the server or workstation on which PAS is installed.

  • Make backup copies of the following files:

    • All *.xml configuration files located in:

      • %ProgramFiles(x86)%\Paymetric\Paymetric Adapters for SAP

        Configuration files should be installed in the PAS folder before you upgrade

    • All certificate files (*.pem). These may reside in the install directory or are commonly saved in c:\certs. Verify these are backed-up to a secure location. The *.pem files are for XiSecure. As part of this release the *.crt file is being replaced with a new one.

  • End prerequisites. Continue with the upgrade steps below.

Perform these steps to run installer and upgrade PAS:

  • Stop the PAS Service (if not already).

  • Run the installer and go through the wizard.

  • If a Question dialog box pops-up regarding a Microsoft Visual C++ 2005 Redistributable Package, click [Yes] to skip message and continue.

  • Reboot the server if prompted by the Install Wizard; otherwise just Continue.

  • Restart the Paymetric Endpoint Manager service. (see for Start-Stop the Adapter on Windows in XiAssist for instructions if needed).

  • Validate Program ID connections ValidateProgAllIcon.

  • End procedure. You are now ready to test your workflows and TLS 1.2 connectivity.

Supporting Integration Documents and Installers

The following are downloadable from the Resources page in Merchant Portal or ask your Implementation Consultant or Support Services.

  • PAS Setup Guide

  • PAS_Windows_Installer.zip

New Features

  • Added new Program for Intercept calls to Credential Management Platform (CMP).

  • Added Http Keep Alive option to maintain XiPay connection for an entire batch.

  • Made logging enhancements to include more details.

Known Issues

Get Transaction Function in PAS is currently not working. This capability is for custom workflows. Please contact Paymetric Support if you use this function.

Problems Addressed

N/A

Compatibility and Requirements

This section highlights the basic compatibility and minimum requirements for this release.

Compatible Operating Systems

  • Windows Server 2016 (64-bit)

  • Windows Server 2012 Standard and R2 (64-bit)

The latest Red Hat Enterprise Linux PAS version is either 2.8.0 or 2.9.0 if you need Get Transaction Operation.

Additional Windows Server Requirements

  • Microsoft .NET Framework 4.7.2

  • Visual C++ Runtime 2017 32-bit

  • Pentium 4 class processor performance

General Requirements

  • 1 GB Ram

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging

  • TLS Port 443 and IP Address Ranges should be open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment (obtain IP ranges from Implementation Consultant)

  • Deployment:

    • A single instance of PAS can support multiple SAP instances

    • Paymetric best practice is to have one instance of PAS for PROD and a separate instance for non-PROD environments

PCMA Compatibility

  • Backwards compatible with prior PCMA ECC and S/4HANA versions.

  • New TMS functionality requires minimum 2.7.0 for SAP ECC only.

XiSecure SAP IK Compatibility

  • Backwards compatible with prior XiSecure SAP IK ECC and S/4HANA versions.

  • New TMS functionality, which requires minimum 3.3.0 for SAP ECC only.

Install and Configuration Notes

New Installation

New Install Prerequisites:

BEFORE beginning installation, ensure you have met the following prerequisites:

  • Dedicated machine identified on which to install PAS with a User Account that has Administrator rights to the system for Windows, root access for RHEL

  • 1 GB of RAM

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging

  • TLS Port 443 and IP Address Range 65.163.245.65 - 65.163.245.94 and open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment to test TLS 1.2 connection

  • The XiPay Web Service Account (WSA) username assigned by Paymetric and QA password assigned by Paymetric (Merchant can change QA password), PROD password set by the Merchant

  • The XiPay Web Service URL for the environment you are configuring

  • The XiSecure Web Service URL for the environment you are configuring

  • The signed client certificate (*.pem) file from Paymetric SaaS Operations for configuring XiSecure in PAS. The file is saved on the PAS machine and you know the file path and file name

  • The private key file and password you generated when creating the CSR for XiSecure

  • Download and install the Microsoft Redistributable Packages defined in the Compatibility and Requirements section For Windows Machines.

New Install Release-Specific Instructions:

There are no installation notes specific to this release for new installs. Detailed instructions for installation and configuration are included in the PAS Setup Guide. See the appropriate section depending upon whether you are installing PAS for RHEL or PAS for Windows.

Upgrade for Windows

BEFORE accessing the new installer, perform the following prerequisite steps to ensure a smooth upgrade process:

  1. Validate the credit card system is fully operational:

    1. From PAS:

      1. Perform a validation of all Program IDs defined in PAS by clicking on the blue button (double arrows) located in the upper portion of PAS configuration console.

      2. If the result is a red circle after performing the validation, you can move the cursor above the red circle to reveal the error messages associated with the failure.

    2. From SAP:

      1. Ensure all RFCs defined in SM59 - TCP connections result in a successful test against PAS.

      2. Please engage with Support Services if necessary to address any errors generated from the above validation prior to initiating the upgrade.

  2. Clear contents of the boost_interprocess directory.

    1. Stop the PAS service (from the PAS Configuration GUI, lower left side of window).

      1. Ensure that all processes associated with PAS disappear in Task Manager once PAS service stops.

      2. If the PAS service is in a Stopped state and the executables highlighted in the screenshot above of the Task Manager, stop the processes manually (right click the orphaned executable(s) and select End Task).

    2. Navigate to \C:\WINDOWS\Temp\boost_interprocess\ and delete all files contained in this directory. If you do not see the directory in the above location, perform a search for "boost_interprocess" on all volumes of the server or workstation on which PAS is installed.

  3. Make backup copies of the following files:

    1. All *config.xml configuration files located in

      1. %ProgramFiles(x86)%\Paymetric\Paymetric Adapters for SAP\ (64-bit) - OR -

      2. %ProgramFiles%\Paymetric\Paymetric Adapters for SAP\ (32-bit)

    2. All certificate files (*.pem). These may reside in the install directory or are commonly saved in c:\certs. Verify these are backed-up to a secure location. The *.pem files are for XiSecure. As part of this release the *.crt file is being replaced with a new one.

  4. End prerequisites. Continue with the upgrade steps below.

Perform these steps to run installer and upgrade PAS:

  1. Stop the PAS Service (if not already).

  2. Run the installer and go through the wizard.

  3. If a Question dialog box pops-up regarding a Microsoft Visual C++ 2005 Redistributable Package, click [Yes] to skip message and continue.

  4. Reboot the server if prompted by the Install Wizard; otherwise just Continue.

  5. Restart the Paymetric Endpoint Manager service. (see for Start-Stop the Adapter on Windows in XiAssist for instructions if needed).

  6. Validate Program ID connections ValidateProgAllIcon .

  7. End procedure. You are now ready to test your workflows and TLS 1.2 connectivity.

Upgrade for Red Had Enterprise Linux (RHEL)

  1. Stop the PAS service.

  2. Run the following command as root to install the package: rpm -Uv pas-<ver#>.i686.rpm

  3. Start the Paymetric Endpoint Manager service. (see Start-Stop the Adapter on Red Hat for instructions if needed).

  4. End procedure. You are now ready to test your workflows.

Supporting Integration Documents and Installers

The following are downloadable from the Resources page in Merchant Portal or ask your Implementation Consultant or Support Services.

  • PAS Setup Guide

  • PAS_Windows_Installer.zip

  • PAS_RHEL_Install_Pkg.zip

New Features

Added a new XiPayNet Function called "Get Transaction" that pulls all of the transaction details for a specified transaction ID. A separate RFC is configured in SAP for this function.

The Get Transaction function is not tied to the SAP CA-PCI (Cross Application-Payment Card Interface) structure. It supports the use of a function module in SAP to pull all of the transaction details from XiPay for various uses, for example, when implementing APMs or card network mandates around stored credentials.

Problems Addressed

  • If Max Number Retries or Retry Delay settings were modified, the new setting was not being saved.

  • A new XiPayNet configuration setting was added, Connect Timeout, to assist in preventing intermittent connectivity problems. This setting limits the time in seconds that PAS can connect to the XiPay web service endpoint.

Compatibility and Requirements

This section highlights the basic compatibility and minimum requirements for this release.

Compatible Operating Systems

  • Red Hat Enterprise Linux (RHEL) 6.x (32 & 64-bit)

  • Windows Server 2016 (64-bit)

  • Windows Server 2012 Standard and R2 (64-bit)

Additional Windows Server Requirements

  • Microsoft .NET Framework 4.7.2

  • Visual C++ Runtime 2017 32-bit

  • Pentium 4 class processor performance

General Requirements

  • 1 GB Ram

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging

  • TLS Port 443 and IP Address Ranges should be open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment:

    65.163.245.65 thru 65.163.245.94

  • Deployment:

    • A single instance of PAS can support multiple SAP instances

    • Paymetric best practice is to have one instance of PAS for PROD and a separate instance for non-PROD environments

PCMA Compatibility

  • All versions

This was tested with PCMA 2.4.1. While PAS is compatible wither other versions, if you wish to use the new Get Transaction function you must have PCMA 2.4.1 minimum.

XiSecure SAP IK Compatibility

  • All versions

  • Note this was tested with XiSecure SAP IK 3.1.0

Install and Configuration Notes

New Installation

New Install Prerequisites:

BEFORE beginning installation, ensure you have met the following prerequisites:

  • Dedicated machine identified on which to install PAS with a User Account that has Administrator rights to the system for Windows, root access for RHEL.

  • 1 GB of RAM

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging

  • TLS Port 443 and IP Address Range 65.163.245.65 - 65.163.245.94 and open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment to test TLS 1.2 connection

  • The XiPay Web Service Account (WSA) username assigned by Paymetric and QA password assigned by Paymetric (Merchant can change QA password), PROD password set by the Merchant

  • The XiPay Web Service URL for the environment you are configuring

  • The XiSecure Web Service URL for the environment you are configuring

  • The signed client certificate (*.pem) file from Paymetric SaaS Operations for configuring XiSecure in PAS. The file is saved on the PAS machine and you know the file path and file name

  • The private key file and password you generated when creating the CSR for XiSecure

  • Download and install the Microsoft Redistributable Packages defined in the Compatibility and Requirements section For Windows Machines.

New Install Release-Specific Instructions:

There are no installation notes specific to this release for new installs. Detailed instructions for installation and configuration are included in the PAS Setup Guide. See the appropriate section depending upon whether you are installing PAS for RHEL or PAS for Windows.

For Windows installations, if a Question dialog box pops-up regarding a Microsoft Visual C++ 2005 Redistributable Package, click [Yes] to skip message and continue.

Upgrade for Windows

BEFORE accessing the new installer, perform the following prerequisite steps to ensure a smooth upgrade process:

  1. Validate the credit card system is fully operational:

    1. From PAS:

      1. Perform a validation of all Program IDs defined in PAS by clicking on the blue button (double arrows) located in the upper portion of PAS configuration console.

      2. If the result is a red circle after performing the validation, you can move the cursor above the red circle to reveal the error messages associated with the failure.

    2. From SAP:

      1. Ensure all RFCs defined in SM59 - TCP connections result in a successful test against PAS.

      2. Please engage with Support Services if necessary to address any errors generated from the above validation prior to initiating the upgrade.

  2. Clear contents of the boost_interprocess directory.

    1. Stop the PAS service (from the PAS Configuration GUI, lower left side of window).

      1. Ensure that all processes associated with PAS disappear in Task Manager once PAS service stops.

      2. If the PAS service is in a Stopped state and the executables highlighted in the screenshot above of the Task Manager, stop the processes manually (right click the orphaned executable(s) and select End Task).

    2. Navigate to \C:\WINDOWS\Temp\boost_interprocess\ and delete all files contained in this directory. If you do not see the directory in the above location, perform a search for "boost_interprocess" on all volumes of the server or workstation on which PAS is installed.

  3. Make backup copies of the following files:

    1. All *config.xml configuration files located in

      1. %ProgramFiles(x86)%\Paymetric\Paymetric Adapters for SAP\ (64-bit) - OR -

      2. %ProgramFiles%\Paymetric\Paymetric Adapters for SAP\ (32-bit)

    2. All certificate files (*.pem). These may reside in the install directory or are commonly saved in c:\certs. Verify these are backed-up to a secure location. The *.pem files are for XiSecure. As part of this release the *.crt file is being replaced with a new one.

  4. End prerequisites. Continue with the upgrade steps below.

Perform these steps to run installer and upgrade PAS:

  1. Stop the PAS Service (if not already).

  2. Run the installer and go through the wizard.

  3. If a Question dialog box pops-up regarding a Microsoft Visual C++ 2005 Redistributable Package, click [Yes] to skip message and continue.

  4. Reboot the server if prompted by the Install Wizard; otherwise just Continue.

  5. Restart the Paymetric Endpoint Manager service. (see for Start-Stop the Adapter on Windows in XiAssist for instructions if needed).

  6. Validate Program ID connections ValidateProgAllIcon .

  7. End procedure. You are now ready to test your workflows and TLS 1.2 connectivity.

Upgrade for Red Had Enterprise Linux (RHEL)

  1. Stop the PAS service.

  2. Run the following command as root to install the package: rpm -Uv pas-<ver#>.i686.rpm

  3. Start the Paymetric Endpoint Manager service. (see Start-Stop the Adapter on Red Hat for instructions if needed).

  4. End procedure. You are now ready to test your workflows.

Supporting Integration Documents and Installers

The following are downloadable from the Resources page in Merchant Portal or ask your Implementation Consultant or Support Services.

  • PAS Setup Guide

  • PAS_Windows_Installer.zip

  • PAS_RHEL_Install_Pkg.zip

New Features

Added the ability to suppress line item data at authorization. The default setting is to send the data. If you have implemented XiVerify, this setting should always be enabled.

Problems Addressed

N/A

Compatibility and Requirements

This section highlights the basic compatibility and minimum requirements for this release.

Compatible Operating Systems

  • Red Hat Enterprise Linux (RHEL) 6.x (32 & 64-bit)

  • Windows Server 2012 Standard and R2 (64-bit)

  • Windows Server 2008 R2 (64-bit)

Windows Server 2008 is no longer supported by Microsoft. Refer to their documentation for instructions on how to ensure your 2008 server is connecting at TLS 1.2.

Additional Windows Server Requirements

  • Microsoft .NET Framework 3.5

  • Pentium 4 class processor performance.

  • Various Microsoft Visual C++ Redistributable Packages (newer packages are downloaded automatically by the installer)

  • Newer packages are automatically downloaded and installed by the PAS installer; however, there are some older packages that are required as well. PAS will check for the older packages, but they must be downloaded and installed if you receive a message that one is missing.

  • If you receive a pop-up message during the install that a package is missing, make a note of the version number from the message. Install that version and any other versions that follow it. For example, if you got a message that Version 8.0.50727.4053 (the middle one below) is missing, install that one and the subsequent 8.0.50727.6195 version.

The filename is the same for the packages (vcredist_x86.exe), so you should save them in different directories and install them in the order below. This file is 32-bit version which is what PAS requires even if your server is 64-bit.

General Requirements

  • 1 GB Ram

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging

  • TLS Port 443 and IP Address Ranges should be open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment:

    65.163.245.65 thru 65.163.245.94

  • Deployment:

    • A single instance of PAS can support multiple SAP instances

    • Paymetric best practice is to have one instance of PAS for PROD and a separate instance for non-PROD environments

PCMA Compatibility

  • All versions

This was tested with PCMA 1.9.0.

XiSecure SAP IK Compatibility

  • All versions

This was tested with XiSecure SAP IK 3.1.0

Install and Configuration Notes

New Installation

New Install Prerequisites:

BEFORE beginning installation, ensure you have met the following prerequisites:

  • Dedicated machine identified on which to install PAS with a User Account that has Administrator rights to the system for Windows, root access for RHEL.

  • 1 GB of RAM.

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging.

  • TLS Port 443 and IP Address Range 65.163.245.65 - 65.163.245.94 and open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment to test TLS 1.2 connection.

  • The XiPay Web Service Account (WSA) username assigned by Paymetric and QA password assigned by Paymetric (Merchant can change QA password), PROD password set by the Merchant.

  • The XiPay Web Service URL for the environment you are configuring.

  • The XiSecure Web Service URL for the environment you are configuring.

  • The signed client certificate (*.pem) file from Paymetric SaaS Operations for configuring XiSecure in PAS. The file is saved on the PAS machine and you know the file path and file name.

  • The private key file and password you generated when creating the CSR for XiSecure.

  • Download and install the Microsoft Redistributable Packages defined in the Compatibility and Requirements section For Windows Machines.

New Install Release-Specific Instructions:

There are no installation notes specific to this release for new installs. Detailed instructions for installation and configuration are included in the PAS Setup Guide. See the appropriate section depending upon whether you are installing PAS for RHEL or PAS for Windows.

For Windows installations, note that if during the install you receive a dialog box regarding a Microsoft Visual C++ Redistributable package, make note of the Version number referenced in the dialog box, then click [No] to stop the installation. See Additional Windows Server Requirements above for the details.

Upgrade for Windows

BEFORE accessing the new installer, perform the following prerequisite steps to ensure a smooth upgrade process:

  1. Validate the credit card system is fully operational:

    1. From PAS:

      1. Perform a validation of all Program IDs defined in PAS by clicking on the blue button (double arrows) located in the upper portion of PAS configuration console.

      2. If the result is a red circle after performing the validation, you can move the cursor above the red circle to reveal the error messages associated with the failure.

    2. From SAP:

      1. Ensure all RFCs defined in SM59 - TCP connections result in a successful test against PAS.

      2. Please engage with Support Services if necessary to address any errors generated from the above validation prior to initiating the upgrade.

  2. Clear contents of the boost_interprocess directory.

    1. Stop the PAS service (from the PAS Configuration GUI, lower left side of window).

      1. Ensure that all processes associated with PAS disappear in Task Manager once PAS service stops.

      2. If the PAS service is in a Stopped state and the executables highlighted in the screenshot above of the Task Manager, stop the processes manually (right click the orphaned executable(s) and select End Task).

    2. Navigate to \C:\WINDOWS\Temp\boost_interprocess\ and delete all files contained in this directory. If you do not see the directory in the above location, perform a search for "boost_interprocess" on all volumes of the server or workstation on which PAS is installed.

  3. Make backup copies of the following files:

    1. All *config.xml configuration files located in

      1. %ProgramFiles(x86)%\Paymetric\Paymetric Adapters for SAP\ (64-bit) - OR -

      2. %ProgramFiles%\Paymetric\Paymetric Adapters for SAP\ (32-bit)

    2. All certificate files (*.pem). These may reside in the install directory or are commonly saved in c:\certs. Verify these are backed-up to a secure location. The *.pem files are for XiSecure. As part of this release the *.crt file is being replaced with a new one.

  4. If needed, download and install the Microsoft Redistributable Packages defined in the Compatibility and Requirements section For Windows Machines.

  5. End prerequisites. Continue with the upgrade steps below.

Perform these steps to run installer and upgrade PAS:

  1. Stop the PAS Service.

  2. Run the installer and go through the wizard.

  3. Launch the PAS GUI.

  4. Change to the new CA Certificate:

    1. On each XiPay program ID change the “Certificate File” to superbundle.crt

    2. On each XiSecure program ID change the “CA Certificate” to superbundle.crt

    3. NOTE: superbundle.crt is in the new install package and is placed in the PAS install directory be default. You may move it to a dedicated certificate directory if you want but move it before you change the above parameters so PAS can find it.

  5. Define a “Logs” directory (if not already defined).

    1. Click the Logging/Tracing Settings icon logSettingsIcon.

    2. Define the “RFC Daemon Trace Log Directory” is blank.

    3. Even if no logging is enable, please define the directory.

    4. NOTE: These logs can become excessive. Define a dedicated logs directory rather than using the default PAS directory so the directory can be easily maintained and cleared out

  6. Reboot the server if prompted by the Install Wizard; otherwise just Continue.

  7. Restart the Paymetric Endpoint Manager service. (see for Start-Stop the Adapter on Windows in XiAssist for instructions if needed).

  8. Validate Program ID connections ValidateProgAllIcon .

  9. End procedure. You are now ready to test your workflows and TLS 1.2 connectivity.

Upgrade for Red Had Enterprise Linux (RHEL)

  1. Stop the PAS service.

  2. Run the following command as root to install the package: rpm -Uv pas-<ver#>.i686.rpm

  3. Start the Paymetric Endpoint Manager service. (see Start-Stop the Adapter on Red Hat for instructions if needed).

  4. End procedure. You are now ready to test your workflows.

Supporting Integration Documents and Installers

The following are downloadable from the Resources page in Merchant Portal or ask your Implementation Consultant or Support Services.

  • PAS Setup Guide

  • PAS_Windows_Installer.zip

  • PAS_RHEL_Install_Pkg.zip

New Features

  • New SSL Certificate Super Bundle

  • TLSv1.1 and TSLv1.2 Support

  • Added Integration Indicator

  • Add Line-Item Data Support at Authorization

  • New Export Function for Logs and Configuration Files

  • Added Support for Future WSS Authentication to XiPay

Problems Addressed

N/A

Compatibility and Requirements

This section highlights the basic compatibility and minimum requirements for this release.

Compatible Operating Systems

  • Red Hat Enterprise Linux (RHEL) 6.x (32 & 64-bit)

  • Windows Server 2012 Standard and R2 (64-bit)

  • Windows Server 2008 R2 (64-bit)

Windows Server 2008 is no longer supported by Microsoft. Refer to their documentation for instructions on how to ensure your 2008 server is connecting at TLS 1.2.

Additional Windows Server Requirements

  • Microsoft .NET Framework 3.5

  • Pentium 4 class processor performance.

  • Various Microsoft Visual C++ Redistributable Packages (newer packages are downloaded automatically by the installer)

  • Newer packages are automatically downloaded and installed by the PAS installer; however, there are some older packages that are required as well. PAS will check for the older packages, but they must be downloaded and installed if you receive a message that one is missing.

  • If you receive a pop-up message during the install that a package is missing, make a note of the version number from the message. Install that version and any other versions that follow it. For example, if you got a message that Version 8.0.50727.4053 (the middle one below) is missing, install that one and the subsequent 8.0.50727.6195 version.

The filename is the same for the packages (vcredist_x86.exe), so you should save them in different directories and install them in the order below. This file is 32-bit version which is what PAS requires even if your server is 64-bit.

General Requirements

  • 1 GB Ram

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging

  • TLS Port 443 and IP Address Ranges should be open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment:

    65.163.245.65 thru 65.163.245.94

  • Deployment:

    • A single instance of PAS can support multiple SAP instances

    • Paymetric best practice is to have one instance of PAS for PROD and a separate instance for non-PROD environments

PCMA Compatibility

  • All versions

This was tested with PCMA 1.9.0.

XiSecure SAP IK Compatibility

  • All versions

This was tested with XiSecure SAP IK 3.0.1

Install and Configuration Notes

New Installation

New Install Prerequisites:

BEFORE beginning installation, ensure you have met the following prerequisites:

  • Dedicated machine identified on which to install PAS with a User Account that has Administrator rights to the system for Windows, root access for RHEL.

  • 1 GB of RAM.

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging.

  • TLS Port 443 and IP Address Range 65.163.245.65 - 65.163.245.94 and open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment to test TLS 1.2 connection.

  • The XiPay Web Service Account (WSA) username assigned by Paymetric and QA password assigned by Paymetric (Merchant can change QA password), PROD password set by the Merchant.

  • The XiPay Web Service URL for the environment you are configuring.

  • The XiSecure Web Service URL for the environment you are configuring.

  • The signed client certificate (*.pem) file from Paymetric SaaS Operations for configuring XiSecure in PAS. The file is saved on the PAS machine and you know the file path and file name.

  • The private key file and password you generated when creating the CSR for XiSecure.

  • Download and install the Microsoft Redistributable Packages defined in the Compatibility and Requirements section For Windows Machines.

New Install Release-Specific Instructions:

There are no installation notes specific to this release for new installs. Detailed instructions for installation and configuration are included in the PAS Setup Guide. See the appropriate section depending upon whether you are installing PAS for RHEL or PAS for Windows.

For Windows installations, note that if during the install you receive a dialog box regarding a Microsoft Visual C++ Redistributable package, make note of the Version number referenced in the dialog box, then click [No] to stop the installation. See Additional Windows Server Requirements above for the details.

Upgrade for Windows

BEFORE accessing the new installer, perform the following prerequisite steps to ensure a smooth upgrade process:

  1. Validate the credit card system is fully operational:

    1. From PAS:

      1. Perform a validation of all Program IDs defined in PAS by clicking on the blue button (double arrows) located in the upper portion of PAS configuration console.

      2. If the result is a red circle after performing the validation, you can move the cursor above the red circle to reveal the error messages associated with the failure.

    2. From SAP:

      1. Ensure all RFCs defined in SM59 - TCP connections result in a successful test against PAS.

      2. Please engage with Support Services if necessary to address any errors generated from the above validation prior to initiating the upgrade.

  2. Clear contents of the boost_interprocess directory.

    1. Stop the PAS service (from the PAS Configuration GUI, lower left side of window).

      1. Ensure that all processes associated with PAS disappear in Task Manager once PAS service stops.

      2. If the PAS service is in a Stopped state and the executables highlighted in the screenshot above of the Task Manager, stop the processes manually (right click the orphaned executable(s) and select End Task).

    2. Navigate to \C:\WINDOWS\Temp\boost_interprocess\ and delete all files contained in this directory. If you do not see the directory in the above location, perform a search for "boost_interprocess" on all volumes of the server or workstation on which PAS is installed.

  3. Make backup copies of the following files:

    1. All *config.xml configuration files located in

      1. %ProgramFiles(x86)%\Paymetric\Paymetric Adapters for SAP\ (64-bit) - OR -

      2. %ProgramFiles%\Paymetric\Paymetric Adapters for SAP\ (32-bit)

    2. All certificate files (*.pem). These may reside in the install directory or are commonly saved in c:\certs. Verify these are backed-up to a secure location. The *.pem files are for XiSecure. As part of this release the *.crt file is being replaced with a new one.

  4. If needed, download and install the Microsoft Redistributable Packages defined in the Compatibility and Requirements section For Windows Machines.

  5. End prerequisites. Continue with the upgrade steps below.

Perform these steps to run installer and upgrade PAS:

  1. Stop the PAS Service.

  2. Run the installer and go through the wizard.

  3. Launch the PAS GUI.

  4. Change to the new CA Certificate:

    1. On each XiPay program ID change the “Certificate File” to superbundle.crt

    2. On each XiSecure program ID change the “CA Certificate” to superbundle.crt

    3. NOTE: superbundle.crt is in the new install package and is placed in the PAS install directory be default. You may move it to a dedicated certificate directory if you want but move it before you change the above parameters so PAS can find it.

  5. Define a “Logs” directory (if not already defined).

    1. Click the Logging/Tracing Settings icon logSettingsIcon.

    2. Define the “RFC Daemon Trace Log Directory” is blank.

    3. Even if no logging is enable, please define the directory.

    4. NOTE: These logs can become excessive. Define a dedicated logs directory rather than using the default PAS directory so the directory can be easily maintained and cleared out

  6. Reboot the server if prompted by the Install Wizard; otherwise just Continue.

  7. Restart the Paymetric Endpoint Manager service. (see for Start-Stop the Adapter on Windows in XiAssist for instructions if needed).

  8. Validate Program ID connections ValidateProgAllIcon .

  9. End procedure. You are now ready to test your workflows and TLS 1.2 connectivity.

Upgrade for Red Had Enterprise Linux (RHEL)

  1. Stop the PAS service.

  2. Run the following command as root to install the package: rpm -Uv pas-<ver#>.i686.rpm

  3. Start the Paymetric Endpoint Manager service. (see Start-Stop the Adapter on Red Hat for instructions if needed).

  4. End procedure. You are now ready to test your workflows.

Supporting Integration Documents and Installers

The following are downloadable from the Resources page in Merchant Portal or ask your Implementation Consultant or Support Services.

  • PAS Setup Guide

  • PAS_Windows_Installer.zip

  • PAS_RHEL_Install_Pkg.zip

New Features

Added support for SHA-2 certificates per industry best practices and PCI v3.1 requirements. For more information regarding SHA-2, you can refer to the following links:

Problems Addressed

N/A

Compatibility and Requirements

This section highlights the basic compatibility and minimum requirements for this release.

Compatible Operating Systems

  • Red Hat Enterprise Linux (RHEL) 6.0 (32 & 64-bit)

  • Windows Server 2012 Standard and R2 (64-bit)

  • Windows Server 2008 R2 (64-bit)

Additional Windows Server Requirements

  • Microsoft .NET Framework 3.5

  • Pentium 4 class processor performance.

  • Various Microsoft Visual C++ Redistributable Packages (newer packages are downloaded automatically by the installer)

  • Newer packages are automatically downloaded and installed by the PAS installer; however, there are some older packages that are required as well. PAS will check for the older packages, but they must be downloaded and installed if you receive a message that one is missing.

  • If you receive a pop-up message during the install that a package is missing, make a note of the version number from the message. Install that version and any other versions that follow it. For example, if you got a message that Version 8.0.50727.4053 (the middle one below) is missing, install that one and the subsequent 8.0.50727.6195 version.

The filename is the same for the packages (vcredist_x86.exe), so you should save them in different directories and install them in the order below. This file is 32-bit version which is what PAS requires even if your server is 64-bit.

General Requirements

  • 1 GB Ram

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging

  • TLS Port 443 and IP Address Ranges should be open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment:

    65.163.245.65 thru 65.163.245.94

  • Deployment:

    • A single instance of PAS can support multiple SAP instances

    • Paymetric best practice is to have one instance of PAS for PROD and a separate instance for non-PROD environments

    • Microsoft .NET Framework 3.5

PCMA Compatibility

  • All versions

This was tested with PCMA 1.9.0.

XiSecure SAP IK Compatibility

  • All versions

This was tested with XiSecure SAP IK 3.0.1

Install and Configuration Notes

New Installation

New Install Prerequisites:

BEFORE beginning installation, ensure you have met the following prerequisites:

  • Dedicated machine identified on which to install PAS with a User Account that has Administrator rights to the system for Windows, root access for RHEL.

  • 1 GB of RAM.

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging.

  • TLS Port 443 and IP Address Range 65.163.245.65 - 65.163.245.94 and open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment to test TLS 1.2 connection.

  • The XiPay Web Service Account (WSA) username assigned by Paymetric and QA password assigned by Paymetric (Merchant can change QA password), PROD password set by the Merchant.

  • The XiPay Web Service URL for the environment you are configuring.

  • The XiSecure Web Service URL for the environment you are configuring.

  • The signed client certificate (*.pem) file from Paymetric SaaS Operations for configuring XiSecure in PAS. The file is saved on the PAS machine and you know the file path and file name.

  • The private key file and password you generated when creating the CSR for XiSecure.

  • Download and install the Microsoft Redistributable Packages defined in the Compatibility and Requirements section For Windows Machines.

New Install Release-Specific Instructions:

There are no installation notes specific to this release for new installs. Detailed instructions for installation and configuration are included in the PAS Setup Guide. See the appropriate section depending upon whether you are installing PAS for RHEL or PAS for Windows.

For Windows installations, note that if during the install you receive a dialog box regarding a Microsoft Visual C++ Redistributable package, make note of the Version number referenced in the dialog box, then click [No] to stop the installation. See Additional Windows Server Requirements above for the details.

Upgrade for Windows

BEFORE accessing the new installer, perform the following prerequisite steps to ensure a smooth upgrade process:

  1. Validate the credit card system is fully operational:

    1. From PAS:

      1. Perform a validation of all Program IDs defined in PAS by clicking on the blue button (double arrows) located in the upper portion of PAS configuration console.

      2. If the result is a red circle after performing the validation, you can move the cursor above the red circle to reveal the error messages associated with the failure.

    2. From SAP:

      1. Ensure all RFCs defined in SM59 - TCP connections result in a successful test against PAS.

      2. Please engage with Support Services if necessary to address any errors generated from the above validation prior to initiating the upgrade.

  2. Clear contents of the boost_interprocess directory.

    1. Stop the PAS service (from the PAS Configuration GUI, lower left side of window).

      1. Ensure that all processes associated with PAS disappear in Task Manager once PAS service stops.

      2. If the PAS service is in a Stopped state and the executables highlighted in the screenshot above of the Task Manager, stop the processes manually (right click the orphaned executable(s) and select End Task).

    2. Navigate to \C:\WINDOWS\Temp\boost_interprocess\ and delete all files contained in this directory. If you do not see the directory in the above location, perform a search for "boost_interprocess" on all volumes of the server or workstation on which PAS is installed.

  3. Make backup copies of the following files:

    1. All *config.xml configuration files located in

      1. %ProgramFiles(x86)%\Paymetric\Paymetric Adapters for SAP\ (64-bit) - OR -

      2. %ProgramFiles%\Paymetric\Paymetric Adapters for SAP\ (32-bit)

    2. All certificate files (*.pem). These may reside in the install directory or are commonly saved in c:\certs. Verify these are backed-up to a secure location. The *.pem files are for XiSecure. As part of this release the *.crt file is being replaced with a new one.

  4. If needed, download and install the Microsoft Redistributable Packages defined in the Compatibility and Requirements section For Windows Machines.

  5. End prerequisites. Continue with the upgrade steps below.

Perform these steps to run installer and upgrade PAS:

  1. Stop the PAS Service.

  2. Run the installer and go through the wizard.

  3. Launch the PAS GUI.

  4. Change to the new CA Certificate:

    1. On each XiPay program ID change the “Certificate File” to superbundle.crt

    2. On each XiSecure program ID change the “CA Certificate” to superbundle.crt

    3. NOTE: superbundle.crt is in the new install package and is placed in the PAS install directory be default. You may move it to a dedicated certificate directory if you want but move it before you change the above parameters so PAS can find it.

  5. Define a “Logs” directory (if not already defined).

    1. Click the Logging/Tracing Settings icon logSettingsIcon.

    2. Define the “RFC Daemon Trace Log Directory” is blank.

    3. Even if no logging is enable, please define the directory.

    4. NOTE: These logs can become excessive. Define a dedicated logs directory rather than using the default PAS directory so the directory can be easily maintained and cleared out

  6. Reboot the server if prompted by the Install Wizard; otherwise just Continue.

  7. Restart the Paymetric Endpoint Manager service. (see for Start-Stop the Adapter on Windows in XiAssist for instructions if needed).

  8. Validate Program ID connections ValidateProgAllIcon .

  9. End procedure. You are now ready to test your workflows and TLS 1.2 connectivity.

Upgrade for Red Had Enterprise Linux (RHEL)

  1. Stop the PAS service.

  2. Run the following command as root to install the package: rpm -Uv pas-<ver#>.i686.rpm

  3. Start the Paymetric Endpoint Manager service. (see Start-Stop the Adapter on Red Hat for instructions if needed).

  4. End procedure. You are now ready to test your workflows.

Supporting Integration Documents and Installers

The following are downloadable from the Resources page in Merchant Portal or ask your Implementation Consultant or Support Services.

  • PAS Setup Guide

  • PAS_Windows_Installer.zip

  • PAS_RHEL_Install_Pkg.zip

New Features

  • Support for XiIntercept SAP Single Sign-On

  • Support for XiRecon - Settlement Reconciliation Report

Problems Addressed

N/A

Compatibility and Requirements

This section highlights the basic compatibility and minimum requirements for this release.

Compatible Operating Systems

  • Red Hat Enterprise Linux (RHEL) 5.5 (32 & 64-bit) and above

  • Windows Server 2012 Standard (64-bit)

  • Windows Server 2008 Enterprise, Standard & R2 Editions (32 & 64-bit)

  • Windows 7 Enterprise and Standard Editions (32 & 64-bit)

Windows Machines

Pentium 4 class processor performance.

The following Microsoft Visual C++ Redistributable Packages are required to run PAS.

The file name is the same for the packages so you should save them in different directories and apply them in the order below.

Name: Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)

Version: 8.0.50727.762

Date: 8/27/2007

URL: http://www.microsoft.com/en-us/download/details.aspx?id=5638

File: vcredist_x86.exe

General Requirements

  • 1 GB Ram

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging

  • TLS Port 443 and IP Address Ranges should be open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment:

    65.163.245.65 thru 65.163.245.94

  • Deployment:

    • A single instance of PAS can support multiple SAP instances

    • Paymetric best practice is to have one instance of PAS for PROD and a separate instance for non-PROD environments

    • Microsoft .NET Framework 3.5 (minimum)

PCMA

  • All versions

XiIntercept SAP Version 2 SSO requires minimum 1.7.0.

XiSecure SAP IK

  • All versions

XiIntercept SAP version 2 SSO requires minimum 2.4.0.

Install and Configuration Notes

BEFORE beginning installation, ensure you have met the following prerequisites:

  • Dedicated machine identified on which to install PAS with a User Account that has Administrator rights to the system for Windows, root access for RHEL.

  • 1 GB of RAM.

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging.

  • TLS Port 443 and IP Address Range 65.163.245.65 - 65.163.245.94 and open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment to test TLS 1.2 connection.

  • The XiPay Web Service Account (WSA) username assigned by Paymetric and QA password assigned by Paymetric (Merchant can change QA password), PROD password set by the Merchant.

  • The XiPay Web Service URL for the environment you are configuring.

  • The XiSecure Web Service URL for the environment you are configuring.

  • The signed client certificate (*.pem) file from Paymetric SaaS Operations for configuring XiSecure in PAS. The file is saved on the PAS machine and you know the file path and file name.

  • The private key file and password you generated when creating the CSR for XiSecure.

  • Download and install the Microsoft Redistributable Packages defined in the Compatibility and Requirements section For Windows Machines.

New Installation:

BEFORE beginning installation, ensure you have met the following prerequisites:

  • Dedicated machine identified on which to install PAS with a User Account that has Administrator rights to the system for Windows, root access for RHEL.

  • 1 GB of RAM.

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging.

  • TLS Port 443 and IP Address Range 65.163.245.65 - 65.163.245.94 and open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment to test TLS 1.2 connection.

  • The XiPay Web Service Account (WSA) username assigned by Paymetric and QA password assigned by Paymetric (Merchant can change QA password), PROD password set by the Merchant.

  • The XiPay Web Service URL for the environment you are configuring.

  • The XiSecure Web Service URL for the environment you are configuring.

  • The signed client certificate (*.pem) file from Paymetric SaaS Operations for configuring XiSecure in PAS. The file is saved on the PAS machine and you know the file path and file name.

  • The private key file and password you generated when creating the CSR for XiSecure.

  • Download and install the Microsoft Redistributable Packages defined in the Compatibility and Requirements section For Windows Machines.

New Install Release-Specific Instructions:

There are no installation notes specific to this release for new installs. Detailed instructions for installation and configuration are included in the PAS Setup Guide. See the appropriate section depending upon whether you are installing PAS for RHEL or PAS for Windows.

For Windows installations, note that if during the install you receive a dialog box regarding a Microsoft Visual C++ Redistributable package, make note of the Version number referenced in the dialog box, then click [No] to stop the installation. See Additional Windows Server Requirements above for the details.

Upgrade for Windows

BEFORE accessing the new installer, perform the following prerequisite steps to ensure a smooth upgrade process:

  1. Validate the credit card system is fully operational:

    1. From PAS:

      1. Perform a validation of all Program IDs defined in PAS by clicking on the blue button (double arrows) located in the upper portion of PAS configuration console.

      2. If the result is a red circle after performing the validation, you can move the cursor above the red circle to reveal the error messages associated with the failure.

    2. From SAP:

      1. Ensure all RFCs defined in SM59 - TCP connections result in a successful test against PAS.

      2. Please engage with Support Services if necessary to address any errors generated from the above validation prior to initiating the upgrade.

  2. Clear contents of the boost_interprocess directory.

    1. Stop the PAS service (from the PAS Configuration GUI, lower left side of window).

      1. Ensure that all processes associated with PAS disappear in Task Manager once PAS service stops.

      2. If the PAS service is in a Stopped state and the executables highlighted in the screenshot above of the Task Manager, stop the processes manually (right click the orphaned executable(s) and select End Task).

    2. Navigate to \C:\WINDOWS\Temp\boost_interprocess\ and delete all files contained in this directory. If you do not see the directory in the above location, perform a search for "boost_interprocess" on all volumes of the server or workstation on which PAS is installed.

  3. Make backup copies of the following files:

    1. All *config.xml configuration files located in

      1. %ProgramFiles(x86)%\Paymetric\Paymetric Adapters for SAP\ (64-bit) - OR -

      2. %ProgramFiles%\Paymetric\Paymetric Adapters for SAP\ (32-bit)

    2. All certificate files (*.pem). These may reside in the install directory or are commonly saved in c:\certs. Verify these are backed-up to a secure location. The *.pem files are for XiSecure. As part of this release the *.crt file is being replaced with a new one.

  4. If needed, download and install the Microsoft Redistributable Packages defined in the Compatibility and Requirements section For Windows Machines.

  5. End prerequisites. Continue with the upgrade steps below.

Perform these steps to run installer and upgrade PAS:

  1. Stop the PAS Service.

  2. Run the installer and go through the wizard.

  3. Launch the PAS GUI.

  4. Change to the new CA Certificate:

    1. On each XiPay program ID change the “Certificate File” to superbundle.crt

    2. On each XiSecure program ID change the “CA Certificate” to superbundle.crt

    3. NOTE: superbundle.crt is in the new install package and is placed in the PAS install directory be default. You may move it to a dedicated certificate directory if you want but move it before you change the above parameters so PAS can find it.

  5. Define a “Logs” directory (if not already defined).

    1. Click the Logging/Tracing Settings icon logSettingsIcon.

    2. Define the “RFC Daemon Trace Log Directory” is blank.

    3. Even if no logging is enable, please define the directory.

    4. NOTE: These logs can become excessive. Define a dedicated logs directory rather than using the default PAS directory so the directory can be easily maintained and cleared out

  6. Reboot the server if prompted by the Install Wizard; otherwise just Continue.

  7. Restart the Paymetric Endpoint Manager service. (see for Start-Stop the Adapter on Windows in XiAssist for instructions if needed).

  8. Validate Program ID connections ValidateProgAllIcon .

  9. End procedure. You are now ready to test your workflows and TLS 1.2 connectivity.

Upgrade for Red Had Enterprise Linux (RHEL)

This release removes the RFC trace setting from PAS and deletes any rfc*.trc files from /var/log/pas.

If you wish to retain these files, please perform a backup prior to beginning the upgrade procedure; however, note that they do contain unmasked credit card numbers.

Upgrading from 2.4.0 or 2.4.1 versions

Upgrades from these versions require an uninstall then install of the new package to ensure that future upgrades work properly. Perform the following steps to upgrade:

  1. Copy the XML configuration files from /etc/pas to a backup location to preserve your configuration settings as /etc/pas is removed during uninstall.

  2. Copy any files from /home/paymetric (the home directory of the paymetric user) to a backup location. The paymetric user and /home/paymetric are removed during uninstall.

  3. Run the following command as root on the 2.4.0 or 2.4.1 package; run it on the highest version installed: (the following example is 2.4.1) rpm -e pas-2.4.1-x.i386.rpm

  4. Run the following command as root to install the 2.7.1 package: rpm –ivh pas-2.7.1-x.i386.rpm

  5. Refer to the PAS Install and Configuration Guide for configuration information if needed.

  6. Copy the XML backup configuration files to new /etc/pas and /home/paymetric directories.

  7. Start the Paymetric Endpoint Manager service. (see PAS Install and Configuration Guide for instructions if needed).

Upgrading from version 2.4.2 and above

  1. Run the following command as root: rpm -Uv pas-2.7.1-x.i386.rpm

  2. Refer to the PAS Install and Configuration Guide for configuration information if needed.

  3. Start the Paymetric Endpoint Manager service. (see PAS Install and Configuration Guide for instructions if needed).

Supporting Integration Documents and Installers

This release is supported by the following product documentation:

  • XiPay Platform SAP Integration Guide

  • XiSecure Platform SAP Integration Guide

New Features

  • Retry Logic for Connection Errors

  • Display Ping Results

  • Audit Log of PAS Configuration Changes

Problems Addressed

  • Stripping Leading Zeros from PO Numbers during Settlement. If leading zeros were supplied in the PO Number during Settlement, they were being removed by PAS. The leading zeros are now passed at settlement for the PO Number field.

  • Library Path being Overwritten when Using the RHEL GUI. For RHEL users, when enabled, logging goes to /var/log/messages; however, if changes to the log configuration were made via the PAS GUI, the path to LogSysLog.so in LoggingConfig.xml was being overwritten when the changes were saved causing logging to stop working. This issue has been addressed going forward. If you are upgrading and previously used the PAS GUI to configure the logging settings, we recommend that you open the PAS Logging Settings dialog box (by clicking the logSettingsIcon icon) and then click Ok to close it. This will ensure the LibraryPath value in the LoggingConfig.xml file is accurate.

  • PAS for RHEL Placing all InfoItems at Header Level. For RHEL users, PAS was incorrectly placing all Info Items at the Header (level 2) level even when the Info Item should be placed at the Transaction Line level (level 3).

  • Invalid Characters in strUserID XiSecure Element. The Decrypt and DecryptByKey Operations have an element called strUserID that is a string of 25 characters. This contains a value that can be used to refer back to the user in the application that initiated the decryption. PAS was appending characters to the string that were sometimes invalid XML characters.

Compatibility and Requirements

This section highlights the basic compatibility and minimum requirements for this release.

Operating Systems

  • Red Hat Enterprise Linux (RHEL) 5.5 (32 & 64-bit) and above

  • Windows Server 2003 Enterprise and Standard Editions (32 & 64-bit)

  • Windows Server 2008 Enterprise, Standard & R2 Editions (32 & 64-bit)

  • Windows 7 Enterprise and Standard Editions (32 & 64-bit)

  • Windows XP (32 and 64-bit)

Windows Machines

The following Microsoft Visual C++ Redistributable Packages are required to run PAS.

The file name is the same for the packages so you should save them in different directories and apply them in the order below.

Name: Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)

Version: 8.0.50727.762

Date: 8/27/2007

URL: http://www.microsoft.com/en-us/download/details.aspx?id=5638

File: vcredist_x86.exe

General Requirements

  • 1 GB Ram

  • 25 MB of disk space to run the program; an additional 225 MB recommended for logging

  • TLS Port 443 and IP Address Ranges should be open on any applicable firewall for outbound traffic from PAS to Paymetric On-Demand environment:

    65.163.245.65 thru 65.163.245.94

  • Deployment:

    • A single instance of PAS can support multiple SAP instances

    • Paymetric best practice is to have one instance of PAS for PROD and a separate instance for non-PROD environments

    • Microsoft .NET Framework 3.5 (minimum)

PCMA

  • All versions

XiSecure SAP IK

  • All versions

Install and Configuration Notes

New Installation with XiPay 3.x (OD3)

There are no installation notes specific to this release for the XiPay 3.x (OD3) environment for new installs. Refer to the PAS Install and Configuration Guide for instructions. See the appropriate section depending upon whether you are installing PAS for RHEL or PAS for Windows. For Windows Users, note if during the install you receive a dialog box regarding a Microsoft Visual C++ Redistributable package, click [No] and verify the packages are installed (see Windows Requirements above).

New Installation with XiPay 2.9 (OD2)

PAS authorization and settlement RFCs are not available for use with XiPayNet 2.9 (OD2) for new installs. If you are implementing XiSecure and currently have an XiPayNet 2.9 environment, refer to the PAS Install and Configuration Guide and follow the standard installation procedure for either Windows or RHEL and then ONLY perform the XiSecureNetRFC configuration for Tokenization.

You must detokenize credit cards directly with XiSecure prior to sending to XiPayNet 2.9.

For Windows Users, note if during the install you receive a dialog box regarding a Microsoft Visual C++ Redistributable package, click [No] and verify the packages are installed (see Windows Requirements above).

Upgrade for Windows

The upgrade steps vary depending upon the PAS version from which you are upgrading. There are some Initial Steps that should be performed prior to the upgrade regardless of your current version.

Initial steps prior to upgrade from ANY version

  1. Install the appropriate Microsoft Visual C++ Redistributable Packages (see Windows Requirements above).

  2. Validate the credit card system is fully operational:

    1. From PAS:

      1. Perform a validation of all Program IDs defined in PAS by clicking on the blue button (double arrows) located in the upper portion of PAS configuration console.

      2. If the result is a red circle after performing the validation, you can move the cursor above the red circle to reveal the error messages associated with the failure.

    2. From SAP:

      1. Ensure all RFCs defined in SM59 - TCP connections result in a successful test against PAS.

      2. Please engage with Support Services if necessary to address any errors generated from the above validation prior to initiating the upgrade.

  3. Clear contents of the boost_interprocess directory.

    1. Stop the PAS service (from the PAS Configuration GUI, lower left side of window).

      1. Ensure that all processes associated with PAS disappear in Task Manager once PAS service stops.

      2. If the PAS service is in a Stopped state and the executables highlighted in the screenshot above of the Task Manager, stop the processes manually (right click the orphaned executable(s) and select End Task).

    2. Navigate to \C:\WINDOWS\Temp\boost_interprocess\ and delete all files contained in this directory. If you do not see the directory in the above location, perform a search for "boost_interprocess" on all volumes of the server or workstation on which PAS is installed.

  4. Make backup copies of the following files:

    1. All *config.xml configuration files located in %ProgramFiles(x86)%\Paymetric\Paymetric Adapters for SAP\.

    2. All certificate files (*.pem). These may reside in the install directory or are commonly saved in c:\certs. Verify these are backed-up to a secure location.

Determine your current version

Perform the following initial steps to ensure a smooth upgrade

  • For PAS 2.3.0 and above: You will see an "About..." link in the PAS GUI. You can click it to see the exact version.

  • For PAS versions prior to 2.3.0:

    • Navigate to %ProgramFiles(x86)%\Paymetric\Paymetric Adapters for SAP\.

    • Right-click on RfcWinService.exe and select the Version tab.

This release removes the RFC trace setting from PAS and deletes any rfc*.trc files from %ProgramFiles(x86)%\Paymetric\Paymetric Adapters for SAP\ and from RFC_TRACE_DIR if that environment variable is set.

If you wish to retain these files, please perform a backup prior to beginning the upgrade procedure; however, note that they do contain unmasked credit card numbers.

Upgrading from PAS version 2.2.4 or prior

Since versions 2.2.4 and prior did not have the RfcDaemonConfig.xml file marked to not be overwritten, it requires backup prior to executing the installer. Perform the following steps to upgrade:

  1. Verify you have backed up RfcDaemonConfig.xml as outlined in the Initial Steps Prior to Upgrade section.

  2. Run the installer and go through the wizard.

  3. For Windows Users, note if during the install you receive a dialog box regarding a Microsoft Visual C++ Redistributable package, click [No] and verify the packages are installed (see Windows Requirements above).

  4. Reboot the server manually if not prompted by the wizard.

  5. Copy the RfcDaemonConfig.xml backup file to the PAS install directory and overwrite the default file.

  6. Restart the Paymetric Endpoint Manager service. (see PAS Install and Configuration Guide for instructions if needed).

Upgrading from PAS version 2.2.5 or above

  1. Run the installer and go through the wizard.

  2. For Windows Users, note if during the install you receive a dialog box regarding a Microsoft Visual C++ Redistributable package, click [No] and verify the packages are installed (see Windows Requirements above).

  3. Restart the Paymetric RFC Endpoint Manager service. (see PAS Install and Configuration Guide for instructions if needed).

Upgrade for Red Had Enterprise Linux (RHEL)

This release removes the RFC trace setting from PAS and deletes any rfc*.trc files from /var/log/pas.

If you wish to retain these files, please perform a backup prior to beginning the upgrade procedure; however, note that they do contain unmasked credit card numbers.

Upgrading from version 2.4.0 or 2.4.1

Upgrades from these versions require an uninstall then install of the new package to ensure that future upgrades work properly. Perform the following steps to upgrade:

  1. Copy the XML configuration files from /etc/pas to a backup location to preserve your configuration settings as /etc/pas is removed during uninstall.

  2. Copy any files from /home/paymetric (the home directory of the paymetric user) to a backup location. The paymetric user and /home/paymetric are removed during uninstall.

  3. Run the following command as root on the 2.4.0 or 2.4.1 package; run it on the highest version installed: (the following example is 2.4.1) rpm -e pas-2.4.1-x.i386.rpm

  4. Run the following command as root to install the 2.7.1 package: rpm –ivh pas-2.7.1-x.i386.rpm

  5. Refer to the PAS Install and Configuration Guide for configuration information if needed.

  6. Copy the XML backup configuration files to new /etc/pas and /home/paymetric directories.

  7. Start the Paymetric Endpoint Manager service. (see PAS Install and Configuration Guide for instructions if needed).

Upgrading from version 2.4.2

  1. Run the following command as root: rpm -Uv pas-2.7.1-x.i386.rpm

  2. Refer to the PAS Install and Configuration Guide for configuration information if needed.

  3. Start the Paymetric Endpoint Manager service. (see PAS Install and Configuration Guide for instructions if needed).

Supporting Integration Documents and Installers

This release is supported by the following product documentation:

  • XiPay Platform SAP Integration Guide

  • XiSecure Platform SAP Integration Guide