UW-Madison Ecommerce (CASHNet)

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.

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.

Common Ecommerce Storefront Checkout Setups

Simple Registration Page | Dynamic Registration Page | Without Shopping Cart | With Shopping Cart

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.
Demonstration Storefront

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 informaiton 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.