The I/NET Store - A Sample Application


The I/NET Store is provided with Merchant/400 to provide the following:

The store is an application that allows the user to select one or more products to order from a list of items that you have for sale. It then calculates the total cost for the customer, allowing the customer to accept the order or to change the items that are to be purchased. When the customer is satisfied with the list of items to be ordered, they enter credit card, personal and address information and then submit the completed order. At this time the credit card is validated using the Merchant/400 API. If the credit card is accepted, the order is stored and the user is given a screen that thanks them for their order. If the validation fails, the user is prompted to correct the information so the validation can be attempted again.

The list of items that the customer selects for purchase is stored using a cookie. A cookie is a piece of information that is stored by the browser. This allows the customer to leave the store and return later with the items that were selected earlier still in their "shopping basket". The list of items remains until a customer completes an order, or closes the browser. For more information on cookies see Cookies.

The application only charges amounts to credit cards via "sale" transactions. That is, it charges the credit card immediately upon verification. For more information on transaction types see Transaction Type.

The application can be configured to fit your requirements. For information on configuring the store see Configuration.

Store Screens

The store consists of four screens that the user interacts with. These screens can be customized to look the way you want them to. All of the text displayed is stored in text files and message files to allow it to be changed to fit your needs.

Order Form

The first screen that the user sees is the Order Form. This screen presents the customer with a list of products that can be ordered. This list displays the product identifier, description, price, unit of measure, and an optional picture for each product. The user types the number of each item to be ordered. When the user has selected everything to be ordered, he/she clicks the "Cash Register" button to complete the order.

This list of items that are displayed is stored in the Product Description physical file (MPRODCTP).

Cash Register

After the customer has selected all of the items to be purchased, he/she is shown this screen. Listed on the screen is the list of all the items that were selected to be ordered and a total, including shipping and handling. If the customer wants to finish the order, he/she clicks the "Yes" button, otherwise the "No" button is clicked, which causes the Order Form to be redisplayed, allowing the customer to change their selections.

The amounts to be charged for shipping and handling is stored in the global configuration physical file (MGLOBALP).

Check Out

When the customer has confirmed that the items to be ordered are correct, the Check Out screen is displayed. This screen prompts for several types of information:

Note: The customer name and billing address must match the information from the credit card.

After the customer fills in the information, he/she presses "Complete Order". At this time, the store attempts to validate the credit card using the Merchant/400 API. If the card is accepted, the order information is stored in the customer order files (MORDERP and MORDITMP). If the card is not accepted, the Check Out screen is redisplayed with an error from the credit card processor to allow the customer to correct the problem and try again.

Thank You

When the order is complete. A screen is displayed that shows the order number and the approval code from the credit card processor.