Exception Codes : Setting Up a Payment Gateway Test Environment

Created by ptoughey, last modified by ssnyder on Aug 08, 2013

If you are an ASP licensed TouchNet DataCenter customer:

If you would like a test environment, please contact Customer Care and we can provide a quote for this additional environment.

If you are not an ASP licensed TouchNet DataCenter customer

As a Payment Gateway customer, you are licensed for one production Payment Gateway environment and one Payment Simulator environment. The Payment Simulator license may be used in a test environment if you desire to create and maintain a test environment.

The Payment Simulator simulates the payment process and does not communicate to a credit card processor. This means that there is no actual processing against credit cards when using Payment Simulator.

The standard Payment Gateway maintenance contract only allows for support of your production environment. Therefore the setup and maintenance of your test environment is your responsibility. The information provided below will help you set up a Payment Simulator environment on your own. If you need our Professional Services to install a Payment Simulator environment for you, please contact Customer Care and we can provide a quote for this service.

Icon

Note: If you want to actually test connectivity and processing with your production credit card processor, Payment Simulator will not accomplish this. Instead, you would need to use real credit cards in production and issue credits after testing is done. Alternatively, some credit card processors and/or banks may issue you a test credit card number. Contact your credit card processor and/or bank to ask if they will provide a test credit card that is safe to use in your production environment.

  1. To set up a Payment Simulator environment, use a separate server from your production Payment Gateway server. Starting with Payment Gateway version 4.6, you cannot have two environments on the same server. If you want to use the same database as production, then the delivered database scripts will not work for you and you will need to create test instances of Payment Gateway in the database.
  2. You will need to install Payment Gateway 4.6 on your Payment Simulator server. To install version 4.6, you will need your Payment Gateway 4.6 CD, Setup Guide, and Administrator's Guide. (Go to support documentation.) The Setup Guide will take you through the necessary steps to get 4.6 up and running. When you come to the step to request your license key from TouchNet, let us know that this is for your Payment Simulator environment.
  3. Once you have 4.6 up and running in your Payment Simulator test environment, you will need to stop or kill all of the Payment Gateway 4.6 processes/services in that environment.

  4. Open the drive:\touchnet\payment46\bin\transmgr.xml file in a text editor. Change this line:

    <ALIAS NAME="$TPG-XML$">[drive]:\touchnet\payment46\bin\[merchant\]\[merchant\].xml</ALIAS>

    To this:

    <ALIAS NAME="$TPG-XML$">[drive]:\touchnet\payment46\bin\paysim\paysimt4.xml</ALIAS>

    Save the changes.

  5. Start the Payment Gateway processes/services. When you start the payment gateway processes/services it utilizes Payment Simulator.
  6. Apply Payment Gateway software updates.
Icon

Important! Please remember that Payment Simulator is a process that simulates payments, but does not actually send any data to a credit card processor. Never use Payment Simulator in a production environment. Payments, authorizations, and settlements are not real if you're using Payment Simulator. In Payment Simulator mode, real credit card numbers will be authorized successfully and processed in batches as settled, but the card is never actually authorized or charged. We recommend that you limit access to your Payment Simulator environment to avoid the scenario where any user could accidentally log in and think they are processing real transactions.