Home

Getting Started
- Process
- Ecommerce Guidelines
- Registration Form
- Glossary of Terms

Financial Processing
- Fulfillment Processing
- Revenue Reconciliation
- Tax Reporting

Software
- Recommended Software

Documentation
- Order Entry, Order Management, and Transaction Reporting (OMARS) in ClearCommerce
- ShopSite

Help

Merchants may combine their own web forms with cgiemail to provide additional flexibility for:

• offering multiple payment methods and customizing payment screens to the payment method selected.
• collecting additional information from buyers that is not passed to the credit card transaction processing servers. This information is sent to the merchant in an email message. For example, a merchant may be hosting an event and wishes to collect information such as graduation year, badge name, guest name(s), dietary preference. Typically, this type of information is not passed to the credit card transaction processing servers. Instead, the merchant can use a custom web form with cgiemail to collect the complete registration information and send it to the merchant in an email message.

How it works:

• The merchant must create the custom web form and templates for each payment option offered as well as for the cgiemail message.
• When the customer submits this form, it invokes cgiemail which sends an email message containing all of the form data to your merchant staff.
• Cgiemail also "hands off" the form to another html form or page that is associated with the payment option that the customer selected. For example, if the customer selects the credit card payment option, the associated page is another html form, that has been partially filled in using the data on the initial form. The customer enters the credit card information and submits this form. This action sends the payment data to the back-end credit card transaction processing servers.

Limitations of using cgiemail with custom web forms:

• At this time, calculations on the custom web form are not supported. Therefore, this option is best used when there are very few ordering options offered.
• The cgiemail message is generated when the custom web form is submitted. Merchants should be aware that their receipt of the email message does not necessarily mean that the payment has been processed. For example, it is possible that a credit card customer may abandon the payment form or that the payment may be declined by the bank. The custom web form supports "server side includes," which generates a unique identifier that can be used to reconcile the email message with the payment.

To see an example of a custom web form using cgiemail, go to our Demonstration Custom Web forms with cgiemail.

Technical information on building custom web forms is available at Building E-Commerce Custom Web Forms.