The Checkout control is a "wizard" control, which means that once it is configured, it contains a three-step checkout process in one control, as shown below. This control can be configured to allow web users who are not logged into your site and who do not wish to create an account for your site, to complete the checkout process by proceeding as a guest. If the web user selects to proceed as guest to complete the checkout process, he/she is taken through the same three-step process, but each screen displays differently to the web user. See Workflows for more information about the two different workflows for a web user who is logged in (authenticated) and web user who is not logged in (unauthenticated) when completing the checkout process.
The checkout process is a multistep process. As a best practice, if you feel that your membership join and/or meeting registration workflow is critical and should be multiple steps, do not create these as "products" listed in the online store. This ensures that your users will have to go through the membership join and/or meeting register process. See Working with the Membership Join .NET Controls and Configuring the Meetings Controls for more information on how to set up these controls.
The checkout process contains the following three built-in steps:
1. Step 1: Address Information
3. Step 3: Payment Information
Before configuring the Checkout control, it is important that your back office configurations are accurate. If not, these configurations will not display properly on your e-Business website. See Configuring the Back Office Settings for the Checkout Control for more information on the system types and codes that need to be web enabled before setting up this control.
As of 7.6.0, web users have the ability to register other people, as well as themselves, for a meeting; this functionality is referred to as Register Someone Else. The web user that placed the order will be saved as the bill-to and order master ship-to customer and will be saved as the ADDOPER on each registration he/she placed. The line ship-to would default to the individual registered for the meeting. The only exception to this functionality is if the if the logged in web user has Bill Primary Employer privileges. In this instance, if the "Allow Bill-Me" checkbox is checked on the eBusiness Control screen in Product Maintenance for the meeting product and the web user has Bill Primary Employer privileges, the web user's primary employer will be set to the bill-to customer and payment will not be required at checkout. For more information, please see the Bill My Primary Employer. The system does not check each registrant’s record for the Bill Primary Employer flag. Use caution when assigning Bill Primary Employer privileges to constituents, because the system will not prevent the web user from paying for employees from different employers.
See Also:
· For an overview on how the Checkout control works, refer to Workflows for the Checkout Control
· To add the Checkout control to a page on the web, refer to Web Settings for the Checkout Control.
· For a video demonstrating how to add the Checkout control to a page, refer to Video Demo: Configuring the Checkout Control.
· To see additional page setups for the Checkout control, refer to Page Setups.