Credit Card Gateway Configuration

© 2015 GoPrint Systems, Inc., All rights reserved. | Authorize.Net Credit Card Gateway 1

Authorize.Net Credit Card Gateway Configuration

Pre-Configuration Requirements

Prior to configuring the gateway in GoPrint, the following networking tasks must be performed

and gateway information obtained from your Authorize.Net campus administrator.

1. An established Authorize.Net account and banking transaction system established.

2. GoPrint GTX server MUST resolve to an external IP Address FQDN name.

3. Authorize.Net communicates over Port 80 and must be enabled for inbound connections

through campus firewalls.

4. Allow inbound traffic from Authorize.net’s postback IP addresses

(198.241.162.104/255.255.255.0 or 64.94.118.33/255.255.255.0).

5. Obtain the Authorize.Net API Login ID and Transaction Key.

6. Obtain the MD5-Hash.

7. Set your Payment Form fields.

8. Test to ensure the required server naming and port resolution items are resolvable.

TouchNet Configuration

API Login ID Transaction Key


MD5-Hash

This setting is needed to receive post back responses from Authorize.Net's payment gateway.

The MD5-Hash Value can be any random value

Important: Write down the Hash Value before

you save it because it will not be displayed at the

confirmation page.


Set the desired payment form fields

The default Authorize.net settings enables a wide variety of fields which get displayed to

the user at the web client. It’s best to disable most of these fields by editing the Payment

Form –Fields options.


Networking Configuration

Confirm GTX Server DNS Resolution

The Authorize.Net server communicates with the GoPrint server via HTTP on port 80. You will

need to ensure that the Authorize.Net servers are able to contact the GoPrint server over the

internet. This will usually involve the following network changes:

1. Set up a public DNS entry to ensure the GoPrint server is publicly accessible via a friendly

name (e.g. gorprintgtxserver.campus.edu).

2. Ensure no other application is using port 80 on the GoPrint server (e.g. IIS or another web

server). To verify this, open the command-prompt (cmd.exe) and type: netstat –na | more

Ensure that port 80 is not in a listening state. That is, the following line should not be displayed:

TCP 0.0.0.0:80 0.0.0.0:0 LISTENING

3. Ensure your firewall allows traffic to port 80 on this server. Methods include adding “TCP

Open” entry to your firewall and/or using port forwarding.

4. Test and ensure that the following URL is accessible via the public internet:

https://goprintgtxserver.edu/7773 where publicservername is the DNS name set up in step 1.

Accessing this URL with a web browser should result in the browser displaying a simple

confirmation page.


From a computer outside your internal network:

1. Attempt to ping the DNS name

2. Perform a nslookup

If the FQDN name is not resolvable, save the results to a text file and send to your

network administrator.


Confirm port 80 is open inbound

1. From an external network open a command prompt

2. Enter: telnet “server external IP Address” 80

Results show port is closed:

1. Check to ensure there are no conflicting applications completing for port 80.

2. Open a command prompt and run a Netstat

netstat –an | find /I “Established”

Displays established connections. You may switch “Established” to

“Listening” to display listening connections.


Issuing netstat –an returns all listening and established connections

Ensure localhost connection is NOT listening over port 80. The follow example

displays an example where an application is listening over port 80. This is not what

you want to see.

Note: commonly many clients install the Windows WWW service which listens over port

80 by default. Check Windows Services to ensure it’s not installed and if so, uninstall the

Windows Feature.


3. If necessary, create an inbound rule on the

server’s Windows Firewall.

Confirm that Authorize.net inbound IP address range is allowed to pass

When setting the GoPrint server to a resolvable FQDN and ensuring port 80 remains open, it’s

also required to allow inbound traffic from Authorize.net’s IP address range.

198.241.162.104

Important: it’s a good idea to check with Authorize.net to ensure this range is still effective.

Authorize.net has been known to change it without notification


GoPrint Authorize.Net Configuration

Step 1 – Configure Authorize.Net

From Control Center select: Payments - Credit Card Gateway

Click on Authorize.Net:

General


Name: Enter a user friendly name to help identify the gateway

Gateway Flat Fee: The value entered here is added to the transaction total and is calculated

along with the Gateway Percentage Fee and is used to offset charges incurred from using

Authorize.Net's Gateway service.

Gateway Percentage Fee: The value entered here is added to the transaction total and is

calculated along with the Gateway Flat Fee and is used to offset charges incurred from using

Authorize.Net's Gateway service.

User Flat Fee: The value entered here is added to each successful transaction and is typically

used by the GoPrint host to compensate offering the credit card services.

Minimum Deposit: The value here sets the minimum amount allowed for a transaction. (Before

the fees listed above are taken into account)

Maximum Deposit: The value here sets the maximum amount allowed for a transaction.

(Before the fees listed above are taken into account)

User Agreement URL: This is an optional link. The user agreement is a custom page created by

the institution and visible on the Internet. Select NONE if an agreement doesn’t exist. This

cannot be blank.

Gateway


Environment: Select LIVE for a production environment or Live Test during a testing phase.

Note: Authorize.Net provides the option to set the gateway in Testing mode to disable

transaction processing.

Item name: The item name is sent to Authorize.Net and appears on student receipts and

administrator transaction receipts

API Login ID: The Authorize.Net Login ID

Transaction Key: Authorize.net's secure key that is used to validate the user with Authorize.Net

to send transaction data.

MD5- Hash Value: MD5-Hash Value that is entered on Authorize.Net's website. It is used to

validate the user for the post back response.

External Hostname: Internet l resolvable DNS name of GoPrint GTX server.

Click the Save button to save any changes

For additional instructions refer to the GoPrint Help section titled Integrated Payments.


Step 2 – Enable Port 80 to 7768 Forwarder

Because Authorize.Net communicates over Port 80, the default GoPrint Port of 7768 needs to

listen for requests over this port.

1. Select the Enabled

2. Restart the GS4 Services (Required)


Step 3 - Configure Quota Payment Method

The credit Card gateways must be associated with a User Class. To do so select:

Accounts – Class Definitions

Select a existing User Class or create a new one

Important: Credit Card Gateways function ONLY with a Quota purse.

Check Quota

Purse Name: Establish a user-friendly name

This name will be visible to the end-user when selecting their purse at the web client. It’s also

used to identify the purse type for administrators when generating reports.

Click Save


Step 4 – Associating the Quota Purse at a PayPoint

Under the PayPoint Financial section select your Quota Purse

From the Add Value Option: select Credit Card Allowed

Note: If not selected, the Credit Card Add Value optional will not appear at the web

client.


Add Value Instructions: Add an optional customize message to appear at Web Client

Putting it all together – Adding funds at the Web Client

To add funds, the user logs in to the Web Client and clicks the ADD VALUE button.

Note: If the Add Value button doesn’t exist check your PayPoint to ensure Credit Card

Allowed is enabled under the Add Value drop down menu.


The next screen prompts them to enter the amount of print funds they will like to purchase,

and if one has been created, check the user agreement form.

The deposit request is Confirmed


Users are taken directly to the Authorize.Net website (Embedded into the Web Client) credit

card information entered:


If successful, a confirmation is sent to the GoPrint GTX server confirming the transaction, and

the amount is deposited into the users Quota account.

Users can confirmed their credit card transactions as viewed under My Account – Transaction

History


Important: If the GoPrint server’s host name doesn’t resolve to an external IP or DNS name,

then GoPrint will not be able to receive the confirmation, and not add the funds to the users

Quota account; although, the funds are received by Authorize.Net.

Vendor Notification

Authorize.Net emails listed administrators a receipt for each credit card transaction.

Note: It’s important to note the “Transaction ID” because this can be used to reference the receipt

emailed to the user as well as GoPrint reports.

Merchant Email Receipt ========= GENERAL INFORMATION ========= Merchant : CCSF (320649)

Date/Time : 30-Jun-2011 10:07:36 PM

========= ORDER INFORMATION =========

Invoice : 3

Description : CCSF CityPrints

Amount : 3.00 (USD)

Payment Method : Visa

Type : Authorization and Capture

============== RESULTS ==============

Response : This transaction has been approved.

Authorization Code : RJU18R

Transaction ID : 2161053898

Address Verification : Street Address: Match -- First 5 Digits of Zip: Match

==== CUSTOMER BILLING INFORMATION ===

Customer ID : 5

First Name : jode

Last Name : doe

Company :

Address : 111

City : Some City

State/Province : CA

Zip/Postal Code : 94583

Country : us

Phone : 555-121-1212

E-Mail : [email protected]

mailto:[email protected]


Student Notification

If email notification is enabled in Authorize.net, students receive an emailed receipt to the

email supplied under the email portion of the credit card submission.

Note: Items, like colors, fonts, and wording, (highlighted in yellow) can be enhanced within

Authorize.Net to fit campus branding.

Jode Doe Customer Receipt/Purchase Confirmation


Vendor Credit Card Settlement Report

A daily credit card Settlement Report is emailed to each administrator on record. To view

details for a specific transaction, you will need to log into the Merchant Interface.

Successful Credit Card Settlement Report

Your Authorize.Net ID is: 320649

The following is your Credit Card settlement report for Sunday, July 03,

2011.

Transaction Volume Statistics for Settlement Batch dated 03-Jul-2011

17:21:39:

Batch ID: 1128760

Business Day: 03-Jul-2011

Net Batch Total: 45.20

Number of Charge Transactions: 3

Amount of Charge Transactions: 45.20

Number of Refund Transactions: 0

Amount of Refund Transactions: 0.00

To view details for a specific transaction, please log into the Merchant Interface.

1. Click "Reports" from the main menu

2. Select "Transaction Details by Settlement Date"

3. Select "Settled Transactions" from the Item Type drop-down box.

4. Select the Settlement Date for the batch you would like to view from the "Date" drop-down box

5. Click "Run Report"

6. In the results, click on any transaction ID to view specific details for that transaction.


Manage Accounts and Transactions

GoPrint Administrators can view successful transactions which can be used to compare to

Authorize.Net reports and to confirm the funds have been applied to the users account. Also,

users may always log into the Web Client to view their complete lists of transactions under

Accounts – Transaction History section.

From Control Center select:

Payments – Credit Card Transactions

The Credit Card Transaction Query page appears:

Queries can be conducted by; date range, individual Gateway Ref# (this is the Transaction

ID), GoPrint Transaction#, or individual user account.


Example: Date Range Query

Returns one user:

You can select the “Details” button to view more specific information:

The Credit Card Transaction Details page appears:


Reconcile incomplete transactions

At times transaction may go through to Authorize.net but due to network issues a confirmation

may not be returned. In this case the transaction is displayed with a red column and a status

of Started.

To reconcile the transaction and apply the funds to the users Quota account:

1. Click Details

2. Press Confirm

3. Click Ok to confirm


Transaction status set to Confirmed

4. Navigate to Accounts – Manager Users to confirm the funds have been added to the

account.

Troubleshooting

What It Means

Issue #1 – Network lag or issue with Authortize.net’ site.

Most commonly caused when Authorize.Net’s IP Address range is blocked

http://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Relay-

Response-Basics-and-Troubleshooting/ba-p/9536

http://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Relay-Response-Basics-and-Troubleshooting/ba-p/9536

http://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Relay-Response-Basics-and-Troubleshooting/ba-p/9536


Issue #2 – Port 80 is blocked

Isssue#3 – the MD5 Hash Value doesn’t match

Issue#4 – Port 80 to 7768 Forwarder isn’t enabled and/or the

GS4 –Services weren’t restarted after


Issue: API Login ID is incorrect

Issue: Transaction Key is incorrect - doesn’t

match what’s set in Authorize.net

Documents

Credit Card Gateway Configuration