• Create a “checkbox” type custom field with value of “I Agree”
• Within the “Description” for the field, create a link to your terms and conditions.

I have read and agree to the <a href="http://www.yoursite.com/terms.php" target="_blank">terms and conditions</a>.

• When creating the registration form, add the field to a field set and make it required.

• Open “admin/includes/general.php”
• Edit the following line from:

$force_ssl = "0";

• To:

$force_ssl = "1";

Please see Forced User Account Updates

• You must have your own website (you cannot be using the ppSD2 hosted package which only works with non-API gateways such as PayPal standard)
• You must have an SSL certificate installed.
• You must sign up for a merchant account from a payment gateway such as Authorize.Net, First Data, PayPal Websites Payments Pro, etc..

• Ensure that the user has not already seen this announcement.
• Ensure that the end date for the announcement is in the future.
• Ensure that the start date for the announcement is in the past.
• Ensure that the secure area criteria for this announcement is matched by the user logging in.

• Accounts are not being created after a purchase
• The order is not showing up in the billing logs
  • Ensure that the user is clicking on “Return to Merchant” after making the purchase through PayPal.
• The wrong currency is being used
  • Update this from “SETUP” > “Payment Gateways”

• If no users can log in:
  • Using an FTP client such as filezilla, set the permissions (CHMOD) on the “ppSD2/sessions” folder to 777.
• If only specific users can’t log in:
  • Ensure that the user has cookies turned on.
  • Ensure that the user’s firewall or virus protection isn’t blocking cookies.
  • Ensure that the user is inputting his/her username/password in a cAsE SeNsItIvE manner.
• Announcements are not being displayed
  • Ensure that the user has not already seen this announcement.
  • Ensure that the end date for the announcement is in the future.
  • Ensure that the start date for the announcement is in the past.
  • Ensure that the secure area criteria for this announcement is matched by the user logging in.
• If you receive a “MySQL Error”
  • Ensure that the database information for all modules is correct (”SETUP” > “Modules”)

• If all transactions are declining:
  • If you are using an API:
    • Confirm that your payment gateway details are correct from “SETUP” > “Payment Gateways”
    • Confirm with your payment gateway company that your account isn’t currently in test mode.
  • If you not using an API:
    • Ensure that the checkout link for your payment gateway is correct from “SETUP” > “Payment Gateways”
• If some transactions are going through but others are not:
  • Ensure that the user is inputting his/her credit card information correctly
  • Ensure that the user is using an non-expired credit card.
  • If the user is using a non-Visa or non-Mastercard, confirm with your payment gateway that you are set up to handle transactions from that user’s credit card company.
  • If this is a subscription renewal, ensure that the user’s credit card in on file and that the information is correct.