Setup or Maintain A Cashnet Storefront

CASHNet allows departments on campus to develop storefronts on the internet and receive credit card payments 24 hours a day, 7 days a week using a stable, fast and secure server.

A merchant ID is required before setting up a CashNet storefront. The entire set up process can take anywhere from three to four weeks.

How Cashnet works

  • The customer browses a merchant storefront and submits an order. The order information is passed along to CashNet’s secure Web server where the customer enters their credit card information. CashNet processes the transaction and displays a confirmation or denial message.
  • The merchant gathers daily transaction information from the CashNet Administration web site. This information is used to perform daily reconciliation.

Acceptable Credit Cards

Visa, MasterCard, Discover, and American Express. Use the following forms to set up.

This is an accordion element with a series of buttons that open and close related content panels.

Face-to-Face operation set up

Internet operations set up


VISA, Mastercard, and Discover: approximately 2.0%.
American Express (AMEX):  approximately 2.25 %

Elavon charges $.05 per refund transaction and a $5.00 monthly maintenance fee for the Merchant ID.

Chargebacks are $7.50.
Discover charges an additional $.05 per transaction.


There are two services available; Basic Service and Premium Service. There is no charge for either.

For more information about the two services use the Merchant Connect Comparative Matrix (pdf).

How to set up a storefront

This is an accordion element with a series of buttons that open and close related content panels.

Simple Registration Page

A simple registration page can contain information such as name, institution, email, multiple registration types, food preferences or lodging requirements. All the data requested fits on one page and none of the information on the page changes dynamically. It’s a simple HTML page that customer fills it out and submits it all at once.

The most common way to handle this situation is for that inital page to submit to another local page that saves all the registration informationm in a local database. The customers browser is then forwarded automatically to the CashNet server where the credit card transaction takes place. If the transaction is successful, CashNet will send an alert to the email address provided by the customer. Optionally CashNet can send a GET command to a hidden page on the local server with the result of the transacion. The result of this GET is not seen on the customers browser and therefore cannot be interrupted. This hidden page call can be used to mark the order as successful in the local database. It can also be used to send an email receipt to the customer.

Dynamic Registration Page

A dynamic registration page has some element that can change each time the page is loaded. An example is a registration page where the customer has to select among different sessions. As sessions fill up they are automatically taken off the page. This type of page requires a database on the back end which is queries each time the page is brought up. Once the page is brought up the rest of the process works like the Simple registration page.

Storefront, no shopping cart

A simple storefront will be one page long and contain all the items that are for sale. The user indicates which items they wish to purchase, fills out their customer information and submits the form. The rest of the process works like the simple registration.

Storefront, with shopping cart

A shopping cart storefront is usually a very complex site. But in general the point of commonality is the shopping cart page. No matter how large the site is everything ends up on the shopping cart page. This page is interfaced to the CashNet pages in the same way as the a shopping cart site. All information about shipping, tax, rebates, etc is collected on the shopping cart page and stored in a local database. The amount is then sent to CashNet and the customer continues as in the other setups.

This is an accordion element with a series of buttons that open and close related content panels.

Storefront requirements

All Ecommerce pages and receipts must contain the following four pieces of information.

  1. Refund Policy
    • Example: If a participant cancels less than seven working days prior to the date of the event, no refund can be issued. A substitute may be sent in the place of the original registrant, but the individual participant or department is responsible for coordinating and communicating this to the <Wherever>.
  2. Privacy Statement
    • Example: The <Merchant Name> does not sell, rent, trade or distribute any personally identifiable information obtained from clients to a third party, except in cooperation with government agencies or as required by law. Information collected by <Merchant Name> is used for the administrative and operational purposes of our services.
  3. Doing Business As
    • Example: Your credit card statement will reflect this merchants Doing Business as name as <Merchant Name>
  4. Customer Service
    • Example: Please contact <Merchant Contact person’s name, phone number, email address, and the address of merchant’s permanent establishment> if you have any questions.


Use the CashNet Training (pdf) on how to use the various features of CashNet, including:

  • Login
  • Finding transactions and reports
  • Transaction details
  • Voided transactions
  • Refunds

Telephone and in-person training is also available. Contact