CheckSite Demo Store

CheckSite Shopping Cart Website Application Demonstration 2010

Branding your shopping cart to fit.

This page is meant to show you the basic functions of our shopping cart solution, as well as some examples of shopping cart search and navigation layout or use. We work with you to make your cart fit your marketing and design requirements. If you need a design, please check the design link below.

Sample Search/Navigation Custom Tags

The following are a few samples of the CheckSite Shopping Cart Search/Navigation server behavior in action.

CheckSite Shopping Cart [SSL SECURE] Admin (live demonstration)

The Admin is used to manage your online store. Your CheckSite Shopping Cart Admin is located at https://secureniagara.com/cart1/cw3/admin/

CheckSite Shopping Cart Design Template

The CheckSite team has decided on this design. http://www.checksite.ca/cart

More designs for shopping / ecommerce sites: http://design.checksite.ca
Even more designs... click here

CheckSite Shopping Cart Pricing & Video Tour

Annual Cart hosting
Secure Processing: SSL via secureniagara.com
Design template purchase and implementation.
=================
Check Price | Video Tour

[we take no commissions or limit the amount of items you list in your store] | Logoff

For security and liability reasons Cartweaver/CheckSite does not store credit card data.
This is always passed off to the payment gateway/processor.

This functionality is not too difficult to add, but it is up to the developer to do so. 
If you are performing this work for a client, we suggest that you educate your client 
to the dangers of storing credit card data and discourage that them from doing so.

If the client must process credit cards manually for whatever reason, we strongly 
recommend getting a signed "hold harmless" agreement before you proceed. This way 
you are less likely to be held liable in the event the credit data is compromised 
in some way. Identity theft has become a big issue on the web; storing customer 
credit data is a potential liability that should be considered carefully.

The big payment processing companies spend a lot of time and money securing credit 
card data. They do not store it in a shared server environment, and if things go 
wrong they have teams of lawyers on staff or retainer and are usually far better 
equipped to handle a lawsuit than the average business owner or web developer.

Please see also: 

http://www.cartweaver.com/faq/index.cfm?faq=35

and

http://blog.cartweaver.com/index.cfm?newsid=13

From all this you can see why we do not give any instructions on how to do 
this. This is intentional as we wish to stay out of the lawyer's "food chain" 
should a customer decide to do this and end up in a law suit.

Gateway or Processor
Your choice of payment methods and vendor are set in the Cartweaver Setup server behavior. Here you designate which method you will be using, Gateway (aprox. $50 monthly) or Payment Processor (aprox. 3%), and the vendor you will be using. The vendors currently available for Cartweaver are; Gateways – Authorize.Net (AIM) and Verisign Payflow Pro; Payment Processors – PayPal and WorldPay Select Junior.

How Real-Time Gateways Work
Gateways process credit card transactions in-line. As an order is processed, Cartweaver sends the credit card details to the gateway. While the gateway verifies the credit card transaction, Cartweaver waits for a response. After the gateway responds Cartweaver continues processing the rest of the order based on the result of the credit card transaction. If a transaction fails for whatever reason (bad card number, incorrect expiration date, etc.), then an error is displayed to the user and they are given the opportunity to enter new credit card information. If the transaction is successful, then the order is immediately written to the database.

How Non-Real-Time Payment Processors Work
Payment processors process the transaction in a completely separate space from the application. The page code, including gateway code, is processed all at once. The parameters are passed to the gateway either via FORM submittal or HTTP Post and the order is written to the database without regard to what happens at the payment processor.