Difference between revisions of "Enom TRUSTe"
(Created page with 'TRUSTe helps businesses promote online safety and trust, and guides consumers to sites that protect their online privacy. TRUSTe helps both consumers click with confidence and on…') |
(No difference)
|
Revision as of 15:09, 4 August 2011
TRUSTe helps businesses promote online safety and trust, and guides consumers to sites that protect their online privacy. TRUSTe helps both consumers click with confidence and online companies promote their Web site privacy policies online. Thousands of Web sites rely on TRUSTe's privacy, including top-fifty sites like Yahoo, Facebook, MSN, eBay, AOL, Disney, Comcast and Apple.
And this new module for WHMCS allows you to offer TRUSTe Privacy Policy products with fully automated provisioning and setup using your WHMCS system.
The Ordering Process
The Privacy Policy Products you can offer have 2 options, the TRUSTe Seal and Registration Length (which can be from 1 to 3 years). A sample of how you can setup these offerings in WHMCS is shown below:
When ordering, the customer has to supply the domain name that they intend to buy privacy policy for, but actual configuration of the policy is done later after checkout. Below is a demo of the checkout process.
Once the user has completed checkout, and paid for the service, then based on your automation settings the product will either be instantly and automatically provisioned by WHMCS, or wait for an admin to manually review & approve the order. Once that's done, the client will then receive a welcome email instructing them to login to the client area where they'll find a link to automatically login to the TRUSTe website to configure their new privacy policy. This appears as shown below:
Installing the Module
The Enom TRUSTe module was first released in August 2011 and so is not included by default in any WHMCS releases prior to V4.6. Therefore if you are running on Version 4.5 of WHMCS or earlier, you will need to download and install the module before you can use it. The download link is below and to install it's simply a case of uploding the module folder to the /modules/servers/ directory of your installation.
http://www.whmcs.com/members/dl.php?type=d&id=89
Setting Up Your Products
To setup a TRUSTe product in WHMCS, simply follow the steps below:
- Begin by navigating to Setup > Products/Services and create a new group for your TRUSTe offerings
- Next proceed to create a new product, giving your product a name and setting the type to Other
- You can then configure a description, welcome email, pricing, etc... as normal for any product
- For Pricing, you can setup the products either as One Time items, so that they don't auto roll over in future years, or enter the prices in the recurring fields - Annually, Biennially & Triennially. You can just offer the Annual 1 Year option, or you can offer a choice of registration periods, that's really up to you.
- Then it's onto the Module Settings tab
- Begin by choosing Enomtruste from the module dropdown menu
- You'll then see a screen like the one below which asks you for your eNom Username & Password, let's you specify whether this product should include the TRUSTe Seal, and let's you specify the Number of Years the product should grant access to
- If you're using the Biennial & Triennial billing cycles on the Pricing tab then these will automatically override the Number of Years to 2 and 3 respectively when ordered
- Configurable options can also be setup to let the user choose if they want the Seal, and the Number of Years from within a single product should you wish, and for those you just need to use they keyword names of Seal and/or NumYears to have them override the appropriate Module Setting values
- Finally you must also create a custom field, set as "Required" with the name Domain Name for the customer to enter the domain they are wanting to order the privacy policy for into when ordering
Note: Enom's API is IP Restricted so if you aren't yet using Enom for anything else in WHMCS, you will need to register your Server IP with them via ticket for them to allow it access to your account before the API connection will work.